Default Control Plan for Capability Appear Unset When Editing Under Different Service Provider Than the One Who Initially Set It
Last updated on DECEMBER 22, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 to 6.0.0 [Release 4.3 to 6.0]
Oracle Communications Convergent Charging Controller - Version 6.0.0 to 6.0.0 [Release 6.0]
Information in this document applies to any platform.
In all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C), when editing a Charging Control Services (CCS) Capability under any service provider other than the one used to initially create/set it, the "Default Control Plan" field appears unset, even if it was set at the creation time.
The aforementioned behavior can be easily observed if the Edit screen for the same Capability is viewed under two different service providers: the one who set Default Control Plan field, and any other service provider.
This is how it looks when editing under service provider which set the "default control plan" field:
This is how it looks when editing under a different service provider:
As a result, it is possible to unintentionally remove/overwrite the Default Call Plan, in the scenario when editing the Capability under a different service provider than the one used to create it.
Trying to set the Default Control Plan in the CCS Capability as a Screens user.
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