DeleteStandingOrderV03

camt.071.001.03

The DeleteStandingOrder message is sent by the system member to delete one or more standing orders within the static data held by the system 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
%% DeleteStandingOrderV03 recursion level 0 with max 0
DeleteStandingOrderV03 *-- "1..1" MessageHeader1 : MessageHeader
DeleteStandingOrderV03 *-- "1..1" IStandingOrderOrAll2Choice : StandingOrderDetails
DeleteStandingOrderV03 *-- "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

StandingOrderDetails building block

Identifies one particular limit set by the member and managed by the transaction administrator. Characteristics of one or all standing orders set by the member and managed by the transaction administrator. For comparison, see the ISO20022 official specification

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

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

classDiagram
    class IOuterRecord
    DeleteStandingOrderV03 --|> IOuterRecord : Implements
    DeleteStandingOrderV03Document --|> IOuterDocument~DeleteStandingOrderV03~ : Implements
    class IOuterDocument~DeleteStandingOrderV03~ {
        DeleteStandingOrderV03 Message
     }
  

Document wrapper for serialization

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

classDiagram
    DeleteStandingOrderV03Document *-- DeleteStandingOrderV03 : 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.071.001.03">
    <DelStgOrdr>
        <MsgHdr>
            <!-- MessageHeader inner content -->
        </MsgHdr>
        <StgOrdrDtls>
            <!-- StandingOrderDetails inner content -->
        </StgOrdrDtls>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </DelStgOrdr>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_jwlbXxbvEeiyVv5j1vf1VQ"
  nextVersions="_ThNX09b6Eeq_l4BJLVUF2Q"
  name="DeleteStandingOrderV03"
  definition="The DeleteStandingOrder message is sent by the system member to delete one or more standing orders within the static data held by the system transaction administrator."
  registrationStatus="Registered"
  messageSet="_S0OMdGY1EeuQ__SOdbf47A"
  xmlTag="DelStgOrdr"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_jwlbYRbvEeiyVv5j1vf1VQ"
    nextVersions="_ThNX29b6Eeq_l4BJLVUF2Q"
    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="_jwlbYxbvEeiyVv5j1vf1VQ"
    nextVersions="_ThNX3db6Eeq_l4BJLVUF2Q"
    name="StandingOrderDetails"
    definition="Identifies one particular limit set by the member and managed by the transaction administrator."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="StgOrdrDtls"
    complexType="_HmQvMW4-EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_jwlbZRbvEeiyVv5j1vf1VQ"
    nextVersions="_ThNX39b6Eeq_l4BJLVUF2Q"
    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="071"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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