Customer Updater to Provide Descriptive Error Messages Along with Failed Account Details
Last updated on OCTOBER 10, 2017
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
On : BRM - 7.5 PS13, PDC - 126.96.36.199.0, and ECE - 188.8.131.52.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.
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