Pin_rerate : The /Event/xxx/Cycle_forward Is Created On The Bad /Item Type
Last updated on JULY 24, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
As the cycle_forward event has already been billed, the 2 new event have to be associated to /item_adjustment.
Note: When one re-rate 2 months ago (suppose re-rate on the 5th May, and the DOM is on 1st), we have the following result :
- the /event/billing/adjustment/event and the /event/billing/product/fee/cycle/cycle_forward_monthly for the rerating of the 1st April are associated to the /item/adjustment.
- the /event/billing/adjustment/event for the rerating of the 1st May is associated to the /item_adjustment.
- the /event/billing/product/fee/cycle/cycle_forward_monthly for the rerating of the 1st May is associated to the /item/cycle_forward ==> this is a problem.
Steps to Reproduce:
1.Create account ( on 1st April).
2.Bill account (on 1st May).
3.Re-rated account on the cycle forward using pin_rerate effective 1st April.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms