Problem With pin_rate_change Which Don't Store The Product To Be Rerated
(Doc ID 1337288.1)
Last updated on SEPTEMBER 02, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
** Checked for relevance on 07 Jan 2014**
Problem with pin_rate_change, which don't store the product to be rerated
Steps to Reproduce
1. create an account with the product A and B (the 1st January).
2. add a new rate tier with new period on a product A (from the 6th january to "never end") ==> /rate_change created on product A.
3. Launch the pin_rate_change ==> create /job/rerate and /job_batch/rerate
4. Launch pin_rerate -rerate -reason 109 ==> ALL the /event/.../cycle_forward_monthly are rerated, and new event are created for each of them.
The issue has the following business impact: we have additional lines in the invoice, because all the /event.../cycle_forward_montly are rerated.
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