Charges Not Applied If Backdated Deal Purchase And Future End Date Set In Delayed Billing Period
(Doc ID 1552488.1)
Last updated on MARCH 19, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.4.0]
Information in this document applies to any platform.
During the delayed billing period, if a monthly cycle arrear deal is purchased with backdated to previous month and then set the end date of same deal to end of current month (valid only for last month and current month), monthly charges for all the deals (already existing deals and newly purchased deal) are not applied for just completed month and also for next month and then all the pending charges of first month, second month + third month are applied in next to next month bill.
Below is a scenario
01.09.2012 - Create customer and subscription account with 1st as billing date and with any monthly cycle arrear charge deal
02.10.2012 - do billing for Sep
02.11.2012 - do billing for Oct
05.12.2012 - Purchase another monthly recurring charge deal/product with start date from previous month 01.11.2012 00:00:00
05.12.2012 - Set the end date to the newly purchased deal as 01.01.2013 00:00:00 and check the dates in PURCHASED_PRODUCT_CYCLE_FEES_T (set to 01.11.2012 to 01.12.2012)
05.12.2012 - do billing for Nov, here no charges are applied for account and dates in PURCHASED_PRODUCT_CYCLE_FEES_T also not advanced (still set to 01.11.2012 to 01.12.2012).
02.01.2013 - do billing for Dec, here also no charges are applied for account but dates in PURCHASED_PRODUCT_CYCLE_FEES_T are wrongly advanced (set to 01.12.2012 to 01.01.2013)
02.02.2013 - do billing for Jan, here charges of Nov and Dec + Jan are applied for account
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document