How To Avoid The Intermittent Error In PCM_OP_BAL_CHANGE_VALIDITY Triggered By Pin_cycle_fees? (Doc ID 1321961.1)

Last updated on DECEMBER 16, 2011

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.2.0.0.0 and later   [Release: 7.2.0 and later ]
Information in this document applies to any platform.

Goal

How to avoid the intermittent error in op_bal_change_validity triggered by pin_cycle_fees?

e.g.
When running pin_cycle_fees, in some instances the PCM_OP_BAL_CHANGE_VALIDITY will report the following error:
E Mon Apr 11 14:34:00 2011 pinappdr cm_bill:26741 fm_bal_change_validity.cpp:196 1:pinappdr:pin_cycle_fees:26709:-143918192:924:1302521640:4
   fm_bal_change_validity_new_format
   <location=PIN_ERRLOC_FLIST:6 class=PIN_ERRCLASS_SYSTEM_DETERMINATE:1 errno=PIN_ERR_NOT_FOUND:3>
   <field num=PIN_FLD_SUB_BALANCES:9,7753 recid=0 reserved=0 reserved2=0 time(sec:usec)=0:0>
   <facility=0 msg_id=0 version=0>


Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms