Impact_type Not Populating Correctly For Backout Events Generated After Rerate Post Billing
(Doc ID 2655744.1)
Last updated on APRIL 08, 2020
Applies to:Oracle Communications Billing and Revenue Management - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management (BRM) 126.96.36.199.0 Version and Elastic Charging Engine (ECE) 188.8.131.52.0 Version,
Impact_type not populating correctly for backout events generated after rerate post billing, ie while rerating an already rerated account post billing.
The backout event's impact type should be generated correctly as that of 1st rerate result.
The issue can be reproduced at will with the following steps:
1. Create an account with cycle forward arrear events and 100% discount
2. Change the price and do rerating
3. Bill the account
4. Again perform rerate on the same event after changing the price
5. Check backout event's impact type generated
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