Control Plan Periodic Charges Can Renew in a Random Order
Last updated on MAY 27, 2015
Applies to:Oracle Communications Network Charging and Control - Version 4.4.0 to 5.0.3 [Release 4.4 to 5.0]
Oracle Solaris on SPARC (64-bit)
In Oracle Communications Network Charging and Control (NCC), all Periodic Charges (PC) need to be assigned to Product Types (PT) in order to provide control over which subscribers can join each PC. In the same PT screen, the order of execution of the PCs can also be decided by shifting the higher priority PCs up the list and the lower priority PCs down the list.
This has the effect of adding 2 seconds per position of the PC.
The beVWARS processes are coded to process the earliest buckets first so the first PC in the list (assuming a group of them were subscribed to at the same time) should have the earliest expiry and will therefore be processed first (since the others all have different factors of 2 seconds added to the).
A problem exists when a group of Control Plan PCs are due to renew at the same time whereby it is possible they are renewed out of order.
Creation of Control Plan (CP) PCs which need to be executed in a specific order.
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