Issue With Expiration Time In Session Management - Multiple Resources

(Doc ID 1469651.1)

Last updated on SEPTEMBER 19, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.4.0]
Information in this document applies to any platform.
***Checked for Relevance on 17-Jul-2014***


This is for real-time prepaid session management.


Test Scenario:

We created a product with two rate-tiers. First tier has MB as resource and second has Rupee. So ideally, once MB resource is consumed or expired, user should be able to use Rupee resource.

While purchasing product we had set resource expiry dates as follows:

MB(1000009) - Fri May 11 19:12:00 2012
Rupee(356) - Fri May 11 19:17:00 2012

1. We started a session(CC-initial request) for this customer at Fri May 11 19:10:00 2012.
2. Passed an CC-update request with END_T Fri May 11 19:11:00 2012 which worked fine and used MB resource.
3. Passed another CC-update request with END_T Fri May 11 19:13:00 2012. At this time , as MB resource is expired, BRM should start using Rupee resource. But instead CC-update was not processed successfully and we got PIN_ERR_NO_CREDIT_BALANCE error.


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