NANC 355

Modification of NPA-NXX Effective Date

Origination Date :04/12/2002



Business Need:


When the NPAC inputs an NPA Split requested by the Service Provider and the effective date and/or time of the new NPA-NXX does not match the start of PDP, the NPAC cannot create the NPA Split in the NPAC SMS.  To correct this problem the NPAC can contact the Service Provider and have them delete and re-enter the new NPA-NXX specified by the NPA Split at the correct time, or the NPAC can delete and re-enter the NPA-NXX for the Service Provider.

However, the NPA-NXX may already be associated with the NPA Split at the Local SMS, and the subsequent deletion of the NPA-NXX will cause that specific record to be old time-stamped.  When the NPA-NXX is re-created, that new record will have a different time stamp, and it requires a manual task for the Service Provider to search for new NPA-NXX records which might match the NPA Split.  If identified and corrected, it will be added.  If not identified, it will affect call routing after PDP.

Final Resolution:

Functional Backward Compatible:  YES


An enhancement to the NPAC SMS will allow NPAC personnel to modify the NPA-NXX Effective Date so long as no pending-like SVs exist so that Service Providers that do not support this modification functionality will still be able to process a delete and re-add from the NPAC.


It would be the responsibility of the owner of the NPA-NXX to resolve issues of pending versions with due dates prior to the new effective date before a change could be made.


The NPAC will notify the SOA/LSMS that support the modification enhancement of a modified effective date (M-SET).


Implemented in FRS 3.4.0a 3/19/10.

Implemented in IIS 3.4.0a 3/19/10

Related Release:

Implemented in FRS 3.4.0a 3/19/10

Implemented in IIS 3.4.0a 3/19/10

Status: Implemented