CHAPTER 12.0 - Error Resolution

12.9 Directions for Correcting Errors Electronically

Table BE. Directions for Correcting Errors Electronically

Directions for Correcting Errors Electronically
Error Code	Error Message	Occurs when. . .	Corrective Action for ICO
100	Customer Code not numeric	A character other than 999 is sent in the customer code field of the incoming record	Issue corrective SOIR for errored TN showing 999 in the customer code field
101	NPA/NXX not valid	The incoming record contains a NPA/NXX combination that is not valid E911 database tables	Determine if NPANXX is correct and· If correct, submit ICO E911 Notification Form to INTRADO (See Tab 3) and resubmit I FOC SOIR for TN· If incorrect, submit E FOC SOIR to delete TN error and submit new SOIR for correct TN
103	Main TN not numeric	The main telephone number shown on the SOIR is non-numeric	Submit E FOC SOIR to delete invalid TN error and resubmit new SOIR for correct TN
105	Name missing	The customer name field on the incoming SOIR is blank	Issue corrective SOIR for errored TN with correct customer name
106	Address missing	The address field on the incoming SOIR is blank	Issue corrective SOIR for errored TN with correct MSAG valid street address.
107	House number contains invalid characters	The house number on the incoming SOIR contains characters other than alpha or numeric.	Determine the correct MSAG valid house number and submit corrective SOIR for errored TN
108	House number is too long	The house number on the incoming SOIR contains too many characters	Determine the correct MSAG valid house number and submit corrective SOIR for errored TN
109	Street direction is too long	The directional prefix for the street on the incoming SOIR contains too many characters	Determine the correct MSAG valid street name and submit corrective SOIR for errored TN
110	Street direction is invalid	The directional prefix for the street on the incoming SOIR contains invalid characters	Determine the correct MSAG valid street name and submit corrective SOIR for errored TN
111	Street name is too long	The street name with thoroughfare and suffix on the incoming SOIR contains too many characters	Determine the correct MSAG valid street name and submit corrective SOIR for errored TN
112	Street name has invalid characters	The street name for the street on the incoming SOIR contains invalid characters	Determine the correct MSAG valid street name and submit corrective SOIR for errored TN
113	Community name is too long	The community name on the incoming SOIR contains too many characters	Determine the correct MSAG valid community name for the street address and submit corrective SOIR for errored TN
115	Service Class Invalid	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).	Submit corrective SOIR with valid class of service.
116	House number suffix is too long	The house number suffix on the incoming SOIR contains too many characters	Determine the correct house number suffix and submit corrective SOIR for errored TN
120	TN is incorrectly formatted	The TN on an incoming SOIR is not made up of ten numeric characters.	Check the NPANXX in the record for all numeric and no blanks. Submit E FOC with NPANXX of errored TN to delete error record then re-submit SOIR with correct TN
126	Invalid type of service	The type of service on an incoming SOIR contains a type of service value other than 0 or 3	Submit SOIR with valid type of service, 0 or 3
701	House number is not in MSAG range	The house number on the incoming SOIR is not found in the house number range for the street and community on the MSAG	Determine if the street range exists in the MSAG. If the house number on the SOIR is correct but is not in the MSAG, issue an AVR to the E911 coordinator to update the MSAG house number range If the house number on the SOIR is incorrect issue a SOIR with the correct house number that matches the MSAG house number range
702	Record already exists, insert not allowed	The SOIR has a FOC of I and attempts to insert a TN into the database that already exists	Using the image of the existing record that is sent with the error, determine if the existing database TN is incorrect or if the SOIR error is incorrect. If the existing database TN is incorrect, resubmit the SOIR with a FOC of C to overlay the existing data with the SOIR data If the error record TN is incorrect, resubmit a SOIR with FOC of E to delete the errored record and then resubmit another SOIR for the correct TN
704	Record does not exist for delete	The TN for the incoming SOIR does not exist in the database	Determine if the account has been disconnected: If disconnected, submit E FOC SOIR to delete error record If error record was issued for invalid TN, submit E FOC SOIR to delete error record and resubmit new D FOC SOIR for correct TN
705	Main account record not found for delete	The main account TN on the incoming SOIR does not exist in the database	Determine if the account has been disconnected: If disconnected, submit E FOC SOIR to delete error record If error record was issued for invalid TN, submit E FOC SOIR to delete error record and resubmit new D FOC SOIR for correct TN
709	Street not found in MSAG	The directional prefix, street name, community or state on the incoming SOIR cannot be found in the MSAG	Determine if the street exists in the MSAG: If the prefix, street, community and state shown on the error record is not found in the MSAG issue an AVR to the E911 Coordinator to have the MSAG updated Note: Once the MSAG is updated the error record will process and load. If the prefix, street, community or state on the error record is incorrect and a valid MSAG entry exists, resubmit a corrective SOIR
710	Customer code doesn't match on change	The customer code shown for the incoming SOIR doesn't match the customer shown on the existing database record	Determine the correct customer code and resubmit corrective SOIR with customer code of 999 or blanks
711	Customer code or street name does not match on delete	The customer code, directional prefix, street name and suffix on the incoming SOIR does not match the TN in the database	Using the image of the existing record that is sent with the error, determine if the TN in the database should be deleted If the existing database TN is should be deleted, resubmit a correct D FOC SOIR If the existing database TN should not be deleted and the error record TN is incorrect, resubmit a SOIR with FOC of E to delete the errored record and then resubmit another SOIR for the correct TN
712	Record does not exist for change	The incoming C FOC SOIR TN is not found in the TN database	Determine if the error record TN is valid: If error record TN is valid, no action is necessary. Processing in the TN database will change the C FOC to an I FOC and insert the record. If the error record TN is invalid, resubmit a D FOC SOIR to delete the TN from the TN database and then resubmit the C FOC SOIR for the correct TN
713	TN and main account mismatch	The main account shown on the incoming SOIR doesn't match the main account shown on the database record. Note: This error will occur frequently if the ICO attempts to use main account / sub account processing.	Submit D FOC on existing database record to delete TN with different main account and IFOC with appropriate changes on corrective SOIR showing the TN and the main account as the same number.
729	Change failed, completion date conflict with disconnect file	An incoming SOIR contains a completion date that is equal to or earlier that the completion date of the record that has been deleted	Determine if TN is valid and should be changed If TN is valid submit corrective SOIR with changes showing a completion date that is later than the disconnect date If the TN is invalid, submit E FOC to delete error record
730	Insert failed, completion date conflict with disconnect file	The incoming insert SOIR is for a TN that has been disconnected and the date on the insert SOIR is the same or prior to the date of the disconnected TN.	Determine if the insert record should have posted prior to the disconnect: If yes, issue E FOC SOIR to delete the error record If no, issue resubmit I FOC SOIR with completion date later than disconnect date
731	Change failed, completion date conflict with TN database	The incoming change SOIR has a completion date that is the same or prior to the date of the TN shown in the database	Determine the correct sequence of order activity for the TN: If the error record change is correct, resubmit C FOC SOIR with later completion date If error record is incorrect, submit E FOC SOIR to delete error record
732	Record in disconnect with greater completion date	The incoming change SOIR has a completion date that is the same or prior to the date of the TN in the disconnect file	Determine the correct sequence of order activity for the TN: If the error record change is correct, resubmit C FOC SOIR with later completion date If error record is incorrect, submit E FOC SOIR to delete error record
735	Delete failed, record in TN database has same completion	The incoming delete SOIR has a completion date that is the same completion date of the TN in the database	Determine the correct sequence of order activity for the TN: If the error record delete is correct, resubmit D FOC SOIR with later completion date If error record is incorrect, submit E FOC SOIR to delete error record
738	MSAG update caused a TN error	This error is not generated as a result of incoming SOIR but is generated when INTRADO performs a MSAG update that deletes the address shown on the TN record	Contact INTRADO Data Analyst for resolution.
739	Invalid house number format	The incoming SOIR contain special or invalid characters for an alpha or alphanumeric house number	Determine correct house number for TN and resubmit correct SOIR
741	Update not allowed, flagged for PS-ALI/PinPoint	The TN on the incoming SOIR belongs to a TN that is shown for a PS/ALI or PinPoint PBX customer	Submit E FOC SOIR to delete error record
751	Invalid function code	The incoming SOIR contains an invalid function code. Valid function codes are: C = CHANGE D = DELETE I = INSERT E = DELETE ERROR U = UNLOCK M = MIGRATE	Resubmit the SOIR with valid function code
752	Invalid company ID	The incoming SOIR has an invalid NENA ID	Resubmit the SOIR with a valid NENA ID
753	No record exists on unlock	The TN on the incoming unlock SOIR does not exist in the TN database	Determine if the correct TN was sent on the error record: If correct, submit IFOC SOIR for TN and then resubmit U FOC SOIR If incorrect, submit E FOC SOIR to delete error record
754	No record exists on lock	The TN on the incoming Migrate SOIR does not exist in the database.	Determine if the error record TN is valid: If error record TN is valid, no action is necessary. Processing in the TN database will change the M FOC to an I FOC and insert the record. If the error record TN is invalid, resubmit a E FOC SOIR to delete the error record
755	Unable to migrate locked record	The TN in the database for the incoming Migrate SOIR shows a locked status	Determine if the error record TN is valid: If valid, contact the donor company to issue an unlock SOIR. The error record will process once the unlock SOIR is received. If the error record TN is invalid, resubmit a E FOC SOIR to delete the error record
756	Company code mismatch on change	The NENA ID on the incoming C FOC SOIR does not match the NENA ID of the TN record in the database	Determine if the error record NENA ID is valid: If valid, contact the donor company to issue an unlock SOIR and resubmit the SOIR as a M FOC with the appropriate changed data If the error record NENA ID is invalid, resubmit a E FOC SOIR to delete the error
757	Company code mismatch on delete	The NENA ID on the incoming D FOC SOIR does not match the NENA ID of the TN record in the database	Determine if the error record NENA ID is valid: If valid, contact the donor company to issue an unlock SOIR and resubmit the SOIR as a M FOC to migrate the record and the a subsequent D FOC to delete the TN record If the error record NENA ID is invalid, resubmit a E FOC SOIR to delete the error
758	Company code mismatch on unlock	The NENA ID on the incoming U FOC SOIR does not match the NENA ID of the TN record in the database	Determine if the error record NENA ID is valid: If valid contact the donor company to issue an unlock SOIR resubmit the SOIR as a M FOC to migrate the record resubmit a subsequent U FOC to unlock If the error record NENA ID is invalid, resubmit a E FOC SOIR to delete the error record
760	Lock exceeds number of retries	The 755 error for a Migrate order is unsuccessful for 14 days	No action required. INTRADO will take appropriate action based on dial tone ownership as shown in NPAC. ICO will receive notification of action taken for the TN on the weekly NPAC Validation report.
762	NENA ID required for U or M FOC SOIR	The incoming U or M SOIR does not have a valid 3 to 5 digit NENA ID	Submit E FOC to delete SOIR record from error Resubmit correct U or M SOIR with valid NENA ID
781	Error record does not exist for delete	The incoming E FOC TN cannot be found in the error database	Verify the TN on the E FOC SOIR record matches the TN in the error database: If TN matches, no action required. The errored record has been previously deleted or resolved. If TN doesn't match re-submit E FOC SOIR for correct TN
782	Company code mismatch on error delete	The incoming E FOC TN contains a NENA company ID that does not match the NENA ID shown on the TN in the error database	Verify the NENA ID on the E FOC SOIR record matches the TN in the error database: If NENA ID matches, no action required. The errored record has been deleted or resolved. If NENA ID doesn't match re-submit E FOC SOIR for correct NENA ID
783	Unlock failed; main account has sublines	The incoming U FOC TN is in the database as a main account with other TNs shown as sublines but no U FOC was received on the sublines Note: Since the ICO main account and Calling number TN are to be the same TN, this error would be received only if the TN in the database had been submitted with a different main account on a previous SOIR.	There are two possible corrective actions: If all accounts shown with the main account are to be unlocked submit a U FOC for each TN associated with the original main account. If all accounts are not to be unlocked submit a D FOC for the existing subline showing the erroneous main account and then resubmit an I FOC for the TN shown with the Calling number TN as the main account.
792	I FOC record exists with a different Company ID	The TN shown on the I FOC SOIR has a different NENA Company ID than the existing TN in the database	Verify the TN on the errored record: If the TN is correct and is to be migrated, submit an E FOC on the error record SOIR and then resubmit a corrective SOIR with appropriate record changes as a M FOC If the TN on the error record is incorrect, submit an E FOC to delete the error record.