Inbound Cancellation-Transaction Is in an Internal Exception Queue
(Doc ID 2575082.1)
Last updated on MAY 22, 2020
Applies to:Oracle Banking Payments - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Steps to simulate :-
1. Txn In BO queue
2. CANCEL from BO queue and keep it as Unauthorized
3. Now inject MT192, go to SCQ and PASS the same
4. In PXSICLBR, MT192, process status changes to 'MATCHED'
5. In PXDIVIEW, MT103, Recall Status changes to 'Recall Requested'
6. Now Delete MT103 from BO queue
Expectation as per FDD :-
User Action : Delete
System will check if any cancellation request is pending for the transaction. If any cancellation request found, then the following actions will be taken on the transaction.
• Recall Status at transaction will be updated as ‘Recall Requested’
• Process Status at Inbound Cancellation Browser will be updated as ‘Transaction Locked’ (NOT happening)
• Transaction will be moved of the internal queue and will be moved to the Inbound Cancellation Request queue (NOT available in this Queue)
• Transaction Status will be updated as ‘Exception’, last queue code as the Internal queue code and Current status as ‘Pending’ in the Inbound Cancellation Request queue
• Queue action will be logged for transaction moving out of the internal queue and for moving to Inbound Cancellation Request queue (Txn NOT moving out of internal Queue)
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