ACH Dispatch ::Files Are Not Getting Dispatched If Multiple Transactions Present
(Doc ID 2977552.1)
Last updated on OCTOBER 04, 2023
Applies to:Oracle Banking Payments - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Implementation Support
ACH Dispatch issue ::Files are not getting dispatched if multiple transactions present
Bank has set the transaction allowed count as 1 in the PMDACHDP (ACH Dispatch Parameter). And dispatch time is set for every 15 minutes interval.
When user creates the multiple transactions , system fails to insert the data into PMTB_ISO_DISPATCH_KEY table and throws unique constraint error in the debug.
all the transaction which are created during this period will have the EXTENDED_DISPATCH_DATETIME as NULL and these will not be dispatched.
If you create single transaction at any point of time, these will be dispatched.
javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.6.7.v20190604-418f1a1c56): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (PK_PMTB_ISO_DISPATCH_KEY) violated
The issue can be reproduced at will with the following steps:
1. Maintain Transaction count allowed as 1
2.Perform 3 Multiple transaction at same time
3. Verify the Dispatched file
4. Perform a Single Transaction and verify the Dispatch file
The issue has the following business impact:
Due to this issue, users cannot dispatch file when multiple transactions are there
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