RequestForDuplicateV06

camt.033.001.06

Scope The RequestForDuplicate 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 RequestForDuplicate 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 RequestForDuplicate 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
%% RequestForDuplicateV06 recursion level 0 with max 0
RequestForDuplicateV06 *-- "1..1" CaseAssignment5 : Assignment
RequestForDuplicateV06 *-- "0..1" Case5 : Case
RequestForDuplicateV06 *-- "0..1" SupplementaryData1 : SupplementaryData

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. Represents the assignment of a case to a party. For comparison, see the ISO20022 official specification

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

CaseAssignment5 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. Provides further details to identify an investigation case. For comparison, see the ISO20022 official specification

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

Case5 members

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

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

classDiagram
    class IOuterRecord
    RequestForDuplicateV06 --|> IOuterRecord : Implements
    RequestForDuplicateV06Document --|> IOuterDocument~RequestForDuplicateV06~ : Implements
    class IOuterDocument~RequestForDuplicateV06~ {
        RequestForDuplicateV06 Message
     }

Document wrapper for serialization

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

classDiagram
    RequestForDuplicateV06Document *-- RequestForDuplicateV06 : 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.06">
    <ReqForDplct>
        <Assgnmt>
            <!-- Assignment inner content -->
        </Assgnmt>
        <Case>
            <!-- Case inner content -->
        </Case>
        <SplmtryData>
            <!-- SupplementaryData inner content -->
        </SplmtryData>
    </ReqForDplct>
</Document>

Data from ISO specification

This is the technical data from the specification document.

<messageDefinition
  xmi:id="_eX_OpW2PEei3KuUgpx7Xcw"
  previousVersion="_nNMjcaqDEeeMmtkfa8-zPg"
  name="RequestForDuplicateV06"
  definition="Scope&#xD;&#xA;The RequestForDuplicate 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 RequestForDuplicate 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 RequestForDuplicate messages must be sent&#xD;&#xA;- must be used exclusively between the case assignee and its case creator/case assigner."
  registrationStatus="Registered"
  messageSet="_moz48_2VEeGjgKzdN0DbWA"
  xmlTag="ReqForDplct"
  rootElement="Document"
  xmlns:xmi="http://www.omg.org/XMI">
  <messageBuildingBlock
    xmi:id="_eX_Op22PEei3KuUgpx7Xcw"
    previousVersion="_nNMjc6qDEeeMmtkfa8-zPg"
    name="Assignment"
    definition="Identifies the assignment of an investigation case from an assigner to an assignee.&#xD;&#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="_BzPdIW49EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_eX_OqW2PEei3KuUgpx7Xcw"
    previousVersion="_nNMjdaqDEeeMmtkfa8-zPg"
    name="Case"
    definition="Identifies the investigation case."
    registrationStatus="Provisionally Registered"
    maxOccurs="1"
    minOccurs="0"
    xmlTag="Case"
    complexType="_8BF4W248EeiU9cctagi5ow" />
  <messageBuildingBlock
    xmi:id="_eX_Oq22PEei3KuUgpx7Xcw"
    previousVersion="_nNMjd6qDEeeMmtkfa8-zPg"
    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="033"
    flavour="001"
    version="06" />
</messageDefinition>

ISO Building Blocks

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