Selective Rerating Not Working As Expected

(Doc ID 957752.1)

Last updated on DECEMBER 28, 2011

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.1.0.0 and later   [Release: 7.3.1 and later ]
Information in this document applies to any platform.
Checked for relevance on 28-Dec-2011

Symptoms

-- Problem Statement:
RERATE_REBILL has three different behaviors that appear randomly (but always one of it appears).

-- Steps To Reproduce:
Product/deal with bimonthly cycle forward fee was bought and then canceled. After few billings rerate_rebill was performed with specified product's poids (selective rerating).

Detailed steps :

(1) created deals , offerA and offerB in Pricing Center and committed to database . Products have simple monthly cycle forward events
(2) Mar 25 : created account with dummy plan ( bill cycle is Mar25 - Apr25 )
(3) Mar 25 : modified billing cycle from CustomerCenter --> Payments tab as : DOM = 1 , Billing Frequency = 2, Bill cycle now shows March 25 - June 01
(4) Purchase offerA
(5) Jun 01 : From /apps/pin_billd run the following commands :
pin_cycle_fees -cycle_fees
pin_cycle_fees -cancel
pin_cycle_forward -verbose
pin_bill_day -verbose
(6) Jul 01 : From /apps/pin_billd run the following commands :
pin_cycle_fees -cycle_fees
pin_cycle_fees -cancel
pin_cycle_forward -verbose
pin_bill_day -verbose
(7) July 02 : cancel offerA with effective date 30.June.2009
(8) July 02 : purchase offerB with effective date 30.June.2009
(9) Aug 01 : From /apps/pin_billd run the following commands :
pin_cycle_fees -cycle_fees
pin_cycle_fees -cancel
pin_cycle_forward -verbose
pin_bill_day -verbose
(10) Sep 15 : cancel offerB with effective date 30.June.2009
(11) Sep 15 : selective rerating using rerate_rebill opcode(#96) with start date equal to account creation date

At step 11 , 3 issues can be seen randomly as highlighted in the below cases :

case a)
In the input flist to rerate_rebill , do not pass any product belonging to this account , still we can see that rerate_rebill returns two incorrect cycle forward events that were not rated and also with cycles not aligned to account billing cycles. Expectation is that no events should be produced at all.

case b)
In the input flist to rerate_rebill , do not pass any product belonging to this account , rerate_rebill returns incorrect cycle forward events that were rated but such event should not appear as product poids for them were not given on input flist for RERATE_REBILL. Hence selective rerating is not working as expected.

case c)
In the input flist to rerate_rebill , pass one of the product poid ( in offerA ) , rerate_rebill returns two incorrect cycle forward events that were rated but for cycles not aligned to account billing cycles.

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