Customer Updater to Provide Descriptive Error Messages Along with Failed Account Details
(Doc ID 2129427.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : BRM - 7.5 PS13, PDC - 18.104.22.168.0, and ECE - 22.214.171.124.3 | Customer data management
Since the whole batch got rejected during incremental loading due to data issues with only 1 account, and since there was no error details for that account logged, it took a huge amount of time to find and to fix the account having data issue. This will directly impact 'Preactivation' completion, and subsequently delay the the selling of SIMs.
1. During loading, if there is any data inconsistencies, the customer updater was not able to load the account to cache.
2. If one account in the batch of accounts failed, the whole batch would be rejected.
Since a batch of accounts could not be loaded to memory, both the usage processing and the event processing would failed.
1. If customer updater failed, it should provide descriptive error messages along with failed account details.
2. If one account in the batch of accounts failed, only that account should be skipped, and the remaining accounts should be loaded.
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