Issue with Sub-Balance Validation During Service Closure

(Doc ID 2146555.1)

Last updated on JULY 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 7.5.0.8.0 version, Balances

There is a different behavior between 7.4 and 7.5 where the sub balances validities are rounded to the start of the day on the day of service closure in 7.5.
In 7.4, it used to be time of the disconnect order to which sub balance validities are set.

In 7.4, Snippet of cm.pinlog
D Sat Apr 16 00:31:23 2016 xxxx master_cm:19769 fm_subscription_utils.cpp:2790 1:xxxx:testnap:19754:1:120001:1460730682:1
  op_bal_change_validity input
# number of field entries allocated 20, used 7
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 418071 0
0 PIN_FLD_BAL_GRP_OBJ POID [0] 0.0.0.1 /balance_group 422810 3
0 PIN_FLD_ELEMENT_ID INT [0] 2
0 PIN_FLD_RESOURCE_ID INT [0] 3000009
0 PIN_FLD_SUB_BALANCES ARRAY [0] allocated 20, used 2
1        PIN_FLD_VALID_TO TSTAMP [0] (1461679200) Wed Apr 27 00:00:00 2016
1        PIN_FLD_VALID_FROM TSTAMP [0] (1460728800) Sat Apr 16 00:00:00 2016
0 PIN_FLD_PROGRAM_NAME STR [0] "change_validity"
0 PIN_FLD_SUB_BALANCES ARRAY [1] allocated 20, used 2
1        PIN_FLD_VALID_FROM TSTAMP [0] (1460728800) Sat Apr 16 00:00:00 2016
1        PIN_FLD_VALID_TO TSTAMP [0] (1460730667) Sat Apr 16 00:31:07 2016 <======== in 7.4, correct behavior, it used time of the disconnect order

In 7.5, Snippet of cm.pinlog
D Sat Apr 16 00:36:20 2016 yyyyy master_cm:5966 fm_subscription_utils.cpp:3223 1:xxxx:testnap:5954:1:120001:1460730979:1
  op_bal_change_validity input
# number of field entries allocated 20, used 8
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 7943593 1
0 PIN_FLD_SERVICE_OBJ POID [0] 0.0.0.1 /service/subscription 7947286 0
0 PIN_FLD_BAL_GRP_OBJ POID [0] 0.0.0.1 /balance_group 7948262 5
0 PIN_FLD_ELEMENT_ID INT [0] 2
0 PIN_FLD_RESOURCE_ID INT [0] 3000009
0 PIN_FLD_SUB_BALANCES ARRAY [0] allocated 20, used 2
1        PIN_FLD_VALID_TO TSTAMP [0] (1461679200) Wed Apr 27 00:00:00 2016
1        PIN_FLD_VALID_FROM TSTAMP [0] (1460728800) Sat Apr 16 00:00:00 2016
0 PIN_FLD_PROGRAM_NAME STR [0] "change_validity"
0 PIN_FLD_SUB_BALANCES ARRAY [1] allocated 20, used 2
1        PIN_FLD_VALID_FROM TSTAMP [0] (1460728800) Sat Apr 16 00:00:00 2016
1        PIN_FLD_VALID_TO TSTAMP [0] (1460728800) Sat Apr 16 00:00:00 2016 <===========rounded to the start of the day

ACTUAL BEHAVIOR
-----------------------
The sub balances validities are rounded to the start of the day on the day of service closure in 7.5

EXPECTED BEHAVIOR
---------------------------
As per the 7.4 behavior

STEPS
--------
The issue can be reproduced at will with the following steps:
1. Purchase a product which grants 1 GB with the validity mentioned in the balance impact as 1 event cycle
2. Purchase this product and verify the bal_grp_sub_bals_t to see valid from and valid_to are set to the correct dates according to the bill cycle
3. Now close the service and verify the validities dates in the bal_grp_sub_bals_t to see the valid_to as shown is rounded off


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