auth.092.001.03
The DerivativesTradeRejectionStatisticalReport message is sent by the trade repository (TR) to the report submitting entity, 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 %% DerivativesTradeRejectionStatisticalReportV03 recursion level 0 with max 0 DerivativesTradeRejectionStatisticalReportV03 *-- "1..1" IStatisticsPerCounterparty17Choice : RejectionStatistics DerivativesTradeRejectionStatisticalReportV03 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
RejectionStatistics building block
Detailed information on rejections of derivative transactions. Statistics per counterparty reporting under the local regulation. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IStatisticsPerCounterparty17Choice recursion level 0 with max 1
StatisticsPerCounterparty17Choice members
Member name | Description | Data Type / Multiplicity |
---|
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
Member name | Description | Data Type / Multiplicity |
---|---|---|
PlaceAndName | Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. | IsoMax350Text - Optional 0..1 |
Envelope | Technical element wrapping the supplementary data. | IsoSupplementaryDataEnvelope1 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the DerivativesTradeRejectionStatisticalReportV03 implementation follows a specific implementaiton pattern. First of all, DerivativesTradeRejectionStatisticalReportV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, DerivativesTradeRejectionStatisticalReportV03Document implements IOuterDocument. Because DerivativesTradeRejectionStatisticalReportV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type DerivativesTradeRejectionStatisticalReportV03.
classDiagram class IOuterRecord DerivativesTradeRejectionStatisticalReportV03 --|> IOuterRecord : Implements DerivativesTradeRejectionStatisticalReportV03Document --|> IOuterDocument~DerivativesTradeRejectionStatisticalReportV03~ : Implements class IOuterDocument~DerivativesTradeRejectionStatisticalReportV03~ { DerivativesTradeRejectionStatisticalReportV03 Message }
Document wrapper for serialization
The only real purpose DerivativesTradeRejectionStatisticalReportV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:auth.092.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using DerivativesTradeRejectionStatisticalReportV03.ToDocument() method. The returned DerivativesTradeRejectionStatisticalReportV03Document value will serialize correctly according to ISO 20022 standards.
classDiagram DerivativesTradeRejectionStatisticalReportV03Document *-- DerivativesTradeRejectionStatisticalReportV03 : 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.092.001.03">
<DerivsTradRjctnSttstclRpt>
<RjctnSttstcs>
<!-- RejectionStatistics inner content -->
</RjctnSttstcs>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</DerivsTradRjctnSttstclRpt>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_pVVvj2mFEe2DRvVJM2Qy-g"
name="DerivativesTradeRejectionStatisticalReportV03"
definition="The DerivativesTradeRejectionStatisticalReport message is sent by the trade repository (TR) to the report submitting entity, identifying the transactions rejected and the reasons for a rejection."
registrationStatus="Registered"
messageSet="_gVqhJBWsEeqvRcdYcNYAVw"
xmlTag="DerivsTradRjctnSttstclRpt"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_pVVvkWmFEe2DRvVJM2Qy-g"
name="RejectionStatistics"
definition="Detailed information on rejections of derivative transactions."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="RjctnSttstcs"
complexType="_x7sJF1yGEe24CqbZJK5XxA" />
<messageBuildingBlock
xmi:id="_pVVvk2mFEe2DRvVJM2Qy-g"
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="092"
flavour="001"
version="03" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.