Wrong Cycle Start/End For Deal Purchased With Backdated Effective Date (Doc ID 847492.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.3.1.0.1 [Release 7.3.1]
Information in this document applies to any platform.
Checked for relevance on 10-Jul-2011
Checked for relevance on 4-Nov-2014

Symptoms

If product with Bimonthly Cycle Forward Fee is purchased with backdated effective date (pin virtual time = second month of billing period, effective date = first month of billing period), it is prorated for wrong periods, which are not aligned to contract billing dates.

Steps To Reproduce:-

1. Create offer with Bimonthly Cycle Forward fee (proration based on the amount used, “Apply on Billing Date” checked)
2. Create a business account on 07.07.2011, bimonthly billing cycle, DOM = 1.
    Account is created with a dummy(empty) Plan. [Here all the dates are in dd/mm/yy format].
    Billing periods for this account :
             07/07/11 – 01/09/11
             01/09/11 – 01/11/11
             01/11/11 – 01/01/12
3. 02/08/11 run billing
4. 02/09/11 run billing
5. 02/10/11 run billing
6. Purchase deal using opcode PCM_OP_SUBSCRIPTION_PURCHASE_DEAL on 12.10.2011 (pin virtual time) with effective date 10.09.2011 (start_t, end_t)
   
Actual Results: The scale is calculated base on following periods:
                      10/09/11 – 01/10/11 (first part of scale)
                      01/10/11 – 01/12/11 (second part of scale)

                      In the log, the scale is shown as below:
                      scale_flist:

# number of field entries allocated 20, used 2
0 PIN_FLD_RESULTS ARRAY [0] allocated 20, used 3
1     PIN_FLD_CYCLE_START_T TSTAMP [0] (1315593000) Sat Sep 10 00:00:00 2011
1     PIN_FLD_CYCLE_END_T TSTAMP [0] (1317407400) Sat Oct 01 00:00:00 2011
1     PIN_FLD_SCALE DECIMAL [0] 0.34426229508196720674
0 PIN_FLD_RESULTS ARRAY [1] allocated 20, used 3
1     PIN_FLD_CYCLE_START_T TSTAMP [0] (1317407400) Sat Oct 01 00:00:00 2011
1     PIN_FLD_CYCLE_END_T TSTAMP [0] (1322677800) Thu Dec 01 00:00:00 2011
1     PIN_FLD_SCALE DECIMAL [0] 1.00000000000000000000

Expected results: The scale should be calculated based on period
                          10/09/11 – 01/11/11

                         The expected scale should be as below in the log:
                         scale_flist:

# number of field entries allocated 20, used 1
0 PIN_FLD_RESULTS ARRAY [0] allocated 20, used 3
1     PIN_FLD_CYCLE_START_T TSTAMP [0] (1315593000) Sat Sep 10 00:00:00 2011
1     PIN_FLD_CYCLE_END_T TSTAMP [0] (1320085800) Tue Nov 01 00:00:00 2011
1     PIN_FLD_SCALE DECIMAL [0] 0.85245901639344257017

 

 


 

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