Resolution of Investigation (camt.029) Message Upload
Inbound Resolution of Investigation (camt.029) message is received with TARGET2 business header.
After receiving the Inbound Resolution of Investigation (camt.029) message the message is created and logged in the incoming message tables.
System does format validations for the camt.029 message received based on the schema details maintained for the message in File Parameter Detailed (PMDFLPRM) maintenance. If any of the format validations fail, error details are recorded in the incoming message tables.
On completing the format validations, the message is parsed and uploaded. Users can view the message status from the Generic Wires ISO Inbound Browser Summary (PGWINBRW) screen.
After parsing the inbound camt.029 message is matched with the original camt.056 message using the following matching criteria:
- Original UETR received in the incoming message is matched with Original UETR of outgoing camt.056 message
If the inbound camt.029 message matching fails, then camt.029 record status is marked as ‘Exception’. The system error code and error details are logged.
Note:
Error Description
Matching of Original UETR failed for the Resolution of Investigation (camt.029) message received.
- The status of the uploaded camt.029 is ‘Matched’.
- Process Status of the uploaded camt.029 is ‘Processed’.
- The inbound camt.029 message get linked with outgoing camt.056 message.
Source Code is derived as currently done for PX module where the Source Maintenance Detailed (PMDSORCE) maintenance is referred with Incoming SWIFT flag as checked.
The Network Code for the payment is derived as the Network Code of the original pacs.008/pacs.009 messages.
Parent topic: Outbound Cancellation Response Processing