SecuritiesFinancingReportingTransactionStatusAdviceV02

auth.084.001.02

The SecuritiesFinancingReportingTransactionStatusAdvice message is sent by the trade repository (TR) to the authority or made available to the report submitting entity and the reporting counterparty as well as the entity responsible for reporting, if applicable, identifying the transactions rejected and the reasons for a rejection.

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
%% SecuritiesFinancingReportingTransactionStatusAdviceV02 recursion level 0 with max 0
SecuritiesFinancingReportingTransactionStatusAdviceV02 *-- "1..1" ITradeData35Choice : TransactionReportStatusAndReason
SecuritiesFinancingReportingTransactionStatusAdviceV02 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

TransactionReportStatusAndReason building block

Provides the status and reason of the transaction report advice. Set of data concerning the reporting trade. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ITradeData35Choice recursion level 0 with max 1
  

TradeData35Choice members

SupplementaryData building block

Additional information that can not be captured in the structured fields 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 SecuritiesFinancingReportingTransactionStatusAdviceV02 implementation follows a specific implementaiton pattern. First of all, SecuritiesFinancingReportingTransactionStatusAdviceV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesFinancingReportingTransactionStatusAdviceV02Document implements IOuterDocument. Because SecuritiesFinancingReportingTransactionStatusAdviceV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesFinancingReportingTransactionStatusAdviceV02.

classDiagram
    class IOuterRecord
    SecuritiesFinancingReportingTransactionStatusAdviceV02 --|> IOuterRecord : Implements
    SecuritiesFinancingReportingTransactionStatusAdviceV02Document --|> IOuterDocument~SecuritiesFinancingReportingTransactionStatusAdviceV02~ : Implements
    class IOuterDocument~SecuritiesFinancingReportingTransactionStatusAdviceV02~ {
        SecuritiesFinancingReportingTransactionStatusAdviceV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SecuritiesFinancingReportingTransactionStatusAdviceV02Document *-- SecuritiesFinancingReportingTransactionStatusAdviceV02 : 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:auth.084.001.02">
    <SctiesFincgRptgTxStsAdvc>
        <TxRptStsAndRsn>
            <!-- TransactionReportStatusAndReason inner content -->
        </TxRptStsAndRsn>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </SctiesFincgRptgTxStsAdvc>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_BdniEcKwEeuzU9S_IANlog"
  previousVersion="_2zvMLwuAEeqVvtu9Ny8FDA"
  name="SecuritiesFinancingReportingTransactionStatusAdviceV02"
  definition="The SecuritiesFinancingReportingTransactionStatusAdvice message is sent by the trade repository (TR) to the authority or made available to the report submitting entity and the reporting counterparty as well as the entity responsible for reporting, if applicable, identifying the transactions rejected and the reasons for a rejection."
  registrationStatus="Registered"
  messageSet="_9iTc0K2XEeuIDus5QP8udw"
  xmlTag="SctiesFincgRptgTxStsAdvc"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_BdniE8KwEeuzU9S_IANlog"
    name="TransactionReportStatusAndReason"
    definition="Provides the status and reason of the transaction report advice."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="TxRptStsAndRsn"
    complexType="_hQSv4cK4EeuFNp8LZAnorg" />
  <messageBuildingBlock
    xmi:id="_BdniFcKwEeuzU9S_IANlog"
    name="SupplementaryData"
    definition="Additional information that can not be captured in the structured fields and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="auth"
    messageFunctionality="084"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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