My Oracle Support Banner

ASR Import API's Handle the CPT Field Edits/Behavior Inconsistently (Doc ID 1643291.1)

Last updated on MARCH 03, 2019

Applies to:

Oracle Communications MetaSolv Solution Module - ASR - Version 48.0.0 and later
Information in this document applies to any platform.


The issues listed below are identified in the CPT field while importing the ASR orders using CORBA APIs.

ASR import APIs allows hyphen as a valid value for CPT
ASR import APIs allows spaces between the numbers in either the first segment/ring or the second segment/ring for CPT

The following should be the correct behavior for the CPT field, which corresponds with the industry regulations.

The import of the ASR should not validate for the hyphen. The data sets will either be 5 characters if only 1 ring is ordered or 10 characters for 2 rings.
The data should be stored in the dB with no hyphens,
The data is displayed in the UI with the hyphen in the 6th position.
The data is exported without hyphen and should be 10 characters long.
The CPT behavior should be consistent for all forms.





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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.