When One Cycle Discount Expires, Rating Engine Messes Scale Values For Other Valid Cycle Discounts
(Doc ID 1491242.1)
Last updated on NOVEMBER 16, 2016
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.
**Checked for relevance on 24-Sep-2012***
*** Checked for relevance on 11-16-2016 ***
When one cycle discount expires, Rating engine messes scale values for other valid cycle discounts. The three discounts are configured as sequential discount.
Billing date - Aug 1, 2012
Cycle Discount "A" valid till - Aug 3, 2012
Cycle Discount "B" valid forever
Cycle Discount "C" valid forever
When billing is run on Aug 1, 2012, cycle_start for cycle discount "B" and "C" is set to Aug 3 , 2012 that coincides with the end date of cycle discount "A".
Consequently, the base charge that is sent to the discounting pipeline is incorrect.
The following three discounts are configured as sequential discount with the same priority, the start_t got set to Aug 3, when it should be Aug 1.
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