seev.005.001.07
Scope The MeetingInstructionCancellationRequest message is sent by the same party that sent the MeetingInstruction message. It is sent to request the cancellation of one, some or all of the instructions included in the original MeetingInstruction message. Usage This message must be answered by a MeetingInstructionStatus message. This message definition is intended for use with the Business Application Header (BAH).
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
%% MeetingInstructionCancellationRequestV07 recursion level 0 with max 0
class MeetingInstructionCancellationRequestV07{
MeetingInstructionIdentification IsoMax35Text
}
MeetingInstructionCancellationRequestV07 *-- "0..1" MeetingReference10 : MeetingReference
MeetingInstructionCancellationRequestV07 *-- "0..1" SecurityIdentification19 : FinancialInstrumentIdentification
MeetingInstructionCancellationRequestV07 *-- "0..1" CancelInstruction2 : ToBeCancelledInstruction
MeetingInstructionCancellationRequestV07 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
MeetingInstructionIdentification building block
Identification of the original meeting instruction message for which the cancellation is requested or the original meeting instruction message containing the individual instruction(s) that is/are to be cancelled. Specifies a character string with a maximum length of 35 characters. For comparison, see the ISO20022 official specification This message is declared as Max35Text in the ISO specification. In our implementation, it is represented in source code as IsoMax35Text. Due to global using directives, it is treated as a System.String by the compiler and runtime.
MeetingReference building block
Set of elements to allow the unambiguous identification of a meeting. Identification of a meeting. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MeetingReference10 recursion level 0 with max 1
class MeetingReference10{
MeetingIdentification IsoMax35Text
IssuerMeetingIdentification IsoMax35Text
MeetingDateAndTime IsoISODateTime
Type MeetingType4Code
}
MeetingReference10 *-- "0..1" IMeetingTypeClassification2Choice : Classification
MeetingReference10 *-- "0..5" PostalAddress1 : Location
MeetingReference10 *-- "0..1" IPartyIdentification129Choice : Issuer
%% IMeetingTypeClassification2Choice 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
}
%% IPartyIdentification129Choice recursion level 1 with max 1
MeetingReference10 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| MeetingIdentification | Identification assigned to the general meeting by the party that provides the meeting notification. It must be unique to the party providing the notification. | IsoMax35Text - Required 1..1 |
| IssuerMeetingIdentification | Identification assigned to the meeting by the issuer. It must be unique for the issuer. | IsoMax35Text - Optional 0..1 |
| MeetingDateAndTime | Date and time at which the meeting will take place. | IsoISODateTime - Required 1..1 |
| Type | Type of meeting for which instructions are sent. | MeetingType4Code - Required 1..1 |
| Classification | Classification type of the meeting. | IMeetingTypeClassification2Choice - Optional 0..1 |
| Location | Place of the company meeting for the scheduled meeting date. | PostalAddress1 - Collection 0..5 |
| Issuer | Institution that is the issuer of the security to which the meeting applies. | IPartyIdentification129Choice - Optional 0..1 |
FinancialInstrumentIdentification building block
Security for which the meeting is organised. Identification of a security. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SecurityIdentification19 recursion level 0 with max 1
class SecurityIdentification19{
ISIN IsoISINOct2015Identifier
Description IsoMax140Text
}
SecurityIdentification19 *-- "0..0" OtherIdentification1 : OtherIdentification
%% OtherIdentification1 recursion level 1 with max 1
class OtherIdentification1{
Identification IsoMax35Text
Suffix IsoMax16Text
}
OtherIdentification1 *-- "1..1" IIdentificationSource3Choice : Type
SecurityIdentification19 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| ISIN | International Securities Identification Number (ISIN). A numbering system designed by the United Nation’s International Organisation for Standardisation (ISO). The ISIN is composed of a 2-character prefix representing the country of issue, followed by the national security number (if one exists), and a check digit. Each country has a national numbering agency that assigns ISIN numbers for securities in that country. | IsoISINOct2015Identifier - Optional 0..1 |
| OtherIdentification | Identification of a security by proprietary or domestic identification scheme. | OtherIdentification1 - Unknown 0..0 |
| Description | Textual description of a security instrument. | IsoMax140Text - Optional 0..1 |
ToBeCancelledInstruction building block
Specifies one or more instructions for which the cancellation is requested. Instruction to be cancelled. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% CancelInstruction2 recursion level 0 with max 1
class CancelInstruction2{
SingleInstructionIdentification IsoMax35Text
}
CancelInstruction2 *-- "0..1" SafekeepingAccount10 : InstructedPosition
%% SafekeepingAccount10 recursion level 1 with max 1
class SafekeepingAccount10{
AccountIdentification IsoMax35Text
SubAccountIdentification IsoMax35Text
}
SafekeepingAccount10 *-- "0..1" IPartyIdentification231Choice : AccountOwner
SafekeepingAccount10 *-- "1..15" HoldingBalance10 : InstructedBalance
SafekeepingAccount10 *-- "0..250" IPartyIdentification233Choice : RightsHolder
CancelInstruction2 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| SingleInstructionIdentification | Identification of the individual instruction previously sent. | IsoMax35Text - Required 1..1 |
| InstructedPosition | Account and instructed positions to which the meeting instruction cancellation request applies. | SafekeepingAccount10 - Optional 0..1 |
SupplementaryData building block
Additional information that cannot be captured in the structured fields 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
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
SupplementaryData1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| PlaceAndName | Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. | IsoMax350Text - Optional 0..1 |
| Envelope | Technical element wrapping the supplementary data. | IsoSupplementaryDataEnvelope1 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the MeetingInstructionCancellationRequestV07 implementation follows a specific implementaiton pattern. First of all, MeetingInstructionCancellationRequestV07 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, MeetingInstructionCancellationRequestV07Document implements IOuterDocument. Because MeetingInstructionCancellationRequestV07 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type MeetingInstructionCancellationRequestV07.
classDiagram
class IOuterRecord
MeetingInstructionCancellationRequestV07 --|> IOuterRecord : Implements
MeetingInstructionCancellationRequestV07Document --|> IOuterDocument~MeetingInstructionCancellationRequestV07~ : Implements
class IOuterDocument~MeetingInstructionCancellationRequestV07~ {
MeetingInstructionCancellationRequestV07 Message
}
Document wrapper for serialization
The only real purpose MeetingInstructionCancellationRequestV07Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:seev.005.001.07’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using MeetingInstructionCancellationRequestV07.ToDocument() method. The returned MeetingInstructionCancellationRequestV07Document value will serialize correctly according to ISO 20022 standards.
classDiagram
MeetingInstructionCancellationRequestV07Document *-- MeetingInstructionCancellationRequestV07 : 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.07">
<MtgInstrCxlReq>
<MtgInstrId>
<!-- MeetingInstructionIdentification inner content -->
</MtgInstrId>
<MtgRef>
<!-- MeetingReference inner content -->
</MtgRef>
<FinInstrmId>
<!-- FinancialInstrumentIdentification inner content -->
</FinInstrmId>
<ToBeCancInstr>
<!-- ToBeCancelledInstruction inner content -->
</ToBeCancInstr>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</MtgInstrCxlReq>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_sVyKXfEkEeqRfth943bvEA"
nextVersions="_lKgSUxrdEeyhRdHRjakS2w"
previousVersion="_yXBbaayREemMosWmlQ33EA"
name="MeetingInstructionCancellationRequestV07"
definition="Scope
The MeetingInstructionCancellationRequest message is sent by the same party that sent the
MeetingInstruction message. It is sent to request the cancellation of one, some or all of the instructions included in the original MeetingInstruction message.
Usage
This message must be answered by a MeetingInstructionStatus message. 
This message definition is intended for use with the Business Application Header (BAH)."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="MtgInstrCxlReq"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<constraint
xmi:id="_sVyKX_EkEeqRfth943bvEA"
nextVersions="_lKgSVRrdEeyhRdHRjakS2w"
previousVersion="_yXBba6yREemMosWmlQ33EA"
name="Cancellation3Guideline"
definition="It is recommended that the request to cancel a meeting instruction with the use of MeetingInstructionIdentification only and that the optional elements are avoided, unless otherwise specified by market practice rules and or legislation. If any optional elements are included, they must be identical to the information in the meeting instruction message being cancelled."
registrationStatus="Provisionally Registered" />
<messageBuildingBlock
xmi:id="_sV77F_EkEeqRfth943bvEA"
nextVersions="_lKgSXRrdEeyhRdHRjakS2w"
previousVersion="_yXBbbayREemMosWmlQ33EA"
name="MeetingInstructionIdentification"
definition="Identification of the original meeting instruction message for which the cancellation is requested or the original meeting instruction message containing the individual instruction(s) that is/are to be cancelled."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MtgInstrId"
simpleType="_YW1tKdp-Ed-ak6NoX_4Aeg_1913463446" />
<messageBuildingBlock
xmi:id="_sV77GfEkEeqRfth943bvEA"
nextVersions="_lKgSXxrdEeyhRdHRjakS2w"
previousVersion="_yXBbb6yREemMosWmlQ33EA"
name="MeetingReference"
definition="Set of elements to allow the unambiguous identification of a meeting."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="MtgRef"
complexType="_UP25gfKxEeqRfth943bvEA" />
<messageBuildingBlock
xmi:id="_sV77G_EkEeqRfth943bvEA"
nextVersions="_lKgSYRrdEeyhRdHRjakS2w"
previousVersion="_yXBbcayREemMosWmlQ33EA"
name="FinancialInstrumentIdentification"
definition="Security for which the meeting is organised."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="0"
xmlTag="FinInstrmId"
complexType="_ho6XQYlXEeWPSZi0kAOXhg" />
<messageBuildingBlock
xmi:id="_sV77HfEkEeqRfth943bvEA"
nextVersions="_lKgSYxrdEeyhRdHRjakS2w"
previousVersion="_u_uMQK-aEemJ1NnLPsTFaw"
name="ToBeCancelledInstruction"
definition="Specifies one or more instructions for which the cancellation is requested."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="ToBeCancInstr"
complexType="_KL1NkfNmEeqRfth943bvEA" />
<messageBuildingBlock
xmi:id="_sV77H_EkEeqRfth943bvEA"
nextVersions="_lKgSZRrdEeyhRdHRjakS2w"
previousVersion="_yXBbdayREemMosWmlQ33EA"
name="SupplementaryData"
definition="Additional information that cannot be captured in the structured fields and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="SplmtryData"
complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
<messageDefinitionIdentifier
businessArea="seev"
messageFunctionality="005"
flavour="001"
version="07" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.