auth.012.001.01
The MoneyMarketSecuredMarketStatisticalReport message is sent by the reporting agents to the relevant competent authority, to report all relevant secured money market transactions.
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 %% MoneyMarketSecuredMarketStatisticalReportV01 recursion level 0 with max 0 MoneyMarketSecuredMarketStatisticalReportV01 *-- "1..1" MoneyMarketReportHeader1 : ReportHeader MoneyMarketSecuredMarketStatisticalReportV01 *-- "1..1" ISecuredMarketReport3Choice : SecuredMarketReport MoneyMarketSecuredMarketStatisticalReportV01 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
ReportHeader building block
Provides the elements specific to the report. Provides the money market statistical report instrument related header details. For comparison, see the ISO20022 official specification
classDiagram direction tb %% MoneyMarketReportHeader1 recursion level 0 with max 1 class MoneyMarketReportHeader1{ ReportingAgent IsoLEIIdentifier } MoneyMarketReportHeader1 *-- "1..1" DateTimePeriod1 : ReferencePeriod %% DateTimePeriod1 recursion level 1 with max 1 class DateTimePeriod1{ FromDateTime IsoISODateTime ToDateTime IsoISODateTime }
MoneyMarketReportHeader1 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
ReportingAgent | Agent which is subject to reporting requirements. | IsoLEIIdentifier - Required 1..1 |
ReferencePeriod | Beginning and ending date-time to which the transaction data refers (trade date in case of new transactions and date of amendment in case of revisions). | DateTimePeriod1 - Required 1..1 |
SecuredMarketReport building block
Provides the reason why no activity is reported or the required list of transactions for the secured market segment. Choice between a reason for no activity and the secured market segment transaction details. For comparison, see the ISO20022 official specification
classDiagram direction tb %% ISecuredMarketReport3Choice recursion level 0 with max 1
SecuredMarketReport3Choice members
Member name | Description | Data Type / Multiplicity |
---|
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
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 MoneyMarketSecuredMarketStatisticalReportV01 implementation follows a specific implementaiton pattern. First of all, MoneyMarketSecuredMarketStatisticalReportV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MoneyMarketSecuredMarketStatisticalReportV01Document implements IOuterDocument. Because MoneyMarketSecuredMarketStatisticalReportV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MoneyMarketSecuredMarketStatisticalReportV01.
classDiagram class IOuterRecord MoneyMarketSecuredMarketStatisticalReportV01 --|> IOuterRecord : Implements MoneyMarketSecuredMarketStatisticalReportV01Document --|> IOuterDocument~MoneyMarketSecuredMarketStatisticalReportV01~ : Implements class IOuterDocument~MoneyMarketSecuredMarketStatisticalReportV01~ { MoneyMarketSecuredMarketStatisticalReportV01 Message }
Document wrapper for serialization
The only real purpose MoneyMarketSecuredMarketStatisticalReportV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:auth.012.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MoneyMarketSecuredMarketStatisticalReportV01.ToDocument() method. The returned MoneyMarketSecuredMarketStatisticalReportV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram MoneyMarketSecuredMarketStatisticalReportV01Document *-- MoneyMarketSecuredMarketStatisticalReportV01 : 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.012.001.01">
<MnyMktScrdMktSttstclRpt>
<RptHdr>
<!-- ReportHeader inner content -->
</RptHdr>
<ScrdMktRpt>
<!-- SecuredMarketReport inner content -->
</ScrdMktRpt>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</MnyMktScrdMktSttstclRpt>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_OgdYwaidEeWHO_l3hf2rlA"
nextVersions="_DufHwcEPEea7jLfvGi1PDw"
name="MoneyMarketSecuredMarketStatisticalReportV01"
definition="The MoneyMarketSecuredMarketStatisticalReport message is sent by the reporting agents to the relevant competent authority, to report all relevant secured money market transactions."
registrationStatus="Registered"
messageSet="_eC9FZCxeEeW8e8DtcHfc3A"
xmlTag="MnyMktScrdMktSttstclRpt"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_OgdYw6idEeWHO_l3hf2rlA"
nextVersions="_DufHw8EPEea7jLfvGi1PDw"
name="ReportHeader"
definition="Provides the elements specific to the report."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="RptHdr"
complexType="_MVvycJfiEeSfnc-VXAEapg" />
<messageBuildingBlock
xmi:id="_OgdYxaidEeWHO_l3hf2rlA"
nextVersions="_DufHxcEPEea7jLfvGi1PDw"
name="SecuredMarketReport"
definition="Provides the reason why no activity is reported or the required list of transactions for the secured market segment."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="ScrdMktRpt"
complexType="_ghnREaidEeWHO_l3hf2rlA" />
<messageBuildingBlock
xmi:id="_OgdYx6idEeWHO_l3hf2rlA"
nextVersions="_DufHx8EPEea7jLfvGi1PDw"
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="012"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.