Reactivation Of Long-cycled Linked Service Gets Chopped Up Into Monthly Charges (Doc ID 2006923.1)

Last updated on MAY 22, 2015

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.0.0 to 7.5.0.0.0 [Release 7.5.0]
Information in this document applies to any platform.

Symptoms

On :  7.5.0.6.0 version, Subscription Management

An inactivation and reactivation of long cycled products results in the reactivation charging as a series of month-long charges instead of a single long-cycled charge.

The customizations in SPEC_CYCLE_FEE_INTERVAL are not resulting in bad dates, the date range looks good, but the OOB rating seems to be refusing to long-cycle upon reactivation. There is some different OOB logging in the immediate aftermath of the SPEC_CYCLE_FEE_INTERVAL calls. It is doing something different with the reactivation than it did with the original charge.

ACTUAL BEHAVIOR  
---------------
The reactivation charges a series of month-long charges. i.e. there are five charges scaled to 1.0 (with corresponding one-month date ranges), and a 6th event for the remaining bit of scale (0.32142857142857).
Here’s the poids and scales:
/event/billing/product/fee/cycle/cycle_forward_monthly 290024779128359001 .321428571428571
/event/billing/product/fee/cycle/cycle_forward_monthly 290024779128359513 1
/event/billing/product/fee/cycle/cycle_forward_monthly 290024779128359257 1
/event/billing/product/fee/cycle/cycle_forward_monthly 290024779128359769 1
/event/billing/product/fee/cycle/cycle_forward_monthly 290024779128359129 1
/event/billing/product/fee/cycle/cycle_forward_monthly 290024779128359641 1

EXPECTED BEHAVIOR
-----------------------
The reactivation charges a single long-cycled charge. i.e. it is expected a single event of scale 5.32142857142857.
That is the result upon initial purchase and the result upon inactivation, and so expected result upon subsequent reactivation

STEPS
-----------------------
1. On Feb 1 2015, create account with Monthly product, so BDOM is 1st.
    In PCM_OP_SUBSCRIPTION_POL_SPEC_CYCLE_FEE_INTERVAL, push the end date out six months, so there is a single charge with a scale of 6.0.
    The cycle forward event is /event/billing/product/fee/cycle/cycle_forward_monthly 289690527593516777 and has a scale of 6.0

2. On Feb 10 2015, inactive the service, which inactivates the product.
    A single credit with a scale of about 5.67 months.
    The credit events is /event/billing/product/fee/cycle/cycle_forward_monthly 289848857267914905 and has a scale of 5.678571428571428

3. On Feb 20 2015, re-activate the service which reactivates the product.
    Again in SPEC_CYCLE_FEE_INTERVAL, the end date is made out to the original end date (which is Aug 1 2015).

The problem is, it is not a single charge scaled to 5.32.

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