RequestForDuplicateV03

camt.033.001.03

Scope The Request For Duplicate message is sent by the case assignee to the case creator or case assigner. This message is used to request a copy of the original payment instruction considered in the case. Usage The Request For Duplicate message:

must be answered with a Duplicate message
must be used when a case assignee requests a copy of the original payment instruction. This occurs, for example, when the case assignee cannot trace the payment instruction based on the elements mentioned in the case assignment message
covers one and only one instruction at a time. If several payment instruction copies are needed by the case assignee, then multiple Request For Duplicate messages must be sent
must be used exclusively between the case assignee and its case creator/case assigner.

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
%% RequestForDuplicateV03 recursion level 0 with max 0
RequestForDuplicateV03 *-- "1..1" CaseAssignment2 : Assignment
RequestForDuplicateV03 *-- "1..1" Case2 : Case

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

Extensibility and generalization considerations

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

classDiagram
    class IOuterRecord
    RequestForDuplicateV03 --|> IOuterRecord : Implements
    RequestForDuplicateV03Document --|> IOuterDocument~RequestForDuplicateV03~ : Implements
    class IOuterDocument~RequestForDuplicateV03~ {
        RequestForDuplicateV03 Message
     }

Document wrapper for serialization

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

classDiagram
    RequestForDuplicateV03Document *-- RequestForDuplicateV03 : 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.033.001.03">
    <ReqForDplct>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <Case>
            <!-- Case inner content -->
        </Case>
    </ReqForDplct>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_SMNVeNE_Ed-BzquC8wXy7w_-723419751"
  nextVersions="_sWGpc1kyEeGeoaLUQk__nA_280962781"
  name="RequestForDuplicateV03"
  definition="Scope&#xD;&#xA;The Request For Duplicate message is sent by the case assignee to the case creator or case assigner.&#xD;&#xA;This message is used to request a copy of the original payment instruction considered in the case.&#xD;&#xA;Usage&#xD;&#xA;The Request For Duplicate message:&#xD;&#xA;- must be answered with a Duplicate message&#xD;&#xA;- must be used when a case assignee requests a copy of the original payment instruction. This occurs, for example, when the case assignee cannot trace the payment instruction based on the elements mentioned in the case assignment message&#xD;&#xA;- covers one and only one instruction at a time. If several payment instruction copies are needed by the case assignee, then multiple Request For Duplicate messages must be sent&#xD;&#xA;- must be used exclusively between the case assignee and its case creator/case assigner."
  registrationStatus="Registered"
  messageSet="_urpIICeJEeOCeO5e7islRQ"
  xmlTag="ReqForDplct"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_SMNVedE_Ed-BzquC8wXy7w_-119051006"
    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="_SMWfYNE_Ed-BzquC8wXy7w_-119050945"
    name="Case"
    definition="Identifies the investigation case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="1"
    xmlTag="Case"
    complexType="_SpAnptp-Ed-ak6NoX_4Aeg_-1565053133" />
  <messageDefinitionIdentifier
    businessArea="camt"
    messageFunctionality="033"
    flavour="001"
    version="03" />
</messageDefinition>

ISO Building Blocks

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