trea.008.001.02
Scope The StatusNotification message is sent by a central system to a participant to notify the current status of a trade in the system. Usage This message will be sent at specific times agreed upon by the central settlement system and a participant in a central settlement system.
This message is obsolete please use ForeignExchangeAndDerivativeTradeStatusNotificationV03 - fxtr.008.001.03
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
%% StatusNotificationV02 recursion level 0 with max 0
StatusNotificationV02 *-- "1..1" TradeData1 : TradeData
Now, we will zero-in one-by-one on each of these building blocks.
TradeData building block
Provides information on the status of a trade in a system. Provides information on the status of a trade. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% TradeData1 recursion level 0 with max 1
class TradeData1{
NotificationIdentification IsoMax35Text
MatchingSystemUniqueReference IsoMax35Text
StatusOriginator IsoMax35Text
CurrentStatus TradeStatus1Code
ExtendedCurrentStatus IsoExtended350Code
CurrentStatusSubType IsoMax70Text
CurrentStatusTime IsoISODateTime
PreviousStatus TradeStatus1Code
ExtendedPreviousStatus IsoExtended350Code
PreviousStatusSubType IsoMax70Text
PreviousStatusTime IsoISODateTime
ProductType IsoMax4AlphaNumericText
}
TradeData1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| NotificationIdentification | Refers to the identification of a notification. | IsoMax35Text - Required 1..1 |
| MatchingSystemUniqueReference | Reference to the unique identification assigned to a trade by a central matching system. | IsoMax35Text - Required 1..1 |
| StatusOriginator | Identifies the party which assigned a status to a treasury trade. | IsoMax35Text - Optional 0..1 |
| CurrentStatus | Specifies the new status of a trade. | TradeStatus1Code - Required 1..1 |
| ExtendedCurrentStatus | Description of the status of a trade when no coded form is available. | IsoExtended350Code - Required 1..1 |
| CurrentStatusSubType | Additional information on the current status of a trade in a central system. | IsoMax70Text - Optional 0..1 |
| CurrentStatusTime | Specifies the time at which the current status was assigned. | IsoISODateTime - Optional 0..1 |
| PreviousStatus | Specifies the previous status of a trade. | TradeStatus1Code - Optional 0..1 |
| ExtendedPreviousStatus | Description of the status of a trade when no coded form is available. | IsoExtended350Code - Optional 0..1 |
| PreviousStatusSubType | Additional information on the previous status of a trade in a central system. | IsoMax70Text - Optional 0..1 |
| PreviousStatusTime | Specifies the time at which the previous status was assigned. | IsoISODateTime - Optional 0..1 |
| ProductType | Specifies the product for which the status of the confirmation is reported. | IsoMax4AlphaNumericText - Optional 0..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the StatusNotificationV02 implementation follows a specific implementaiton pattern. First of all, StatusNotificationV02 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, StatusNotificationV02Document implements IOuterDocument. Because StatusNotificationV02 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type StatusNotificationV02.
classDiagram
class IOuterRecord
StatusNotificationV02 --|> IOuterRecord : Implements
StatusNotificationV02Document --|> IOuterDocument~StatusNotificationV02~ : Implements
class IOuterDocument~StatusNotificationV02~ {
StatusNotificationV02 Message
}
Document wrapper for serialization
The only real purpose StatusNotificationV02Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:trea.008.001.02’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using StatusNotificationV02.ToDocument() method. The returned StatusNotificationV02Document value will serialize correctly according to ISO 20022 standards.
classDiagram
StatusNotificationV02Document *-- StatusNotificationV02 : 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:trea.008.001.02">
<trea.008.001.02>
<TradData>
<!-- TradeData inner content -->
</TradData>
</trea.008.001.02>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_VgTq09E8Ed-BzquC8wXy7w_1259743081"
name="StatusNotificationV02"
definition="Scope
The StatusNotification message is sent by a central system to a participant to notify the current status of a trade in the system.
Usage
This message will be sent at specific times agreed upon by the central settlement system and a participant in a central settlement system.


This message is obsolete please use ForeignExchangeAndDerivativeTradeStatusNotificationV03 - fxtr.008.001.03"
registrationStatus="Registered"
messageSet="_wRx2x02rEeG_I4xRYCA_7g"
xmlName="trea.008.001.02"
xmlTag="trea.008.001.02"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_VgTq1NE8Ed-BzquC8wXy7w_-575229954"
name="TradeData"
definition="Provides information on the status of a trade in a system."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="TradData"
complexType="_UscfANp-Ed-ak6NoX_4Aeg_1902245509" />
<messageDefinitionIdentifier
businessArea="trea"
messageFunctionality="008"
flavour="001"
version="02" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.