ProcessingRequestV02

admi.017.001.02

The Processing Request message is sent by a participant to a central system to request the initiation of a system process supported by a central system.

Message Construction

Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification

classDiagram
     direction LR
%% ProcessingRequestV02 recursion level 0 with max 0
class ProcessingRequestV02{
    MessageIdentification IsoMax35Text
    SettlementSessionIdentifier IsoExact4AlphaNumericText
}
ProcessingRequestV02 *-- "1..1" RequestDetails30 : Request
ProcessingRequestV02 *-- "0..1" SupplementaryData1 : SupplementaryData
  

Now, we will zero-in one-by-one on each of these building blocks.

MessageIdentification building block

Unique and unambiguous identifier for the message, as assigned by the sender. Specifies a character string with a maximum length of 35 characters. For comparison, see the ISO20022 official specification This message is declared as Max35Text in the ISO specification. In our implementation, it is represented in source code as IsoMax35Text. Due to global using directives, it is treated as a System.String by the compiler and runtime.

SettlementSessionIdentifier building block

Indicates the requested CLS Settlement Session that the related trade is part of. Specifies an alphanumeric string with a length of 4 characters. For comparison, see the ISO20022 official specification This message is declared as Exact4AlphaNumericText in the ISO specification. In our implementation, it is represented in source code as IsoExact4AlphaNumericText. Due to global using directives, it is treated as a System.String by the compiler and runtime.

Request building block

Contains the details of the processing request. Details of the processing request. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% RequestDetails30 recursion level 0 with max 1
class RequestDetails30{
    Type IsoMax35Text
    AdditionalRequestInformation IsoMax35Text
}
RequestDetails30 *-- "0..1" IPartyIdentification242Choice : RequestorIdentification
%% IPartyIdentification242Choice recursion level 1 with max 1
  

RequestDetails30 members

SupplementaryData building block

Additional information that cannot be captured in the structured elements and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
    PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
  

SupplementaryData1 members

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the ProcessingRequestV02 implementation follows a specific implementaiton pattern. First of all, ProcessingRequestV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, ProcessingRequestV02Document implements IOuterDocument. Because ProcessingRequestV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type ProcessingRequestV02.

classDiagram
    class IOuterRecord
    ProcessingRequestV02 --|> IOuterRecord : Implements
    ProcessingRequestV02Document --|> IOuterDocument~ProcessingRequestV02~ : Implements
    class IOuterDocument~ProcessingRequestV02~ {
        ProcessingRequestV02 Message
     }
  

Document wrapper for serialization

The only real purpose ProcessingRequestV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:admi.017.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using ProcessingRequestV02.ToDocument() method. The returned ProcessingRequestV02Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    ProcessingRequestV02Document *-- ProcessingRequestV02 : Document
  

Sample of message format

This is an abbreviated version of what the message should look like.

<Document xmlns="urn:iso:std:iso:20022:tech:xsd:admi.017.001.02">
    <PrcgReq>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <SttlmSsnIdr>
            <!-- SettlementSessionIdentifier inner content -->
        </SttlmSsnIdr>
        <Req>
            <!-- Request inner content -->
        </Req>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </PrcgReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_1MsY4QR4Ee29PP19jELcvQ"
  previousVersion="_4X6DQJXbEeaYkf5FCqYMeA"
  name="ProcessingRequestV02"
  definition="The Processing Request message is sent by a participant to a central system to request the initiation of a system process supported by a central system."
  registrationStatus="Registered"
  messageSet="_wiatARJsEeSstbhSoCHcWw"
  xmlTag="PrcgReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_1Ms_8QR4Ee29PP19jELcvQ"
    previousVersion="_Tos68ZXcEeaYkf5FCqYMeA"
    name="MessageIdentification"
    definition="Unique and unambiguous identifier for the message, as assigned by the sender."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgId"
    simpleType="_YW1tKdp-Ed-ak6NoX_4Aeg_1913463446" />
  <messageBuildingBlock
    xmi:id="_1Ms_8wR4Ee29PP19jELcvQ"
    previousVersion="_V3DB0ZXcEeaYkf5FCqYMeA"
    name="SettlementSessionIdentifier"
    definition="Indicates the requested CLS Settlement Session that the related trade is part of."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SttlmSsnIdr"
    simpleType="_YYLJ6Np-Ed-ak6NoX_4Aeg_-1265890753" />
  <messageBuildingBlock
    xmi:id="_1Ms_9QR4Ee29PP19jELcvQ"
    previousVersion="_K1IXEJXdEeaYkf5FCqYMeA"
    name="Request"
    definition="Contains the details of the processing request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Req"
    complexType="_6f_egQR4Ee29PP19jELcvQ" />
  <messageBuildingBlock
    xmi:id="_36KEsQR4Ee29PP19jELcvQ"
    name="SupplementaryData"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="admi"
    messageFunctionality="017"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.