C1-TXNIP Batch Duplicate Transaction Issue
(Doc ID 2846981.1)
Last updated on DECEMBER 01, 2023
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 2.8.0.0.0 to 2.8.0.0.0 [Release 2]Information in this document applies to any platform.
Symptoms
On : 2.8.0.0.0 version,
ACTUAL BEHAVIOR
---------------
When it is used the Base Algorithm Spot TFM – Product Derivation Post Processing to perform custom aggregation of transactions, these algorithms on this spot are invoked while running C1-TXNIP batch.
However, when there is any error in algorithms plugged at this spot, the C1-TXNIP batch marks those transactions into ERROR status in CI_TXN_DETAIL.
While doing so, it should remove those transactions from CI_TXTN_DETAIL_STG which is not happening.
The same transactions remain in CI_TXN_DETAIL and CI_TXN_DETAIL_STG at the same time, which is incorrect.
Further when Rollback batch is run, the transactions are moved back to CI_TXN_DETAIL_STG.
Now for the same TXN_DETAIL_ID there are duplicates in CI_TXN_DETAIL_STG table as this table does not have any primary key.
This issue is observed only when the batch is run in global mode i.e. without giving any parameter.
When run using a particular Transaction header ID it runs fine.
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 |
| References |