reda.007.001.01
SCOPE An instructing party sends a SecurityMaintenanceRequest message to an executing/servicing party to request the maintenance of financial instrument details in their system.
The instructing party - executing/servicing party relationship may be:
- Central Securities Depositories (CSD) who would like to publish security static data, or
- a Corporate, or
- a Bank, or
- a Market Infrastructure, or
- a Market Data Provider.
USAGE The request is sent when the instructing party identified a gap in the security data within the executing/servicing party system. The instructing party needs this security to be updated at the executing /servicing party to perform its activities.
Initiator: instructing party.
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
%% SecurityMaintenanceRequestV01 recursion level 0 with max 0
SecurityMaintenanceRequestV01 *-- "0..1" MessageHeader1 : MessageHeader
SecurityMaintenanceRequestV01 *-- "1..1" IUpdateType36Choice : UpdateType
SecurityMaintenanceRequestV01 *-- "0..1" ISecuritiesUpdateReason1Choice : UpdateReason
SecurityMaintenanceRequestV01 *-- "1..1" SecurityIdentification39 : FinancialInstrumentIdentification
SecurityMaintenanceRequestV01 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
MessageHeader building block
Common business identification for the message. Set of characteristics, such as the identification or the creation date and time, specific to the message. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MessageHeader1 recursion level 0 with max 1
class MessageHeader1{
MessageIdentification IsoMax35Text
CreationDateTime IsoISODateTime
}
MessageHeader1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MessageIdentification | Point to point reference, as assigned by the sender, to unambiguously identify the message. Usage: The sender has to make sure that MessageIdentification is unique for a pre-agreed period. | IsoMax35Text - Required 1..1 |
| CreationDateTime | Date and time at which the message was created. | IsoISODateTime - Optional 0..1 |
UpdateType building block
Request to maintain data’s of a security. Choice between action to request on a security. For comparison, see the ISO20022 official specification
classDiagram direction tb %% IUpdateType36Choice recursion level 0 with max 1
UpdateType36Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
UpdateReason building block
Reason for the update of a security. Specifies the reason for the update of securities. For comparison, see the ISO20022 official specification
classDiagram direction tb %% ISecuritiesUpdateReason1Choice recursion level 0 with max 1
SecuritiesUpdateReason1Choice members
| Member name | Description | Data Type / Multiplicity |
|---|
FinancialInstrumentIdentification building block
Identification of the financial instrument. Identification of a security. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SecurityIdentification39 recursion level 0 with max 1
class SecurityIdentification39{
ISIN IsoISIN2021Identifier
Description IsoMax140Text
}
SecurityIdentification39 *-- "0..0" OtherIdentification1 : OtherIdentification
%% OtherIdentification1 recursion level 1 with max 1
class OtherIdentification1{
Identification IsoMax35Text
Suffix IsoMax16Text
}
OtherIdentification1 *-- "1..1" IIdentificationSource3Choice : Type
SecurityIdentification39 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| ISIN | International Securities Identification Number (ISIN). A numbering system designed by the United Nation’s International Organisation for Standardisation (ISO). The ISIN is composed of a 2-character prefix representing the country of issue, followed by the national security number (if one exists), and a check digit. Each country has a national numbering agency that assigns ISIN numbers for securities in that country. | IsoISIN2021Identifier - Optional 0..1 |
| OtherIdentification | Identification of a security by proprietary or domestic identification scheme. | OtherIdentification1 - Unknown 0..0 |
| Description | Textual description of a security instrument. | IsoMax140Text - Optional 0..1 |
SupplementaryData building block
Additional information that cannot be captured in the structured elements 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 SecurityMaintenanceRequestV01 implementation follows a specific implementaiton pattern. First of all, SecurityMaintenanceRequestV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecurityMaintenanceRequestV01Document implements IOuterDocument. Because SecurityMaintenanceRequestV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecurityMaintenanceRequestV01.
classDiagram
class IOuterRecord
SecurityMaintenanceRequestV01 --|> IOuterRecord : Implements
SecurityMaintenanceRequestV01Document --|> IOuterDocument~SecurityMaintenanceRequestV01~ : Implements
class IOuterDocument~SecurityMaintenanceRequestV01~ {
SecurityMaintenanceRequestV01 Message
}
Document wrapper for serialization
The only real purpose SecurityMaintenanceRequestV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:reda.007.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecurityMaintenanceRequestV01.ToDocument() method. The returned SecurityMaintenanceRequestV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
SecurityMaintenanceRequestV01Document *-- SecurityMaintenanceRequestV01 : 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:reda.007.001.01">
<SctyMntncReq>
<MsgHdr>
<!-- MessageHeader inner content -->
</MsgHdr>
<UpdTp>
<!-- UpdateType inner content -->
</UpdTp>
<UpdRsn>
<!-- UpdateReason inner content -->
</UpdRsn>
<FinInstrmId>
<!-- FinancialInstrumentIdentification inner content -->
</FinInstrmId>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</SctyMntncReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_jTvNwR62Eeu31YsWNiv_cw"
name="SecurityMaintenanceRequestV01"
definition="SCOPE
An instructing party sends a SecurityMaintenanceRequest message to an executing/servicing party to request the maintenance of financial instrument details in their system.

The instructing party - executing/servicing party relationship may be:
- Central Securities Depositories (CSD) who would like to publish security static data, or 
- a Corporate, or
- a Bank, or
- a Market Infrastructure, or 
- a Market Data Provider.

USAGE
The request is sent when the instructing party identified a gap in the security data within the executing/servicing party system. The instructing party needs this security to be updated at the executing /servicing party to perform its activities.

Initiator: instructing party."
registrationStatus="Registered"
messageSet="_XwWqJB62Eeu31YsWNiv_cw"
xmlTag="SctyMntncReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_Qqn3IZIxEeuAlLVx8pyt3w"
name="MessageHeader"
definition="Common business identification for the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="MsgHdr"
complexType="_75DzkaMgEeCJ6YNENx4h-w_-613853819" />
<messageBuildingBlock
xmi:id="_jTvNzx62Eeu31YsWNiv_cw"
name="UpdateType"
definition="Request to maintain data's of a security."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="UpdTp"
complexType="_QGUHDZJKEeuAlLVx8pyt3w" />
<messageBuildingBlock
xmi:id="_nwYQwZI8EeuAlLVx8pyt3w"
name="UpdateReason"
definition="Reason for the update of a security."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="UpdRsn"
complexType="_20ciUJI7EeuAlLVx8pyt3w" />
<messageBuildingBlock
xmi:id="_jTvN0R62Eeu31YsWNiv_cw"
name="FinancialInstrumentIdentification"
definition="Identification of the financial instrument."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="FinInstrmId"
complexType="_Pvjzt5JKEeuAlLVx8pyt3w" />
<messageBuildingBlock
xmi:id="_wEnt8ZIzEeuAlLVx8pyt3w"
name="SupplementaryData"
definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="SplmtryData"
complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
<messageDefinitionIdentifier
businessArea="reda"
messageFunctionality="007"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.