Integrating Requests for Cancellation

This section guides you through the setup and integration of request for cancellation messages MT392 and MT692.

 

1. Setup Requirements

Add the following values to the domain "IncomingSwiftTrade":

Value = MT392

Value = MT692

 

Add the following values to the domain "incomingType:

Value = MT392, Comment = IncomingConfirmation

Value = MT692, Comment = IncomingConfirmation

 

The message workflow for IncomingConfirmation messages should already be defined.

 

2. Integration

Processing a MT392/MT692 message is the same than processing a confirmation with TAG 22A=CANC.

When integrating a MT392/692, TAG 21 is stored in ExtMsg RelatedRef and we check if this value is already in the system:

•

If true, we store in Msg Linked Id attribute the message id corresponding of this RelatedRef and we apply the CANCEL action

•

If not, message is identified as a process issue OutOfSequence, and not eligible for the matching. When integrating the corresponding NEWT message, it is flagged as OutOfSequence process issue and not eligible for the matching as well.