Rerating Issue In Case Of Conditional RUM
(Doc ID 2616225.1)
Last updated on DECEMBER 06, 2019
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
- During rating of a data event (say for /service/telco/gprs) one has two separate events created, one event for conditional RUM (Ratable Usage Metric) and one for MB (RUM MegaByte).
- Now when rerating is done for this account, system is triggering conditional and MB impacts in the same event.
- Due to this, even when there is no rate change in the product, rerating is happening and resulting in additional event being persisted.
- The expected behavior is that, since there is no change in price, rerated event should be dropped in BRM (Billing and Revenue Management) before passing the event to ECE (Elastic Charging Engine).
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