BRM Txn Is Not Committed In BRM DB But Committed In ECE Cache Which Leads Into Data Inconsistency
(Doc ID 2665089.1)
Last updated on MAY 06, 2020
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
The following scenario is causing a Data inconsistency between BRM(Billing and Revenue Management) and ECE(Elastic Charging Engine). For example when customer create a service even when the transaction is failed the service is getting created or commit in ECE where as in BRM it's not committed
1) Take an existing account
2) Create a service, purchase a product and discount (by invoking MODIFY_CUSTOMER)
3) Now let's say, while creating a service there is an un-handled exception (NullPointerExpection) raised by ECE.
4) Due the error the transaction is roll backed in BRM - service is not created in BRM
5) However the service(Product) object is get created in ECE , even after the transaction is roll backed in BRM.
ECE Version: 126.96.36.199.0
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