CHAPTER 12.0 - Error Resolution

12.7 Error Codes and Error Descriptions

The errors listed below may be included on the daily error print.

Table L. ERROR CODES AND ERROR DESCRIPTIONS

Error	Description
072	PILOT TN IS NON-NUMERIC ON LOAD
073	CLASS OF SERVICE INVALID ON LOAD
074	TYPE OF SERVICE IS INVALID ON LOAD
081	DUPLICATE TN RECORD ON LOAD
084	MAIN TN IS NOT A TRUE MAIN TN ON LOAD
100	INVALID/NON-NUMERIC CUSTOMER CODE
101	NPA/NXX NOT VALID
103	MAIN TN NOT NUMERIC
105	CUSTOMER NAME MISSING
107	HOUSE NUMBER CONTAINS INVALID CHARACTERS
115	SERVICE CLASS INVALID
120	TN IS INCORRECTLY FORMATTED
126	INVALID TYPE OF SERVICE
701	HOUSE NUMBER NOT WITHIN RANGE
702	INSERT NOT ALLOWED, RECORD ALREADY EXISTS
703	MAIN ACCOUNT NOT FOUND
704	RECORD DOESN'T EXIST FOR DELETE
707	CUSTOMER CODE DOES NOT MATCH MAIN CUSTOMER CODE ON INSERT
709	STREET NOT FOUND
710	CUS CODE DOESN'T MATCH ON CHANGE
711	STREET OR CUS CODE DOESN'T MATCH FOR DELETE
712	RECORD DOESN'T EXIST FOR CHANGE
713	TN AND MAIN NUMBER MISMATCH
729	CHANGE FAILED, COMPLETION DATE CONFLICT WITH DISCONNECT FILE
730	INSERT FAILED, COMPLETION DATE CONFLICT WITH DISCONNECT FILE
731	CHANGE FAILED, COMPLETION DATE CONFLICT WITH TN DATABASE
732	RECORD IN DISCONNECT WITH GREATER COMPLETION DATE
734	DELETE RECORD IS FOR A LINE, TN IN DATABASE IS MAIN WITH SUBLINE
735	DELETE FAILED, RECORD IN TN DATABASE HAS SAME COMPLETION DATE
739	INVALID HOUSE NUMBER FORMAT
741	UPDATE NOT ALLOWED; FLAGGED FOR PS/ALI
742	SERVICE CLASS DOES NOT MATCH MAIN
743	SERVICE TYPE DOES NOT MATCH MAIN
744	CUSTOMER NAME DOES NOT MATCH MAIN
747	"S" ERROR WITHOUT MATCHING "I"
748	LOC DOESN'T MATCH MAIN
749	CUSTOMER CODE DOES NOT MATCH MAIN
751	INVALID FUNCTION CODE
752	INVALID NENA COMPANY ID
753	NO RECORD EXIST ON UNLOCK ( See section entitled "Special Service Offerings")
754	NO RECORD EXIST ON LOCK ( See section entitled "Special Service Offerings")
755	UNABLE TO MOGRATE A LOCKED RECORD ( See section entitled "Special Service Offerings")
756	COMPANY CODE MISMATCH ON CHANGE ( See section entitled "Special Service Offerings")
757	COMPANY CODE MISMATCH ON DELETE ( See section entitled "Special Service Offerings")
758	NENA COMPANY ID MISMATCH ON UNLOCK( See section entitled "Special Service Offerings")
760	LOCK EXCEEDED NUMBER OF RETRIES( See section entitled "Special Service Offerings")
762	REQUIRED NENA COMPANY ID MISSING FROM U OR M FUNCTION( See section entitled "Special Service Offerings")
763	PILOT DELETE ORPHANED SUBLINES

12.7.1 072 ERROR

Table M. 072 ERROR

072 ERROR	MAIN TN IS NON-NUMERIC
Definition	Initial load: 072 errors occur when the input record contains a non-numeric TN. (Previously BST 708 error)
Action	Check the NPANXX in the input record for all numerics and no blanks. Determine if the error resulted from a TN being incorrectly typed on the service order. If so, issue a corrected service order. If the customer information is correct, mark the print "COR" and write in the correct TN.

12.7.2 073 ERROR

Table N. 073 ERROR

073 ERROR	CLASS OF SERVICE INVALID ON LOAD
Definition	Initial load: 073 errors occur when the incoming record contains a class of service that is not defined as 911 valid (i.e. Class of service is not equal to 0-9 or A-D, previously BST 726 error.)
Action	Correct the class of service code to an allowed value and mark the error print "COR".

12.7.3 074 ERROR

Table O. 074 ERROR

074 ERROR	TYPE OF SERVICE INVALID ON LOAD
Definition	Initial load: 074 errors occur when the incoming record contains a type of service that is not defined as 911 valid (i.e. Type of service is not equal to 1-5, previously BST 727 error.)
Action	Correct the type of service code to an allowed value and mark the error print "COR".

12.7.4 081 ERROR

Table P. 081 ERROR

081 ERROR	DUPLICATE TN RECORD ON LOAD
Definition	Initial load: 081 errors occur if TSS process attempts two(2) or more inserts for the same TN. May be caused by duplicate TN sent in initial load file or initial load programs stopped and restarted at a point which had already processed. New error code.
Action	Verify extract problem did not create duplicate records and contact INTRADO DIU Analyst to request INTRADO investigate.

12.7.5 082 ERROR

Table Q. 082 ERROR

082 ERROR	STREET NOT IN MSAG ON LOAD
Definition	Initial load: A082 error is generated when a match on the directional prefix, street name, direction suffix, thoroughfare, community name, state and exchange cannot be found in the MSAG. (Cross reference error code 709 from BST process.)
Action	Determine if the street exists in the MSAG: If the street name on the error record is correct, but not in the MSAG, issue an AVR to the City / County / Parish to have the MSAG updated. If the street name on the error record is incorrect, and a valid MSAG entry exists, issue a service order to update the account data to existing MSAG standards. Mark the printout "SOI" and INTRADO will delete the error from the error file.

12.7.6 083 ERROR

Table R. 083 ERROR

083 ERROR	HOUSE NUMBER NOT IN RANGE ON LOAD
Definition	Initial load: 083 errors occur when the house number on the incoming record is not found in the house number range for the street, community and exchange on the MSAG. (Cross reference error code 701 from BST process.)
Action	Determine whether the TN record or MSAG data is correct: If the house number on the error record is correct, but not in the MSAG, issue an AVR to the City / County / Parish to have the MSAG updated. If the house number on the error record is incorrect, and a valid MSAG entry exists, issue a service order to update the account data to existing MSAG standards. Mark the printout "SOI" and INTRADO will delete the error from the error file.

12.7.7 084 ERROR

Table S. 084 ERROR

084 ERROR	MAIN TN IS NOT A TRUE MAIN TN
Definition	Initial load: 084 errors occur if the main TN on the incoming record is a subline associated with another main TN. This is a new error code.
Action	Determine if the main TN is correct: If the main TN is incorrect, correct the main account number field of the error record and note "COR". If the main TN is correct contact the INTRADO DIU Analyst to resolve the TN in the TSS database creating the conflict.

12.7.8 100 ERROR

Table T. 100 ERROR

100 ERROR	INVALID/NON-NUMERIC CUSTOMER CODE
Definition	100 errors occur when the customer code of the incoming record is not numeric. (Cross reference error code 764 from BST process.)
Action	Determine the correct customer code and issue an order to correct the customer code; if the record being processed is incorrect, note the error printout "SOI"; if the customer code of the main account is incorrect, send a Manual TN Maintenance form to correct the customer code and mark the error printout "COR".

Note:
All ICO service orders that are typed into the system by INTRADO have a customer code of 999. If the error record is for a subsidiary TN, be sure the correct customer code matched the customer code of the main account record in the database. If not, follow the error correction procedures for a 707 error prior to processing the error record.

12.7.9 101 ERROR

Table U. 101 ERROR

101 ERROR	NPA/NXX NOT VALID
Definition	101 errors occur when the incoming records contain a NPANXX combination that has not been found in the TSS prefix Table. (Cross reference error code 723 from BST process.)
Action	Determine if the NXX on the record is correct; if the NXX on the error record is correct and is a valid E911 NXX , refer the error to INTRADO and submit a new NXX form; if the NXX on there error record is incorrect, issue a service order to correct and mark the error printout "SOI".

12.7.10 103 ERROR

Table V. 103 ERROR

103 ERROR	MAIN TN NOT NUMERIC
Definition	103 errors occur when the main telephone number is not made up of ten numeric characters. (Cross reference error code 760 from BST process.)
Action	Determine the correct main account number. Issue a service order to correct the error and mark the error record "SOI".

12.7.11 105 ERROR

Table W. 105 ERROR

105 ERROR	CUSTOMER NAME MISSING
Definition	105 errors occur when the incoming record is owned by an ICO that has requested validation for blank Customer names. Cross reference error code 765 from BST process.
Action	Determine if the blank name on the error record is correct. If the error record is correct mark the print "COR" and request the INTRADO Analyst to remove edits for blank names. If the error record is incorrect, issue a service order to update the Customer name and mark the error printout "SOI".

12.7.12 107 ERROR

Table X. 107 ERROR

107 ERROR	HOUSE NUMBER CONTAINS INVALID CHARACTERS
Definition	107 errors will occur when the house number on the incoming record contains characters other than alphas or numerics. Cross reference error code 762 from BST process.
Action	Determine the correct house number. Issue a service order to correct the house number and mark the error print "SOI".

12.7.13 115 ERROR

Table Y. 115 ERROR

115 ERROR	SERVICE CLASS INVALID
Definition	115 errors occur when the incoming record contains a class of service that is not defined as 911 valid (i.e. Class of service is not equal to 0-9 or A-B). Cross reference error code 726 from BST process.
Action	Correct the class of service code to an allowed value and mark the error print "COR".

12.7.14 120 ERROR

Table Z. 120 ERROR

120 ERROR	TN IS INCORRECTLY FORMATTED
Definition	120 errors occur when the subline telephone number on an incoming record is not made up of ten numeric characters. Cross reference error code 708 from BST process.
Action	Determine the correct subline account number. Issue a service order to correct the error and mark the error record "SOI".

12.7.15 126 ERROR

Table AA. 126 ERROR

126 ERROR	INVALID TYPE OF SERVICE
Definition	126 errors occur when the incoming record contains a type of service that is not defined as 911 valid (i.e. Type of service is not equal to 1-5 Previously BST 727 error.)
Action	Correct the type of service code to an allowed value and mark the error print "COR".

12.7.16 701 ERROR

Table AB. 701 ERROR

701 ERROR	HOUSE NUMBER IS NOT IN MSAG RANGE
Definition	This error will occur if the street (matching on directional prefix, street name, directional suffix, thoroughfare, community, state, and exchange) was found in the MSAG, but the house number on the record being processed was not within the house number range on the MSAG.
Action	Determine if the street range exists in the MSAG. If the house number on the error record is correct, but not in the MSAG, issue an AVR to the City / County / Parish to have the MSAG updated. If the house number on the error record is incorrect, and a valid MSAG entry exists, issue a service order to update the account data to existing MSAG standards. Mark the printout "SOI" and INTRADO will delete the error from the error file.

12.7.17 702 ERROR

Table AC. 702 ERROR

702 ERROR	RECORD ALREADY EXISTS, INSERT NOT ALLOWED
Definition	This error will occur if a new record attempts to insert into the database and the NPA, NXX, and line number already exist.
Action	Using the Clean-up, determine whether the database record or the "error" record is correct. If the error record is correct, mark the print "COR" and change the Function of Change (FOC) code from "I" to "C". Once corrected by INTRADO, the error record will "overlay" the database record. If the database record is correct, mark the printout "DEL ERR REC".

12.7.18 703 ERROR

Table AD. 703 ERROR

703 ERROR	MAIN ACCOUNT NOT FOUND
Definition	This error will occur if the main account for the subsidiary record being processed cannot be found in the database. This can occur if either the main account on the subline record cannot be found in the TN database or the main account TN on the subline record being processed is found in the TN database but is not a main account. Cross reference error code 703 from BST process.
Action	Determine the TN's main account number. If the main account number is not in the TSS database, send a Manual TN Maintenance Form to INTRADO for the main account to be added to the database. When the database is updated with the main account number, and the error file is processed, the record will load to the TSS database.

12.7.19 704 ERROR

Table AE. 704 ERROR

704 ERROR	RECORD DOES NOT EXIST FOR DELETE
Definition	704 errors occur when the TN on an incoming delete SOI does not exist in the TN database or error file. This error will only go into an error batch if there is a problem that the automated process has detected.
Action	Determine if the account has been disconnected. If the account has been disconnect, line through the error on the print If the account is a working telephone number, issue a service order to add the telephone number to the E911 database. If issuance of a service order is not possible, send a Manual TN Maintenance form to INTRADO. Mark the error print "SOI".

12.7.20 705 ERROR

Table AF. 705 ERROR

705 ERROR	MAIN RECORD NOT FOUND FOR DELETE
Definition	This error will occur when the SOI can not be deleted because it does not exist. Cross reference error code 704 from BST process.
Action	Determine if the account has been disconnected. If the account has been disconnected, line through the error on the print and mark "DEL ERR REC". If the account is a working telephone number, issue a service order to add the TN to TSS and mark the print "SOI". If a service order is not possible, send a Manual TN Maintenance form to INTRADO to add the record.

12.7.21 707 ERROR

Table AG. 707 ERROR

707 ERROR	CUSTOMER CODE DOES NOT MATCH MAIN CUSTOMER CODE ON INSERT
Definition	This error will occur when the customer code on the subline on an SOI insert record does not match the customer code on the main TN in TSS. Cross reference error code 753 from BST process
Action	Determine the correct customer code for the subsidiary record and its main account: If the customer code on the record being process is incorrect, and the main account database record customer code is correct, issue a service order and note the error print "SOI". If the customer code of the main account database record is incorrect, send a Manual TN Maintenance Form to INTRADO to correct the customer code and mark the printout "COR".

12.7.22 708 ERROR

Table AH. 708 ERROR

708 ERROR	INVALID TN
Definition	This error will occur when the input record contains a non-numeric TN.
Action	Check the NPA NXX in the input record for all numeric and no blanks. Determine if the error resulted from a TN being incorrectly typed on the service order. If so, issue a corrected service order. Mark the error print "SOI".

12.7.23 709 ERROR

Table AI. 709 ERROR

709 ERROR	STREET NOT FOUND
Definition	If there is a community name on the interface record, a 709 error is generated when a match on directional prefix, street name, directional suffix, thoroughfare, community, state, and exchange cannot be found in the MSAG.
Action	Determine if the street exists in the MSAG. If the street name on the error record is correct, but not in the MSAG, issue an AVR to the City / County / Parish to have the MSAG updated. If the street name on the error record is incorrect, and a valid MSAG entry exists, issue a service order to update the account data to existing MSAG standards. Mark the printout "SOI" and INTRADO will delete the error from the error file.

12.7.24 710 ERROR

Table AJ. 710 ERROR

710 ERROR	CUS CODE DOESN'T MATCH ON CHANGE
Definition	This error occurs when the customer code on the SOI record does not match the customer code for the telephone number in the database. Cross reference error code 710 from BST process.
Action	Determine the customer code on the TN database record from the clean-up. Determine which customer code is correct, the database record, or the error record. If the TSS database record (clean-up) is correct, and all the other information on the error record is the same, mark the print "DEL ERR REC". If the customer code on the database record is correct, and all the other information on the error record is not the same, issue a service order and mark the print "SOI". If the customer code on the error record is correct, a database record on the old account was never deleted. Mark "DEL DB REC" on the error print with the incorrect TN and customer code. Change the FOC code on the error record to an "I" and note the error record "COR".

12.7.25 711 ERROR

Table AK. 711 ERROR

711 ERROR	STREET OR CUS CODE DOESN'T MATCH FOR DELETE
Definition	This error occurs when the directional prefix, street name, thoroughfare, and suffix on the record being processed doesn't match the record in the database. Cross reference error code 711 from BST process.
Action	Determine the existing street fields on the TN in the database (from the clean-up). Determine if the TN should be deleted. If the database record should not be deleted, mark the error record If the TN should be deleted from the TN database, note the error record "DEL DB ERR" and "DEL ERR REC". "DEL ERR REC".

12.7.26 712 ERROR

Table AL. 712 ERROR

712 ERROR	RECORD DOESN'T EXIST FOR A CHANGE
Definition	This error occurs when the ten(10) digit TN on the record being processed was not found in the database. Cross reference error code 712 from BST process. An option exists to have the FOC code on 712 errors automatically changed to an "I" and the record can be reprocessed. Contact INTRADO if this option is desirable.
Action	Verify that the TN on the error print should have been inserted in the database. If not a working TN mark the error print "DEL ERR REC". If working TN, mark them error print "COR"and change the action code from "C" to "I".

12.7.27 713 ERROR

Table AM. 713 ERROR

713 ERROR	TN AND MAIN NUMBER MISMATCH
Definition	713 errors occur when the SOI could not be processed successfully because it involves conflicting main and subline TNs. The incoming subline exists in the TN database associated with a different main TN. This is a new error code for BellSouth.
Action	Determine which main line TN is correct. If the error record main account TN is correct, mark the printout "COR" and note the correct main TN for the sublines associated with the conflicting main TN. If the error record main account TN is incorrect, mark the printout "SOI".

12.7.28 729 ERROR

Table AN. 729 ERROR

729 ERROR	CHANGE FAILED, COMPLETION DATE CONFLICT WITH DISCONNECT FILE
Definition	729 errors occur when the SOI is received with a completion date that is prior to the completion date on the TN in the disconnect file.This is a new error code for BellSouth.
Action	Determine if the error record should have posted prior to the disconnect record. If the TN error record should apply mark the print "COR". If the TN error record should not apply mark the print "DEL ERR REC."

12.7.29 730 ERROR

Table AO. 730 ERROR

730 ERROR	INSERT FAILED, COMPLETION DATE CONFLICT WITH DISCONNECT FILE
Definition	730 errors occur when the SOI insert record is for a TN that is in the disconnect file and the insert record has a completion date that is the same or prior to the completion date in the disconnect file.This is a new error code for BellSouth.
Action	Determine if the insert record should have posted before the disconnect and if yes, mark print "DEL ERR REC". If the TN should be added to the TN database, mark the print "COR" and INTRADO will process the TN.

12.7.30 731 ERROR

Table AP. 731 ERROR

731 ERROR	CHANGE FAILED, COMPLETION DATE CONFLICT WITH TN DATABASE
Definition	731 errors occur when the SOI change record could not be processed because another record for the same TN exists with the same or later completion date. This is a new error code for BellSouth.
Action	Determine the correct sequence of order activity. If the record in error is correct mark the print "COR" and INTRADO will update the TN database. If the error record is incorrect mark the print "DEL ERR REC".

12.7.31 732 ERROR

Table AQ. 732 ERROR

732 ERROR	RECORD IN DISCONNECT WITH GREATER COMPLETION DATE
Definition	732 errors occur when the SOI change record is received with a completion date that is prior to the completion date on the TN in the disconnect file.This is a new error code for BellSouth.
Action	Determine the correct sequence of order activity. If the record in error is correct mark the print "COR"and INTRADO will update the TN database. If the error record is incorrect mark the print "DEL ERR REC".

12.7.32 734 ERROR

Table AR. 734 ERROR

734 ERROR	DELETE RECORD IS FOR A LINE, TN IN DATABASE IS MAIN WITH SUBLINE
Definition	734 errors occur when the SOI is being processed with function code equal to "D" on a main account TN and sublines exist. Cross reference error code 729 from BST process.
Action	Determine if the main account and all sublines should be disconnected: If yes, change action code to "P"and mark error print "COR". If only the TN on the record being processed should be deleted, the associated sublines must first be associated with the correct main TN. Mark error print "COR" and provide the correct main telephone number for affected sublines.

12.7.33 735 ERROR

Table AS. 735 ERROR

735 ERROR	DELETE FAILED, RECORD IN TN DATABASE HAS SAME COMPLETION
Definition	735 errors occur when there is a record in the TN database with the same completion date as the SOI delete record. Possible causes could be due to processing synchronization problems.This is a new error code for BellSouth.
Action	Determine the status of the telephone number: If the delete should be made mark the error print "DEL ERR REC" and "DEL DB RCD". If the delete should not be made, mark the print "DEL ERR REC".

12.7.34 739 ERROR

Table AT. 739 ERROR

739 ERROR	INVALID HOUSE NUMBER FORMAT
Definition	739 errors occur when the SOI house number contains special characters in an alpha or alphanumeric house number. Cross reference error code 762 from BST process.
Action	Determine the correct house number. Issue a service order to correct the house number and mark the error print "SOI".

12.7.35 741 ERROR

Table AU. 741 ERROR

741 ERROR	UPDATE NOT ALLOWED; FLAGGED FOR PS/ALI
Definition	741 errors occur to protect the TN database from SOI processing on a PS/ALI (i.e. PinPoint or PBX/ALI) account which can only be updated by the PS/ALI process. New error code for BST.
Action	Mark the error print "DEL ERR REC".

12.7.36 742 ERROR

Table AV. 742 ERROR

742 ERROR

SERVICE CLASS DOES NOT MATCH MAIN

Definition

742 errors occur when the class of service on the SOI subline does not match the class of service on the main TN in the database. Cross reference error code 755 from BST process

Action

Determine the correct class of service for the subline and main TN.

If the class of service on the error record is incorrect, and the main TN database record class of service is correct, note the correct service class and mark the print "COR".
If the class of service of the main TN in the database is incorrect, prepare a Manual TN Maintenance Form with corrected class of service.

Note:
The class of service edit may be lifted if desired.

12.7.37 743 ERROR

Table AW. 743 ERROR

743 ERROR

SERVICE TYPE DOES NOT MATCH MAIN

Definition

743 errors occur when the type of service on the SOI subline does not match the class of service on the main TN in the database. Cross reference error code 756 from BST process.

Action

Determine the correct class of service for the subline and main TN.

If the class of service on the error record is incorrect and the main TN database record class of service is correct, note the correct service class and mark the print "COR".
If the class of service of the main TN in the database is incorrect, prepare a Manual TN Maintenance Form with corrected type of service.

Note:
The type of service edit may be lifted if desired.

12.7.38 744 ERROR

Table AX. 744 ERROR

744 ERROR	CUSTOMER NAME DOES NOT MATCH MAIN
Definition	744 errors occur when the customer name on the SOI subline does not match the customer name on the main TN in the database. Cross reference error code 754 from BST process.
Action	Determine the correct customer name for the subline and main TN. If the customer name on the error record is incorrect and the main TN database record customer name is correct, issue an order to correct the record. Mark the error print "SOI". If the customer name of the main TN in the database is incorrect issue an order to correct the main TN customer name. Mark the error print 'SO ISSUED".

Note:
The customer name edit may be lifted if desired.

12.7.39 747 ERROR

Table AY. 747 ERROR

747 ERROR	"S" ERROR WITHOUT MATCHING "I"
Definition	747 "S" errors are generated when there is a main TN change. A"D" record is created for the old main TN and an "I" is created for the new main field of the "D: interface record allowing it to be "held or saved" until the "I" matching record is found. The match is made on service order number. The 747 error is generated when the matching "I" record is not found. Cross reference error code 730 from BST process.
Action	This error may occur when an existing subsidiary line is used as the new main account number. If this is the case, there will also be a 702 error for the new main account number on the error file. Send a Manual TN Maintenance For to INTRADO to update the main account number on all subsidiary the 730 error record "COR" and it will be process against the database to remove the old main account number. Change the FOC code on the 702 error for the associated insert record from an I to a C to overlay the record with the more current information. The system will update all the subsidiary records with any new address information.

12.7.40 748 ERROR

Table AZ. 748 ERROR

748 ERROR	LOC DOESN'T MATCH MAIN
Definition	748 errors occur when the SOI change or insert of a subline, non SLA, does not match the LOC of the main TN. This is a new error code for BellSouth.
Action	Determine if a secondary listed address should be present. If yes, mark print "COR" and INTRADO will set the appropriate SLA flag. If not, fix the LOC on the subline to match main as appropriate or fix the LOC on the main if appropriate. Issue service order and mark error print "SOI".

12.7.41 749 ERROR

Table BA. 749 ERROR

749 ERROR	CUSTOMER CODE DOES NOT MATCH MAIN
Definition	749 errors occur when the customer code on the SOI subline does not match the customer code of the main account in the TN database.
Action	Determine the correct customer code for the subline and its main account. If the customer code on the record being processed is incorrect, and the main account database record customer code is correct, issue a service order and note the error print "SOI". If the customer code of the main account database record is incorrect, send a Manual TN Maintenance Form to INTRADO to correct the customer code. Mark the error print "COR".

12.7.42 751 ERROR

Table BB. 751 ERROR

751 ERROR	INVALID FUNCTION CODE
Definition	A 751 error occurs if the incoming SOI record contains an invaD - Delete lid function code. Valid function codes are: C - Change D - Delete I - Insert P - Pilot Delete U - Unlock TN (LNP) M - Migrate TN (LNP) E - Error Delete (LNP)
Action	Resend the order with a valid function code. Mark the error print "SOI".

12.7.43 752 ERROR

Table BC. 752 ERROR

752 ERROR	INVALID NENA COMPANY ID
Definition	Occurs when the NENA Company ID on the SOI record is either invalid or unrecognized.
Action	Determine that data being sent contains a valid NENA Company ID If valid, verify the NENA Company ID is in the proper field position: 232-Byte Positions 225-229 or 512-Byte Positions 261-265 If valid, and NENA Company ID is in the proper field position: Contact INTRADO to have NENA CO ID built into TSS system, and have current data converted. Return faxed error report to INTRADO and request that INTRADO apply record If not valid, obtain a valid NENA Company ID by visiting the NENA homepage http://www.nena9-1-1.org/companyid or call 800 332-3911. Click here to access website Notify INTRADO of newly registered NENA Company ID Return faxed error report to INTRADO with correction and request that INTRADO apply record Include a valid NENA Company ID on all future orders If no data is to be sent in the previously stated field positions Return faxed error report to INTRADO and request that INTRADO apply record.

12.7.44 763 ERROR

Table BD. 763 ERROR

763 ERROR	PILOT DELETE ORPHANED SUBLINES
Definition	A 763 error occurs if a delete SOI record for a pilot TN with sublines is processed, but no deletes were received for the sublines. The pilot TN posts to the error database with a 763 error. Both the pilot and sublines records remain in the TN database.
Action	Determine if the sublines associated with the error pilot record should be deleted. Once determined, issue a service order accordingly. Mark the error print "SOI".