camt.033.001.04
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 %% RequestForDuplicateV04 recursion level 0 with max 0 RequestForDuplicateV04 *-- "1..1" CaseAssignment3 : Assignment RequestForDuplicateV04 *-- "1..1" Case3 : Case RequestForDuplicateV04 *-- "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 %% CaseAssignment3 recursion level 0 with max 1 class CaseAssignment3{ Identification IsoMax35Text CreationDateTime IsoISODateTime } CaseAssignment3 *-- "1..1" IParty12Choice : Assigner CaseAssignment3 *-- "1..1" IParty12Choice : Assignee %% IParty12Choice recursion level 1 with max 1 %% IParty12Choice recursion level 1 with max 1
CaseAssignment3 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 %% Case3 recursion level 0 with max 1 class Case3{ Identification IsoMax35Text ReopenCaseIndication IsoYesNoIndicator } Case3 *-- "1..1" IParty12Choice : Creator %% IParty12Choice recursion level 1 with max 1
Case3 members
Member name | Description | Data Type / Multiplicity |
---|---|---|
Identification | Uniquely identifies the case. | IsoMax35Text - Required 1..1 |
Creator | Party that created the investigation case. | IParty12Choice - 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 RequestForDuplicateV04 implementation follows a specific implementaiton pattern. First of all, RequestForDuplicateV04 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, RequestForDuplicateV04Document implements IOuterDocument. Because RequestForDuplicateV04 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type RequestForDuplicateV04.
classDiagram class IOuterRecord RequestForDuplicateV04 --|> IOuterRecord : Implements RequestForDuplicateV04Document --|> IOuterDocument~RequestForDuplicateV04~ : Implements class IOuterDocument~RequestForDuplicateV04~ { RequestForDuplicateV04 Message }
Document wrapper for serialization
The only real purpose RequestForDuplicateV04Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:camt.033.001.04’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using RequestForDuplicateV04.ToDocument() method. The returned RequestForDuplicateV04Document value will serialize correctly according to ISO 20022 standards.
classDiagram RequestForDuplicateV04Document *-- RequestForDuplicateV04 : 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.04">
<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="_sWGpc1kyEeGeoaLUQk__nA_280962781"
nextVersions="_nNMjcaqDEeeMmtkfa8-zPg"
previousVersion="_SMNVeNE_Ed-BzquC8wXy7w_-723419751"
name="RequestForDuplicateV04"
definition="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."
registrationStatus="Registered"
messageSet="_urpIICeJEeOCeO5e7islRQ"
xmlTag="ReqForDplct"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_sWGpdFkyEeGeoaLUQk__nA_1599523567"
nextVersions="_nNMjc6qDEeeMmtkfa8-zPg"
name="Assignment"
definition="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."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Assgnmt"
complexType="_sbKvolkyEeGeoaLUQk__nA_1583838951" />
<messageBuildingBlock
xmi:id="_sWGpdVkyEeGeoaLUQk__nA_716290280"
nextVersions="_nNMjdaqDEeeMmtkfa8-zPg"
name="Case"
definition="Identifies the investigation case."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="Case"
complexType="_tijOcFkyEeGeoaLUQk__nA_-1838378407" />
<messageBuildingBlock
xmi:id="_sWGpdlkyEeGeoaLUQk__nA_484850933"
nextVersions="_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="04" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.