admi.017.001.01
The Processing Request message is sent by a participant to a central system to request the initiation of a system process suported 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 %% ProcessingRequestV01 recursion level 0 with max 0 class ProcessingRequestV01{ MessageIdentification IsoMax35Text SettlementSessionIdentifier IsoExact4AlphaNumericText } ProcessingRequestV01 *-- "1..1" RequestDetails19 : Request
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 %% RequestDetails19 recursion level 0 with max 1 class RequestDetails19{ Type IsoMax35Text AdditionalRequestInformation IsoMax35Text } RequestDetails19 *-- "0..1" IPartyIdentification73Choice : RequestorIdentification %% IPartyIdentification73Choice recursion level 1 with max 1
RequestDetails19 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Type | Type of data being requested, for example, a sub-member BIC. | IsoMax35Text - Required 1..1 |
RequestorIdentification | Identificates the requestor. | IPartyIdentification73Choice - Optional 0..1 |
AdditionalRequestInformation | Additional information to support the processing request. | IsoMax35Text - Unknown 0..0 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the ProcessingRequestV01 implementation follows a specific implementaiton pattern. First of all, ProcessingRequestV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, ProcessingRequestV01Document implements IOuterDocument. Because ProcessingRequestV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type ProcessingRequestV01.
classDiagram class IOuterRecord ProcessingRequestV01 --|> IOuterRecord : Implements ProcessingRequestV01Document --|> IOuterDocument~ProcessingRequestV01~ : Implements class IOuterDocument~ProcessingRequestV01~ { ProcessingRequestV01 Message }
Document wrapper for serialization
The only real purpose ProcessingRequestV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:admi.017.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using ProcessingRequestV01.ToDocument() method. The returned ProcessingRequestV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram ProcessingRequestV01Document *-- ProcessingRequestV01 : 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.01">
<PrcgReq>
<MsgId>
<!-- MessageIdentification inner content -->
</MsgId>
<SttlmSsnIdr>
<!-- SettlementSessionIdentifier inner content -->
</SttlmSsnIdr>
<Req>
<!-- Request inner content -->
</Req>
</PrcgReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_4X6DQJXbEeaYkf5FCqYMeA"
nextVersions="_1MsY4QR4Ee29PP19jELcvQ"
name="ProcessingRequestV01"
definition="The Processing Request message is sent by a participant to a central system to request the initiation of a system process suported by a central system."
registrationStatus="Registered"
messageSet="_nB3wITJaEeOX98kTVpuqCw"
xmlTag="PrcgReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_Tos68ZXcEeaYkf5FCqYMeA"
nextVersions="_1Ms_8QR4Ee29PP19jELcvQ"
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="_V3DB0ZXcEeaYkf5FCqYMeA"
nextVersions="_1Ms_8wR4Ee29PP19jELcvQ"
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="_K1IXEJXdEeaYkf5FCqYMeA"
nextVersions="_1Ms_9QR4Ee29PP19jELcvQ"
name="Request"
definition="Contains the details of the processing request."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Req"
complexType="_qWuLAZXcEeaYkf5FCqYMeA" />
<messageDefinitionIdentifier
businessArea="admi"
messageFunctionality="017"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.