Last updated on JUNE 22, 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 business logic
Customer deployed the latest ECE ( Version: 184.108.40.206.1 ) in both SIT and QA environments , also deployed it into one dev Env.
When rate some usage for AMABAF mediation chain in Q.A and DEV , and ECE is responding for all EDRs the following error code:
Checking the ECE logs, the usage was rated for the RUM Duration ( correct ) and wasn’t rated for the Rum Occurrence (also correct, only some calls types are Rated by Occurrence), but there is an unratedNetAndOriginalQtyMap that seems to be the cause of the rejected usage ..
After some discussions with Engineering , customer has created a dummy system offer with low priority so the usage that was rated only by duration is not rejected , however this workaround will populate the event_bals_impact_t table with a lot of dummy information, it will kill BRM performance.
The edrs should be only rejected when there is no balance impact information generated, if the usage was rated by at least one of the RUMs defined within the event_type , it should be uploaded to BRM db with the balance information generated for the RUM it was used during the rating process.
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