SMS Charge Is Prorated and Allowed even when There Is Less Credit
Last updated on NOVEMBER 17, 2016
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
On : 184.108.40.206.0 version, Rating business logic
SMS charge was prorated and allowed even when there was less credit.
The actual charge configured for SMS was 4NGN and the user was able to send SMS even when the balance was -2.4NGN.
The SMS has been charged @2.4NGN which should not be the case.
1) Create ChargeOffer as mentioned in above screen shots
2) Purchase the ChargeOffer to the customer and set credit limit to 0 for the currency bucket
3) Ensure customer balance of currency bucket is < 4 NGN ,say -2.4.
4) Rate an SMS .
Expected Result: SMS should not be allowed .
Actual result: SMS is allowed and charged @2.4NGN even if charge configured is 4NGN/SMS in the charge offer.
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