SecuritiesSettlementConditionsModificationRequestV01

sese.030.001.01

Scope An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information. The account owner/servicer relationship may be:

a central securities depository participant which has an account with a central securities depository. It could also be, if agreed in a service level agreement:
a global custodian which has an account with its local agent (sub-custodian), or
an investment management institution which manage a fund account opened at a custodian, or
a broker which has an account with a custodian, or
a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure. Usage The message may also be used to:
re-send a message previously sent (the sub-function of the message is Duplicate),
provide a third party with a copy of a message for information (the sub-function of the message is Copy),
re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate). This message cannot be used to request the modification of trade or event details. The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice. ISO 15022 - 20022 Coexistence This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”.

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
%% SecuritiesSettlementConditionsModificationRequestV01 recursion level 0 with max 0
SecuritiesSettlementConditionsModificationRequestV01 *-- "1..1" DocumentIdentification11 : Identification
SecuritiesSettlementConditionsModificationRequestV01 *-- "0..1" IPartyIdentification13Choice : AccountOwner
SecuritiesSettlementConditionsModificationRequestV01 *-- "1..1" SecuritiesAccount13 : SafekeepingAccount
SecuritiesSettlementConditionsModificationRequestV01 *-- "1..1" RequestDetails1 : RequestDetails
SecuritiesSettlementConditionsModificationRequestV01 *-- "0..1" AdditionalInformation3 : AdditionalInformation
SecuritiesSettlementConditionsModificationRequestV01 *-- "0..1" IPartyIdentification10Choice : MessageOriginator
SecuritiesSettlementConditionsModificationRequestV01 *-- "0..1" IPartyIdentification10Choice : MessageRecipient
SecuritiesSettlementConditionsModificationRequestV01 *-- "0..1" Extension2 : Extension

Now, we will zero-in one-by-one on each of these building blocks.

Identification building block

Information that unambiguously identifies a SettlementConditionModification transaction and a SecuritiesSettlementConditionsModificationRequest message as known by the account owner (or the instructing party acting on its behalf). Identification and creation date of a document. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% DocumentIdentification11 recursion level 0 with max 1
class DocumentIdentification11{
    Identification IsoMax35Text
    CopyDuplicate CopyDuplicate1Code
}
DocumentIdentification11 *-- "0..1" IDateAndDateTimeChoice : CreationDateTime
%% IDateAndDateTimeChoice recursion level 1 with max 1

DocumentIdentification11 members

Member name	Description	Data Type / Multiplicity
Identification	Unique identifier of the document (message) assigned by the sender of the document.	IsoMax35Text - Required 1..1
CreationDateTime	Date and time at which the document (message) was created by the sender.	IDateAndDateTimeChoice - Optional 0..1
CopyDuplicate	Specifies if this document is a copy, a duplicate, or a duplicate of a copy.	CopyDuplicate1Code - Optional 0..1

AccountOwner building block

Party that legally owns the account. Choice of identification of a party. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IPartyIdentification13Choice recursion level 0 with max 1

PartyIdentification13Choice members

Member name	Description	Data Type / Multiplicity

SafekeepingAccount building block

Account to or from which a securities entry is made. Account to or from which a securities entry is made. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SecuritiesAccount13 recursion level 0 with max 1
class SecuritiesAccount13{
    Identification IsoMax35Text
    Name IsoMax70Text
}
SecuritiesAccount13 *-- "0..1" GenericIdentification20 : Type
%% GenericIdentification20 recursion level 1 with max 1
class GenericIdentification20{
    Identification IsoExact4AlphaNumericText
    Issuer IsoMax35Text
    SchemeName IsoMax35Text
}

SecuritiesAccount13 members

Member name	Description	Data Type / Multiplicity
Identification	Unambiguous identification for the account between the account owner and the account servicer.”.	IsoMax35Text - Required 1..1
Type	Specifies the type of securities account.	GenericIdentification20 - Optional 0..1
Name	Description of the account.	IsoMax70Text - Optional 0..1

RequestDetails building block

Details of the request. Details of the settlement condition modification request. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% RequestDetails1 recursion level 0 with max 1
class RequestDetails1{
    RetainIndicator IsoYesNoIndicator
    PartialSettlementIndicator IsoYesNoIndicator
    HoldIndicator IsoYesNoIndicator
}
RequestDetails1 *-- "1..1" References1 : Reference
RequestDetails1 *-- "0..1" IAutomaticBorrowing2Choice : AutomaticBorrowing
RequestDetails1 *-- "0..1" ILinkageType1Choice : Linkage
RequestDetails1 *-- "0..1" IPriorityNumeric1Choice : Priority
RequestDetails1 *-- "0..0" GenericIdentification20 : OtherProcessing
RequestDetails1 *-- "0..1" ISecuritiesRTGS1Choice : SecuritiesRTGS
RequestDetails1 *-- "0..1" IMatchingDenied1Choice : MatchingDenial
RequestDetails1 *-- "0..1" IUnilateralSplit1Choice : UnilateralSplit
RequestDetails1 *-- "0..0" Linkages3 : Linkages
%% References1 recursion level 1 with max 1
class References1{
    AccountOwnerTransactionIdentification IsoMax35Text
    AccountServicerTransactionIdentification IsoMax35Text
    MarketInfrastructureTransactionIdentification IsoMax35Text
    PoolIdentification IsoMax35Text
    CommonIdentification IsoMax35Text
    TradeIdentification IsoMax35Text
}
%% IAutomaticBorrowing2Choice recursion level 1 with max 1
%% ILinkageType1Choice recursion level 1 with max 1
%% IPriorityNumeric1Choice recursion level 1 with max 1
%% GenericIdentification20 recursion level 1 with max 1
class GenericIdentification20{
    Identification IsoExact4AlphaNumericText
    Issuer IsoMax35Text
    SchemeName IsoMax35Text
}
%% ISecuritiesRTGS1Choice recursion level 1 with max 1
%% IMatchingDenied1Choice recursion level 1 with max 1
%% IUnilateralSplit1Choice recursion level 1 with max 1
%% Linkages3 recursion level 1 with max 1
Linkages3 *-- "0..1" IProcessingPosition2Choice : ProcessingPosition
Linkages3 *-- "0..1" IDocumentNumber1Choice : MessageNumber
Linkages3 *-- "1..1" IReferences6Choice : Reference

RequestDetails1 members

Member name	Description	Data Type / Multiplicity
Reference	References of the transaction for which the securities settlement condition modification is requested.	References1 - Required 1..1
AutomaticBorrowing	Condition for automatic borrowing.	IAutomaticBorrowing2Choice - Optional 0..1
RetainIndicator	Specifies whether the instruction due to expire is confirmed for settlement.	IsoYesNoIndicator - Optional 0..1
Linkage	Specifies the type of linkage requested.	ILinkageType1Choice - Optional 0..1
Priority	Specifies whether the transaction is to be executed with a high priority.	IPriorityNumeric1Choice - Optional 0..1
OtherProcessing	Specifies another type of processing change request.	GenericIdentification20 - Unknown 0..0
PartialSettlementIndicator	Specifies whether partial settlement is allowed.	IsoYesNoIndicator - Optional 0..1
SecuritiesRTGS	Specifies whether the settlement transaction is to be settled through an RTGS or a non RTGS system.	ISecuritiesRTGS1Choice - Optional 0..1
HoldIndicator	Specifies whether the transaction is on hold/blocked/frozen.	IsoYesNoIndicator - Optional 0..1
MatchingDenial	Specifies the matching processing change requested.	IMatchingDenied1Choice - Optional 0..1
UnilateralSplit	Specifies that the transaction is requested to be unilaterally split.	IUnilateralSplit1Choice - Optional 0..1
Linkages	Information regarding the linkage requested.	Linkages3 - Unknown 0..0

AdditionalInformation building block

Additional information that cannot be captured in the structured elements and/or any other specific block. Additional specific modification criteria. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% AdditionalInformation3 recursion level 0 with max 1
class AdditionalInformation3{
    AccountOwnerTransactionIdentification IsoMax35Text
}
AdditionalInformation3 *-- "0..1" IClassificationType1Choice : ClassificationType
AdditionalInformation3 *-- "0..1" SecuritiesAccount13 : SafekeepingAccount
AdditionalInformation3 *-- "0..1" SecurityIdentification11 : FinancialInstrumentIdentification
AdditionalInformation3 *-- "0..1" IFinancialInstrumentQuantity1Choice : Quantity
AdditionalInformation3 *-- "0..1" IDateAndDateTimeChoice : EffectiveDate
AdditionalInformation3 *-- "0..1" IDateAndDateTimeChoice : ExpiryDate
AdditionalInformation3 *-- "0..1" IDateAndDateTimeChoice : CutOffDate
AdditionalInformation3 *-- "0..1" IPartyIdentification10Choice : Investor
AdditionalInformation3 *-- "0..1" PartyIdentificationAndAccount16 : DeliveringParty1
AdditionalInformation3 *-- "0..1" PartyIdentificationAndAccount16 : ReceivingParty1
%% IClassificationType1Choice recursion level 1 with max 1
%% SecuritiesAccount13 recursion level 1 with max 1
class SecuritiesAccount13{
    Identification IsoMax35Text
    Name IsoMax70Text
}
SecuritiesAccount13 *-- "0..1" GenericIdentification20 : Type
%% SecurityIdentification11 recursion level 1 with max 1
class SecurityIdentification11{
    Description IsoMax140Text
}
SecurityIdentification11 *-- "1..1" ISecurityIdentification11Choice : Identification
%% IFinancialInstrumentQuantity1Choice recursion level 1 with max 1
%% IDateAndDateTimeChoice recursion level 1 with max 1
%% IDateAndDateTimeChoice recursion level 1 with max 1
%% IDateAndDateTimeChoice recursion level 1 with max 1
%% IPartyIdentification10Choice recursion level 1 with max 1
%% PartyIdentificationAndAccount16 recursion level 1 with max 1
class PartyIdentificationAndAccount16{
    ProcessingIdentification IsoMax35Text
}
PartyIdentificationAndAccount16 *-- "1..1" IPartyIdentification10Choice : Identification
PartyIdentificationAndAccount16 *-- "0..1" SecuritiesAccount13 : SafekeepingAccount
%% PartyIdentificationAndAccount16 recursion level 1 with max 1
class PartyIdentificationAndAccount16{
    ProcessingIdentification IsoMax35Text
}
PartyIdentificationAndAccount16 *-- "1..1" IPartyIdentification10Choice : Identification
PartyIdentificationAndAccount16 *-- "0..1" SecuritiesAccount13 : SafekeepingAccount

AdditionalInformation3 members

Member name	Description	Data Type / Multiplicity
AccountOwnerTransactionIdentification	Identification of the transaction as known by the account owner. Will be used in a unilateral split to provide the executing party with the account owner identification of each split transaction.	IsoMax35Text - Optional 0..1
ClassificationType	Type of instrument involved in the transactions on which the modification request should apply.	IClassificationType1Choice - Optional 0..1
SafekeepingAccount	Account to or from which a securities entry is made.	SecuritiesAccount13 - Optional 0..1
FinancialInstrumentIdentification	Identification of the financial instrument involved in the transactions on which the modification request should apply.	SecurityIdentification11 - Optional 0..1
Quantity	Quantity of financial instrument concerned by the settlement condition modification request.	IFinancialInstrumentQuantity1Choice - Optional 0..1
EffectiveDate	Date/time when the request should take effect.	IDateAndDateTimeChoice - Optional 0..1
ExpiryDate	Date/time when the request should cease to be in effect.	IDateAndDateTimeChoice - Optional 0..1
CutOffDate	Date/time of the release.	IDateAndDateTimeChoice - Optional 0..1
Investor	Party, either an individual or organisation, whose assets are being invested.	IPartyIdentification10Choice - Optional 0..1
DeliveringParty1	Party that, in a settlement chain interacts with the depository.	PartyIdentificationAndAccount16 - Optional 0..1
ReceivingParty1	Party that, in a settlement chain interacts with the depository.	PartyIdentificationAndAccount16 - Optional 0..1

MessageOriginator building block

Party that originated the message, if other than the sender. Choice of identification of a party. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IPartyIdentification10Choice recursion level 0 with max 1

PartyIdentification10Choice members

Member name	Description	Data Type / Multiplicity

MessageRecipient building block

Party that is the final destination of the message, if other than the receiver. Choice of identification of a party. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% IPartyIdentification10Choice recursion level 0 with max 1

PartyIdentification10Choice members

Member name	Description	Data Type / Multiplicity

Extension 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
%% Extension2 recursion level 0 with max 1
class Extension2{
    PlaceAndName IsoMax350Text
}
Extension2 *-- "1..1" ExtensionEnvelope1 : ExtensionEnvelope
%% ExtensionEnvelope1 recursion level 1 with max 1
ExtensionEnvelope1 *-- "1..1" ExtensionContents1 : ExtensionContents

Extension2 members

Member name	Description	Data Type / Multiplicity
PlaceAndName	Name qualifying the information provided in the Text field, and place where this information should be inserted.	IsoMax350Text - Optional 0..1
ExtensionEnvelope	Technical element wrapping the extension.	ExtensionEnvelope1 - Required 1..1

Extensibility and generalization considerations

To facilitate generalized design patterns in the system, the SecuritiesSettlementConditionsModificationRequestV01 implementation follows a specific implementaiton pattern. First of all, SecuritiesSettlementConditionsModificationRequestV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SecuritiesSettlementConditionsModificationRequestV01Document implements IOuterDocument. Because SecuritiesSettlementConditionsModificationRequestV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SecuritiesSettlementConditionsModificationRequestV01.

classDiagram
    class IOuterRecord
    SecuritiesSettlementConditionsModificationRequestV01 --|> IOuterRecord : Implements
    SecuritiesSettlementConditionsModificationRequestV01Document --|> IOuterDocument~SecuritiesSettlementConditionsModificationRequestV01~ : Implements
    class IOuterDocument~SecuritiesSettlementConditionsModificationRequestV01~ {
        SecuritiesSettlementConditionsModificationRequestV01 Message
     }

Document wrapper for serialization

The only real purpose SecuritiesSettlementConditionsModificationRequestV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:sese.030.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SecuritiesSettlementConditionsModificationRequestV01.ToDocument() method. The returned SecuritiesSettlementConditionsModificationRequestV01Document value will serialize correctly according to ISO 20022 standards.

classDiagram
    SecuritiesSettlementConditionsModificationRequestV01Document *-- SecuritiesSettlementConditionsModificationRequestV01 : 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:sese.030.001.01">
    <SctiesSttlmCondsModReq>
        <Id>
            <!-- Identification inner content -->
        </Id>
        <AcctOwnr>
            <!-- AccountOwner inner content -->
        </AcctOwnr>
        <SfkpgAcct>
            <!-- SafekeepingAccount inner content -->
        </SfkpgAcct>
        <ReqDtls>
            <!-- RequestDetails inner content -->
        </ReqDtls>
        <AddtlInf>
            <!-- AdditionalInformation inner content -->
        </AddtlInf>
        <MsgOrgtr>
            <!-- MessageOriginator inner content -->
        </MsgOrgtr>
        <MsgRcpt>
            <!-- MessageRecipient inner content -->
        </MsgRcpt>
        <Xtnsn>
            <!-- Extension inner content -->
        </Xtnsn>
    </SctiesSttlmCondsModReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_0LJH2NE5Ed-BzquC8wXy7w_2056028498"
  nextVersions="_YAYA8dtaEd-RF5yaMAVhAw"
  name="SecuritiesSettlementConditionsModificationRequestV01"
  definition="Scope&#xD;&#xA;An account owner sends a SecuritiesSettlementConditionsModificationRequest to an account servicer to request the modification of a processing indicator or another non-matching information.&#xD;&#xA;The account owner/servicer relationship may be:&#xD;&#xA;- a central securities depository participant which has an account with a central securities depository.&#xD;&#xA;It could also be, if agreed in a service level agreement:&#xD;&#xA;- a global custodian which has an account with its local agent (sub-custodian), or&#xD;&#xA;- an investment management institution which manage a fund account opened at a custodian, or&#xD;&#xA;- a broker which has an account with a custodian, or&#xD;&#xA;- a central securities depository which has an account with a custodian, another central securities depository or another settlement market infrastructure.&#xD;&#xA;Usage&#xD;&#xA;The message may also be used to:&#xD;&#xA;- re-send a message previously sent (the sub-function of the message is Duplicate),&#xD;&#xA;- provide a third party with a copy of a message for information (the sub-function of the message is Copy),&#xD;&#xA;- re-send to a third party a copy of a message for information (the sub-function of the message is Copy Duplicate).&#xD;&#xA;This message cannot be used to request the modification of trade or event details.&#xD;&#xA;The use of AdditionalInformation and its fields must be pre-agreed between account servicer and account owner. The fields in that sequence cannot be used to amend a trade or event detail unless authorised by country market practice.&#xA;ISO 15022 - 20022 Coexistence&#xA;This ISO 20022 message is reversed engineered from ISO 15022. Both standards will coexist for a certain number of years. Until this coexistence period ends, the usage of certain data types is restricted to ensure interoperability between ISO 15022 and 20022 users. Compliance to these rules is mandatory in a coexistence environment. The coexistence restrictions are described in a Textual Rule linked to the Message Items they concern. These coexistence textual rules are clearly identified as follows: “CoexistenceXxxxRule”."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="SctiesSttlmCondsModReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <semanticMarkup
    xmi:id="_dXX_lA5lEeO42pgjaJ50lw"
    type="Synonym">
    <elements
      xmi:id="_dXX_lQ5lEeO42pgjaJ50lw"
      name="context"
      value="ISO 15022" />
    <elements
      xmi:id="_dXX_lg5lEeO42pgjaJ50lw"
      name="value"
      value="MT 530" />
  </semanticMarkup>
  <constraint
    xmi:id="_0LS41tE5Ed-BzquC8wXy7w_1362773098"
    name="CoexistenceCharacterSetXRule"
    definition="During ISO 15022 – 20022 coexistence, characters used in all text fields must correspond to character set X, that is, a-z A-Z / - ? : ( ) . , ‘ + { } CR LF."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_0LcCwtE5Ed-BzquC8wXy7w_1455708976"
    name="CoexistenceIdentificationRule"
    definition="During ISO 15022 – 20022 coexistence, all transaction and document identifications or references must be 16 characters or less. The field must not start or end with a slash ‘/’ or contain two consecutive slashes ‘//’."
    registrationStatus="Provisionally Registered" />
  <constraint
    xmi:id="_0LcCxdE5Ed-BzquC8wXy7w_-679686854"
    name="SecuritiesMarketPracticeGroupGuideline"
    definition="The Securities Market Practice Group (SMPG) has published market practice recommendations on the use of this message.&#xD;&#xA;These market practices are available on www.smpg.info."
    registrationStatus="Provisionally Registered" />
  <messageBuildingBlock
    xmi:id="_0LJH2dE5Ed-BzquC8wXy7w_-726211265"
    name="Identification"
    definition="Information that unambiguously identifies a SettlementConditionModification transaction and a SecuritiesSettlementConditionsModificationRequest message as known by the account owner (or the instructing party acting on its behalf)."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Id"
    complexType="_RBcz8tp-Ed-ak6NoX_4Aeg_-746423515" />
  <messageBuildingBlock
    xmi:id="_0LJH2tE5Ed-BzquC8wXy7w_-440841879"
    name="AccountOwner"
    definition="Party that legally owns the account."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="AcctOwnr"
    complexType="_QQIEsNp-Ed-ak6NoX_4Aeg_-1062714307" />
  <messageBuildingBlock
    xmi:id="_0LS40NE5Ed-BzquC8wXy7w_-408519540"
    name="SafekeepingAccount"
    definition="Account to or from which a securities entry is made."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="SfkpgAcct"
    complexType="_T_vKAdp-Ed-ak6NoX_4Aeg_-178975462" />
  <messageBuildingBlock
    xmi:id="_0LS40dE5Ed-BzquC8wXy7w_1422822557"
    name="RequestDetails"
    definition="Details of the request."
    registrationStatus="Provisionally Registered"
    minOccurs="1"
    xmlTag="ReqDtls"
    complexType="_UhHYzNp-Ed-ak6NoX_4Aeg_-52038934" />
  <messageBuildingBlock
    xmi:id="_0LS40tE5Ed-BzquC8wXy7w_328303562"
    name="AdditionalInformation"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="AddtlInf"
    complexType="_TwGLjNp-Ed-ak6NoX_4Aeg_289518143" />
  <messageBuildingBlock
    xmi:id="_0LS409E5Ed-BzquC8wXy7w_-1791644676"
    name="MessageOriginator"
    definition="Party that originated the message, if other than the sender."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MsgOrgtr"
    complexType="_QQR1tdp-Ed-ak6NoX_4Aeg_-1244141483" />
  <messageBuildingBlock
    xmi:id="_0LS41NE5Ed-BzquC8wXy7w_-1690058569"
    name="MessageRecipient"
    definition="Party that is the final destination of the message, if other than the receiver."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MsgRcpt"
    complexType="_QQR1tdp-Ed-ak6NoX_4Aeg_-1244141483" />
  <messageBuildingBlock
    xmi:id="_0LS41dE5Ed-BzquC8wXy7w_541497815"
    name="Extension"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="Xtnsn"
    complexType="_QzJSNdp-Ed-ak6NoX_4Aeg_251191216" />
  <messageDefinitionIdentifier
    businessArea="sese"
    messageFunctionality="030"
    flavour="001"
    version="01" />
</messageDefinition>

ISO Building Blocks

The following items are used as building blocks to construct this message.