SecuritiesFinancingReportingTransactionQueryV02

auth.094.001.02

The SecuritiesFinancingReportingTransactionQuery message is sent by the authority to the trade repositories, to query data based on the search criteria for the transactions as defined by the system user.

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
%% SecuritiesFinancingReportingTransactionQueryV02 recursion level 0 with max 0
SecuritiesFinancingReportingTransactionQueryV02 *-- "1..1" IPartyIdentification121Choice : RequestingAuthority
SecuritiesFinancingReportingTransactionQueryV02 *-- "1..1" ITradeReportQuery13Choice : TradeQueryData
SecuritiesFinancingReportingTransactionQueryV02 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

RequestingAuthority building block

Set of information identifying the authority that requests the query report. Choice of identification of a party. For comparison, see the ISO20022 official specification

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

PartyIdentification121Choice members

TradeQueryData building block

Criteria for defining recurrent and ad-hoc queries. Defines the type of the query, a recurrent or an ad-hoc query. For comparison, see the ISO20022 official specification

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

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

classDiagram
    class IOuterRecord
    SecuritiesFinancingReportingTransactionQueryV02 --|> IOuterRecord : Implements
    SecuritiesFinancingReportingTransactionQueryV02Document --|> IOuterDocument~SecuritiesFinancingReportingTransactionQueryV02~ : Implements
    class IOuterDocument~SecuritiesFinancingReportingTransactionQueryV02~ {
        SecuritiesFinancingReportingTransactionQueryV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    SecuritiesFinancingReportingTransactionQueryV02Document *-- SecuritiesFinancingReportingTransactionQueryV02 : 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.094.001.02">
    <SctiesFincgRptgTxQry>
        <RqstngAuthrty>
            <!-- RequestingAuthority inner content -->
        </RqstngAuthrty>
        <TradQryData>
            <!-- TradeQueryData inner content -->
        </TradQryData>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </SctiesFincgRptgTxQry>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_vY6mgcKvEeuzU9S_IANlog"
  previousVersion="_2zvMFQuAEeqVvtu9Ny8FDA"
  name="SecuritiesFinancingReportingTransactionQueryV02"
  definition="The SecuritiesFinancingReportingTransactionQuery message is sent by the authority to the trade repositories, to query data based on the search criteria for the  transactions as defined by the system user."
  registrationStatus="Registered"
  messageSet="_9iTc0K2XEeuIDus5QP8udw"
  xmlTag="SctiesFincgRptgTxQry"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_vY6mg8KvEeuzU9S_IANlog"
    name="RequestingAuthority"
    definition="Set of information identifying the authority that requests the query report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RqstngAuthrty"
    complexType="_c7VdkJQVEeiok48Eh9lW9Q" />
  <messageBuildingBlock
    xmi:id="_vY6mhcKvEeuzU9S_IANlog"
    name="TradeQueryData"
    definition="Criteria for defining recurrent and ad-hoc queries."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TradQryData"
    complexType="_1LqeURfMEeyPHpqpKwtFdw" />
  <messageBuildingBlock
    xmi:id="_vY6mh8KvEeuzU9S_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="094"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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