SecuritiesFinancingReportingMissingCollateralRequestV02

auth.083.001.02

The SecuritiesFinancingReportingMissingCollateralRequest is made available by the trade repository (TR) to the report submitting entity and the reporting counterparty as well as the entity responsible for reporting, if applicable, with a request to submit collateral information for a given trade.

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
%% SecuritiesFinancingReportingMissingCollateralRequestV02 recursion level 0 with max 0
SecuritiesFinancingReportingMissingCollateralRequestV02 *-- "1..1" TradeTransactionIdentification18 : TransactionIdentification
SecuritiesFinancingReportingMissingCollateralRequestV02 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

TransactionIdentification building block

Set of information identifying the missing transactions that are to be supplemented. Provides details on transaction and conducting counterparty. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% TradeTransactionIdentification18 recursion level 0 with max 1
class TradeTransactionIdentification18{
    UniqueTradeIdentifier IsoMax52Text
}
TradeTransactionIdentification18 *-- "1..1" IOrganisationIdentification15Choice : ReportingCounterparty
TradeTransactionIdentification18 *-- "1..1" IPartyIdentification236Choice : OtherCounterparty
TradeTransactionIdentification18 *-- "0..1" MasterAgreement7 : MasterAgreement
%% IOrganisationIdentification15Choice recursion level 1 with max 1
%% IPartyIdentification236Choice recursion level 1 with max 1
%% MasterAgreement7 recursion level 1 with max 1
class MasterAgreement7{
    Version IsoMax50Text
    OtherMasterAgreementDetails IsoMax350Text
}
MasterAgreement7 *-- "1..1" IAgreementType2Choice : Type
  

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

classDiagram
    class IOuterRecord
    SecuritiesFinancingReportingMissingCollateralRequestV02 --|> IOuterRecord : Implements
    SecuritiesFinancingReportingMissingCollateralRequestV02Document --|> IOuterDocument~SecuritiesFinancingReportingMissingCollateralRequestV02~ : Implements
    class IOuterDocument~SecuritiesFinancingReportingMissingCollateralRequestV02~ {
        SecuritiesFinancingReportingMissingCollateralRequestV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SecuritiesFinancingReportingMissingCollateralRequestV02Document *-- SecuritiesFinancingReportingMissingCollateralRequestV02 : 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.083.001.02">
    <SctiesFincgRptgMssngCollReq>
        <TxId>
            <!-- TransactionIdentification inner content -->
        </TxId>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </SctiesFincgRptgMssngCollReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_EGxyIcKvEeuzU9S_IANlog"
  previousVersion="_2zvL9wuAEeqVvtu9Ny8FDA"
  name="SecuritiesFinancingReportingMissingCollateralRequestV02"
  definition="The SecuritiesFinancingReportingMissingCollateralRequest is made available by the trade repository (TR) to the  report submitting entity and the reporting counterparty as well as the entity responsible for reporting, if applicable, with a request to submit collateral information for a given trade. "
  registrationStatus="Registered"
  messageSet="_9iTc0K2XEeuIDus5QP8udw"
  xmlTag="SctiesFincgRptgMssngCollReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_EGxyI8KvEeuzU9S_IANlog"
    name="TransactionIdentification"
    definition="Set of information identifying the missing transactions that are to be supplemented. "
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="TxId"
    complexType="_O3OZgcgsEeuGrNSsxk3B0A" />
  <messageBuildingBlock
    xmi:id="_EGxyJcKvEeuzU9S_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="083"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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