OBPM - PBDOTONL - ECA Block is not Auto Releasing During Network Cut Off is maintained as Cancel
(Doc ID 3050572.1)
Last updated on OCTOBER 01, 2024
Applies to:
Oracle Banking Payments - Version 14.6.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
OBPM - PBDOTONL - ECA Block Auto Release is Not Happening
Transaction Booked in PBDOTONL has moved to network cutoff queue. And the amount is blocked in the debit account.
As per the maintenance in PMDSORCE ->System Action is maintained as "Cancel", system has marked the system action in PQSNETCQ as Cancelled.
But the Current Status still remained as "Pending" and also the ECA block is also no released.
EXPECTED BEHAVIOR
-----------------------
Bank expectation is to release the ECA block automatically if the transaction is moved to network cut off / accounting is pending.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Booked a transaction in PBDOTONL.
2. Approved the transaction and the transaction moved to network cutoff queue.
3. The amount was blocked in the debit account.
4. In PMDSORCE, auto queue preferences, system action is maintained as "CANCEL" (PMDSORCE2 image).
5. When we check the transaction in PQSNETCQ, current status is pending (capture1) and system action is 'Cancelled' (Capture2).
6. If transaction is cancelled, then the ECA block should release automatically
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, transactions have remained as Pending in PQSNETCQ and ECA block is not released
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |