Txn Pending In EC & EA- Duplicate QueueReferencenumber
(Doc ID 2936492.1)
Last updated on MARCH 24, 2023
Applies to:
Oracle Banking Payments - Version 14.4.0.0.0 and laterInformation in this document applies to any platform.
Queue ref no is generated the same for two different txns created at the same time.
In this case both the txns were in the same server and was at the same time and synchronized integer has returned same value as per the queuerefno.
Due to this below error is raised and captured in pmtb_exception_log.
Symptoms
Case:
BOOK payment initiated from channel and BOOk_CUST network payment processed from SI job PMDSIECT has generated same queue ref no for EC and EA requests.
Both txns were intitiated at different time but EA and EC requests for both were generated at the same time with Queuerefno as 2305401933923001
Reference number split is as -->
calendar year and julian date 23054
server id 01
hardcoded param 9
seconds from midnight 33923
synchronized sequence 001
In this case both the txns were in the same server and was at the same time and synchronized integer has returned same value as per the queuerefno.
Due to this below error is raised and captured in pmtb_exception_log.
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 |
| Cause |
| Solution |