Iso20022

DeleteLimitV07

camt.012.001.07

Scope The DeleteLimit message is sent by a member to the transaction administrator. It is used to request the deletion of one particular, several or all limits set by the member and managed by the transaction administrator. The DeleteLimit message may delete several types of current limits (risk or liquidity management limit), based on a multiple requests. Usage The member will submit a DeleteLimit message identifying which limit(s) it wants to delete (current limit risk/liquidity limit concepts have been merged) based on following criteria:

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
%% DeleteLimitV07 recursion level 0 with max 0
DeleteLimitV07 *-- "1..1" MessageHeader1 : MessageHeader
DeleteLimitV07 *-- "1..1" ILimitStructure2Choice : LimitDetails
DeleteLimitV07 *-- "0..1" SupplementaryData1 : SupplementaryData

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

MessageHeader building block

Common business identification for the message. Set of characteristics, such as the identification or the creation date and time, specific to the message. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% MessageHeader1 recursion level 0 with max 1
class MessageHeader1{
    MessageIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}

MessageHeader1 members

Member name Description Data Type / Multiplicity
MessageIdentification Point to point reference, as assigned by the sender, to unambiguously identify the message. Usage: The sender has to make sure that MessageIdentification is unique for a pre-agreed period. IsoMax35Text - Required 1..1
CreationDateTime Date and time at which the message was created. IsoISODateTime - Optional 0..1

LimitDetails building block

Identifies one particular limit set by the member and managed by the transaction administrator. Limit details of one or more limits set by the member and managed by the transaction administrator. For comparison, see the ISO20022 official specification

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

LimitStructure2Choice members

Member name Description Data Type / Multiplicity

SupplementaryData 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
%% 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 DeleteLimitV07 implementation follows a specific implementaiton pattern. First of all, DeleteLimitV07 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, DeleteLimitV07Document implements IOuterDocument. Because DeleteLimitV07 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type DeleteLimitV07.

classDiagram
    class IOuterRecord
    DeleteLimitV07 --|> IOuterRecord : Implements
    DeleteLimitV07Document --|> IOuterDocument~DeleteLimitV07~ : Implements
    class IOuterDocument~DeleteLimitV07~ {
        DeleteLimitV07 Message
     }

Document wrapper for serialization

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

classDiagram
    DeleteLimitV07Document *-- DeleteLimitV07 : 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:camt.012.001.07">
    <DelLmt>
        <MsgHdr>
            <!-- MessageHeader inner content -->
        </MsgHdr>
        <LmtDtls>
            <!-- LimitDetails inner content -->
        </LmtDtls>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </DelLmt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_jwlbTxbvEeiyVv5j1vf1VQ"
  name="DeleteLimitV07"
  definition="Scope&#xD;&#xA;The DeleteLimit message is sent by a member to the transaction administrator.&#xD;&#xA;It is used to request the deletion of one particular, several or all limits set by the member and managed by the transaction administrator.&#xD;&#xA;The DeleteLimit message may delete several types of current limits (risk or liquidity management limit), based on a multiple requests.&#xD;&#xA;Usage&#xD;&#xA;The member will submit a DeleteLimit message identifying which limit(s) it wants to delete (current limit risk/liquidity limit concepts have been merged) based on following criteria:&#xD;&#xA;- type of limit(s) (current/default)&#xD;&#xA;- value of the limit(s) (default and/or current limit(s))&#xD;&#xA;- identification of the counterparty (bilateral limit)&#xD;&#xA;Based on the criteria received within the DeleteLimit message, the transaction administrator will execute or reject the requested modifications.&#xD;&#xA;The transaction administrator may send a Receipt message as a reply to the DeleteLimit request.&#xD;&#xA;To verify the outcome of the request, the member may submit a GetLimit message with the appropriate search criteria."
  registrationStatus="Registered"
  messageSet="_SZTDoxcNEeiyVv5j1vf1VQ"
  xmlTag="DelLmt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_jwlbURbvEeiyVv5j1vf1VQ"
    name="MessageHeader"
    definition="Common business identification for the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgHdr"
    complexType="_75DzkaMgEeCJ6YNENx4h-w_-613853819" />
  <messageBuildingBlock
    xmi:id="_jwlbUxbvEeiyVv5j1vf1VQ"
    name="LimitDetails"
    definition="Identifies one particular limit set by the member and managed by the transaction administrator."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="LmtDtls"
    complexType="__lXa7249EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_jwlbVRbvEeiyVv5j1vf1VQ"
    name="SupplementaryData"
    definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
    registrationStatus="Provisionally Registered"
    minOccurs="0"
    xmlTag="SplmtryData"
    complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="012"
    flavour="001"
    version="07" />
</messageDefinition>

ISO Building Blocks

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