Last updated on SEPTEMBER 26, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 220.127.116.11.1
Information in this document applies to any platform.
Checked for relevance on 22-Dec-2009
***Checked for relevance on 31-Oct-2011***
If we do a credit adjustment or purchase a prepaid credit during the delayed billing period, the next_bal is also getting impacted along with current_bal, resulting in a negative value for next_bal.
During stop accounting for credit limit check we consider “current_bal + next_bal” and since next_bal is negative the customer can send sms even though current_bal is zero.
Steps To Reproduce:
1. Set the delay billing to 10 days.
2. Create a prepaid account on say 03/01/08 with CL=0, CF = -20. Have a purchase product fee of -10. As expected ----> Current balance = -10 and Next balance = 0
3. Move pin_virtual_time to 04/04/08.
4. Do a credit adjustment of decreasing the credit by 10
Now Current balance = -20 and Next balance = -10. The Next balance value is getting impacted alongwith Current balance, due to which it causes an issue wherein even if Current balance becomes 0.The customer can make sms as during stop accounting the credit limit check considers 'Current balance + Next balance'
One can see the difference in read obj for balance group, before and after credit adjustment:
1 PIN_FLD_NEXT_BAL DECIMAL  0
2 PIN_FLD_CURRENT_BAL DECIMAL  -10
1 PIN_FLD_NEXT_BAL DECIMAL  -10
2 PIN_FLD_CURRENT_BAL DECIMAL  -20
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms