An Incoming MT192 Generated An Outgoing MT196 To SWIFT Tracker Instead Of Sender Of MT192
(Doc ID 2790291.1)
Last updated on JULY 17, 2021
Applies to:Oracle Banking Payments - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 14]
Information in this document applies to any platform.
On : 126.96.36.199.0 version, Production Support
OBP has generated MT196s to the Sender of incoming MT192s when bank accepted the Inbound Cancellation Requests in PQSICLRQ.
There is a recent case when bank received an MT192 from DEUTDEFFXXX requesting the cancellation of their MT103. Bank accepted it because the payment was in Repair Queue and could not be executed as it was.
OBP generated an outgoing MT196 but this time not to DEUTDEFFXXX (sender of MT192) but to TRCKCHZZXXX (SWIFT Tracker) which is a problem because bank is not GPI member and bank can send just MT199 to GPI service. SWIFT Tracker was already notified with MT199 RJCT about the cancellation of payment.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document