Rerating Of In-Advance-Billing Cycle Forward Event Failed when Rerated More than Once (Doc ID 2199109.1)

Last updated on NOVEMBER 16, 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.13.0 version, Rerating/Rebilling

Rerating of In-Advance-Billing cycle forward event did not work when it was rerated more than once.

STEPS
-----------------------
1. On 14-Jul,  created a new account (BILL_WHEN = 3, DOM = 1), ChargeOffer with In Advance Billing = 3 months is purchased under the service of this account.
    MCF events got created:
    14-Jul to 01-Aug (/event/billing/product/fee/cycle/cycle_forward_monthly 298996798298432202)
    01-Aug to 01-Nov (/event/billing/product/fee/cycle/cycle_forward_monthly 298996798298433994)

2. On 14-Jul, changed (and submitted from PDC) the price from 70 NOK to 100 NOK in the charge offer to introduce a new Date Range.
    The new price is configured to be effective from (which is equal to start date of new Date Range) 16-Aug.

3. Executed from command-line:  

pin_rate_change -v

    Rerate objects got created: /job/rerate and /job_batch/rerate

4. Executed from command-line in step by step:

    Refund adjustment and rerate events got created:
    14-Jul to 01-Aug (/event/billing/adjustment/event 298996798298402390)
    01-Aug to 01-Nov (/event/billing/adjustment/event 298996798298401110)

    14-Jul to 01-Aug (/event/billing/product/fee/cycle/cycle_forward_monthly 298996798298398934)
    01-Aug to 16-Aug (/event/billing/product/fee/cycle/cycle_forward_monthly 298996798298400470)
    16-Aug to 01-Nov (/event/billing/product/fee/cycle/cycle_forward_monthly 298996798298402262)

5. On 04-Aug, executed PCM_OP_BILL_MAKE_BILL
    MCF event got created:
    (/event/billing/product/fee/cycle/cycle_forward_monthly 299366234205369825)

6. On 04-Aug, changed (and submitted from PDC) the price in the same charge offer from 100 NOK to 110 NOK to introduce another new Date Range.
    The new price is configured to be effective from (which is equal to start date of new Date Range) 16-Oct.

7. Repeated step 3 and step 4

Changes


ACTUAL BEHAVIOR
-----------------------------
Adjustment events got created:
    14-Jul to 01-Aug (/event/billing/adjustment/event 299366234205363910)
    01-Aug to 16-Aug (/event/billing/adjustment/event 299366234205361862)
    16-Aug to 01-Nov (/event/billing/adjustment/event 299366234205362886)
    01-Nov to 01-Dec (/event/billing/adjustment/event 299366234205360582)

    14-Jul to 01-Aug (/event/billing/product/fee/cycle/cycle_forward_monthly 299366234205364166)
    01-Aug to 16-Aug (/event/billing/product/fee/cycle/cycle_forward_monthly 299366234205362726)
    16-Aug to 01-Sep (/event/billing/product/fee/cycle/cycle_forward_monthly 299366234205361446)
    01-Sep to 01-Oct (/event/billing/product/fee/cycle/cycle_forward_monthly 299366234205360294)

No rerate events generated for the period of 01-Oct to 01-Dec.


EXPECTED BEHAVIOR
-----------------------------
These should have been the events created for the period between 16-Aug and 01-Dec (with a charge of 110 NOK/month):
16-Aug to 16-Oct
16-Oct to 01-Nov
01-Nov to 01-Dec

 

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