DerivativesTradeReportQueryV01

auth.029.001.01

The DerivativesTradeReportQuery message is sent by the supervisory authority system to the trade repositories, to query data based on the search criteria for the trade transaction 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
%% DerivativesTradeReportQueryV01 recursion level 0 with max 0
DerivativesTradeReportQueryV01 *-- "1..1" IPartyIdentification121Choice : RequestingAuthority
DerivativesTradeReportQueryV01 *-- "1..1" ITradeReportQuery4Choice : TradeQueryData
DerivativesTradeReportQueryV01 *-- "0..1" SupplementaryData1 : SupplementaryData
  

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

RequestingAuthority building block

Indicates 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
%% ITradeReportQuery4Choice recursion level 0 with max 1
  

TradeReportQuery4Choice members

SupplementaryData building block

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

classDiagram
    class IOuterRecord
    DerivativesTradeReportQueryV01 --|> IOuterRecord : Implements
    DerivativesTradeReportQueryV01Document --|> IOuterDocument~DerivativesTradeReportQueryV01~ : Implements
    class IOuterDocument~DerivativesTradeReportQueryV01~ {
        DerivativesTradeReportQueryV01 Message
     }
  

Document wrapper for serialization

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

classDiagram
    DerivativesTradeReportQueryV01Document *-- DerivativesTradeReportQueryV01 : 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.029.001.01">
    <DerivsTradRptQry>
        <RqstngAuthrty>
            <!-- RequestingAuthority inner content -->
        </RqstngAuthrty>
        <TradQryData>
            <!-- TradeQueryData inner content -->
        </TradQryData>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </DerivsTradRptQry>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_wdKwQxWsEeqvRcdYcNYAVw"
  nextVersions="_F_JP4d1bEeqxpKDfBZC1vg"
  name="DerivativesTradeReportQueryV01"
  definition="The DerivativesTradeReportQuery message is sent by the supervisory authority system to the trade repositories, to query data based on the search criteria for the trade transaction as defined by the system user."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="DerivsTradRptQry"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_wdKwRRWsEeqvRcdYcNYAVw"
    nextVersions="_F_JP491bEeqxpKDfBZC1vg"
    name="RequestingAuthority"
    definition="Indicates the authority that requests the query report."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="RqstngAuthrty"
    complexType="_c7VdkJQVEeiok48Eh9lW9Q" />
  <messageBuildingBlock
    xmi:id="_wdKwRxWsEeqvRcdYcNYAVw"
    nextVersions="_F_J28d1bEeqxpKDfBZC1vg"
    name="TradeQueryData"
    definition="Criteria for defining recurrent and ad-hoc queries."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="TradQryData"
    complexType="_P3lVAYeAEei-Poi-FosJdw" />
  <messageBuildingBlock
    xmi:id="_wdKwSRWsEeqvRcdYcNYAVw"
    nextVersions="_F_J2891bEeqxpKDfBZC1vg"
    name="SupplementaryData"
    definition="Additional information that cannot 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="029"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

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