Backdating Applied Purchase Fee On Wrong Billing Cycle (Doc ID 1572339.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

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

Symptoms

Backdating operation applied purchase fee on a wrong billing cycle.
It only occurred when creating a new account and purchasing a product with a purchase_start date in the past (but later than account creation date).

Replication Steps:
=====================
1.  On 2013-Aug-01, in a single transaction through testnap, create an account on 2013-Jan-01 and purchase a product on 2013-Jun-10
     i.e. the purchase is in the past but not on the same month as the account creation date
2.  Close the transaction
3.  Check the bill cycle in which the purchase fee is applied
 
Actual Behavior:
==================
The bills are not getting generated on performing backdated events and the purchase fee is getting applied on the wrong bill cycle (Feb-Mar).
 
Expected Behavior:
===================
The bills should get generated based on the product purchase end date passed in the flist (till previous bill cycle of purchase date).
The purchase fee should be applied to the bill cycle corresponding to the purchase date (Jun-Jul bill cycle).



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