DuplicateV03

camt.034.001.03

Scope The Duplicate message is used by financial institutions, with their own offices, and/or with other financial institutions with which they have established bilateral agreements. It allows to exchange duplicate payment instructions. Usage This message must be sent in response to a Request For Duplicate message. The Duplicate Data element must contain a well formed XML document. This means XML special characters such as ‘<’ must be used in a way that is consistent with XML well-formedness 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
%% DuplicateV03 recursion level 0 with max 0
DuplicateV03 *-- "1..1" CaseAssignment2 : Assignment
DuplicateV03 *-- "1..1" Case2 : Case
DuplicateV03 *-- "1..1" ProprietaryData4 : Duplicate

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

Assignment building block

Identifies the assignment of an investigation case from an assigner to an assignee. Usage: The Assigner must be the sender of this confirmation and the Assignee must be the receiver. Set of elements used to represent the assignment of a case to a party. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% CaseAssignment2 recursion level 0 with max 1
class CaseAssignment2{
    Identification IsoMax35Text
    CreationDateTime IsoISODateTime
}
CaseAssignment2 *-- "1..1" IParty7Choice : Assigner
CaseAssignment2 *-- "1..1" IParty7Choice : Assignee
%% IParty7Choice recursion level 1 with max 1
%% IParty7Choice recursion level 1 with max 1

CaseAssignment2 members

Member name	Description	Data Type / Multiplicity
Identification	Uniquely identifies the case assignment.	IsoMax35Text - Required 1..1
Assigner	Party who assigns the case.	Usage: This is also the sender of the message.
Assignee	Party to which the case is assigned.	Usage: This is also the receiver of the message.
CreationDateTime	Date and time at which the assignment was created.	IsoISODateTime - Required 1..1

Case building block

Identifies the investigation case. Set of elements used to identify a case. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% Case2 recursion level 0 with max 1
class Case2{
    Identification IsoMax35Text
    ReopenCaseIndication IsoYesNoIndicator
}
Case2 *-- "1..1" IParty7Choice : Creator
%% IParty7Choice recursion level 1 with max 1

Case2 members

Member name	Description	Data Type / Multiplicity
Identification	Uniquely identifies the case.	IsoMax35Text - Required 1..1
Creator	Party that created the investigation case.	IParty7Choice - Required 1..1
ReopenCaseIndication	Indicates whether or not the case was previously closed and is now re-opened.	IsoYesNoIndicator - Optional 0..1

Duplicate building block

Duplicate of a previously sent message. Container for proprietary information. Business content of this element is not specified. For comparison, see the ISO20022 official specification

classDiagram
   direction tb
%% ProprietaryData4 recursion level 0 with max 1
class ProprietaryData4{
    Type IsoMax35Text
}
ProprietaryData4 *-- "1..1" ProprietaryData3 : Data
%% ProprietaryData3 recursion level 1 with max 1
ProprietaryData3 *-- "1..1" SkipProcessing : Any

ProprietaryData4 members

Member name	Description	Data Type / Multiplicity
Type	Specifies the type of proprietary document.	IsoMax35Text - Required 1..1
Data	Proprietary data content.	ProprietaryData3 - Required 1..1

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    DuplicateV03 --|> IOuterRecord : Implements
    DuplicateV03Document --|> IOuterDocument~DuplicateV03~ : Implements
    class IOuterDocument~DuplicateV03~ {
        DuplicateV03 Message
     }

Document wrapper for serialization

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

classDiagram
    DuplicateV03Document *-- DuplicateV03 : 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.034.001.03">
    <Dplct>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <Case>
            <!-- Case inner content -->
        </Case>
        <Dplct>
            <!-- Duplicate inner content -->
        </Dplct>
    </Dplct>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_X-6wYtE-Ed-BzquC8wXy7w_654549647"
  nextVersions="_sWZkYFkyEeGeoaLUQk__nA_-179757236"
  name="DuplicateV03"
  definition="Scope&#xD;&#xA;The Duplicate message is used by financial institutions, with their own offices, and/or with other financial institutions with which they have established bilateral agreements. It allows to exchange duplicate payment instructions.&#xD;&#xA;Usage&#xD;&#xA;This message must be sent in response to a Request For Duplicate message.&#xD;&#xA;The Duplicate Data element must contain a well formed XML document. This means XML special characters such as '&lt;' must be used in a way that is consistent with XML well-formedness criteria.&#xD;."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="Dplct"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_X-6wY9E-Ed-BzquC8wXy7w_-1056990922"
    name="Assignment"
    definition="Identifies the assignment of an investigation case from an assigner to an assignee.&#xA;Usage: The Assigner must be the sender of this confirmation and the Assignee must be the receiver."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Assgnmt"
    complexType="_T9Nac9p-Ed-ak6NoX_4Aeg_-1609381277" />
  <messageBuildingBlock
    xmi:id="_X-6wZNE-Ed-BzquC8wXy7w_-1056990861"
    name="Case"
    definition="Identifies the investigation case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Case"
    complexType="_SpAnptp-Ed-ak6NoX_4Aeg_-1565053133" />
  <messageBuildingBlock
    xmi:id="_X-6wZdE-Ed-BzquC8wXy7w_654549710"
    name="Duplicate"
    definition="Duplicate of a previously sent message."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Dplct"
    complexType="_RqIklNp-Ed-ak6NoX_4Aeg_1327453189" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="034"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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