Expiration Time in Session Management - Multiple Resources
(Doc ID 1469651.1)
Last updated on MARCH 12, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.4.0]
Information in this document applies to any platform.
This is for real-time prepaid session management.
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, users should be able to use Rupee resource.
While purchasing product, resource expiry dates are set as following:
MB(1000009) - Fri May 11 19:12:00 2012
Rupee(356) - Fri May 11 19:17:00 2012
1. 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.
Expected: At this time, as MB resource is expired, BRM should start using Rupee resource.
Actual: But instead CC-update was not processed successfully and gives PIN_ERR_NO_CREDIT_BALANCE error.
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