Workaround to Handle Change in Charging Conditions in Prepaid Usage
(Doc ID 1610097.1)
Last updated on DECEMBER 03, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.3.1.0.0 to 7.5.0.0.0 [Release 7.3.0 to 7.5.0]Information in this document applies to any platform.
Goal
During Prepaid Authentication, Authorization, and Accounting (AAA) usage, a workaround to handle change in charging conditions during the course of a long data session when any of the following scenarios occur will be covered in this article:
- A Product with higher priority than the currently selected product is purchased (with possible change of quota/Rateable Usage Metric (RUM))
- A Topup is done after the start of the session
- Any new eligible resources become available after the start of the session
Solution
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
| Goal |
| Solution |