Duplicated Txn In NON STP Queue
(Doc ID 2983316.1)
Last updated on DECEMBER 28, 2023
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, Implementation Support
Patch set :14.7.0.2.0
ACTUAL BEHAVIOR
----------------------------
Duplicated txn in NON STP queue
In NON STP queue for the same reference system is showing duplicated transactions.
As per analysis:
It seems to display two records of the same Transaction reference number:2325801357701000 in screen PQSNSTPQ.
Same Queue reference number is created in table PQTB_QUEUE_ACTION_LOG for two different Transaction reference number: 2325801357701000 and 2325800576610003.
As the summary query in screen PQSNSTPQ is based on queue ref no, it is displaying duplicate records misleading the user.
Either the summary query has to be fixed or duplicate Queue reference number should not be allowed to be created if it already exists in PQTB_QUEUE_ACTION_LOG.
EXPECTED BEHAVIOR
---------------------------------
Either the summary query has to be fixed or duplicate Queue reference number should not be allowed to be created if it already exists in PQTB_QUEUE_ACTION_LOG.
BUSINESS IMPACT
---------------------------
The issue has the following business impact:
Due to this issue, in NON STP queue for the same reference system is showing duplicated transactions.
Changes
Fix is given in summary view to fetch unique records present in queue table and queue action log table.
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 |