setr.013.001.03
Scope An instructing party, for example, an investment manager or its authorised representative, sends the SwitchOrder message 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, eg, 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, eg, 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, eg, the redemption of EUR 1,000 of financial instrument ISIN LU1234567890, or
- Unit: the number of units of financial instrument to be redeemed, eg, the redemption of 10 units of financial instrument ISIN LU1234567890, or
- Rate: the part of the portfolio to be redeemed, eg, 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 %% SwitchOrderV03 recursion level 0 with max 0 SwitchOrderV03 *-- "1..1" MessageIdentification1 : MessageIdentification SwitchOrderV03 *-- "0..1" AdditionalReference3 : PoolReference SwitchOrderV03 *-- "0..1" AdditionalReference3 : PreviousReference SwitchOrderV03 *-- "0..1" Pagination : MessagePagination SwitchOrderV03 *-- "1..1" SwitchOrder4 : SwitchOrderDetails SwitchOrderV03 *-- "0..1" CopyInformation2 : CopyDetails SwitchOrderV03 *-- "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 a 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 %% AdditionalReference3 recursion level 0 with max 1 class AdditionalReference3{ Reference IsoMax35Text MessageName IsoMax35Text } AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer %% IPartyIdentification2Choice recursion level 1 with max 1
AdditionalReference3 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Reference | Business reference of a message assigned by the party issuing the message. This reference must be unique amongst all messages of the same name sent by the same party. | IsoMax35Text - Required 1..1 |
ReferenceIssuer | Issuer of the reference. | IPartyIdentification2Choice - Optional 0..1 |
MessageName | Name of a 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 %% AdditionalReference3 recursion level 0 with max 1 class AdditionalReference3{ Reference IsoMax35Text MessageName IsoMax35Text } AdditionalReference3 *-- "0..1" IPartyIdentification2Choice : ReferenceIssuer %% IPartyIdentification2Choice recursion level 1 with max 1
AdditionalReference3 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Reference | Business reference of a message assigned by the party issuing the message. This reference must be unique amongst all messages of the same name sent by the same party. | IsoMax35Text - Required 1..1 |
ReferenceIssuer | Issuer of the reference. | IPartyIdentification2Choice - Optional 0..1 |
MessageName | Name of a 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 %% SwitchOrder4 recursion level 0 with max 1 class SwitchOrder4{ MasterReference IsoMax35Text OrderDateTime IsoISODateTime OrderReference IsoMax35Text ClientReference IsoMax35Text TotalRedemptionAmount IsoActiveOrHistoricCurrencyAndAmount TotalSubscriptionAmount IsoActiveOrHistoricCurrencyAndAmount RequestedFutureTradeDate IsoISODate SettlementAmount IsoActiveCurrencyAndAmount CashSettlementDate IsoISODate SettlementMethod DeliveryReceiptType2Code AdditionalCashIn IsoActiveOrHistoricCurrencyAndAmount ResultingCashOut IsoActiveOrHistoricCurrencyAndAmount CancellationRight CancellationRight1Code ExtendedCancellationRight IsoExtended350Code FinancialAdvice FinancialAdvice1Code NegotiatedTrade NegotiatedTrade1Code } SwitchOrder4 *-- "0..1" InvestmentAccount21 : InvestmentAccountDetails SwitchOrder4 *-- "0..1" IDateAndDateTimeChoice : ExpiryDateTime SwitchOrder4 *-- "0..10" Intermediary8 : RelatedPartyDetails SwitchOrder4 *-- "1..0" SwitchRedemptionLegOrder3 : RedemptionLegDetails SwitchOrder4 *-- "1..0" SwitchSubscriptionLegOrder3 : SubscriptionLegDetails SwitchOrder4 *-- "0..1" PaymentTransaction25 : CashSettlementDetails SwitchOrder4 *-- "0..1" ForeignExchangeTerms6 : ForeignExchangeDetails %% InvestmentAccount21 recursion level 1 with max 1 class InvestmentAccount21{ AccountName IsoMax35Text AccountDesignation IsoMax35Text OrderOriginatorEligibility OrderOriginatorEligibility1Code } InvestmentAccount21 *-- "1..1" AccountIdentification1 : AccountIdentification InvestmentAccount21 *-- "0..0" IPartyIdentification2Choice : OwnerIdentification InvestmentAccount21 *-- "0..1" IPartyIdentification2Choice : AccountServicer InvestmentAccount21 *-- "0..1" SubAccount1 : SubAccountDetails %% IDateAndDateTimeChoice recursion level 1 with max 1 %% Intermediary8 recursion level 1 with max 1 class Intermediary8{ OrderOriginatorEligibility OrderOriginatorEligibility1Code Role InvestmentFundRole2Code ExtendedRole IsoExtended350Code } Intermediary8 *-- "1..1" IPartyIdentification2Choice : Identification Intermediary8 *-- "0..1" Account7 : Account %% SwitchRedemptionLegOrder3 recursion level 1 with max 1 class SwitchRedemptionLegOrder3{ LegIdentification IsoMax35Text IncomePreference IncomePreference1Code Group1Or2Units UKTaxGroupUnitCode RequestedSettlementCurrency ActiveCurrencyCode RequestedNAVCurrency ActiveOrHistoricCurrencyCode PhysicalDeliveryIndicator IsoYesNoIndicator NonStandardSettlementInformation IsoMax350Text } SwitchRedemptionLegOrder3 *-- "1..1" FinancialInstrument10 : FinancialInstrumentDetails SwitchRedemptionLegOrder3 *-- "0..1" IFinancialInstrumentQuantity5Choice : FinancialInstrumentQuantityChoice SwitchRedemptionLegOrder3 *-- "0..1" InvestmentAccount21 : InvestmentAccountDetails SwitchRedemptionLegOrder3 *-- "0..0" Charge17 : ChargeDetails SwitchRedemptionLegOrder3 *-- "0..0" Commission10 : CommissionDetails SwitchRedemptionLegOrder3 *-- "0..0" Tax16 : TaxDetails SwitchRedemptionLegOrder3 *-- "0..1" FundSettlementParameters3 : SettlementAndCustodyDetails SwitchRedemptionLegOrder3 *-- "0..1" DeliveryParameters3 : PhysicalDeliveryDetails SwitchRedemptionLegOrder3 *-- "0..1" Equalisation1 : Equalisation %% SwitchSubscriptionLegOrder3 recursion level 1 with max 1 class SwitchSubscriptionLegOrder3{ LegIdentification IsoMax35Text IncomePreference IncomePreference1Code RequestedSettlementCurrency ActiveCurrencyCode RequestedNAVCurrency ActiveOrHistoricCurrencyCode PhysicalDeliveryIndicator IsoYesNoIndicator NonStandardSettlementInformation IsoMax350Text } SwitchSubscriptionLegOrder3 *-- "1..1" FinancialInstrument10 : FinancialInstrumentDetails SwitchSubscriptionLegOrder3 *-- "0..1" IFinancialInstrumentQuantity6Choice : FinancialInstrumentQuantityChoice SwitchSubscriptionLegOrder3 *-- "0..1" InvestmentAccount21 : InvestmentAccountDetails SwitchSubscriptionLegOrder3 *-- "0..0" Charge17 : ChargeDetails SwitchSubscriptionLegOrder3 *-- "0..0" Commission10 : CommissionDetails SwitchSubscriptionLegOrder3 *-- "0..1" FundSettlementParameters4 : SettlementAndCustodyDetails SwitchSubscriptionLegOrder3 *-- "0..0" Tax16 : TaxDetails SwitchSubscriptionLegOrder3 *-- "0..1" NameAndAddress4 : PhysicalDeliveryDetails SwitchSubscriptionLegOrder3 *-- "0..1" Equalisation1 : Equalisation %% PaymentTransaction25 recursion level 1 with max 1 PaymentTransaction25 *-- "0..1" ICashInOrOut5Choice : CashInOrOut %% ForeignExchangeTerms6 recursion level 1 with max 1 class ForeignExchangeTerms6{ UnitCurrency ActiveOrHistoricCurrencyCode QuotedCurrency ActiveOrHistoricCurrencyCode ExchangeRate IsoBaseOneRate QuotationDate IsoISODateTime } ForeignExchangeTerms6 *-- "0..1" IPartyIdentification2Choice : QuotingInstitution
SwitchOrder4 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 at which the order was placed by the investor. | IsoISODateTime - Optional 0..1 |
OrderReference | Unique and unambiguous identifier for an order, as assigned by the instructing party. | IsoMax35Text - Required 1..1 |
ClientReference | Unique and unambiguous investor’s identification of an 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 between an investor(s) and a fund manager or a fund. The account can contain holdings in any investment fund or investment fund class managed (or distributed) by the fund manager, within the same fund family. | InvestmentAccount21 - Optional 0..1 |
TotalRedemptionAmount | Amount of money used to derive the quantity of investment fund units to be redeemed. | IsoActiveOrHistoricCurrencyAndAmount - Optional 0..1 |
TotalSubscriptionAmount | Amount of money used to derive the quantity of investment fund units to be subscribed. | IsoActiveOrHistoricCurrencyAndAmount - Optional 0..1 |
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 |
ExpiryDateTime | Date on which the order expires. | IDateAndDateTimeChoice - Optional 0..1 |
AdditionalCashIn | Additional amount of money paid by the investor in addition to the switch redemption amount. | IsoActiveOrHistoricCurrencyAndAmount - Optional 0..1 |
ResultingCashOut | Amount of money that results from a switch-out, that is not reinvested in another investment fund, and is repaid to the investor. | IsoActiveOrHistoricCurrencyAndAmount - Optional 0..1 |
RelatedPartyDetails | Information about parties related to the transaction. | Intermediary8 - Collection 0..10 |
CancellationRight | Cancellation right of an investor with respect to an investment fund order. | CancellationRight1Code - Optional 0..1 |
ExtendedCancellationRight | Cancellation right of an investor with respect to an investment fund order. | IsoExtended350Code - Optional 0..1 |
RedemptionLegDetails | Part of an investment fund switch order that is a redemption. | SwitchRedemptionLegOrder3 - Unknown 1..0 |
SubscriptionLegDetails | Part of an investment fund switch order that is a subscription. | SwitchSubscriptionLegOrder3 - Unknown 1..0 |
CashSettlementDetails | Payment processes required to transfer cash from the debtor to the creditor. | PaymentTransaction25 - Optional 0..1 |
ForeignExchangeDetails | Information needed to process a currency exchange or conversion. | ForeignExchangeTerms6 - 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 |
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 %% CopyInformation2 recursion level 0 with max 1 class CopyInformation2{ CopyIndicator IsoYesNoIndicator } CopyInformation2 *-- "0..1" BICIdentification1 : OriginalReceiver %% BICIdentification1 recursion level 1 with max 1 class BICIdentification1{ BIC IsoBICIdentifier }
CopyInformation2 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. | BICIdentification1 - 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 SwitchOrderV03 implementation follows a specific implementaiton pattern. First of all, SwitchOrderV03 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, SwitchOrderV03Document implements IOuterDocument. Because SwitchOrderV03 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type SwitchOrderV03.
classDiagram class IOuterRecord SwitchOrderV03 --|> IOuterRecord : Implements SwitchOrderV03Document --|> IOuterDocument~SwitchOrderV03~ : Implements class IOuterDocument~SwitchOrderV03~ { SwitchOrderV03 Message }
Document wrapper for serialization
The only real purpose SwitchOrderV03Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:setr.013.001.03’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using SwitchOrderV03.ToDocument() method. The returned SwitchOrderV03Document value will serialize correctly according to ISO 20022 standards.
classDiagram SwitchOrderV03Document *-- SwitchOrderV03 : 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.03">
<SwtchOrdrV03>
<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>
</SwtchOrdrV03>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_8jfn8tE7Ed-BzquC8wXy7w_-1983893425"
nextVersions="_Aab64TbLEead9bDRE_1DAQ"
previousVersion="_8JIAINE7Ed-BzquC8wXy7w_-1831529909"
name="SwitchOrderV03"
definition="Scope
An instructing party, for example, an investment manager or its authorised representative, sends the SwitchOrder message 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, eg, 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, eg, 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, eg, the redemption of EUR 1,000 of financial instrument ISIN LU1234567890, or 
- Unit: the number of units of financial instrument to be redeemed, eg, the redemption of 10 units of financial instrument ISIN LU1234567890, or
- Rate: the part of the portfolio to be redeemed, eg, 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="_wFQdsE2rEeG_I4xRYCA_7g"
xmlTag="SwtchOrdrV03"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<constraint
xmi:id="_8jpY89E7Ed-BzquC8wXy7w_-1825045720"
name="AccountIdentificationRule"
definition="If this message is linked to an account opening request and the account identification is not yet known then the value of the AccountIdentification element in SwitchOrderDetails/InvestmentAccountDetails must be UNKNOWN."
registrationStatus="Provisionally Registered" />
<constraint
xmi:id="_8jpY9tE7Ed-BzquC8wXy7w_1562093499"
name="OrderOriginatorEligibility4Rule"
definition="Either SwitchOrderDetails/InvestmentAccountDetails/OrderOriginatorEligibility or (one or more instances of SwitchOrderDetails/RelatedPartyDetails/OrderOriginatorEligibility) may be present, but not both."
registrationStatus="Provisionally Registered" />
<constraint
xmi:id="_8jpY-dE7Ed-BzquC8wXy7w_113242751"
nextVersions="_Aab65zbLEead9bDRE_1DAQ"
name="MultipleSwitchOrderRule"
definition="If SwitchOrderDetails is present more than once, then SwitchOrderDetails/RedemptionLegDetails and SwitchOrderDetails/SubscriptionLegDetails may only be present once."
registrationStatus="Provisionally Registered" />
<messageBuildingBlock
xmi:id="_8jfn89E7Ed-BzquC8wXy7w_668566761"
nextVersions="_Aab66zbLEead9bDRE_1DAQ"
name="MessageIdentification"
definition="Reference that uniquely identifies a message from a business application standpoint."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MsgId"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_8jfn9NE7Ed-BzquC8wXy7w_-1478725370"
nextVersions="_Aab67TbLEead9bDRE_1DAQ"
name="PoolReference"
definition="Collective reference identifying a set of messages."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="PoolRef"
complexType="_Q6vvAdp-Ed-ak6NoX_4Aeg_2101402955" />
<messageBuildingBlock
xmi:id="_8jfn9dE7Ed-BzquC8wXy7w_743595041"
nextVersions="_Aab67zbLEead9bDRE_1DAQ"
name="PreviousReference"
definition="Reference to a linked message that was previously sent."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="PrvsRef"
complexType="_Q6vvAdp-Ed-ak6NoX_4Aeg_2101402955" />
<messageBuildingBlock
xmi:id="_8jfn9tE7Ed-BzquC8wXy7w_1164299570"
nextVersions="_Aab68TbLEead9bDRE_1DAQ"
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="_8jpY8NE7Ed-BzquC8wXy7w_-2137463604"
nextVersions="_Aab68zbLEead9bDRE_1DAQ"
name="SwitchOrderDetails"
definition="Information related to the switch order."
registrationStatus="Provisionally Registered"
minOccurs="1"
xmlTag="SwtchOrdrDtls"
complexType="_SMZkJ9p-Ed-ak6NoX_4Aeg_81412346" />
<messageBuildingBlock
xmi:id="_8jpY8dE7Ed-BzquC8wXy7w_954155400"
nextVersions="_Aab69TbLEead9bDRE_1DAQ"
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="_Q7Vk4tp-Ed-ak6NoX_4Aeg_-1918092012" />
<messageBuildingBlock
xmi:id="_8jpY8tE7Ed-BzquC8wXy7w_956001907"
nextVersions="_Aab69zbLEead9bDRE_1DAQ"
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="03" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.