Setting Impact Validity Dates Expressed In Number Of Recurring Cycles Does Not Work Correctly
(Doc ID 2482613.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Pricing Design Center - Version 184.108.40.206.0 and later
Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
The goal of this knowledge article is to clarify the following scenario:
1. Define a charge offer with a charge having balance impacts as below:
a) credit balance with Amount Is Valid set to From Event Occurence - 1 Recurring Cycle(s) From Validity Start
b) credit balance with Amount Is Valid set to 1 Recurring Cycle(s) from event Occurence - 2 Hour(s) From Validity Start
2. Define a bundle and include the charge offer.
3. Submit change set, restart pipeline
4. Create a customer, purchase the bundle
When defining impact validity dates relative to event occurrence expressed in number of recurring cycles, the resulting impact validity dates are not correct.
Actual result is :
a) grant on first resource starting immediately but no end date set
b) grant on second resource starting immediately and ending at the current cycle end date
The dates are completely wrong.
a) grant on first balance, starting immediately, ending at the end of the current cycle
b) grant on second balance, starting at the end of the current cycle, ending 2 hours later
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