SecuritiesFinancingReportingTransactionStateReportV02

auth.079.001.02

The SecuritiesFinancingReportingTransactionStateReport is sent by the trade repository (TR) to the other trade repository (TR) or the authority or made available to the report submitting entity and the reporting counterparty as well as the entity responsible for reporting, if applicable, containing latest state of the transaction.

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
%% SecuritiesFinancingReportingTransactionStateReportV02 recursion level 0 with max 0
SecuritiesFinancingReportingTransactionStateReportV02 *-- "1..1" ITradeStateReport5Choice : TradeData
SecuritiesFinancingReportingTransactionStateReportV02 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

TradeData building block

Information related to trade state reporting. Provides details for a trade state report. For comparison, see the ISO20022 official specification

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

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

classDiagram
    class IOuterRecord
    SecuritiesFinancingReportingTransactionStateReportV02 --|> IOuterRecord : Implements
    SecuritiesFinancingReportingTransactionStateReportV02Document --|> IOuterDocument~SecuritiesFinancingReportingTransactionStateReportV02~ : Implements
    class IOuterDocument~SecuritiesFinancingReportingTransactionStateReportV02~ {
        SecuritiesFinancingReportingTransactionStateReportV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SecuritiesFinancingReportingTransactionStateReportV02Document *-- SecuritiesFinancingReportingTransactionStateReportV02 : 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.079.001.02">
    <SctiesFincgRptgTxStatRpt>
        <TradData>
            <!-- TradeData inner content -->
        </TradData>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </SctiesFincgRptgTxStatRpt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_9g7DAcKvEeuzU9S_IANlog"
  previousVersion="_2zvMKQuAEeqVvtu9Ny8FDA"
  name="SecuritiesFinancingReportingTransactionStateReportV02"
  definition="The SecuritiesFinancingReportingTransactionStateReport is sent by the trade repository (TR) to the other trade repository (TR) or the authority or made available to the  report submitting entity and the reporting counterparty as well as the entity responsible for reporting, if applicable, containing latest state of the transaction."
  registrationStatus="Registered"
  messageSet="_9iTc0K2XEeuIDus5QP8udw"
  xmlTag="SctiesFincgRptgTxStatRpt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_9g7DA8KvEeuzU9S_IANlog"
    name="TradeData"
    definition="Information related to trade state reporting."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TradData"
    complexType="_x9GcscK-EeuCIrYISEfoUg" />
  <messageBuildingBlock
    xmi:id="_9g7DBcKvEeuzU9S_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="079"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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