Non-Currency Resource Valid_To Set To Purchase Date And Deal Cancel Date (Doc ID 970244.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.2.1.0.1 to 7.2.0.1.1 [Release 7.2.1 to 7.2.0]
Information in this document applies to any platform.
Checked for relevance on 05-Dec-2011.
Checked for relevance on 09-Dec-2015.

Goal

An unexpected behaviour is observed when canceling a product including a non-currency monthly cycle forward (e.g. awarding free bytes) along with a rollover configured for "Rollover entire amount" proration.

On product cancel, the validity range (valid_to) of the resource awarded during current billing cycle is set to the cancel date, while it is expected to be set to cycle end date.

Steps To Reproduce

1)  Create a product with the following configuration:

     Monthly Cycle Forward grant of -3600 units (resource ID 1000095)
     Cycle Rollover Monthly, with "Rollover entire amount" proration on both purchase and cancel.


2)  Create a new account on Feb 9th.

     After creation, a BAL_GRP_SUB_BALS_T query returns the following:

select bgb.rec_id, bgsb.current_bal, fabio_util.conv_unix_to_date(bgsb.valid_from) valid_from, fabio_util.conv_unix_to_date(bgsb.valid_to) valid_to
from BAL_GRP_T bg,BAL_GRP_BALS_T bgb,BAL_GRP_SUB_BALS_T bgsb
where bg.account_obj_id0 = <ACCOUNT POID>
      and bgb.obj_id0 = bg.poid_id0
      and bgsb.obj_id0 = bg.poid_id0
      and bgsb.rec_id2 = bgb.rec_id;

REC_ID    CURRENT_BAL  VALID_FROM   VALID_TO

1000095   -3600        08-Feb-12    29-Feb-12


3)  Move into next month (account's DOM = 1) and make bill.

     After billing, the same query data returns:

REC_ID    CURRENT_BAL  VALID_FROM   VALID_TO

1000095   0            08-Feb-12    29-Feb-12
1000095   -3600        29-Feb-12    31-Mar-12
1000095   -3600        08-Feb-12    31-Mar-12


4)  Move later into this month, e.g. Mar 15th, and cancel the deal.

     Same query as above returns:

REC_ID    CURRENT_BAL  VALID_FROM   VALID_TO

1000095   0            08-Feb-12    29-Feb-12
1000095   -3600        29-Feb-12    14-Mar-12
1000095   -3600        08-Feb-12    31-Mar-12


As seen, second bucket (29-Feb-12 to 14-Mar-12) is set with valid_to equal to cancel date. The following was expected instead:

REC_ID    CURRENT_BAL  VALID_FROM   VALID_TO

1000095   0            08-Feb-12    29-Feb-12
1000095   -3600        29-Feb-12    31-Mar-12
1000095   -3600        08-Feb-12    31-Mar-12

Solution

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