Rating Difference Due to RUM Based Evaluation of ECE
Last updated on DECEMBER 14, 2017
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, Rating
There were differences in rating for some of scenarios between Pipeline and ECE, which seemed to be due to the inherent difference in rating (multi-RUM) evaluation.
- Pipeline Rateplan analysis is based on Impact categories derived from zoning and USC,
Accordingly, rates with single product (evaluated in order of priority) have impact based on RUMs which were configured in the respective price model.
- There are multi RUMs which could be either with same expression or with different/fixed ones like occurrence.
For eg: If only for certain impact categories to be charged on occurrence (like a connect fee), one cannot control populating these conditions in the ECE input unless you evaluate the pricing configuration.
- ECE, by design, evaluates every possible RUM configured for the service with each of the products (in order of priority) to rate the usage.
For instance, say if the customer has two products, Product A (low priority) configured with RUM X and Product B (high priority) configured with RUM Y for rating the same event, below is the difference, while expected is to have the same behavior as in Pipeline :
Pipeline: Rates only with Product B, Impacts Balance according to RUM Y
ECE: ->Evaluates RUM X and rates with Product A, Impacts Balance according to RUM X
->Evaluates RUM Y and rates with Product B, Impacts Balance according to RUM Y.
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