Duplicate Check Field For DDA Payments
(Doc ID 2999672.1)
Last updated on JANUARY 30, 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.2.0 version, Production Support
ACTUAL BEHAVIOR
---------------
Duplicate Check Field for DDA payments
We've maintained Duplicate Check Fields for MANL source code. The check is needed to be done against SOURCE_REFERENCE_NUMBER field.
The issue is due to duplicate payments without validating the 'Duplicate Check Fields' maintained in source level.
Meanwhile as it is shown in the printscreen, both payments are successfully processed.
EXPECTED BEHAVIOR
-----------------------
Based on the parametrizations, System should reject the second payment as duplicate.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Maintain Duplicate check fields for Source reference number for MANL source code in PMDSORCE screen.
2. Try to do the transaction and view the transactions.
Two transactions are processed.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users will get duplicate transaction in same ref number.
Changes
Fix :- Based on the parametrizations, System should reject the second payment as duplicate.
Components Affected
-------------------
ddduplicatecheckservice.java;
abstractachdebitintxnprocessor.java;
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 |
References |