My Oracle Support Banner

Realtime Threshold Notifications on Usage (Doc ID 2491681.1)

Last updated on MARCH 05, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.20.0 and later
Information in this document applies to any platform.

Symptoms

On Oracle Communications Billing and Revenue Management (BRM) version 7.5.0.20.0 version, when configuring realtime threshold notifications on usage, credit floor breach errors are being thrown when trying to trigger services that use the resource.

For example, consider a package with name "Silver".

The "Silver" package gives a 50 Short Message Service allowance.  In the plan, credit_floor is set to -50 and credit limit is set to 0.  The credit profile to the balance is assigned (floor and limit are set notify customers on 80% and 90% of usage consumption).  Also, any balance left in the previous month is rolled over to the next month.

On Sep 1st, the package is purchased and it gives 50 SMS.  No SMS usage is done in this month.

On Oct 1st, billing is run so the previous month's balance is rolled over to this month and the current month's allowance is also given.  Total SMS now is in credit of 100, but the credit profile for the balance in bal_grp object remains the same (credit floor -50 and limit 0), where as the total balance now is -100.

When SMS usage is triggered to ECE, it throws credit floor breach error, as it tries to reduce -100 SMS to -99 and the credit floor for this balance is set as -50.

How can credit profile mapping to the balances be handled based on dynamic changes to the balances (like rollover from previous month balance, or another instance of the addon purchased etc)?

The issue can be reproduced at will with the following steps:

1. Sep 1st the package is purchased and it gives 50 SMS.  No SMS usage is done in this month.
2. Oct 1st billing is run, so the previous month balance is rolled over to this month and the current month allowance is also given.  Total SMS now is credit of 100, but the credit profile for the balance in bal_grp object remains the same (credit floor -50 and limit 0), where as the total balance now is -100.

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
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.