Modifications Done In Verification Queue Is Not Updating The PXDOTONL Contract Value As Well As MT.
(Doc ID 3037486.1)
Last updated on JULY 26, 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
Modifications done in Verification Queue is not updating the PXDOTONL contract value as well as MT.
PXDOTONL outgoing transaction moved to Verification Queue after save and authorize based on source code used (verification rule). Amendment field enabled in PMDVFAMD Screen as well.
After modification and authorization the amended field value is not getting updated in the PXDOTONL contract.
ERROR
-----------------------
java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (PK01_PXZB_OUT_TXN_CHG) violated
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create verification rule based on Source code
2.Do a Transaction and auth the same
3. Go to Verification queue modify the details and try to proceed
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot authorize the verification queue
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 |