Product Type Branching Node Content Is Not Validated while Importing Call Plan Using Call Plan Editor
(Doc ID 1581487.1)
Last updated on FEBRUARY 28, 2019
Applies to:
Oracle Communications Network Charging and Control - Version 5.0.0 to 5.0.1 [Release 5.0]Information in this document applies to any platform.
Symptoms
On Network Charging and Control (NCC), if a call plan having product type branching is imported, the Call Plan Editor (CPE) does not validate non-existing product types. For example as per below screen if highlighted PTB_05 does not exist on NCC system where call plan is being imported, no warning will appear during the import process.
This is contrary to expected product behavior as stated in release notes. Release notes can be downloaded by following instructions of Document 1341844.1 (How to Download Oracle Communications Network Charging and Control (OCNCC/NCC) Documentation)
Relevent section of release notes for release Release: NCC5.0.0 stating validation process of imported call plan
Section Control Plan Editor Enhancements
Sub-Section Validation Improvements.
A number of validation enhancements have been made in order to pre-empt and prevent common compilation errors rather than the CPE waiting until compile time to notify the user - including:
2.) On importing a control plan, the control plan editor will pre-validate each node in the control plan and clearly display nodes which need adjustment.
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 |