27. NACKed Message Repair

 

27.1 Message Repair

This feature repair Outbound SWIFT CBPRPlus / TARGET2 ISO messages sent out to the network and got NACKed.

27.1.1 NACKed Message Processing

NACKed Message follows below processing steps:

l Section 27.1.1.1, "Incoming Negative Acknowledgement Processing"

l Section 27.1.1.2, "Outbound Message Repair Processing"

l Section 27.1.1.3, "Outbound Message Resend Processing"

27.1.1.1 Incoming Negative Acknowledgement Processing

l After receiving the negative acknowledgment and matching with the original outbound SWIFT CBPRPlus / TARGET2 ISO message, the system logs the original Outbound message in the  Outbound Messages Repair Queue.

Note

Negative Acknowledgement message refers to NACK from SWIFT FINPlus/Interact,  admi.007 (Receipt Acknowledgement) from TARGET2 and admi.002 (Message Rejection).

 

l A new queue reference is generated, and the below fields of the outbound message get populated.

– Original Transaction Reference as Reference Number

– UETR

– Message Format (Value as MX)

– SWIFT Message Type

– Network

– Branch

– Receiver (Instructed Agent or To BIC)

– Currency

– Amount

– Acknowledgement Status

– Network Acknowledgement Status

– Current Status as 'Pending'

Note

If the NACKed message is embedded in the DataPDU header, the DataPDU gets removed and the payload (Business Application Header and payment message) is logged in the Message Repair Queue.

 

27.1.1.2 Outbound Message Repair Processing

l The system generates a new Document Number (DCN). The generated Document Number (DCN) gets auto populated in the repaired message.

l Below table lists the SWIFT CBPRPlus message types and the tag details that gets updated with the generated Document Number (DCN).

l Below table lists the TARGET2 message types and the tag details that get updated with the generated Document Number (DCN):

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.

 

l The 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

l The SWIFT Message Notification Browser (MSSNOTIB) is also updated. The Acknowledgement Status and the Acknowledgement Message values get updated.

l The original message that got NACKed is marked as suppressed in Outbound Message Browser (PMSOUTBR).

27.1.1.3 Outbound Message Resend Processing

l The Outbound Message Resend Processing is same as the Repair Processing.

27.1.2 Outbound Message Repair Queue

This screen populates the Outbound SWIFT CBPRPlus / TARGET2 ISO messages that are NACKed.

You can invoke “Outbound Message Repair Queue” screen by typing the function ID ‘PQSMSONK’ in the field at the top right corner of the Application tool bar and clicking on the adjoining arrow button.

You can search using one or more of the following parameters:

l Queue Reference Number

l Document Number (DCN)

l Original DCN

l Reference Number

l UETR

l Branch

l Receiver

l Media

l Message Format

l Message Type

l SWIFT MX Type

l Network

l Currency

l Amount

l Network Type Code

l Acknowledgement Status

l Network Acknowledgement Status

l Current Status

l Authorization Status

l Verification Status

l Transaction Type

l Network Acknowledgement Message Type

l Maker ID

l Checker ID

Once you have specified the search parameters, click ‘Search’ button. The system displays the records that match the search criteria.

Double click a record or click the ‘Details’ button after selecting a record to view the detailed screen.

The following actions can be performed for the selected transactions: