Error While Managing Balance Bucket through PCM_OP_BAL_CHANGE_VALIDITY opcode inside a Transaction Block (Doc ID 790823.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.0.0.0 to 7.3.0.0.1 - Release: 7.3.0 to 7.3.0
Information in this document applies to any platform.
Checked for relevance on 23-Mar-2012

Symptoms

An error is encountered while managing the balance bucket through PCM_OP_BAL_CHANGE_VALIDITY opcode inside a transaction block. Following replication steps can explore the scenario -

Steps To Reproduce: 

Step-1: Create an account on 16th Feb08

Step-2: Call PCM_OP_BILL_SET_LIMIT_AND_CR opcode to purchase following resource ids - 840,
1000092, 1000099, 1000101

Step-3: On date 16th Feb08 create 5 balance buckets for that account with PCM_OP_BILL_DEBIT :
res_id 840 with VALID_FROM = 16/02/2008 and VALID_TO = 31/12/2035
res_id 1000092 with VALID_FROM = 17/02/2008 and VALID_TO = 17/02/2008
res_id 1000099 with VALID_FROM = 16/02/2008 and VALID_TO = 17/02/2008
res_id 1000099 with VALID_FROM = 17/02/2008 and VALID_TO = 17/02/2008
res_id 1000101 with VALID_FROM = 17/02/2008 and VALID_TO = 17/03/2008

Step-4: Moved to 17th Feb08.

Step-5: Locked the account as bellow :-
nap(18006)> open lock - 0.0.0.1 /account 20612609320938

Step-6: On date 17/02/2008 called of PCM_OP_BAL_CHANGE_VALIDITY opcode to modify the range of
balance bucket for res_id 1000099 with VALID_FROM = 17/02/2008 and VALID_TO = 17/02/2008 in order
to have VALID_FROM = 17/02/2008 and VALID_TO = 18/02/2008

Step-7: On date 17/02/2008 call of PCM_OP_BAL_CHANGE_VALIDITY opcode to modify the range of
balance bucket for res_id 1000092 with VALID_FROM = 17/02/2008 and VALID_TO = 17/02/2008 in order
to have VALID_FROM = 17/02/2008 and VALID_TO = 18/02/2008
nap(18124)> d 1
# number of field entries allocated 20, used 7
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 20612609320938 0
0 PIN_FLD_PROGRAM_NAME STR [0] "ADD_PRODLIST"
0 PIN_FLD_BAL_GRP_OBJ POID [0] 0.0.0.1 /balance_group 20630533021462 0
0 PIN_FLD_RESOURCE_ID INT [0] 1000092
0 PIN_FLD_ELEMENT_ID INT [0] 4
0 PIN_FLD_SUB_BALANCES ARRAY [0] allocated 20, used 2
1 PIN_FLD_VALID_FROM TSTAMP [0] (1203186603) Sun Feb 17 00:00:03 2008
1 PIN_FLD_VALID_TO TSTAMP [0] (1203186603) Sun Feb 17 00:00:03 2008
0 PIN_FLD_SUB_BALANCES ARRAY [1] allocated 20, used 2
1 PIN_FLD_VALID_FROM TSTAMP [0] (1203186603) Sun Feb 17 00:00:03 2008
1 PIN_FLD_VALID_TO TSTAMP [0] (1203273002) Mon Feb 18 00:00:02 2008
nap(18006)> xop PCM_OP_BAL_CHANGE_VALIDITY 0 1
xop: opcode 3703, flags 0
XOP "3703" failed: err 3:PIN_ERR_NOT_FOUND, field 0/199:PIN_FLD_CURRENT_BAL,
loc 6:PIN_ERRLOC_FLIST, errclass 1:PIN_ERRCLASS_SYSTEM_DETERMINATE, rec_id 0, resvd 0
# number of field entries allocated 20, used 2
0 PIN_FLD_POID POID [0] 0.0.0.1 /error_poid 20612609320938 0
0 PIN_FLD_ERR_BUF ERR [0]
<location=PIN_ERRLOC_FLIST:6 class=PIN_ERRCLASS_SYSTEM_DETERMINATE:1
errno=PIN_ERR_NOT_FOUND:3>
<field num=PIN_FLD_CURRENT_BAL:14,199 recid=0 reserved=0 reserved2=0
time(sec:usec)=0:0>
<facility=0 msg_id=0 version=0>


Error  occurred at step-7



Cause

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