Incorrect Granted Quantity During Realtime Rating When There are Two or More Shared Balance Reservations (Doc ID 2299765.1)

Last updated on SEPTEMBER 07, 2017

Applies to:

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

Symptoms

On : 7.5.0.16.0 version, Rating

ACTUAL BEHAVIOR
---------------
The user observed incorrect granted quantity during realtime rating in below test scenarios:

Scenario 1:
Unit : 3062218851
Subscription Account : 490829701772
Payee Account : 490829702004

Customer has Shared Data = -100 MB
Data Cap : -50
Current Balance : 150.24
Spending limit : 150

1) Authorization request for 25 MB . Granted and reserved correct quantity successfully.
2) Consumed 25 MB and requested another 25MB with Reauth request. Granted and reserved successfully.
3) Consumed 25 MB and requested another 25MB with Reauth request. Granted and reserved successfully.
4) Consumed 25 MB and requested another 25MB with Reauth request. Granted and reserved successfully. Now the Balance of Shared bucket has become 0
5) Consumed 25 MB and requested another 25MB with Reauth request . The expectation is that re-authorization should fail since customer has consumed 100 MB free data and currency spending limit has already reached, therefore he cannot be charged.
However, granted amount is 0.
After send stop accounting, all the 100 MB consumed earlier went to Unrated quantity. Customer shared bucket was not updated, but instead it was left in the reserved amount under balance group.

Scenario 2:
Same test on Consumer Account, but the results are different .
Here, the user is receiving Bad Argument error.

Unit : 3062293381
Account : 490831184008

Customer has shared data on subscription account.

Shared Data = -25 MB
Data Cap : -50
Current Balance : 618.51
Spending limit : 415

1) Authorization request for 25 MB . Granted and reserved correct quantity successfully. Now the Balance of Shared bucket has become 0
2) Consumed 25 MB and requested another 25MB with Reauth request. Opcode returned PIN_ERR_BAD_ARG error instead of re-authorization denied (result=0,reason=4 and rating_status=26)


Changes

 

Cause

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