System Allows New Reversal Request When Existing Reversal Request In Unauth Status
(Doc ID 2717024.1)
Last updated on JUNE 22, 2021
Applies to:
Oracle Banking Payments - Version 14.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.3.0.0.0 version, Implementation Support
ACTUAL BEHAVIOR
---------------
System allows to save reversal request even though an existing request is in Unauthorized status.
EXPECTED BEHAVIOR
-----------------------
System should check for any existing unauthorized reversal transaction.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Initiate an Reversal request for processed Book Transfer transaction - and cancel the reversal request from Sanction queue or any applicable queue.
2. Initiate & Save another reversal request for the Transaction (Using same user Id)
3. Create new request when previous request is in Unauthorized status (Using same user Id)
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, user is able to post multiple reversal transaction for a book transfer transaction.
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 |