ASR Import API's Handle the CPT Field Edits/Behavior Inconsistently
Last updated on APRIL 03, 2014
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 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 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.
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