"Unexpected exception" Twrown by ECE During Rerating
(Doc ID 2689056.1)
Last updated on JULY 15, 2020
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
During the rerate job for some newly created accounts, "Unexpected exception" was returned by the Elastic Charing Engine (ECE).
Each new subscriber has a Product plan associated which gives them access to the Telecom Services. For each Product, customers should pay a session fee. When this price is changing, rerate job should be run for affected customers to correct the charge difference.
In the current scenario, it was seen that rerate job is executed successfully after the Product's price was changed, but even though a new rerate job is crated with status 1 (NEW) for one account. The new job seems to be created because of an error message returned by ECE (billing system) which talks about a discrepancy between the balanceID needed for Product's session fee and the customer's available balances:
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