Bucket Expiry Minutes and Seconds Not Saved when Updated in the Subscriber Management Screens
(Doc ID 2751931.1)
Last updated on MARCH 27, 2023
Applies to:
Oracle Communications Network Charging and Control - Version 4.3.0 to 12.0.3.0.0 [Release 4.3 to 12.0.0]Information in this document applies to any platform.
Symptoms
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) up to and including 12.0.3.0, when updating a subscriber's bucket expiry date, the minutes are inconsistently saved, and the seconds are never saved.
Specific use cases:
1. Updating the Hours, Minutes, and Seconds: Hours and Minutes are saved
2. Updating the Minutes, and Seconds: None are saved
3. Updating the Seconds: Nothing is saved
Due to this, it is not possible to set accurate expiry dates on buckets to align them with other action that may be occurring against a Wallet (Periodic Charges firing for example).
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |