My Oracle Support Banner

Balance Type is Allowed to Go Negative in the Final Commit when "Mid-Session Commit" with Balance Cascade are Used (Doc ID 1348650.1)

Last updated on FEBRUARY 25, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.

Symptoms

How to identify the symptom?

This issue can be identified by analyzing this following information from Billing Engine (BE) Event Data Record (EDR):

1. What balance types which are involved during the rating, this can refer to the BALANCE_TYPES Tag.

As the subject of this article explains about balance type cascade then you will see at least two balance types are being presented by this tag.

2. The value of previous balances, this can refer to BALANCES Tag.

3. And the final charges which have been applied for the transaction, this can refer to COSTS Tag.

What is the symptom?

Once you have collected above information, you can confirm the issue exists if the costs which have been deducted for the particular balance type is greater than the previous balance.

Please refer to this following example as the glance of BE EDR:

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.