auth.028.001.01
The MoneyMarketStatisticalReportStatusAdvice message is sent by the relevant competent authority to the reporting agents to provide the status on the reported 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
%% MoneyMarketStatisticalReportStatusAdviceV01 recursion level 0 with max 0
MoneyMarketStatisticalReportStatusAdviceV01 *-- "1..1" MoneyMarketStatusReportHeader1 : StatusReportHeader
MoneyMarketStatisticalReportStatusAdviceV01 *-- "0..1" MoneyMarketTransactionStatus2 : TransactionStatus
MoneyMarketStatisticalReportStatusAdviceV01 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
StatusReportHeader building block
Provides the status on the global report. Provides the money market statistical status report header details. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MoneyMarketStatusReportHeader1 recursion level 0 with max 1
class MoneyMarketStatusReportHeader1{
ReportingAgent IsoLEIIdentifier
ReportStatus StatisticalReportingStatus1Code
}
MoneyMarketStatusReportHeader1 *-- "1..1" DateTimePeriod1 : ReportingPeriod
MoneyMarketStatusReportHeader1 *-- "0..0" GenericValidationRuleIdentification1 : ValidationRule
%% DateTimePeriod1 recursion level 1 with max 1
class DateTimePeriod1{
FromDateTime IsoISODateTime
ToDateTime IsoISODateTime
}
%% GenericValidationRuleIdentification1 recursion level 1 with max 1
class GenericValidationRuleIdentification1{
Identification IsoMax35Text
Description IsoMax350Text
Issuer IsoMax35Text
}
GenericValidationRuleIdentification1 *-- "0..1" IValidationRuleSchemeName1Choice : SchemeName
MoneyMarketStatusReportHeader1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| ReportingAgent | Agent which is subject to reporting requirements. | IsoLEIIdentifier - Required 1..1 |
| ReportingPeriod | For daily reporting this is the day to which the transaction data in the status message refers (trade date or amendment date if there are corrections). For periodic reporting this is the first and the last day to which the transaction data in the status message refers (trade date or amendment date in case of corrections). | DateTimePeriod1 - Required 1..1 |
| ReportStatus | Provides the status for the full report. | StatisticalReportingStatus1Code - Required 1..1 |
| ValidationRule | Provides the details of the rule which could not be validated. | GenericValidationRuleIdentification1 - Unknown 0..0 |
TransactionStatus building block
Provides the status on an individual transaction and the related reason if required. Provides the details of each individual secured market transaction. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MoneyMarketTransactionStatus2 recursion level 0 with max 1
class MoneyMarketTransactionStatus2{
UniqueTransactionIdentifier IsoMax105Text
ProprietaryTransactionIdentification IsoMax105Text
BranchIdentification IsoLEIIdentifier
Status StatisticalReportingStatus2Code
}
MoneyMarketTransactionStatus2 *-- "0..0" GenericValidationRuleIdentification1 : ValidationRule
MoneyMarketTransactionStatus2 *-- "0..0" SupplementaryData1 : SupplementaryData
%% GenericValidationRuleIdentification1 recursion level 1 with max 1
class GenericValidationRuleIdentification1{
Identification IsoMax35Text
Description IsoMax350Text
Issuer IsoMax35Text
}
GenericValidationRuleIdentification1 *-- "0..1" IValidationRuleSchemeName1Choice : SchemeName
%% SupplementaryData1 recursion level 1 with max 1
class SupplementaryData1{
PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
MoneyMarketTransactionStatus2 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| UniqueTransactionIdentifier | Unique transaction identifier will be created at the time a transaction is first executed, shared with all registered entities and counterparties involved in the transaction, and used to track that particular transaction during its lifetime. | IsoMax105Text - Optional 0..1 |
| ProprietaryTransactionIdentification | Internal unique transaction identifier used by the reporting agent for each transaction. | IsoMax105Text - Required 1..1 |
| BranchIdentification | Unique and unambiguous legal entity identification of the branch of the reporting agent in which the transaction has been booked. Usage: This field must only be provided if the transaction has been conducted and booked by a branch of the reporting agent and only if this branch has its own LEI that the reporting agent can clearly identify. Where the transaction has been booked by the head office or the reporting agent cannot be identified by a unique branch-specific LEI, the reporting agent must provide the LEI of the head office. | IsoLEIIdentifier - Optional 0..1 |
| Status | Defines status of the reported transaction. | StatisticalReportingStatus2Code - Required 1..1 |
| ValidationRule | Provides the details of the rule which could not be validated. | GenericValidationRuleIdentification1 - Unknown 0..0 |
| SupplementaryData | Additional information that can not be captured in the structured fields and/or any other specific block. | SupplementaryData1 - Unknown 0..0 |
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 MoneyMarketStatisticalReportStatusAdviceV01 implementation follows a specific implementaiton pattern. First of all, MoneyMarketStatisticalReportStatusAdviceV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MoneyMarketStatisticalReportStatusAdviceV01Document implements IOuterDocument. Because MoneyMarketStatisticalReportStatusAdviceV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MoneyMarketStatisticalReportStatusAdviceV01.
classDiagram
class IOuterRecord
MoneyMarketStatisticalReportStatusAdviceV01 --|> IOuterRecord : Implements
MoneyMarketStatisticalReportStatusAdviceV01Document --|> IOuterDocument~MoneyMarketStatisticalReportStatusAdviceV01~ : Implements
class IOuterDocument~MoneyMarketStatisticalReportStatusAdviceV01~ {
MoneyMarketStatisticalReportStatusAdviceV01 Message
}
Document wrapper for serialization
The only real purpose MoneyMarketStatisticalReportStatusAdviceV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:auth.028.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MoneyMarketStatisticalReportStatusAdviceV01.ToDocument() method. The returned MoneyMarketStatisticalReportStatusAdviceV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MoneyMarketStatisticalReportStatusAdviceV01Document *-- MoneyMarketStatisticalReportStatusAdviceV01 : 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.028.001.01">
<MnyMktSttstclRptStsAdvc>
<StsRptHdr>
<!-- StatusReportHeader inner content -->
</StsRptHdr>
<TxSts>
<!-- TransactionStatus inner content -->
</TxSts>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</MnyMktSttstclRptStsAdvc>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_1P-hEaieEeWHO_l3hf2rlA"
name="MoneyMarketStatisticalReportStatusAdviceV01"
definition="The MoneyMarketStatisticalReportStatusAdvice message is sent by the relevant competent authority to the reporting agents to provide the status on the reported transactions."
registrationStatus="Registered"
messageSet="_eC9FZCxeEeW8e8DtcHfc3A _eEhc0MEOEea7jLfvGi1PDw"
xmlTag="MnyMktSttstclRptStsAdvc"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_1P-hE6ieEeWHO_l3hf2rlA"
name="StatusReportHeader"
definition="Provides the status on the global report."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="StsRptHdr"
complexType="_olkndNjLEeSD0e0ybx5L5Q" />
<messageBuildingBlock
xmi:id="_1P-hFaieEeWHO_l3hf2rlA"
name="TransactionStatus"
definition="Provides the status on an individual transaction and the related reason if required."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="TxSts"
complexType="_CiwJQaigEeWHO_l3hf2rlA" />
<messageBuildingBlock
xmi:id="_1P-hF6ieEeWHO_l3hf2rlA"
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="028"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.