OBPM: Clearing Query Not Giving The Actual Reject Reason.
(Doc ID 3047250.1)
Last updated on SEPTEMBER 17, 2024
Applies to:
Oracle Banking Payments - Version 14.7.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.7.0.0.0 version, Implementation Support
ACTUAL BEHAVIOR
---------------
Clearing Query not giving the actual reject reason.
We have performed an outward clearing transaction using API.
Though the transaction was not performed we received 'Transaction Processed and Authorized . PM-SAVE-002' message as response but actually the transaction was not performed.
Then we execute the query service but there also we didn't find the actual reject reason. But from front end view screen we got the actual reject reason.
EXPECTED BEHAVIOR
-----------------------
Clearing Query from API should give the Error message
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Do a Clearing Transaction which results in Error
2.Query the Transaction and check for the Error reason
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot find the Error reason based on API response
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 |