GetLimitV07

camt.009.001.07

The GetLimit message is used to request information on the details of one or more limits set by the member (or on behalf of the member) and managed by the transaction administrator.

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
%% GetLimitV07 recursion level 0 with max 0
GetLimitV07 *-- "1..1" MessageHeader9 : MessageHeader
GetLimitV07 *-- "0..1" LimitQuery4 : LimitQueryDefinition
GetLimitV07 *-- "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
%% MessageHeader9 recursion level 0 with max 1
class MessageHeader9{
    MessageIdentification IsoMax35Text
    CreationDateTime IsoISODateTime
}
MessageHeader9 *-- "0..1" IRequestType4Choice : RequestType
%% IRequestType4Choice recursion level 1 with max 1
  

MessageHeader9 members

LimitQueryDefinition building block

Defines the limit query criteria. Defines the query criteria. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% LimitQuery4 recursion level 0 with max 1
class LimitQuery4{
    QueryType QueryType2Code
}
LimitQuery4 *-- "0..1" ILimitCriteria6Choice : LimitCriteria
%% ILimitCriteria6Choice recursion level 1 with max 1
  

LimitQuery4 members

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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    GetLimitV07 --|> IOuterRecord : Implements
    GetLimitV07Document --|> IOuterDocument~GetLimitV07~ : Implements
    class IOuterDocument~GetLimitV07~ {
        GetLimitV07 Message
     }
  

Document wrapper for serialization

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

classDiagram
    GetLimitV07Document *-- GetLimitV07 : 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.009.001.07">
    <GetLmt>
        <MsgHdr>
            <!-- MessageHeader inner content -->
        </MsgHdr>
        <LmtQryDef>
            <!-- LimitQueryDefinition inner content -->
        </LmtQryDef>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </GetLmt>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_jwlbhxbvEeiyVv5j1vf1VQ"
  name="GetLimitV07"
  definition="The GetLimit message is used to request information on the details of one or more limits set by the member (or on behalf of the member) and managed by the transaction administrator."
  registrationStatus="Registered"
  messageSet="_SZTDoxcNEeiyVv5j1vf1VQ"
  xmlTag="GetLmt"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_jwlbiRbvEeiyVv5j1vf1VQ"
    name="MessageHeader"
    definition="Common business identification for the message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="MsgHdr"
    complexType="_jAUZkZIhEeect698_YsnIA" />
  <messageBuildingBlock
    xmi:id="_jwlbixbvEeiyVv5j1vf1VQ"
    name="LimitQueryDefinition"
    definition="Defines the limit query criteria."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="LmtQryDef"
    complexType="_E2br6W4-EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_jwlbjRbvEeiyVv5j1vf1VQ"
    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="009"
    flavour="001"
    version="07" />
</messageDefinition>

ISO Building Blocks

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