My Oracle Support Banner

The Reservation and API Checkpoint ID are Carried to the New Suffix of the Telephone Number (Doc ID 2155539.1)

Last updated on MARCH 13, 2019

Applies to:

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


Issue with the ability to reuse telephone numbers (TN's) because the reservation number and/or API Checkpoint ID is being carried to the new suffix of the TN when attempting to create the "Pending" suffix of the TN. These values should really be removed at the time the TN goes to an "InService" status, as they would not be used after the due date (DD) of that first order placing them in service. These values would be unique to the suffix on which they were obtained and it causes orders to reject when they are carried forward to the new suffix. It is a manual effort to remove these from the reservation and clear the API Checkpoint ID.

In the TN search window, while assigning a pending disconnect telephone number (TN) that was reserved through API to a PSR order, the application does not return the pending disconnect TN for assignment.
This is because the suffix that is in pending disconnect status has the following database columns API_CHECKPOINT_ID and API_ACTIVITY_NBR_CD populated. This issue occurs for both U.S & International TN.


1 In GUI create PSR order to disconnect a telephone number

2. In GUI create another PSR order to assign the telephone number being disconnected in step 1 (PendDisc)
    Fails to retrieve TN
    a. Click on Assign Telephone Number
    b. Search on NPA=XXX NXX=XXX Line=XXXX Type=Local (Company Owned) Status=(none) or blank
    c. Click on Search receive message "No Matches were found for your search"

    Successfully retrieves TN
    a. Click on Assign Telephone Number
    b. Search on NPA=XXX NXX=XX Line=XXXX Type=Local (Company Owned) Status=(none) or blank add API_CHECKPOINT_ID=12345
    c. Click on Search and PendDisc XXX-XXX-XXXX successfully retrieved
    d. TEL_NUM_INV row with TEL_NBR_SUF=1 sets the API_CHECKPOINT_ID null

Due to this issue, users cannot assign a "PendDisc" TN that has an API_CHECKPOINT_ID unless a manual SQL update is done to remove the API_CHECKPOINT_ID




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.