Wrong Event Type Creation On Rerating
Last updated on SEPTEMBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 7.5.0]
Information in this document applies to any platform.
While rerating the rerated events are created with different type other than the event type of original event.
For an unbilled account, when the events are re-rated , the rerated events are created with the type adjustment. Actually it should be the type of original event. Let say the original event is /event/delayed/session/telco/gsm/voice, the rerated event is created as /event/delayed/session/telco/gsm/voice. And the item created is /item/adjustment instead of /item/voice_usage.
Because of this for the same event, the customer is not able to rerate more than once with the OOB pin_event_extract utility.
1. Create an account with GSM Plan. Pass service usage, rate the service usage and then run rerating using pin_event_extract utility.
2. Now, move pvt (pin_virtual_time) 1 month ahead and run pin_bill_day, then move the pvt to 2-3 days ahead, modify the rate from Pricing Center, restart services and then run pin_rerate, so that /item/adjustment gets created.
3. Now, run the pin_event_extract utility with only account number and impact_category in pin_event_extract.cfg file.
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