reda.006.001.01
SCOPE An instructing party sends a SecurityCreationRequest message to an executing/servicing party to request the creation of financial instrument static 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 securities coverage of the executing/servicing party. The instructing party needs this security to be set-up 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
%% SecurityCreationRequestV01 recursion level 0 with max 0
SecurityCreationRequestV01 *-- "0..1" MessageHeader1 : MessageHeader
SecurityCreationRequestV01 *-- "1..1" SecurityAttributes10 : Security
SecurityCreationRequestV01 *-- "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 |
Security building block
Represents the financial instruments details. Tangible items of value to a business. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SecurityAttributes10 recursion level 0 with max 1
SecurityAttributes10 *-- "1..1" SecurityIdentification39 : FinancialInstrumentIdentification
SecurityAttributes10 *-- "0..0" FinancialInstrument97 : FinancialInstrumentType
SecurityAttributes10 *-- "0..0" CommonFinancialInstrumentAttributes10 : FinancialInstrumentAttributes
%% SecurityIdentification39 recursion level 1 with max 1
class SecurityIdentification39{
ISIN IsoISIN2021Identifier
Description IsoMax140Text
}
SecurityIdentification39 *-- "0..0" OtherIdentification1 : OtherIdentification
%% FinancialInstrument97 recursion level 1 with max 1
FinancialInstrument97 *-- "0..1" Equity3 : Equity
FinancialInstrument97 *-- "0..1" Warrant4 : Warrant
FinancialInstrument97 *-- "0..1" Debt5 : Debt
FinancialInstrument97 *-- "0..1" Derivative4 : Derivative
%% CommonFinancialInstrumentAttributes10 recursion level 1 with max 1
class CommonFinancialInstrumentAttributes10{
ISOSecurityLongName IsoMax350Text
ISOSecurityShortName IsoMax35Text
DenominationCurrency ActiveOrHistoricCurrencyCode
CertificateNumber IsoMax35Text
ContractVersionNumber IsoNumber
CouponAttachedNumber IsoMax3NumericText
TaxLotNumber IsoMax15NumericText
PoolNumber IsoMax15NumericText
CoveredIndicator IsoYesNoIndicator
ListingDate IsoISODate
RecordDate IsoISODateTime
ExpiryDate IsoISODate
Purpose IsoMax256Text
FungibleIndicator IsoYesNoIndicator
Confidential IsoYesNoIndicator
PrivatePlacement IsoYesNoIndicator
ConvertibleIndicator IsoYesNoIndicator
SerieNumber IsoMax16Text
Class IsoMax16Text
CommonSafekeeper IsoAnyBICDec2014Identifier
RedemptionPaymentCurrency ActiveCurrencyCode
}
CommonFinancialInstrumentAttributes10 *-- "0..1" ISecurityStatus3Choice : SecurityStatus
CommonFinancialInstrumentAttributes10 *-- "0..1" IDateAndDateTime2Choice : NameValidFrom
CommonFinancialInstrumentAttributes10 *-- "0..1" ILegalRestrictions4Choice : LegalRestrictions
CommonFinancialInstrumentAttributes10 *-- "0..1" IFinancialInstrumentQuantity1Choice : PositionLimit
CommonFinancialInstrumentAttributes10 *-- "0..1" IFinancialInstrumentQuantity1Choice : NearTermPositionLimit
CommonFinancialInstrumentAttributes10 *-- "0..1" ClassificationType2 : ClassificationType
CommonFinancialInstrumentAttributes10 *-- "0..1" Issuance5 : Issuance
CommonFinancialInstrumentAttributes10 *-- "0..0" TradingParameters2 : TradingMarket
CommonFinancialInstrumentAttributes10 *-- "0..0" BenchmarkCurve6 : SpreadAndBenchmarkCurve
CommonFinancialInstrumentAttributes10 *-- "0..1" IPutType3Choice : PutType
CommonFinancialInstrumentAttributes10 *-- "0..1" ICallType3Choice : CallType
CommonFinancialInstrumentAttributes10 *-- "0..1" DateTimePeriod1 : ConversionPeriod
CommonFinancialInstrumentAttributes10 *-- "0..1" IFinancialInstrumentQuantity1Choice : ConversionRatioNumerator
CommonFinancialInstrumentAttributes10 *-- "0..1" IFinancialInstrumentQuantity1Choice : ConversionRatioDenominator
CommonFinancialInstrumentAttributes10 *-- "0..1" PartyIdentification136 : PrimaryPlaceOfDeposit
CommonFinancialInstrumentAttributes10 *-- "0..1" IUnitOrFaceAmount1Choice : TradingMethod
CommonFinancialInstrumentAttributes10 *-- "0..1" ITEFRARules3Choice : TEFRARule
CommonFinancialInstrumentAttributes10 *-- "0..0" SecurityWithHoldingTax1 : WithholdingTaxRegime
CommonFinancialInstrumentAttributes10 *-- "0..1" ISecuritiesPaymentStatus5Choice : PaymentStatus
CommonFinancialInstrumentAttributes10 *-- "0..1" IInitialPhysicalForm4Choice : InitialPhysicalForm
CommonFinancialInstrumentAttributes10 *-- "0..1" IInitialPhysicalForm3Choice : AfterExchangePhysicalForm
CommonFinancialInstrumentAttributes10 *-- "0..1" IMaturityRedemptionType3Choice : RedemptionType
CommonFinancialInstrumentAttributes10 *-- "0..0" SecurityRestriction3 : Restriction
CommonFinancialInstrumentAttributes10 *-- "0..0" SettlementInformation17 : SettlementInformation
CommonFinancialInstrumentAttributes10 *-- "0..1" FinancialInstrumentForm2 : FinancialInstrumentForm
CommonFinancialInstrumentAttributes10 *-- "0..1" Organisation38 : ContactName
CommonFinancialInstrumentAttributes10 *-- "0..1" Organisation38 : LeadManager
CommonFinancialInstrumentAttributes10 *-- "0..1" Organisation38 : PrincipalPayingAgent
CommonFinancialInstrumentAttributes10 *-- "0..1" Organisation38 : PayingAgent
CommonFinancialInstrumentAttributes10 *-- "0..1" Organisation38 : Depository
CommonFinancialInstrumentAttributes10 *-- "0..1" Organisation38 : UnderlyingRisk
SecurityAttributes10 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| FinancialInstrumentIdentification | Identification of a security. | SecurityIdentification39 - Required 1..1 |
| FinancialInstrumentType | Provides additional details about the financial instrument. | FinancialInstrument97 - Unknown 0..0 |
| FinancialInstrumentAttributes | Financial instruments representing a sum of rights of the investor vis-a-vis the issuer. | CommonFinancialInstrumentAttributes10 - Unknown 0..0 |
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 SecurityCreationRequestV01 implementation follows a specific implementaiton pattern. First of all, SecurityCreationRequestV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecurityCreationRequestV01Document implements IOuterDocument. Because SecurityCreationRequestV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecurityCreationRequestV01.
classDiagram
class IOuterRecord
SecurityCreationRequestV01 --|> IOuterRecord : Implements
SecurityCreationRequestV01Document --|> IOuterDocument~SecurityCreationRequestV01~ : Implements
class IOuterDocument~SecurityCreationRequestV01~ {
SecurityCreationRequestV01 Message
}
Document wrapper for serialization
The only real purpose SecurityCreationRequestV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:reda.006.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecurityCreationRequestV01.ToDocument() method. The returned SecurityCreationRequestV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
SecurityCreationRequestV01Document *-- SecurityCreationRequestV01 : 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.006.001.01">
<SctyCreReq>
<MsgHdr>
<!-- MessageHeader inner content -->
</MsgHdr>
<Scty>
<!-- Security inner content -->
</Scty>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</SctyCreReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_jTt_oR62Eeu31YsWNiv_cw"
name="SecurityCreationRequestV01"
definition="SCOPE
An instructing party sends a SecurityCreationRequest message to an executing/servicing party to request the creation of financial instrument static 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 securities coverage of the executing/servicing party. The instructing party needs this security to be set-up at the executing /servicing party to perform its activities.

Initiator: instructing party."
registrationStatus="Registered"
messageSet="_XwWqJB62Eeu31YsWNiv_cw"
xmlTag="SctyCreReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_C0kGQZIxEeuAlLVx8pyt3w"
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="_jTt_rx62Eeu31YsWNiv_cw"
name="Security"
definition="Represents the financial instruments details."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Scty"
complexType="_PxlM8ZJKEeuAlLVx8pyt3w" />
<messageBuildingBlock
xmi:id="_jTt_tR62Eeu31YsWNiv_cw"
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="006"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.