My Oracle Support Banner

Local Company Owned (WTN) numbers are being placed In Service as Ported In (NPIN) numbers (Doc ID 788061.1)

Last updated on MARCH 05, 2019

Applies to:

Oracle Communications MetaSolv Solution - Version 6.0.15 and later
Information in this document applies to any platform.
*** Reviewed on October 23, 2012 ***

Symptoms

Users have the ability to create a telephone number as a Number Ported In (NPIN) even though the number is a Local Company Owned (WTN) number. This behavior occurs in a specific scenario where the WTN was updated to a Number Ported Out (NPOUT) after the service was lost and the number won back, but the user did not run TN Recall to move the NPOUT TN back to a WTN and instead created an NPIN number from the Assigned Telephone Number window.

Steps To Reproduce:

1. Create a PSR order and put a WTN in service

WTN-0, tel_nbr_status = '6'

2. Create a PSR to disconnect the WTN and port out the TN on the same order

WTN-0, tel_nbr_status = '8'
NPOUT-1, tel_nbr_status = '6'

3. Create a PSR to disconnect the NPOUT and create the TN as an NPIN on the same order

WTN-0, tel_nbr_status = '8'
NPOUT-1, tel_nbr_status = '8'
NPIN-2, tel_nbr_status = '6'

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

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