setr.013.001.04
Scope The SwitchOrder message is sent by an instructing party, for example, an investment manager or its authorised representative, to the executing party, for example, a transfer agent, to instruct a switch transaction from a financial instrument or multiple financial instruments to a different specified financial instrument or instruments for a specified amount/quantity. Usage The SwitchOrder message is used to either:
- instruct one switch transaction comprising one or more redemption legs and one or more subscription legs, that is, a single switch transaction that can be a one to one, many to one, many to many or one to many switch transaction, or,
- instruct one or many switch transactions each comprising one redemption leg and one subscription leg, that is, multiple simple switch transactions. The SwitchOrder message may be used to either:
- instruct a switch transaction for one investment account, or,
- instruct a switch transaction for separate accounts at the redemption and subscription leg levels. The message caters for a switch from one financial instrument to another financial instrument (within the same fund family), many to one, many to many and one to many. The message caters for switch transactions that result in an additional cash payment from the investor or a transaction that results in a net payment to the investor. Not all institutions or funds permit this type of switch and acceptance is therefore not automatic. There is no limitation on the number of switch legs in a switch message. The number allowed is defined by the fund prospectus or by the service level agreement (SLA) in place between the two parties. However, if the SwitchOrderDetails sequence is present more than once, then the RedemptionLegDetails and SubscriptionLegDetails sequences may only be present once. If SwitchOrderDetails\InvestmentAccount is used, then the InvestmentAccountDetails sequences in SubscriptionLegDetails and RedemptionLegDetails are not allowed. This functionality is to be used by institutions that set up two accounts per investor, rather than one investment account. There is no switch driver type in the message to indicate whether the switch is buy or sell driven. A driver is not needed since it is possible to indicate the total subscription amount or the total redemption amount. Only one of these two amounts should be used. The subscription quantity can be expressed in one of the following ways:
- Amount: the monetary value (either GROSS or NET) of the financial instrument to be subscribed to, for example, the subscription of EUR 1,000 of financial instrument ISIN LU1234567890 or
- Unit: the number of units of the financial instrument to be subscribed to, for example, the subscription of 10 units of financial instrument ISIN LU1234567890 or
- Percentage of the total redemption amount: when the switch transaction is redemption driven, it is the part of the redemption amount that must be switched to a specific financial instrument, for example, the subscription quantity of financial instrument ISIN LU1234567890 represents 50% of the redemption amount of the financial instrument ISIN LU4444444444. The redemption quantity can be expressed in one of the following ways:
- Amount: the monetary value (either GROSS or NET) of the financial instrument to be redeemed, for example, the redemption of EUR 1,000 of financial instrument ISIN LU1234567890, or
- Unit: the number of units of financial instrument to be redeemed, for example, the redemption of 10 units of financial instrument ISIN LU1234567890, or
- Rate: the part of the portfolio to be redeemed, for example, the redemption of 10% of the holdings in financial instrument ISIN LU1234567890, or
- Percentage of the total subscription amount: when the switch transaction is subscription driven, it is the part of the subscription amount that must be the result of the redemption of a specific financial instrument, for example, the redemption quantity in financial instrument ABC represents 50% of the subscription amount of the financial instrument ISIN LU4444444444.
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 %% SwitchOrderV04 recursion level 0 with max 0 SwitchOrderV04 *-- "1..1" MessageIdentification1 : MessageIdentification SwitchOrderV04 *-- "0..1" AdditionalReference9 : PoolReference SwitchOrderV04 *-- "0..1" AdditionalReference8 : PreviousReference SwitchOrderV04 *-- "0..1" Pagination : MessagePagination SwitchOrderV04 *-- "1..1" SwitchOrder7 : SwitchOrderDetails SwitchOrderV04 *-- "0..1" CopyInformation4 : CopyDetails SwitchOrderV04 *-- "0..1" Extension1 : Extension
Now, we will zero-in one-by-one on each of these building blocks.
MessageIdentification building block
Reference that uniquely identifies the message from a business application standpoint. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification
classDiagram direction tb %% MessageIdentification1 recursion level 0 with max 1 class MessageIdentification1{ Identification IsoMax35Text CreationDateTime IsoISODateTime }
MessageIdentification1 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Identification of the message. | IsoMax35Text - Required 1..1 |
CreationDateTime | Date of creation of the message. | IsoISODateTime - Required 1..1 |
PoolReference building block
Collective reference identifying a set of messages. References a related message or provides another reference, such as a pool reference, linking a set of messages. The party which issued the related reference may be the Sender of the referenced message or a party other than the Sender. For comparison, see the ISO20022 official specification
classDiagram direction tb %% AdditionalReference9 recursion level 0 with max 1 class AdditionalReference9{ Reference IsoMax35Text MessageName IsoMax35Text } AdditionalReference9 *-- "0..1" PartyIdentification113 : ReferenceIssuer %% PartyIdentification113 recursion level 1 with max 1 class PartyIdentification113{ LEI IsoLEIIdentifier } PartyIdentification113 *-- "1..1" IPartyIdentification90Choice : Party
AdditionalReference9 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Reference | Reference identifying a set of messages. | IsoMax35Text - Required 1..1 |
ReferenceIssuer | Issuer of the reference. | PartyIdentification113 - Optional 0..1 |
MessageName | Name of the message. | IsoMax35Text - Optional 0..1 |
PreviousReference building block
Reference to a linked message that was previously sent. References a related message or provides another reference, such as a pool reference, linking a set of messages. The party which issued the related reference may be the Sender of the referenced message or a party other than the Sender. For comparison, see the ISO20022 official specification
classDiagram direction tb %% AdditionalReference8 recursion level 0 with max 1 class AdditionalReference8{ Reference IsoMax35Text MessageName IsoMax35Text } AdditionalReference8 *-- "0..1" PartyIdentification113 : ReferenceIssuer %% PartyIdentification113 recursion level 1 with max 1 class PartyIdentification113{ LEI IsoLEIIdentifier } PartyIdentification113 *-- "1..1" IPartyIdentification90Choice : Party
AdditionalReference8 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Reference | Reference issued by a party to identify an instruction, transaction or a message. | IsoMax35Text - Required 1..1 |
ReferenceIssuer | Issuer of the reference. | PartyIdentification113 - Optional 0..1 |
MessageName | Name of the message. | IsoMax35Text - Optional 0..1 |
MessagePagination building block
Pagination of the message. Number used to sequence pages when it is not possible for data to be conveyed in a single message and the data has to be split across several pages (messages). For comparison, see the ISO20022 official specification
classDiagram direction tb %% Pagination recursion level 0 with max 1 class Pagination{ PageNumber IsoMax5NumericText LastPageIndicator IsoYesNoIndicator }
Pagination members
Member name | Description | Data Type / Multiplicity |
---|---|---|
PageNumber | Page number. | IsoMax5NumericText - Required 1..1 |
LastPageIndicator | Indicates the last page. | IsoYesNoIndicator - Required 1..1 |
SwitchOrderDetails building block
Information related to the switch order. Transfer from one investment fund/fund class to another investment fund or investment fund class by the investor. A switch is composed of one or several subscription legs, and one or several redemption legs. For comparison, see the ISO20022 official specification
classDiagram direction tb %% SwitchOrder7 recursion level 0 with max 1 class SwitchOrder7{ MasterReference IsoMax35Text OrderDateTime IsoISODateTime OrderReference IsoMax35Text ClientReference IsoMax35Text RequestedFutureTradeDate IsoISODate SettlementAmount IsoActiveCurrencyAndAmount CashSettlementDate IsoISODate SettlementMethod DeliveryReceiptType2Code FinancialAdvice FinancialAdvice1Code NegotiatedTrade NegotiatedTrade1Code } SwitchOrder7 *-- "0..1" IPlaceOfTradeIdentification1Choice : PlaceOfTrade SwitchOrder7 *-- "0..1" InvestmentAccount58 : InvestmentAccountDetails SwitchOrder7 *-- "0..10" Intermediary40 : RelatedPartyDetails SwitchOrder7 *-- "0..1" IAdditionalAmount1Choice : AdditionalAmount SwitchOrder7 *-- "0..1" IDateAndDateTimeChoice : ExpiryDateTime SwitchOrder7 *-- "0..1" ICancellationRight1Choice : CancellationRight SwitchOrder7 *-- "1..0" SwitchRedemptionLegOrder6 : RedemptionLegDetails SwitchOrder7 *-- "1..0" SwitchSubscriptionLegOrder6 : SubscriptionLegDetails SwitchOrder7 *-- "0..1" PaymentTransaction71 : CashSettlementDetails SwitchOrder7 *-- "0..1" ForeignExchangeTerms32 : ForeignExchangeDetails SwitchOrder7 *-- "0..1" ICustomerConductClassification1Choice : CustomerConductClassification SwitchOrder7 *-- "0..1" ITransactionChannelType1Choice : TransactionChannelType SwitchOrder7 *-- "0..1" ISignatureType1Choice : SignatureType SwitchOrder7 *-- "0..1" OrderWaiver1 : OrderWaiverDetails %% IPlaceOfTradeIdentification1Choice recursion level 1 with max 1 %% InvestmentAccount58 recursion level 1 with max 1 class InvestmentAccount58{ AccountIdentification IsoMax35Text AccountName IsoMax35Text AccountDesignation IsoMax35Text OrderOriginatorEligibility OrderOriginatorEligibility1Code } InvestmentAccount58 *-- "0..0" PartyIdentification113 : OwnerIdentification InvestmentAccount58 *-- "0..1" PartyIdentification113 : AccountServicer InvestmentAccount58 *-- "0..1" SubAccount6 : SubAccountDetails %% Intermediary40 recursion level 1 with max 1 class Intermediary40{ OrderOriginatorEligibility OrderOriginatorEligibility1Code } Intermediary40 *-- "1..1" PartyIdentification113 : Identification Intermediary40 *-- "0..1" Account22 : Account Intermediary40 *-- "0..1" IInvestmentFundRole2Choice : Role %% IAdditionalAmount1Choice recursion level 1 with max 1 %% IDateAndDateTimeChoice recursion level 1 with max 1 %% ICancellationRight1Choice recursion level 1 with max 1 %% SwitchRedemptionLegOrder6 recursion level 1 with max 1 class SwitchRedemptionLegOrder6{ LegIdentification IsoMax35Text IncomePreference IncomePreference1Code Group1Or2Units UKTaxGroupUnit1Code RequestedSettlementCurrency ActiveCurrencyCode RequestedNAVCurrency ActiveOrHistoricCurrencyCode PhysicalDeliveryIndicator IsoYesNoIndicator NonStandardSettlementInformation IsoMax350Text } SwitchRedemptionLegOrder6 *-- "1..1" FinancialInstrument57 : FinancialInstrumentDetails SwitchRedemptionLegOrder6 *-- "0..1" IFinancialInstrumentQuantity29Choice : FinancialInstrumentQuantityChoice SwitchRedemptionLegOrder6 *-- "0..1" InvestmentAccount58 : InvestmentAccountDetails SwitchRedemptionLegOrder6 *-- "0..1" FeeAndTax1 : TransactionOverhead SwitchRedemptionLegOrder6 *-- "0..1" FundSettlementParameters12 : SettlementAndCustodyDetails SwitchRedemptionLegOrder6 *-- "0..1" DeliveryParameters3 : PhysicalDeliveryDetails SwitchRedemptionLegOrder6 *-- "0..1" Equalisation1 : Equalisation %% SwitchSubscriptionLegOrder6 recursion level 1 with max 1 class SwitchSubscriptionLegOrder6{ LegIdentification IsoMax35Text IncomePreference IncomePreference1Code RequestedSettlementCurrency ActiveCurrencyCode RequestedNAVCurrency ActiveOrHistoricCurrencyCode PhysicalDeliveryIndicator IsoYesNoIndicator NonStandardSettlementInformation IsoMax350Text } SwitchSubscriptionLegOrder6 *-- "1..1" FinancialInstrument57 : FinancialInstrumentDetails SwitchSubscriptionLegOrder6 *-- "0..1" IFinancialInstrumentQuantity26Choice : FinancialInstrumentQuantityChoice SwitchSubscriptionLegOrder6 *-- "0..1" InvestmentAccount58 : InvestmentAccountDetails SwitchSubscriptionLegOrder6 *-- "0..1" FeeAndTax1 : TransactionOverhead SwitchSubscriptionLegOrder6 *-- "0..1" FundSettlementParameters11 : SettlementAndCustodyDetails SwitchSubscriptionLegOrder6 *-- "0..1" NameAndAddress4 : PhysicalDeliveryDetails SwitchSubscriptionLegOrder6 *-- "0..1" Equalisation1 : Equalisation %% PaymentTransaction71 recursion level 1 with max 1 PaymentTransaction71 *-- "1..1" ICashInOrOut7Choice : CashInOrOut %% ForeignExchangeTerms32 recursion level 1 with max 1 class ForeignExchangeTerms32{ UnitCurrency ActiveCurrencyCode QuotedCurrency ActiveCurrencyCode ExchangeRate IsoBaseOneRate QuotationDate IsoISODateTime } ForeignExchangeTerms32 *-- "0..1" PartyIdentification113 : QuotingInstitution %% ICustomerConductClassification1Choice recursion level 1 with max 1 %% ITransactionChannelType1Choice recursion level 1 with max 1 %% ISignatureType1Choice recursion level 1 with max 1 %% OrderWaiver1 recursion level 1 with max 1 class OrderWaiver1{ InformationValue IsoMax350Text } OrderWaiver1 *-- "0..0" IOrderWaiverReason3Choice : OrderWaiverReason
SwitchOrder7 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
MasterReference | Unique and unambiguous identifier for a group of individual orders, as assigned by the instructing party. This identifier links the individual orders together. | IsoMax35Text - Optional 0..1 |
OrderDateTime | Date and time the order is placed by the investor or its agent. | IsoISODateTime - Optional 0..1 |
PlaceOfTrade | Market in which the advised trade transaction was executed. | IPlaceOfTradeIdentification1Choice - Optional 0..1 |
OrderReference | Unique and unambiguous identifier for the order, as assigned by the instructing party. | IsoMax35Text - Required 1..1 |
ClientReference | Unique and unambiguous investor’s identification of the order. This reference can typically be used in a hub scenario to give the reference of the order as assigned by the underlying client. | IsoMax35Text - Optional 0..1 |
InvestmentAccountDetails | Account impacted by the investment fund order. | InvestmentAccount58 - Optional 0..1 |
RelatedPartyDetails | Party related to the transaction. | Intermediary40 - Collection 0..10 |
RequestedFutureTradeDate | Future date at which the investor requests the order to be executed. | The specification of a requested future trade date is not allowed in some markets. The date must be a date in the future. |
SettlementAmount | Total amount of money paid /to be paid or received in exchange for the financial instrument in the individual order. | IsoActiveCurrencyAndAmount - Optional 0..1 |
CashSettlementDate | Date on which cash is available. | IsoISODate - Optional 0..1 |
SettlementMethod | Method by which the transaction is settled. | DeliveryReceiptType2Code - Optional 0..1 |
AdditionalAmount | Choice between additional cash in or resulting cash out. | IAdditionalAmount1Choice - Optional 0..1 |
ExpiryDateTime | Date on which the order expires. | IDateAndDateTimeChoice - Optional 0..1 |
CancellationRight | Cancellation right of the investor with respect to the investment fund order. | ICancellationRight1Choice - Optional 0..1 |
RedemptionLegDetails | Part of the investment fund switch order that is a redemption. | SwitchRedemptionLegOrder6 - Unknown 1..0 |
SubscriptionLegDetails | Part of the investment fund switch order that is a subscription. | SwitchSubscriptionLegOrder6 - Unknown 1..0 |
CashSettlementDetails | Payment process for the transfer of cash from the debtor to the creditor. | PaymentTransaction71 - Optional 0..1 |
ForeignExchangeDetails | Information needed to process a currency exchange or conversion. Information needed to process a currency exchange or conversion. How the exchange rate is expressed determines which currency is the Unit Currency and Quoted Currency. If the amounts concerned are EUR 1000 and USD 1300, the exchange rate may be expressed as per either of the following examples: EXAMPLE 1 UnitCurrency EUR QuotedCurrency USD ExchangeRate 1.300 EXAMPLE 2 UnitCurrency USD QuotedCurrency EUR ExchangeRate 0.769. | ForeignExchangeTerms32 - Optional 0..1 |
FinancialAdvice | Specifies if advice has been received from an independent financial advisor. | FinancialAdvice1Code - Optional 0..1 |
NegotiatedTrade | Specifies whether the trade is negotiated. | NegotiatedTrade1Code - Optional 0..1 |
CustomerConductClassification | Assessment of the customer’s behaviour at the time of the account opening application. | ICustomerConductClassification1Choice - Optional 0..1 |
TransactionChannelType | Means by which the investor or account owner submits the open account form. | ITransactionChannelType1Choice - Optional 0..1 |
SignatureType | Type of signature. | ISignatureType1Choice - Optional 0..1 |
OrderWaiverDetails | Information about a non-standard order. | OrderWaiver1 - Optional 0..1 |
CopyDetails building block
Information provided when the message is a copy of a previous message. Information provided when the message is a copy of a previous message. For comparison, see the ISO20022 official specification
classDiagram direction tb %% CopyInformation4 recursion level 0 with max 1 class CopyInformation4{ CopyIndicator IsoYesNoIndicator OriginalReceiver IsoAnyBICIdentifier }
CopyInformation4 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
CopyIndicator | Indicates whether the message is a copy. | IsoYesNoIndicator - Required 1..1 |
OriginalReceiver | Original receiver of the message, if this message is a copy. | IsoAnyBICIdentifier - Optional 0..1 |
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 %% Extension1 recursion level 0 with max 1 class Extension1{ PlaceAndName IsoMax350Text Text IsoMax350Text }
Extension1 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 - Required 1..1 |
Text | Text of the extension. | IsoMax350Text - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the SwitchOrderV04 implementation follows a specific implementaiton pattern. First of all, SwitchOrderV04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SwitchOrderV04Document implements IOuterDocument. Because SwitchOrderV04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SwitchOrderV04.
classDiagram class IOuterRecord SwitchOrderV04 --|> IOuterRecord : Implements SwitchOrderV04Document --|> IOuterDocument~SwitchOrderV04~ : Implements class IOuterDocument~SwitchOrderV04~ { SwitchOrderV04 Message }
Document wrapper for serialization
The only real purpose SwitchOrderV04Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:setr.013.001.04’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SwitchOrderV04.ToDocument() method. The returned SwitchOrderV04Document value will serialize correctly according to ISO 20022 standards.
classDiagram SwitchOrderV04Document *-- SwitchOrderV04 : 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:setr.013.001.04">
<SwtchOrdr>
<MsgId>
<!-- MessageIdentification inner content -->
</MsgId>
<PoolRef>
<!-- PoolReference inner content -->
</PoolRef>
<PrvsRef>
<!-- PreviousReference inner content -->
</PrvsRef>
<MsgPgntn>
<!-- MessagePagination inner content -->
</MsgPgntn>
<SwtchOrdrDtls>
<!-- SwitchOrderDetails inner content -->
</SwtchOrdrDtls>
<CpyDtls>
<!-- CopyDetails inner content -->
</CpyDtls>
<Xtnsn>
<!-- Extension inner content -->
</Xtnsn>
</SwtchOrdr>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_Aab64TbLEead9bDRE_1DAQ"
previousVersion="_8jfn8tE7Ed-BzquC8wXy7w_-1983893425"
name="SwitchOrderV04"
definition="Scope
The SwitchOrder message is sent by an instructing party, for example, an investment manager or its authorised representative, to the executing party, for example, a transfer agent, to instruct a switch transaction from a financial instrument or multiple financial instruments to a different specified financial instrument or instruments for a specified amount/quantity.
Usage
The SwitchOrder message is used to either:
- instruct one switch transaction comprising one or more redemption legs and one or more subscription legs, that is, a single switch transaction that can be a one to one, many to one, many to many or one to many switch transaction, or,
- instruct one or many switch transactions each comprising one redemption leg and one subscription leg, that is, multiple simple switch transactions.
The SwitchOrder message may be used to either:
- instruct a switch transaction for one investment account, or,
- instruct a switch transaction for separate accounts at the redemption and subscription leg levels.
The message caters for a switch from one financial instrument to another financial instrument (within the same fund family), many to one, many to many and one to many.
The message caters for switch transactions that result in an additional cash payment from the investor or a transaction that results in a net payment to the investor. Not all institutions or funds permit this type of switch and acceptance is therefore not automatic. 
There is no limitation on the number of switch legs in a switch message. The number allowed is defined by the fund prospectus or by the service level agreement (SLA) in place between the two parties. However, if the SwitchOrderDetails sequence is present more than once, then the RedemptionLegDetails and SubscriptionLegDetails sequences may only be present once.
If SwitchOrderDetails\InvestmentAccount is used, then the InvestmentAccountDetails sequences in SubscriptionLegDetails and RedemptionLegDetails are not allowed. This functionality is to be used by institutions that set up two accounts per investor, rather than one investment account.
There is no switch driver type in the message to indicate whether the switch is buy or sell driven. A driver is not needed since it is possible to indicate the total subscription amount or the total redemption amount. Only one of these two amounts should be used. 
The subscription quantity can be expressed in one of the following ways:
- Amount: the monetary value (either GROSS or NET) of the financial instrument to be subscribed to, for example, the subscription of EUR 1,000 of financial instrument ISIN LU1234567890 or 
- Unit: the number of units of the financial instrument to be subscribed to, for example, the subscription of 10 units of financial instrument ISIN LU1234567890 or 
- Percentage of the total redemption amount: when the switch transaction is redemption driven, it is the part of the redemption amount that must be switched to a specific financial instrument, for example, the subscription quantity of financial instrument ISIN LU1234567890 represents 50% of the redemption amount of the financial instrument ISIN LU4444444444.
The redemption quantity can be expressed in one of the following ways:
- Amount: the monetary value (either GROSS or NET) of the financial instrument to be redeemed, for example, the redemption of EUR 1,000 of financial instrument ISIN LU1234567890, or 
- Unit: the number of units of financial instrument to be redeemed, for example, the redemption of 10 units of financial instrument ISIN LU1234567890, or
- Rate: the part of the portfolio to be redeemed, for example, the redemption of 10% of the holdings in financial instrument ISIN LU1234567890, or
- Percentage of the total subscription amount: when the switch transaction is subscription driven, it is the part of the subscription amount that must be the result of the redemption of a specific financial instrument, for example, the redemption quantity in financial instrument ABC represents 50% of the subscription amount of the financial instrument ISIN LU4444444444."
registrationStatus="Registered"
messageSet="_hijK0WiLEeOuqdLlpUIWBw _qCumkAFwEeu2__1EbNXzuA"
xmlTag="SwtchOrdr"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<constraint
xmi:id="_Aab65zbLEead9bDRE_1DAQ"
previousVersion="_8jpY-dE7Ed-BzquC8wXy7w_113242751"
name="MultipleSwitchOrderRule"
definition="If SwitchOrderDetails is present more than once, then SwitchOrderDetails/RedemptionLegDetails and SwitchOrderDetails/SubscriptionLegDetails must only be present once."
registrationStatus="Provisionally Registered" />
<messageBuildingBlock
xmi:id="_Aab66zbLEead9bDRE_1DAQ"
previousVersion="_8jfn89E7Ed-BzquC8wXy7w_668566761"
name="MessageIdentification"
definition="Reference that uniquely identifies the message from a business application standpoint."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MsgId"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_Aab67TbLEead9bDRE_1DAQ"
previousVersion="_8jfn9NE7Ed-BzquC8wXy7w_-1478725370"
name="PoolReference"
definition="Collective reference identifying a set of messages."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="PoolRef"
complexType="_N4g3EXETEea2e4bzJ8TyEw" />
<messageBuildingBlock
xmi:id="_Aab67zbLEead9bDRE_1DAQ"
previousVersion="_8jfn9dE7Ed-BzquC8wXy7w_743595041"
name="PreviousReference"
definition="Reference to a linked message that was previously sent."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="PrvsRef"
complexType="_udnPoTbsEead9bDRE_1DAQ" />
<messageBuildingBlock
xmi:id="_Aab68TbLEead9bDRE_1DAQ"
previousVersion="_8jfn9tE7Ed-BzquC8wXy7w_1164299570"
name="MessagePagination"
definition="Pagination of the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="MsgPgntn"
complexType="_Q65gBdp-Ed-ak6NoX_4Aeg_-21330104" />
<messageBuildingBlock
xmi:id="_Aab68zbLEead9bDRE_1DAQ"
previousVersion="_8jpY8NE7Ed-BzquC8wXy7w_-2137463604"
name="SwitchOrderDetails"
definition="Information related to the switch order."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="SwtchOrdrDtls"
complexType="_2qDsoTbsEead9bDRE_1DAQ" />
<messageBuildingBlock
xmi:id="_Aab69TbLEead9bDRE_1DAQ"
previousVersion="_8jpY8dE7Ed-BzquC8wXy7w_954155400"
name="CopyDetails"
definition="Information provided when the message is a copy of a previous message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="CpyDtls"
complexType="_7VUJ8degEeSA_uUacqhl1Q" />
<messageBuildingBlock
xmi:id="_Aab69zbLEead9bDRE_1DAQ"
previousVersion="_8jpY8tE7Ed-BzquC8wXy7w_956001907"
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="_Q6vvCNp-Ed-ak6NoX_4Aeg_1503007069" />
<messageDefinitionIdentifier
businessArea="setr"
messageFunctionality="013"
flavour="001"
version="04" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.