New PRCITEM_PARM_GRP_ID Getting Stamped In PRITM And SUMMARY For Existing PARM_STR In _K Table
(Doc ID 2760983.1)
Last updated on MARCH 26, 2021
Applies to:
Oracle Financial Services Revenue Management and Billing - Version 2.9.0.0.0 and laterInformation in this document applies to any platform.
Goal
On : 2.9.0.0.0 version, BT - Batch
New PRCITEM_PARM_GRP_ID getting stamped in PRITM and SUMMARY for existing PARM_STR in _K table
Customer faced an issue in TXNVP job. It failed due to new PRICEITEM_PARM_GRP_ID being stamped in CI_TXN_DTL_PRITM and CI_TXN_DTL_PRITM_SUMMARY tables for which there's no entry in CI_PRICEITEM_PARM_GRP_K table. Looking at the aggregation parameters, this table (PRICEITEM_PARM_GRP_K) already had a different ID for the same PARM_STR.
Looking at base code to generate ID, it appears that this situation might occur if multiple transactions will result in same PARM_STR and db takes time between checking for existing PARM_STR and generating a new one. As per code, if new insert fails, function still returns the generated PRICEITEM_PARM_GRP_ID for which there is no entry in CI_PRICEITEM_PARM_GRP_K table. Highlighted those specific sections in image attached.
Solution
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
| Goal |
| Solution |
| References |