Outbound Message Repair Processing
- System generates a new Document Number (DCN). The generated Document Number (DCN) gets auto populated in the repaired message.
- Below table lists the SWIFT CBPRPlus message types and the tag details that gets updated with the generated Document Number (DCN).
| Message Type | Node | Tag Name | Tag |
|---|---|---|---|
| pacs.008 | Business Application Header | Business Message Identifier | BizMsgIdr |
| pacs.008 | Group Header | Message Identification | MsgId |
| pacs.009 | Business Application Header | Business Message Identifier | BizMsgIdr |
| pacs.009 | Group Header | Message Identification | MsgId |
| pacs.004 | Business Application Header | Business Message Identifier | BizMsgIdr |
| pacs.004 | Group Header | Message Identification | MsgId |
| pacs.002 | Business Application Header | Business Message Identifier | BizMsgIdr |
| pacs.002 | Group Header | Message Identification | MsgId |
| pain.001 | Business Application Header | Business Message Identifier | BizMsgIdr |
| pain.001 | Group Header | Message Identification | MsgId |
| pain.002 | Business Application Header | Business Message Identifier | BizMsgIdr |
| pain.002 | Group Header | Message Identification | MsgId |
| camt.056 | Business Application Header | Business Message Identifier | BizMsgIdr |
| camt.029 | Business Application Header | Business Message Identifier | BizMsgIdr |
| camt.054 | Business Application Header | Business Message Identifier | BizMsgIdr |
| camt.054 | Group Header | Message Identification | MsgId |
Below table lists the TARGET2 message types and the tag details that get updated
with the generated Document Number (DCN):
| Message Type | Node | Tag Name | Tag |
|---|---|---|---|
| pacs.008 | Business Application Header | Business Message Identifier | BizMsgIdr |
| pacs.009 | Business Application Header | Business Message Identifier | BizMsgIdr |
| pacs.004 | Business Application Header | Business Message Identifier | BizMsgIdr |
| pacs.002 | Business Application Header | Business Message Identifier | BizMsgIdr |
| camt.056 | Business Application Header | Business Message Identifier | BizMsgIdr |
| camt.029 | Business Application Header | Business Message Identifier | BizMsgIdr |
| camt.050 | Business Application Header | Business Message Identifier | BizMsgIdr |
| camt.003 | Business Application Header | Business Message Identifier | BizMsgIdr |
| admi.005 | Business Application Header | Business Message Identifier | BizMsgIdr |
Note:
As per the TARGET2 rule book, the system populates 'NONREF' value in the Message Identification tag. So, this tag value is not overwritten with the newly generated Document Number (DCN) value.- System populates a regenerated message in the Outbound Message Browser
(PMSOUTBR) against the newly generated Document Number (DCN):
- Message Status is updated as 'Generated'
- Acknowledgement Status is updated as 'Pending'
- Network Acknowledgement Status is updated as Blank
- The SWIFT Message Notification Browser (MSSNOTIB) is also updated. The Acknowledgement Status and the Acknowledgement Message values get updated.
- The original message that got NACKed is marked as suppressed in Outbound Message Browser (PMSOUTBR).
Parent topic: NACKed Message Processing