supl.010.001.01
The DTCCCAPSSD1 message extends ISO corporate action event processing status advice message with DTCC corporate action elements not covered in the standard message.
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 %% DTCCCAPSSD1V01 recursion level 0 with max 0 DTCCCAPSSD1V01 *-- "0..1" CorporateActionGeneralInformationSD3 : CorporateActionGeneralInformation
Now, we will zero-in one-by-one on each of these building blocks.
CorporateActionGeneralInformation building block
Extension block for the information to be extended as corporate action general information. Provides additional information regarding corporate action general information. For comparison, see the ISO20022 official specification
classDiagram direction tb %% CorporateActionGeneralInformationSD3 recursion level 0 with max 1 class CorporateActionGeneralInformationSD3{ PlaceAndName IsoMax350Text RecordDate IsoISODate } CorporateActionGeneralInformationSD3 *-- "1..1" SecurityIdentification15 : SecurityIdentification CorporateActionGeneralInformationSD3 *-- "0..1" IDateFormat22Choice : PaymentDate CorporateActionGeneralInformationSD3 *-- "0..0" CorporateActionUnallocatedDetailsSD1 : UnallocatedDetails %% SecurityIdentification15 recursion level 1 with max 1 class SecurityIdentification15{ ISIN IsoISINIdentifier Description IsoRestrictedFINXMax140Text } SecurityIdentification15 *-- "0..0" OtherIdentification2 : OtherIdentification %% IDateFormat22Choice recursion level 1 with max 1 %% CorporateActionUnallocatedDetailsSD1 recursion level 1 with max 1 class CorporateActionUnallocatedDetailsSD1{ SafekeepingAccount IsoRestrictedFINXMax35Text } CorporateActionUnallocatedDetailsSD1 *-- "0..1" ICorporateActionUnallocatedBalanceSD1Choice : UnallocatedBalance CorporateActionUnallocatedDetailsSD1 *-- "0..0" CorporateActionUnallocatedSecuritiesTransactionDetailsSD1 : UnallocatedSecuritiesTransactionDetails CorporateActionUnallocatedDetailsSD1 *-- "0..0" CorporateActionUnallocatedCashTransactionDetailsSD1 : UnallocatedCashTransactionDetails
CorporateActionGeneralInformationSD3 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
PlaceAndName | xPath to the element that is being extended. | IsoMax350Text - Required 1..1 |
SecurityIdentification | Identifies the financial instrument. | SecurityIdentification15 - Required 1..1 |
RecordDate | Date at which positions are stuck at the end of the day to note which parties will receive the relevant amount of entitlement, due to be distributed on payment date. DTC (The Depository Trust Corporation) and its Participants may use this as a reference. | IsoISODate - Optional 0..1 |
PaymentDate | Date/time at which the movement was due to take place (cash and/or securities). | IDateFormat22Choice - Optional 0..1 |
UnallocatedDetails | Additional information about the corporate action event. | CorporateActionUnallocatedDetailsSD1 - Unknown 0..0 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the DTCCCAPSSD1V01 implementation follows a specific implementaiton pattern. First of all, DTCCCAPSSD1V01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, DTCCCAPSSD1V01Document implements IOuterDocument. Because DTCCCAPSSD1V01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type DTCCCAPSSD1V01.
classDiagram class IOuterRecord DTCCCAPSSD1V01 --|> IOuterRecord : Implements DTCCCAPSSD1V01Document --|> IOuterDocument~DTCCCAPSSD1V01~ : Implements class IOuterDocument~DTCCCAPSSD1V01~ { DTCCCAPSSD1V01 Message }
Document wrapper for serialization
The only real purpose DTCCCAPSSD1V01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:supl.010.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using DTCCCAPSSD1V01.ToDocument() method. The returned DTCCCAPSSD1V01Document value will serialize correctly according to ISO 20022 standards.
classDiagram DTCCCAPSSD1V01Document *-- DTCCCAPSSD1V01 : 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:supl.010.001.01">
<DTCCCAPSSD1>
<CorpActnGnlInf>
<!-- CorporateActionGeneralInformation inner content -->
</CorpActnGnlInf>
</DTCCCAPSSD1>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_1NaWBDL3EeKU9IrkkToqcw_997459875"
nextVersions="_eaasX12lEeOb__BffbPEig"
name="DTCCCAPSSD1V01"
definition="The DTCCCAPSSD1 message extends ISO corporate action event processing status advice message with DTCC corporate action elements not covered in the standard message."
registrationStatus="Provisionally Registered"
xmlTag="DTCCCAPSSD1"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_1NaWBTL3EeKU9IrkkToqcw_-1234558780"
nextVersions="_eaasYV2lEeOb__BffbPEig"
name="CorporateActionGeneralInformation"
definition="Extension block for the information to be extended as corporate action general information."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="CorpActnGnlInf"
complexType="_1Yb6QDL3EeKU9IrkkToqcw_-1179649801">
<semanticMarkup
xmi:id="_e-yCMg5lEeO42pgjaJ50lw"
type="Synonym">
<elements
xmi:id="_e-yCMw5lEeO42pgjaJ50lw"
name="context"
value="DTCC" />
<elements
xmi:id="_e-yCNA5lEeO42pgjaJ50lw"
name="value"
value="Event (Details)" />
</semanticMarkup>
</messageBuildingBlock>
<messageDefinitionIdentifier
businessArea="supl"
messageFunctionality="010"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.