My Oracle Support Banner

New PRICEITEM_PARM_GRP_ID Getting Stamped In PRITM And SUMMARY For Existing PARM_STR In _K Table (Doc ID 2570375.1)

Last updated on JULY 30, 2019

Applies to:

Oracle Financial Services Revenue Management and Billing - Version 2.5.0.3.0 and later
Information in this document applies to any platform.

Symptoms

On : 2.5.0.3.0 version, BT - Batch

ACTUAL BEHAVIOR
---------------
New PRICEITEM_PARM_GRP_ID getting stamped in PRITM and SUMMARY for existing PARM_STR in _K table.

In TXNVP job (which is at 2.5.0.3) Failure was due to a new PRICEITEM_PARM_GRP_ID being stamped in the CI_TXN_DTL_PRITM and CI_TXN_DTL_PRITM_SUMMARY tables for which there is 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.

After reviewing the base code to generate ID, it appears that this situation might occur if multiple transactions result in the same PARM_STR and the db takes time between checking for the existing PARM_STR and generating a new one. As per the code, if a new insert fails, the function still returns the generated PRICEITEM_PARM_GRP_ID for which there is no entry in the CI_PRICEITEM_PARM_GRP_K 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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.