Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 184.108.40.206.0
This problem can occur on any platform.
When a product is canceled using backdate and that product has a cycle-arrear event, the system is duplicating the charge.
For example, an account has a Product A with cycle arrear event, DOM = 25. The account was billed until Jan/25/2008.
On Feb/1/2008, a backdated cancellation happens and the purchase/cycle/usage end date was set to
Under these circumstances the system is generating a new (positive) cycle-arrear charge for Product A from Dec/25/2007 to Jan/20/2008, but there is already a charge from Dec/25/2007 to Jan/25/2008.
As in the documentation refund for cycle arrear is not supported, expect to see no additional charge.
Steps To Reproduce:
1. Nov/25/2007: Create an account with a product with cycle arrear event, DOM = 25.
2. Bill the account on Dec/25/2007, and Jan/25/2008.
3. On Feb/1/2008, backdate the cancellation of the product by setting the purchase/cycle/usage end date to Jan/20/2008.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms