MeetingInstructionCancellationRequestV03

seev.005.001.03

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
%% MeetingInstructionCancellationRequestV03 recursion level 0 with max 0
MeetingInstructionCancellationRequestV03 *-- "1..1" MessageIdentification1 : Identification
MeetingInstructionCancellationRequestV03 *-- "1..1" MessageIdentification : PreviousReference
MeetingInstructionCancellationRequestV03 *-- "0..1" MeetingReference4 : MeetingReference
MeetingInstructionCancellationRequestV03 *-- "0..1" IPartyIdentification9Choice : RequestingParty
MeetingInstructionCancellationRequestV03 *-- "0..1" SecurityIdentification11 : SecurityIdentification
MeetingInstructionCancellationRequestV03 *-- "0..1" SafekeepingAccount4 : InstructedPosition
  

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

Identification 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
%% MeetingReference4 recursion level 0 with max 1
class MeetingReference4{
    MeetingIdentification IsoMax35Text
    IssuerMeetingIdentification IsoMax35Text
    MeetingDateAndTime IsoISODateTime
    Type MeetingType2Code
}
MeetingReference4 *-- "0..1" IMeetingTypeClassification1Choice : Classification
MeetingReference4 *-- "0..5" PostalAddress1 : Location
%% IMeetingTypeClassification1Choice recursion level 1 with max 1
%% 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
}
  

MeetingReference4 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. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% SecurityIdentification11 recursion level 0 with max 1
class SecurityIdentification11{
    Description IsoMax140Text
}
SecurityIdentification11 *-- "1..1" ISecurityIdentification11Choice : Identification
%% ISecurityIdentification11Choice recursion level 1 with max 1
  

SecurityIdentification11 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
%% SafekeepingAccount4 recursion level 0 with max 1
class SafekeepingAccount4{
    AccountIdentification IsoMax35Text
}
SafekeepingAccount4 *-- "0..1" IPartyIdentification9Choice : AccountOwner
SafekeepingAccount4 *-- "0..1" SubAccount2 : SubAccountDetails
SafekeepingAccount4 *-- "1..10" HoldingBalance5 : InstructedBalance
SafekeepingAccount4 *-- "0..10" IPartyIdentification9Choice : RightsHolder
%% IPartyIdentification9Choice recursion level 1 with max 1
%% SubAccount2 recursion level 1 with max 1
class SubAccount2{
    Identification IsoMax35Text
}
%% HoldingBalance5 recursion level 1 with max 1
class HoldingBalance5{
    BalanceType SecuritiesEntryType2Code
}
HoldingBalance5 *-- "1..1" IUnitOrFaceAmountOrCode1Choice : Balance
HoldingBalance5 *-- "0..1" ISafekeepingPlaceFormatChoice : SafekeepingPlace
%% IPartyIdentification9Choice recursion level 1 with max 1
  

SafekeepingAccount4 members

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    MeetingInstructionCancellationRequestV03 --|> IOuterRecord : Implements
    MeetingInstructionCancellationRequestV03Document --|> IOuterDocument~MeetingInstructionCancellationRequestV03~ : Implements
    class IOuterDocument~MeetingInstructionCancellationRequestV03~ {
        MeetingInstructionCancellationRequestV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    MeetingInstructionCancellationRequestV03Document *-- MeetingInstructionCancellationRequestV03 : 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.03">
    <MtgInstrCxlReq>
        <Id>
            <!-- Identification inner content -->
        </Id>
        <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="_TnYQwNEwEd-BzquC8wXy7w_355910963"
  nextVersions="_TniBy9EwEd-BzquC8wXy7w_-914512760"
  previousVersion="_TnFV2tEwEd-BzquC8wXy7w_-50610544"
  name="MeetingInstructionCancellationRequestV03"
  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="_TnYQx9EwEd-BzquC8wXy7w_488897498"
    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="_TnYQwdEwEd-BzquC8wXy7w_1015295249"
    name="Identification"
    definition="Uniquely identifies the cancellation request."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Id"
    complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
  <messageBuildingBlock
    xmi:id="_TnYQwtEwEd-BzquC8wXy7w_1044847089"
    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="_TnYQw9EwEd-BzquC8wXy7w_1088252061"
    name="MeetingReference"
    definition="Series of elements which allow to identify a meeting."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="MtgRef"
    complexType="_Tj3tZtp-Ed-ak6NoX_4Aeg_-658253867" />
  <messageBuildingBlock
    xmi:id="_TnYQxNEwEd-BzquC8wXy7w_-975159654"
    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="_TnYQxdEwEd-BzquC8wXy7w_-946528538"
    name="SecurityIdentification"
    definition="Identifies the security for which the meeting is organised."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="SctyId"
    complexType="_TBKB89p-Ed-ak6NoX_4Aeg_-524266634" />
  <messageBuildingBlock
    xmi:id="_TnYQxtEwEd-BzquC8wXy7w_-920672368"
    name="InstructedPosition"
    definition="Identifies the account and instructed positions for which the instruction cancellation request applies."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="InstdPos"
    complexType="_QTQRM9p-Ed-ak6NoX_4Aeg_1467329706" />
  <messageDefinitionIdentifier
    businessArea="seev"
    messageFunctionality="005"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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