setr.018.001.03
Scope An instructing party, for example, an investment manager or its authorised representative, sends the RequestForOrderStatusReport to the executing party, for example, a transfer agent, to request the status of one or more order instruction or order cancellation request messages. Usage The RequestForOrderStatusReport message is used to request the status of:
- one or several individual order instructions, or,
- one or several order messages, or
- one or several individual order cancellation requests, or,
- one or several order cancellation request messages. The response to a RequestForOrderStatusReport message is the OrderInstructionStatusReport message or OrderCancellationStatusReport message. If the RequestForOrderStatusReport message is used to request the status of several individual order instructions or one or more order instruction messages, then the instructing party may receive several OrderInstructionStatusReport messages from the executing party. If the RequestForOrderStatusReport message is used to request the status of several individual order cancellation requests or one or more order cancellation messages, then the instructing party may receive several OrderCancellationStatusReport messages from the executing party. When the RequestForOrderStatusReport is used to request the status of one or more individual orders or order cancellations, each individual order is identified with its order reference. The investment account and/or financial instrument related to the order can also be identified. The message identification of the message in which the individual order was conveyed may also be quoted in PreviousReference. When the RequestForOrderStatusReport is used to request the status of an order message or an order cancellations request message, then the message identification of the order or cancellation message is identified in PreviousReference. The RequestForOrderStatusReport message may not be used to request the status of an investment account, a transfer or the status of a financial instrument.
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 %% RequestForOrderStatusReportV03 recursion level 0 with max 0 RequestForOrderStatusReportV03 *-- "1..1" MessageIdentification1 : MessageIdentification RequestForOrderStatusReportV03 *-- "1..1" MessageAndBusinessReference4 : RequestDetails RequestForOrderStatusReportV03 *-- "0..1" Extension1 : Extension
Now, we will zero-in one-by-one on each of these building blocks.
MessageIdentification building block
Reference that uniquely identifies a message from a business application standpoint. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification
classDiagram direction tb %% MessageIdentification1 recursion level 0 with max 1 class MessageIdentification1{ Identification IsoMax35Text CreationDateTime IsoISODateTime }
MessageIdentification1 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Identification of the message. | IsoMax35Text - Required 1..1 |
CreationDateTime | Date of creation of the message. | IsoISODateTime - Required 1..1 |
RequestDetails building block
Information to identify the order(s) for which the status is requested. Information to identify funds order(s). For comparison, see the ISO20022 official specification
classDiagram direction tb %% MessageAndBusinessReference4 recursion level 0 with max 1 MessageAndBusinessReference4 *-- "0..1" AdditionalReference3 : OtherReference MessageAndBusinessReference4 *-- "0..1" AdditionalReference3 : PreviousReference MessageAndBusinessReference4 *-- "0..1" AdditionalReference3 : RelatedReference MessageAndBusinessReference4 *-- "0..0" InvestmentFundOrder2 : OrderReference %% AdditionalReference3 recursion level 1 with max 1 class AdditionalReference3{ Reference IsoMax35Text MessageName IsoMax35Text } AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer %% AdditionalReference3 recursion level 1 with max 1 class AdditionalReference3{ Reference IsoMax35Text MessageName IsoMax35Text } AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer %% AdditionalReference3 recursion level 1 with max 1 class AdditionalReference3{ Reference IsoMax35Text MessageName IsoMax35Text } AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer %% InvestmentFundOrder2 recursion level 1 with max 1 class InvestmentFundOrder2{ MasterReference IsoMax35Text OrderReference IsoMax35Text ClientReference IsoMax35Text CancellationReference IsoMax35Text DealReference IsoMax35Text } InvestmentFundOrder2 *-- "0..1" InvestmentAccount13 : InvestmentAccountDetails InvestmentFundOrder2 *-- "0..1" FinancialInstrument10 : FinancialInstrumentDetails
MessageAndBusinessReference4 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
OtherReference | Reference to a linked message sent in a proprietary way or reference of a system. | AdditionalReference3 - Optional 0..1 |
PreviousReference | Reference to a linked message that was previously sent. | AdditionalReference3 - Optional 0..1 |
RelatedReference | Reference to a linked message that was previously received. | AdditionalReference3 - Optional 0..1 |
OrderReference | Unique and unambiguous identifiers of one or more indiviudal order instructions or individual order cancellation requests. | InvestmentFundOrder2 - Unknown 0..0 |
Extension 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 %% Extension1 recursion level 0 with max 1 class Extension1{ PlaceAndName IsoMax350Text Text IsoMax350Text }
Extension1 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
PlaceAndName | Name qualifying the information provided in the Text field, and place where this information should be inserted. | IsoMax350Text - Required 1..1 |
Text | Text of the extension. | IsoMax350Text - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the RequestForOrderStatusReportV03 implementation follows a specific implementaiton pattern. First of all, RequestForOrderStatusReportV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, RequestForOrderStatusReportV03Document implements IOuterDocument. Because RequestForOrderStatusReportV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type RequestForOrderStatusReportV03.
classDiagram class IOuterRecord RequestForOrderStatusReportV03 --|> IOuterRecord : Implements RequestForOrderStatusReportV03Document --|> IOuterDocument~RequestForOrderStatusReportV03~ : Implements class IOuterDocument~RequestForOrderStatusReportV03~ { RequestForOrderStatusReportV03 Message }
Document wrapper for serialization
The only real purpose RequestForOrderStatusReportV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:setr.018.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using RequestForOrderStatusReportV03.ToDocument() method. The returned RequestForOrderStatusReportV03Document value will serialize correctly according to ISO 20022 standards.
classDiagram RequestForOrderStatusReportV03Document *-- RequestForOrderStatusReportV03 : 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:setr.018.001.03">
<ReqForOrdrStsRptV03>
<MsgId>
<!-- MessageIdentification inner content -->
</MsgId>
<ReqDtls>
<!-- RequestDetails inner content -->
</ReqDtls>
<Xtnsn>
<!-- Extension inner content -->
</Xtnsn>
</ReqForOrdrStsRptV03>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_wy_OWNE7Ed-BzquC8wXy7w_1331513670"
nextVersions="_Aab7UzbLEead9bDRE_1DAQ"
previousVersion="_wWrFyNE7Ed-BzquC8wXy7w_-1373686594"
name="RequestForOrderStatusReportV03"
definition="Scope
An instructing party, for example, an investment manager or its authorised representative, sends the RequestForOrderStatusReport to the executing party, for example, a transfer agent, to request the status of one or more order instruction or order cancellation request messages.
Usage
The RequestForOrderStatusReport message is used to request the status of:
- one or several individual order instructions, or,
- one or several order messages, or
- one or several individual order cancellation requests, or,
- one or several order cancellation request messages.
The response to a RequestForOrderStatusReport message is the OrderInstructionStatusReport message or OrderCancellationStatusReport message.
If the RequestForOrderStatusReport message is used to request the status of several individual order instructions or one or more order instruction messages, then the instructing party may receive several OrderInstructionStatusReport messages from the executing party.
If the RequestForOrderStatusReport message is used to request the status of several individual order cancellation requests or one or more order cancellation messages, then the instructing party may receive several OrderCancellationStatusReport messages from the executing party.
When the RequestForOrderStatusReport is used to request the status of one or more individual orders or order cancellations, each individual order is identified with its order reference. The investment account and/or financial instrument related to the order can also be identified. The message identification of the message in which the individual order was conveyed may also be quoted in PreviousReference.
When the RequestForOrderStatusReport is used to request the status of an order message or an order cancellations request message, then the message identification of the order or cancellation message is identified in PreviousReference.
The RequestForOrderStatusReport message may not be used to request the status of an investment account, a transfer or the status of a financial instrument."
registrationStatus="Registered"
messageSet="_wFQdsE2rEeG_I4xRYCA_7g"
xmlTag="ReqForOrdrStsRptV03"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_wy_OWdE7Ed-BzquC8wXy7w_390506052"
nextVersions="_Aab7VTbLEead9bDRE_1DAQ"
name="MessageIdentification"
definition="Reference that uniquely identifies a message from a business application standpoint."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MsgId"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_wy_OWtE7Ed-BzquC8wXy7w_1331513937"
nextVersions="_Aab7VzbLEead9bDRE_1DAQ"
name="RequestDetails"
definition="Information to identify the order(s) for which the status is requested."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="ReqDtls"
complexType="_RMVOSdp-Ed-ak6NoX_4Aeg_-22206736" />
<messageBuildingBlock
xmi:id="_wy_OW9E7Ed-BzquC8wXy7w_-800406650"
nextVersions="_Aab7WTbLEead9bDRE_1DAQ"
name="Extension"
definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="Xtnsn"
complexType="_Q6vvCNp-Ed-ak6NoX_4Aeg_1503007069" />
<messageDefinitionIdentifier
businessArea="setr"
messageFunctionality="018"
flavour="001"
version="03" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.