Pin_cycle_forward Creates Incorrect Cycle Events After Contract Reactivation (Offer Including Tiers) (Doc ID 1078759.1)

Last updated on SEPTEMBER 19, 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 to 7.3.1
Information in this document applies to any platform.
***Checked for relevance on 12-Apr-2012***

Symptoms

Pin_cycle_forward creates incorrect events for reactivated accounts with price configured on tiers.

The user has bimonthly cycle offer with two prices configured on tiers:

1st valid up to 1.Feb
2nd valid from 1.Feb

and is reactivating account (with bimonthly billing cycle) on 27.Jan.

Reactivation operation creates charge for period from 27.Jan to 01.Feb.

Steps to reproduce issue:

Offer with bimonthly cycle fee and two prices configured on tiers:
1 - 10$ up to 1.Feb (excluded)
2 - 20$ from 1.Feb (included)
param rate_change set to 1
account with bimonthly billing period and DOM=1

02/10/09 - create account, purchase offer
02/11/09 - billing
02/12/09 - billing, 1st bill for account, invoice lines:
X$ for period 02/10/09 - 01/12/09 (prorated charge for first short billing cycle)
10$ for period 01/12/09 - 01/02/20
02/01/10 - billing
10/01/10 - inactivate account (system creates refund)
27/01/10 - reactivate account (system creates event)
28/01/10 - daily batch (pin_cycle_forward creates incorrect event)
29/01/10 - daily batch (pin_cycle_forward creates incorrect event)
30/01/10 - daily batch (pin_cycle_forward creates incorrect event)
31/01/10 - daily batch (pin_cycle_forward creates incorrect event)
02/02/10 - billing, 2nd bill for account, invoice lines:
Y$ for period 10/01/10 - 01/02/10 (prorated refund)
20$ for period 01/02/10 - 01/04/10 (std fee)
Z$ for period 27/01/10 - 01/02/10 (prorated charge after reactivation)
Z$ for period 27/01/10 - 01/02/10 (incorrect charge)
Z$ for period 27/01/10 - 01/02/10 (incorrect charge)
Z$ for period 27/01/10 - 01/02/10 (incorrect charge)
Z$ for period 27/01/10 - 01/02/10 (incorrect charge)
When the user executes daily batch on 28.Jan, pin_cycle_forward creates incorrect event to charge client for period 27.Jan-01.Feb.

Executing pin_cycle_forward next day results in another incorrect event for period 27.Jan-01.Feb.
On Feb bill client is charge 5 times (event created during reactivation process, and daily batch on 28,29,30 and 31 Jan) for the same period from 27.Jan to 01.Feb.

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