On inbound map control segments

Table 1-14 lists the format, cause, and solution (if applicable) for the ECMap messages related to inbound map control segments, in numeric order by message number.

**Table 1-14: ECMap messages related to inbound map control segments**
Message	Cause	Solution
`(6000) TRACE: Reading < >- Seg Delim <segment delimiter> Elem Delim <element delimiter> Sub Delim <subelement delimiter> Test Ind <test indicator value>`
`(6001) ERROR: expected < segment> read <segment>, Skipping Forward to Next <segment>`	Expecting a control segment such as GS or ST and MAPPER is not finding it. It therefore, is reading forward to next occurrence of one of those records.	EDI data sent is corrupted. Report to sender.
`(6002) ERROR: expected <segment> read <segment>, Aborting`	Expecting a read of a particular segment type and did not find it. The MAPPER aborts the transaction.	EDI data sent is corrupted. Report to sender.
`(6003) TRACE: Looking.. Segment <segment> (control)`	Occurs when Verbose Trace is on. Informational message indicates processing is looking for a particular Segment control.
`(6004) TRACE: Level <level number>, Segment <segment> (control)`	Occurs when Verbose Trace is on. Informational message indicates current level number and looking for a particular Segment control.
`(6005) ERROR: errors in processing ST, skipping forward`	Expecting a control segment such as GS or ST and MAPPER is not finding it. It therefore, is reading forward to next occurrence of one of those records.	EDI data sent is corrupted. Report to sender.
`(6006) TRACE: Level <level number>, Segment <segment> (control) Rules`	Occurs when Verbose Trace is on. Informational message indicates current level number and the execution of a particular control rule number.
`(6007) TRACE: Level <level number>, Segment <segment> (default) Rules`	Occurs when Verbose Trace is on. Informational message indicates current level number and the execution of the default rule. This is used in the default flow, where you can change levels based on the default.
`(6008) TRACE: Level <level number>, Segment <segment> <element> Rules`	This message occurs when Verbose Trace is on. Informational message indicates that at this Segment Name/Element number the execution of a particular rule number is performed.
`(6009) TRACE: Level <level number>, Segment <segment> (mapping)`	Occurs when Verbose Trace is on. Informational message indicates that at this level, the Segment is mapped.
`(6010) TRACE: Level <level number>, Segment <segment> (conditional) <NOT MAPPED>`	Occurs when Verbose Trace is on. Informational message indicates that at this level, the Segment is conditional and is not mapped.
`(6011) TRACE: Level<level number>, MEMVAR Rules`	Occurs when Verbose Trace is on. Informational message indicates levels have changed based on a Memory variable rule.
`(6012) TRACE: <segment> CNDVAR LOAD`	Occurs when Verbose Trace is on. Informational message indicates the processing of a Segment loading the Conditional Store variables.
`(6013) ERROR: <segment> Not Terminated By <segment>`	The EDI X12 envelope defines segments that must be followed by specific segments. The MAPPER has encountered a Segment that is not in the proper location, or has not been properly terminated before encountering another Segment	EDI data sent is corrupted. Report to sender.
`(6014) ERROR: ISA # < > Not Equal to Expected # < >, Resetting ISA # to < > for Tptner <trading partner name >`	If WWIXERR set, this message can appear. Error based on ISA control counters. Not finding correct control count and generating message accordingly.	Bad EDI data. Report to sender.
`(6015) ERROR: Group Control # < > Not Equal to Expected Number < >`	Group control count does not match expected resulted.	Bad EDI data. Report to sender. The following messages are related to the BIN segment, that is the binary segment. (allows you to place binary data within an X12 transmission)
`(6016) ERROR: Incoming EDI BIN seg Numeric Field Has Non-Numeric Data: < > Transaction Aborted`	Number of bytes in file in not numeric.	Bad Data. Report to Sender.
`(6017) ERROR: Incoming EDI BIN segment with Non-Zero Char Count is Missing File Transaction Aborted`	Actual data after the character count can not be found.	Bad Data. Report to Sender.
`(6018) ERROR: Incoming EDI BIN File <binary file name> EOF After < > Chars`	Number of characters transmitted does not match expected number of characters.	Bad Data. Report to Sender.
(6019)`WARNING: BIN FILE <binary file name> is EMPTY	Binary file has no data.	Bad Data. Report to Sender.
`(6020) WARNING: BIN FILE NAME BLANK`	Name of binary file has not been entered. Parameter is blank.	Bad Data. Report to Sender.
`(6021) ERROR: Can’t Open BIN File <binary file name> Transaction Aborted`	Binary segment was transmitted and system could not create a file definition to place binary data.	Bad Data. Report to Sender.
`(6022) ERROR: Reset EDI File to First Seg Delim in BIN FILE after < > Chars`	Binary segment was transmitted and system could not create a file definition to place binary data. Length of binary file does not match the BIN segment specifications.	Bad Data. Report to Sender.
`(6023) ERROR: Read Unexpected < >`
`(6024) ERROR: < > Not Terminated by < >`
`(6025) ERROR: ISA Control Number < > exceeds max length`
`(6026) ERROR: ISA Control Number not numeric using < >`
`(6029) TRACE: Level <level number>, <amount of RAM available> of RAM Memory Free`	Occurs when Verbose Trace is on. Informational message indicates the amount of RAM Memory available at this level.
`(6030) TRACE: Level <level number>, Segment<segment><element> Edit Rule`	Occurs when Verbose Trace is on. Informational message indicates that at this Level, Segment, Element, this rule is performed.
`(6031) TRACE: Level <level number>, Segment <segment> (mapping)`	Occurs when Verbose Trace is on. Informational message indicates an element is mapped at this Level, Segment.
`(6032) TRACE: Level <level number>, Segment <segment> (conditional) <NOT MAPPED>`	Occurs when Verbose Trace is on. Informational message indicates an element is not mapped at this Level, Segment, because it is conditional
`(6033) TRACE: Level <level number>, <#> processing RPTMAP Segment <segment>`	Occurs when Verbose Trace is on. Informational message indicates a Repeat Map function is processed for this Level, Segment.
`(6034) TRACE: Level<level number>, Loading Next <#> CNDVAR`	Occurs when Verbose Trace is on. Informational message indicates that the next Conditional Store Variable is loaded for this Level.
`(6050) ERROR: Segment <segment name> exceeds Max Elements`	Occurs on Inbound when the expected number of elements for this segment is exceeded.	Check incoming data.
`(6051) ERROR: Level <level number>, Ignored < > Contains Data`
`(6060) ERROR: Invalid source string`
`(6061) ERROR: Invalid search string`
`(6062) ERROR: Invalid number of occurrence string`
`(6063) ERROR: Invalid replace string`
`(6064) ERROR: The replace string is too big`
`(6080) ERROR: Batch Group Count <value> Does not Match Trailer Count <value>`	The number of records in the batch does not match the count in the trailer record.
`(6081) ERROR: Batch Control Number <value> Does Not Match Trailer <value>`	The control number in the batch header does not match the batch trailer control number.
`(6082) ERROR: EOF Reached - Expecting %s`	EOF (end of file) is received unexpectedly.
`(6082) ERROR: EOF Reached - Expecting %s`	Errors prevented the Batch file from being processed.
`(6084) OK: Received Batch Transmission Error Header`	An error occurred in the batch transmission header.
`(6085) ERROR: Batch Header Number Not Numeric: <value>`	The batch header number was not a valid numeric value.
`(6086) ERROR:Batch Transmission Type Invalid: <value>`	Batch Transmission Type Invalid
`(6087) ERROR: Batch Header Has Version: <value> Expecting`	An unexpected Batch Version is sent.
`(6088) ERROR: Expected Batch Trailer, Read Batch Header`	Expected Batch Trailer, Read Batch Header.
`(6089) ERROR:Invalid Transmission Header, Searching Forward`	The transmission header is invalid. The program searches ahead for the next header.
`(6090) ERROR: Transmission Bin Header Number Not Numeric: <value>`	Transmission Bin Header Number Not Numeric: <value>
`(6091) ERROR: Mandatory NCPDP Field %s is Blank`	A mandatory field is missing.
`(6092) ERROR: NCPDP Telecom Version <value> unexpected`	An unsupported Telecommunications version is trying to be processed.
`(6093) ERROR: Read Batch Header, Expected Group or Trailer`	Read Batch Header, Expected Group or Trailer
`(6094) ERROR: Invalid TP Lookup Choice for NCPDP`	An inbound error. The type of TP lookup is invalid for NCPDP, because NCPDP requires an ODBC trading partner.
`(6095) ERROR: Invalid NCPDP Segment Name %s`	Invalid NCPDP Segment Name %s
`(6096) ERROR: Transmission Hdr Transaction Count <value> But Actual Count is <value>, Aborting Trans`	The actual count of transactions in a transmission does not match the value specified in the file.
`(6097) ERROR: Expected Segment Sep After Group Sep, Aborting Trans`	Expected Segment Sep After Group Sep, Aborting Trans
`(6098) FATAL: Transaction Header Not Found, Aborting`	Transaction Header Not Found, Aborting
`(6099) ERROR: Transaction Count %ld Does Not Match Transactions`	Transaction Count %ld Does Not Match Transactions
`(9000) ERROR: NCPDP switch does not match TP lookup switch`	A TP lookup is used that does not support the inbound type (Batch or Telecom) selected.
`(6070) ERROR: Invalid string offset or length`
`(6071) ERROR: Exceeds the string boundary`
`(7001) ERROR: No Table Ref Destination Field`	Cross reference rule executed to a table but there is no field for it to go into.	Check cross reference table definitions to ensure that destination field has been defined.
`(7002) OK: Transaction for Trade Partner<trading partner name>Copied To File<file name>`
`(7003) OK: Destination File <file name>`	Information only. Transaction was copied to a file instead of passing through a map. 7002 displays what transaction was copied to what file. 7003 displays destination filename.	This is controlled through the Trade Agreement records where you instruct the system to copy the EDI data to another file while it is passing through a map.
`(7004) WARNING: No Flow Records Defined for < map name >`	Indicates that flow has not been defined.	Define the levels and flow information and regenerate the map.
`(7005) WARNING: Map Line Count Does Not Match HDR Count`	Indicates the *.MAP file is invalid or has somehow been corrupted.	Regenerate the map. If the error occurs again, call support for assistance.
`(7006) FATAL: < xref map table > Index Out of Range`	Occurs during map generation when loading the map into memory. This internal check occurs when table header information such as the total number of tables in map does not match the number of tables in the map.	Regenerate map. If the error occurs again, call support for assistance
`(7007) FATAL: Invalid record in map at <line number> line`	Indicates that map definition contains errors.	Check map definition and modify. regenerate map. If the error occurs again, call support for assistance.
`(7008) FATAL: No Trading Partner Fields Were Defined`	No Trading Partner field has been defined in the application.	First record read on an outbound map must contain a field where the attribute has been set to Trading Partner. Check Trading Partner Status to ensure that field attribute has been selected.
`(7009) FATAL: Map Error Keyed IO Rule with No Filename`	A keyed- I/O rule was executed with no filename specified.	Modify the rule in question.
`(7010) ERROR: < Backout > point < point position > out of range`	The number of checkpoints or backout points is over the maximum number of system-defined checkpoints.	Call Support for assistance.
`(7011) ERROR: < Files/X12 > Backout point < point number > Called When File Closed`	System error message for the Checkpoint Backout command.	Call Support for assistance.
`(7012) ERROR: < >Backout point < > With No Prior Save`	Backout command was requested before a checkpoint command was issued.	Modify map to insert a checkpoint prior to doing a backout. All backouts must have prior checkpoints, as you are backing out to the prior checkpoint.
`(7013) OK: EDI Backout point < point number > Executed.`	Information only. The backout was executed.
`(7014) FATAL: Failed Backout Pt < point number > TpNo <internal trading partner number>`	System error message. Backout failed for this trading partner.	Call support for assistance.
`(7015) ERROR: Output Files Reset Due To Transaction Errs`	Indicates that the system encountered a Fatal error and backed out the transaction.	Data is corrupted and has been backed out. Modify data or report to sender.
`(7016) OK: Output Files Reset to Backout Point < point number >`	Information only. Output Files Reset to Backout Point.
`(7017) FATAL: Destination File Switch and not ST Seg`	Occurs on Inbound when the EDI Out Destination File field has been checked in the Trade Agreement record. Performs mapping rules on incoming data. The ST segment initiates this action.	Call support for assistance.
`(7018) FATAL: Exceeded max Field size < system-defined maximum size of a field > searching for Field delim, EDI Rec # < inbound number of X12 records >`	Missing delimiters.	Modify file and regenerate the map.
`(7019) FATAL: Failed trying to open < original number > File, errno = < >`	Insufficient number of file handles.	Set system’s config.sys file to allow for a sufficient number of files to be opened. If you are mapping multiple record types, the system creates a new file for each record type.
`(7020) FATAL: Could Not Load < dynamic link library name>`	Cannot find <dynamic link library> in system paths.	Double check whether the <dynamic link library> path is located in the system path.
`(7021) FATAL: Could Not Get Address for Procedure <procedure name>`	To use User exit command, the USEREXIT.DLL file must be available.	Ensure that USEREXIT.DLL file is in current path.