MeetingInstructionCancellationRequestV02

seev.005.001.02

Scope The MeetingInstructionCancellationRequest message is sent by the same party that sent the MeetingInstruction message. It is sent to request the cancellation of all instructions included in the original the MeetingInstruction message. Usage This message must be answered by a MeetingInstructionStatus message. Some instructions in the previously sent MeetingInstruction message may have already been executed and cannot be cancelled. This information should appear clearly in the status message.

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
%% MeetingInstructionCancellationRequestV02 recursion level 0 with max 0
MeetingInstructionCancellationRequestV02 *-- "1..1" MessageIdentification1 : InstructionCancellationIdentification
MeetingInstructionCancellationRequestV02 *-- "1..1" MessageIdentification : PreviousReference
MeetingInstructionCancellationRequestV02 *-- "0..1" MeetingReference3 : MeetingReference
MeetingInstructionCancellationRequestV02 *-- "0..1" IPartyIdentification9Choice : RequestingParty
MeetingInstructionCancellationRequestV02 *-- "0..1" SecurityIdentification3 : SecurityIdentification
MeetingInstructionCancellationRequestV02 *-- "0..1" SafekeepingAccount3 : InstructedPosition
  

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

InstructionCancellationIdentification building block

Uniquely identifies the cancellation request. 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

PreviousReference building block

Identifies the instruction to be cancelled. Unique and unambiguous identifier for a message, as assigned by the Sender. This unique identifier can be used for cross-referencing purposes in subsequent messages. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageIdentification recursion level 0 with max 1
class MessageIdentification{
    Identification IsoMax35Text
}
  

MessageIdentification members

MeetingReference building block

Series of elements which allow to identify a meeting. Elements which allow to identify a meeting. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MeetingReference3 recursion level 0 with max 1
class MeetingReference3{
    MeetingIdentification IsoMax35Text
    IssuerMeetingIdentification IsoMax35Text
    MeetingDateAndTime IsoISODateTime
    Type MeetingType2Code
    Classification MeetingTypeClassification1Code
    ExtendedClassification IsoExtended350Code
}
MeetingReference3 *-- "0..5" PostalAddress1 : Location
%% PostalAddress1 recursion level 1 with max 1
class PostalAddress1{
    AddressType AddressType2Code
    AddressLine IsoMax70Text
    StreetName IsoMax70Text
    BuildingNumber IsoMax16Text
    PostCode IsoMax16Text
    TownName IsoMax35Text
    CountrySubDivision IsoMax35Text
    Country CountryCode
}
  

MeetingReference3 members

RequestingParty building block

Party requesting the cancellation. Identification of a party. For comparison, see the ISO20022 official specification

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

PartyIdentification9Choice members

SecurityIdentification building block

Identifies the security for which the meeting is organised. Identification of a security by its symbol. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SecurityIdentification3 recursion level 0 with max 1
class SecurityIdentification3{
    ISIN IsoISINIdentifier
    TickerSymbol IsoTickerIdentifier
    CUSIP IsoCUSIPIdentifier
    SEDOL IsoSEDOLIdentifier
    QUICK IsoQUICKIdentifier
}
SecurityIdentification3 *-- "0..1" AlternateFinancialInstrumentIdentification1 : OtherIdentification
%% AlternateFinancialInstrumentIdentification1 recursion level 1 with max 1
class AlternateFinancialInstrumentIdentification1{
    DomesticIdentificationSource CountryCode
    ProprietaryIdentificationSource IsoMax16Text
    Identification IsoMax35Text
}
  

SecurityIdentification3 members

InstructedPosition building block

Identifies the account and instructed positions for which the instruction cancellation request applies. A safekeeping account is an account on which a securities entry is made. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SafekeepingAccount3 recursion level 0 with max 1
class SafekeepingAccount3{
    AccountIdentification IsoMax35Text
}
SafekeepingAccount3 *-- "0..1" IPartyIdentification9Choice : AccountOwner
SafekeepingAccount3 *-- "0..1" SubAccount2 : SubAccountDetails
SafekeepingAccount3 *-- "1..10" HoldingBalance4 : InstructedBalance
SafekeepingAccount3 *-- "0..10" IPartyIdentification9Choice : RightsHolder
%% IPartyIdentification9Choice recursion level 1 with max 1
%% SubAccount2 recursion level 1 with max 1
class SubAccount2{
    Identification IsoMax35Text
}
%% HoldingBalance4 recursion level 1 with max 1
class HoldingBalance4{
    BalanceType SecuritiesEntryType2Code
}
HoldingBalance4 *-- "1..1" IUnitOrFaceAmountOrCodeChoice : Balance
HoldingBalance4 *-- "0..1" ISafekeepingPlaceFormatChoice : SafekeepingPlace
%% IPartyIdentification9Choice recursion level 1 with max 1
  

SafekeepingAccount3 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    MeetingInstructionCancellationRequestV02 --|> IOuterRecord : Implements
    MeetingInstructionCancellationRequestV02Document --|> IOuterDocument~MeetingInstructionCancellationRequestV02~ : Implements
    class IOuterDocument~MeetingInstructionCancellationRequestV02~ {
        MeetingInstructionCancellationRequestV02 Message
     }
  

Document wrapper for serialization

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

classDiagram
    MeetingInstructionCancellationRequestV02Document *-- MeetingInstructionCancellationRequestV02 : 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:seev.005.001.02">
    <MtgInstrCxlReq>
        <InstrCxlId>
            <!-- InstructionCancellationIdentification inner content -->
        </InstrCxlId>
        <PrvsRef>
            <!-- PreviousReference inner content -->
        </PrvsRef>
        <MtgRef>
            <!-- MeetingReference inner content -->
        </MtgRef>
        <RqstngPty>
            <!-- RequestingParty inner content -->
        </RqstngPty>
        <SctyId>
            <!-- SecurityIdentification inner content -->
        </SctyId>
        <InstdPos>
            <!-- InstructedPosition inner content -->
        </InstdPos>
    </MtgInstrCxlReq>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_TnFV2tEwEd-BzquC8wXy7w_-50610544"
  nextVersions="_TnYQwNEwEd-BzquC8wXy7w_355910963"
  name="MeetingInstructionCancellationRequestV02"
  definition="Scope&#xD;&#xA;The MeetingInstructionCancellationRequest message is sent by the same party that sent the MeetingInstruction message. It is sent to request the cancellation of all instructions included in the original the MeetingInstruction message.&#xD;&#xA;Usage&#xD;&#xA;This message must be answered by a MeetingInstructionStatus message. Some instructions in the previously sent MeetingInstruction message may have already been executed and cannot be cancelled. This information should appear clearly in the status message."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="MtgInstrCxlReq"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <constraint
    xmi:id="_TnPG1NEwEd-BzquC8wXy7w_-753803486"
    name="Cancellation3Guideline"
    definition="It is recommended to cancel an instruction message by using PreviousReference only. It is recommended to avoid the repetition of optional building blocks, unless otherwise specified by market practise rules and or legislation."
    registrationStatus="Provisionally Registered" />
  <messageBuildingBlock
    xmi:id="_TnFV29EwEd-BzquC8wXy7w_-50610266"
    name="InstructionCancellationIdentification"
    definition="Uniquely identifies the cancellation request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="InstrCxlId"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_TnFV3NEwEd-BzquC8wXy7w_-50610509"
    name="PreviousReference"
    definition="Identifies the instruction to be cancelled."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="PrvsRef"
    complexType="_Q6l-Cdp-Ed-ak6NoX_4Aeg_1451391033" />
  <messageBuildingBlock
    xmi:id="_TnPG0NEwEd-BzquC8wXy7w_-50610526"
    name="MeetingReference"
    definition="Series of elements which allow to identify a meeting."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MtgRef"
    complexType="_TlgsINp-Ed-ak6NoX_4Aeg_-1687570906" />
  <messageBuildingBlock
    xmi:id="_TnPG0dEwEd-BzquC8wXy7w_-50610497"
    name="RequestingParty"
    definition="Party requesting the cancellation."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="RqstngPty"
    complexType="_QRUXhtp-Ed-ak6NoX_4Aeg_967984948" />
  <messageBuildingBlock
    xmi:id="_TnPG0tEwEd-BzquC8wXy7w_-1638529229"
    name="SecurityIdentification"
    definition="Identifies the security for which the meeting is organised."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyId"
    complexType="_QdiOk9p-Ed-ak6NoX_4Aeg_2006961788" />
  <messageBuildingBlock
    xmi:id="_TnPG09EwEd-BzquC8wXy7w_-2011631186"
    name="InstructedPosition"
    definition="Identifies the account and instructed positions for which the instruction cancellation request applies."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="InstdPos"
    complexType="_QT_4Etp-Ed-ak6NoX_4Aeg_599991386" />
  <messageDefinitionIdentifier
    businessArea="seev"
    messageFunctionality="005"
    flavour="001"
    version="02" />
</messageDefinition>

ISO Building Blocks

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