Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 18.104.22.168.0
Information in this document applies to any platform.
For example, in 7.2, if a deal has relative start 1 cycle, end 2 cycles, the deal is purchased on 1-Jan, the product start date will be 1-Feb, and end date will be 1-Mar.
However on 7.3 or 7.4, the same value will result differently, i.e, if the deal is purchased on 1-Jan, the product start date will be 1-Feb, but end date will be 1-Apr.
When upgrade from 7.2 to 7.3, this fact is actually not considered and it added extra cycle(s) to the product's purchase/cycle/usage end.
Here is another example:
In 7.2, Deal D has product P which is set to
start cycle after 12 cycles, i.e. cycle_start = 12 cycles
end the cycle after 12 cycles, i.e. cycle_end = 24 cycles
(Since the cycle_start and cycle_end dates were calculated based on purchase date in 7.2 and no relative dates supported).
After the upgrade, the user expects deal cycle dates to be inline with current logic of relative dates.
cycle_start = 12 cycles
cycle_end = 12 cycles (relative to cycle_start)
But one will see cycle_end = 24 cycles (which extends the validity by 12 more cycles, which is not expected).
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