PCM_OP_BAL_CHANGE_VALIDITY Opcode Not Setting Valid_from & Valid_to In ECE Cache (Doc ID 2150849.1)

Last updated on JANUARY 05, 2017

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.2.0.7.0 and later
Information in this document applies to any platform.

Symptoms

On :  11.2.0.7.5 version, Balance Management

ACTUAL BEHAVIOR  
---------------
Valid_from and Valid_to fields of PCM_OP_BAL_CHANGE_VALIDITY opcode are not syncing in ECE cache  

As per Business requirement need to change the Valid details.

Used below Flist to set Valid_from & Valid_to for PCM_OP_BAL_CHANGE_VALIDITY Opcode.

0 PIN_FLD_POID           POID [0] 0.0.0.1 /account 8483181 0
0 PIN_FLD_PROGRAM_NAME    STR [0] "TESTNAP"
0 PIN_FLD_SUB_BALANCES      ARRAY [1] allocated 32, used 32
1 PIN_FLD_VALID_FROM   TSTAMP [0] (1465401874)
1 PIN_FLD_VALID_TO      TSTAMP [0] (1465401974)
1 PIN_FLD_RESOURCE_ID   INT [0] 1000102
1 PIN_FLD_ELEMENT_ID    INT [0] 2
1 PIN_FLD_BAL_GRP_OBJ    POID [0] 0.0.0.1 /balance_group 8487924 0

In BRM, Valid_from & valid_to updating successfully but its not updating in ECE cache.

Getting below error in customerUpdater log

 

EXPECTED BEHAVIOR
-----------------------
Valid_from & Valid_to details should be set correctly in the ECE cache  

STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Create an account

2. Perform bill debit for resource id 1000102 to ensure there is balance as below
r << 1 1
0     PIN_FLD_POID           POID [0] 0.0.0.1 /service/telco/lte/data 8490357 9
0    PIN_FLD_LOGIN           STR [0] "2348040013017"
0 PIN_FLD_MODE                  ENUM [0] 1
1
nap(1644)> xop PCM_OP_BAL_GET_ECE_BALANCES 0 1
xop: opcode 1281, flags 0
# number of field entries allocated 20, used 5
0 PIN_FLD_POID           POID [0] 0.0.0.1 /service/telco/lte/data 8490357 9
0 PIN_FLD_MODE           ENUM [0] 1
0 PIN_FLD_BAL_IMPACTS   ARRAY [1000101] allocated 20, used 3
1     PIN_FLD_CREDIT_LIMIT DECIMAL [0] .0
1     PIN_FLD_CREDIT_PROFILE    INT [0] 20
1     PIN_FLD_CREDIT_FLOOR DECIMAL [0] 5.0
0 PIN_FLD_BAL_IMPACTS   ARRAY [1000102] allocated 20, used 5
1     PIN_FLD_CREDIT_LIMIT DECIMAL [0] 9223372036854775807
1     PIN_FLD_CURRENT_BAL  DECIMAL [0] .00
1     PIN_FLD_CREDIT_PROFILE    INT [0] 0
1     PIN_FLD_CREDIT_FLOOR DECIMAL [0] -9223372036854775808
1     PIN_FLD_SUB_BAL_IMPACTS  ARRAY [2] allocated 20, used 3
2         PIN_FLD_CONSUMED_RESERVED_AMOUNT DECIMAL [0] 0
2         PIN_FLD_AMOUNT       DECIMAL [0] .00
2         PIN_FLD_VALID_FROM   TSTAMP [0] (1463401874) Mon May 16 18:01:14 2016
0 PIN_FLD_BAL_IMPACTS   ARRAY [566] allocated 20, used 3
1     PIN_FLD_CREDIT_LIMIT DECIMAL [0] 0
1     PIN_FLD_CREDIT_PROFILE    INT [0] 2
1     PIN_FLD_CREDIT_FLOOR DECIMAL [0] -9223372036854775808

3. Then call PCM_OP_BAL_CHANGE_VALIDITY
 nap(8723)> r << 1 1
0     PIN_FLD_POID           POID [0] 0.0.0.1 /account 8483181 0
0 PIN_FLD_PROGRAM_NAME    STR [0] "TESTNAP"
0 PIN_FLD_SUB_BALANCES      ARRAY [1] allocated 32, used 32
1 PIN_FLD_VALID_FROM   TSTAMP [0] (1465401874)
1 PIN_FLD_VALID_TO      TSTAMP [0] (1465401874)
1 PIN_FLD_RESOURCE_ID   INT [0] 1000102
1 PIN_FLD_ELEMENT_ID    INT [0] 2
1 PIN_FLD_BAL_GRP_OBJ    POID [0] 0.0.0.1 /balance_group 8487924 0 1
nap(8723)> xop PCM_OP_BAL_CHANGE_VALIDITY 0 1
xop: opcode 3703, flags 0
# number of field entries allocated 20, used 2
0 PIN_FLD_POID           POID [0] 0.0.0.1 /event/billing/sub_bal_validity 297976447228808909 0
0 PIN_FLD_DESCR           STR [0] "success"              


BUSINESS IMPACT
-----------------------
The issue has the following business impact:

Customer needs this functionality to track the usage of resources per month and they are not able to achieve it due to this issue.

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