Improved BRM To ECE Data Synchronization
(Doc ID 3011697.1)
Last updated on MARCH 29, 2024
Applies to:
Oracle Communications BRM - Elastic Charging Engine - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Goal
On Oracle Communications Elastic Charging Engine (ECE) 12.0.0.3.0 version, it is observed that PIN_ERR_UNKNOWN_EXCEPTION or PIN_ERR_STREAM_IO issues are causing purchase sync issue in BRM. Consider an order purchase scenario during which the purchase orders are getting failed with PIN_ERR_UNKNOWN_EXCEPTION or PIN_ERR_STREAM_IO, it is observed that these purchased details are updated in ECE, but not synchronized to Billing and Revenue Management (BRM). What would happen in this case where the transaction was successful in ECE and EMGateway sent a success response but somehow it did not reach BRM?
Solution
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
Goal |
Solution |
References |