Annual Cycle Forward is Wrongly Charged When Purchased On 29th,30th or 31st Day Of Month
(Doc ID 1921809.1)
Last updated on FEBRUARY 03, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.5.0.0.0 [Release 7.3.1 to 7.5.0]Information in this document applies to any platform.
Symptoms
Purchasing of annual cycle forward product on 29th, 30th or 31st day of month creates events with wrong balance impact as compared to those purchased on other days.
Scenario:
setup:
- cm pin.conf --> timestamp_rounding = 0
- object --> /config_validate.MAXIMUM=31
- business param --> move_day_forward = 1
- deal/product --> Annual Cycle Forward, prorate based on usage
steps:
(1) 15 Mar : created a/c with dummy plan ip
(2) 28 Mar : purchased deal using op_subscripton_purchase_deal. See result below:
# number of field entries allocated 20, used 4
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 128890 6
0 PIN_FLD_OFFERING_OBJ POID [0] 0.0.0.1 /purchased_product 131864 0
...
0 PIN_FLD_RESULTS ARRAY [0] allocated 20, used 11
1 PIN_FLD_CYCLE_INFO SUBSTRUCT [0] allocated 20, used 5
2 PIN_FLD_CYCLE_START_T TSTAMP [0] (1395961201) Fri Mar 28 00:00:01 2014
2 PIN_FLD_CYCLE_END_T TSTAMP [0] (1427497200) Sat Mar 28 00:00:00 2015
2 PIN_FLD_FLAGS INT [0] 1032
2 PIN_FLD_ORIGINAL_SCALE DECIMAL [0] 1
2 PIN_FLD_SCALE DECIMAL [0] 0.999999968290207
...
1 PIN_FLD_SUB_BAL_IMPACTS ARRAY [0] allocated 20, used 3
2 PIN_FLD_BAL_GRP_OBJ POID [0] 0.0.0.1 /balance_group 129786 1
2 PIN_FLD_RESOURCE_ID INT [0] 978
2 PIN_FLD_SUB_BALANCES ARRAY [0] allocated 20, used 8
3 PIN_FLD_VALID_FROM TSTAMP [0] (1395961201) Fri Mar 28 00:00:01 2014
3 PIN_FLD_VALID_TO TSTAMP [0] (0) <null>
3 PIN_FLD_ROLLOVER_DATA INT [0] 0
3 PIN_FLD_VALID_FROM_DETAILS INT [0] 0
3 PIN_FLD_VALID_TO_DETAILS INT [0] 0
3 PIN_FLD_GRANTOR_OBJ POID [0] 0.0.0.1 /purchased_product 131864 0
3 PIN_FLD_CONTRIBUTOR_STR STR [0] ""
3 PIN_FLD_AMOUNT DECIMAL [0] 1317.60 <---------------- see this
...
(3) 30 Mar : purchased same deal using op_subscripton_purchase_deal. See result below:
# number of field entries allocated 20, used 4
0 PIN_FLD_POID POID [0] 0.0.0.1 /account 128890 6
0 PIN_FLD_OFFERING_OBJ POID [0] 0.0.0.1 /purchased_product 129607 0
...
0 PIN_FLD_RESULTS ARRAY [0] allocated 20, used 11
1 PIN_FLD_CYCLE_INFO SUBSTRUCT [0] allocated 20, used 5
2 PIN_FLD_CYCLE_START_T TSTAMP [0] (1396134001) Sun Mar 30 00:00:01 2014
2 PIN_FLD_CYCLE_END_T TSTAMP [0] (1427666400) Mon Mar 30 00:00:00 2015
2 PIN_FLD_FLAGS INT [0] 1032
2 PIN_FLD_ORIGINAL_SCALE DECIMAL [0] 1
2 PIN_FLD_SCALE DECIMAL [0] 0.999669042821734
...
1 PIN_FLD_SUB_BAL_IMPACTS ARRAY [0] allocated 20, used 3
2 PIN_FLD_BAL_GRP_OBJ POID [0] 0.0.0.1 /balance_group 132954 1
2 PIN_FLD_RESOURCE_ID INT [0] 978
2 PIN_FLD_SUB_BALANCES ARRAY [0] allocated 20, used 8
3 PIN_FLD_VALID_FROM TSTAMP [0] (1396134001) Sun Mar 30 00:00:01 2014
3 PIN_FLD_VALID_TO TSTAMP [0] (0) <null>
3 PIN_FLD_ROLLOVER_DATA INT [0] 0
3 PIN_FLD_VALID_FROM_DETAILS INT [0] 0
3 PIN_FLD_VALID_TO_DETAILS INT [0] 0
3 PIN_FLD_GRANTOR_OBJ POID [0] 0.0.0.1 /purchased_product 129607 0
3 PIN_FLD_CONTRIBUTOR_STR STR [0] ""
3 PIN_FLD_AMOUNT DECIMAL [0] 1317.16 <-------------------- see this
...
See that the amounts are not matching, while it is expected that the amount in step 3 must be same as amount in step 2.
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 |