My Oracle Support Banner

createOrderByValueRequest XML API Incorrectly Determines Telephone Number Type for a 'Pending Disconnect' Ported Out Telephone Number (Doc ID 2139405.1)

Last updated on MARCH 21, 2019

Applies to:

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

Symptoms

While executing the createOrderByValueRequest XML API, when a 'Pending Disconnect' ported out telephone number (TN) is assigned to a Line, the type of the TN does not change to locally owned but instead remains as a ported out TN.  The new suffix that is created should be a type of WTN.

 

Changes

 

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
Changes
Cause
Solution
References


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