Iso20022

RequestForOrderConfirmationStatusReportV01

setr.058.001.01

Scope An executing party, for example, a transfer agent, send the RequestForOrderConfirmationStatusReport message to the instructing party, for example, an investment manager or its authorised representative, to request the status of one or several order confirmations. Usage The RequestForOrderConfirmationStatusReport message is used to request the status of either:

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
%% RequestForOrderConfirmationStatusReportV01 recursion level 0 with max 0
RequestForOrderConfirmationStatusReportV01 *-- "1..1" MessageIdentification1 : MessageIdentification
RequestForOrderConfirmationStatusReportV01 *-- "1..1" MessageAndBusinessReference5 : RequestDetails
RequestForOrderConfirmationStatusReportV01 *-- "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 confirmation for which the status is requested. Information to identify the funds order confirmations. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageAndBusinessReference5 recursion level 0 with max 1
MessageAndBusinessReference5 *-- "0..1" AdditionalReference3 : OtherReference
MessageAndBusinessReference5 *-- "0..1" AdditionalReference3 : PreviousReference
MessageAndBusinessReference5 *-- "0..1" AdditionalReference3 : RelatedReference
MessageAndBusinessReference5 *-- "0..0" InvestmentFundOrder3 : 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
%% InvestmentFundOrder3 recursion level 1 with max 1
class InvestmentFundOrder3{
    MasterReference IsoMax35Text
    OrderReference IsoMax35Text
    ClientReference IsoMax35Text
    DealReference IsoMax35Text
}
InvestmentFundOrder3 *-- "0..1" InvestmentAccount13 : InvestmentAccountDetails
InvestmentFundOrder3 *-- "0..1" FinancialInstrument10 : FinancialInstrumentDetails

MessageAndBusinessReference5 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 individual order instructions. InvestmentFundOrder3 - 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 RequestForOrderConfirmationStatusReportV01 implementation follows a specific implementaiton pattern. First of all, RequestForOrderConfirmationStatusReportV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, RequestForOrderConfirmationStatusReportV01Document implements IOuterDocument. Because RequestForOrderConfirmationStatusReportV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type RequestForOrderConfirmationStatusReportV01.

classDiagram
    class IOuterRecord
    RequestForOrderConfirmationStatusReportV01 --|> IOuterRecord : Implements
    RequestForOrderConfirmationStatusReportV01Document --|> IOuterDocument~RequestForOrderConfirmationStatusReportV01~ : Implements
    class IOuterDocument~RequestForOrderConfirmationStatusReportV01~ {
        RequestForOrderConfirmationStatusReportV01 Message
     }

Document wrapper for serialization

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

classDiagram
    RequestForOrderConfirmationStatusReportV01Document *-- RequestForOrderConfirmationStatusReportV01 : 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.058.001.01">
    <ReqForOrdrConfStsRptV01>
        <MsgId>
            <!-- MessageIdentification inner content -->
        </MsgId>
        <ReqDtls>
            <!-- RequestDetails inner content -->
        </ReqDtls>
        <Xtnsn>
            <!-- Extension inner content -->
        </Xtnsn>
    </ReqForOrdrConfStsRptV01>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_v7tBCNE7Ed-BzquC8wXy7w_-862773278"
  nextVersions="_Aab8RzbLEead9bDRE_1DAQ"
  name="RequestForOrderConfirmationStatusReportV01"
  definition="Scope&#xD;&#xA;An executing party, for example, a transfer agent, send the RequestForOrderConfirmationStatusReport message to the instructing party, for example, an investment manager or its authorised representative, to request the status of one or several order confirmations.&#xD;&#xA;Usage&#xD;&#xA;The RequestForOrderConfirmationStatusReport message is used to request the status of either:&#xD;&#xA;- one or several individual order confirmations, or,&#xD;&#xA;- one or several order confirmation messages.&#xD;&#xA;The response to a RequestForOrderConfirmationStatusReport message is the OrderConfirmationStatusReport message.&#xD;&#xA;When the RequestForOrderConfirmationStatusReport message is used to request the status of several individual order confirmations or one or more order confirmation messages, the executing party may receive several OrderConfirmationStatusReport messages from the instructing party.&#xD;&#xA;When the RequestForOrderConfirmationStatusReport is used to request the status of one or more individual order confirmations, each individual order confirmation is identified with its order reference. The message identification of the message in which the individual order confirmation was conveyed may also be quoted in PreviousReference.&#xD;&#xA;When the RequestForOrderConfirmationStatusReport is used to request the status of an order confirmation message, then the message identification of the order confirmation message is identified in PreviousReference."
  registrationStatus="Registered"
  messageSet="_wFQdsE2rEeG_I4xRYCA_7g"
  xmlTag="ReqForOrdrConfStsRptV01"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_v72yANE7Ed-BzquC8wXy7w_1937667668"
    nextVersions="_Aab8STbLEead9bDRE_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="_v72yAdE7Ed-BzquC8wXy7w_-374664944"
    nextVersions="_Aab8SzbLEead9bDRE_1DAQ"
    name="RequestDetails"
    definition="Information to identify the order confirmation for which the status is requested."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="ReqDtls"
    complexType="_RMLdRtp-Ed-ak6NoX_4Aeg_1019850992" />
  <messageBuildingBlock
    xmi:id="_v72yAtE7Ed-BzquC8wXy7w_-2086704739"
    nextVersions="_Aab8TTbLEead9bDRE_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="058"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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