On types, usage and type linking

The messages in this section focus on valid data entry and correct definitions of fields in the User Field/Element Map, User File, and Map rules. Some of the messages are displayed during data entry and other of the messages are written to error logs as the maps are generated and run. Some messages are described as internal program errors. Internal program error messages are not expected to ever be displayed. If an internal error message occurs or if the suggested corrective action for a message does not solve the problem, call support for assistance.

Table 1-8 lists the format, cause, and solution (if applicable) for the ECMap messages related to types, usage, and type linking, in numeric order by message number.

**Table 1-8: ECMap messages related to types, usage, and type linking**
Format	Cause	Solution
`(0101) FATAL: invalid type – <field>`	An arithmetic rule could be attempting to process alphanumeric field types. This error should be reported when Map generation takes place.	Modify arithmetic rule or modify data types to allow arithmetic operation on numeric fields.
`(2102) ERROR: invalid Rule Parameters`	A run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. This message is usually caused by a map rule with incorrect parameter type fields. This message is not expected to be displayed because the “Define Rules” option does data entry time checking on valid map rule parameters.
`(2104) ERROR: invalid relational operator code`	A run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It is usually caused by a map rule with an incorrect relational operator code. This message is not expected to be displayed because the “Define Rules” option does data entry checking on valid relational operator codes.	If the cause is not apparent from the error log, call support for assistance.
`(2105) ERROR: invalid conditional check type`	A run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It is caused by a map rule making a comparison between incompatible field value types or by one of the field values compared not having been designated with a correct type of field. This message is not expected to be displayed because the because the “Define Rules” option and “User File” mapping options do data entry time checking on valid field types.	Examine the error log to identify the field name or map rule with the invalid field type. Then examine the User File or Map Rule definition of this field. Correct any User File or Map Rule errors. Regenerate the map. If the error occurs again, call support for assistance.
`(2106) ERROR: invalid EDI standard field type`	A run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It is caused by a generated table field with an invalid field type. This message is not expected to be displayed because both the “User File” option and the generate map option check for valid field types.	Examine the error log to identify the field name with the invalid field type. Then examine the User File definition of this field. Correct any User File errors. Regenerate the map. If the error occurs again, call support for assistance.
`(2107) ERROR: condition and field- must be a RECFLD or MEMVAR`	A run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It is usually caused by an invalid outbound Conditional Check field specified during User Field/Element mapping. Conditional check fields must be defined as either record fields or memory variables in the User File database. This message is not expected to be displayed because the “User Field/Element” mapping option does data entry time checking on valid Conditional fields.	If the cause is not apparent from the error log, call support for assistance.
`(2120) ERROR: unexpected authority qualifier <authority qualifier read>`	In the inbound file, GS section, you have an authority qualifier that does not belong in this section.	In the inbound file, remove the authority qualifier.
`(2121) ERROR: unexpected security qualifier <security qualifier read>`	In the inbound file, GS section, you have a security qualifier that does not belong in this section.	In the inbound file, remove the security qualifier.
`(2122) ERROR: unexpected sender qualifier <sender qualifier read>`	In the inbound file, a bad sender ID qualifier is listed that is not in the Standard.	In the inbound file, verify that the ISA sender qualifier is correct.
`(2123) ERROR: unexpected receiver qualifier <receiver qualifier read>`	In the inbound file, a bad receiver ID qualifier is listed that is not in the Standard.	In the inbound file, verify that the ISA receiver qualifier is correct.
`(2124) ERROR: unexpected end-of-segment while decoding <segment name> Segment`	An inbound run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It occurs if an end of segment delimiter is read while processing a GS or ST segment in the incoming transaction X12 file before all of the required EDI fields have been read.	Examine the error log and Incoming X12 transaction file to locate and correct the invalid GS or ST transaction file record.
`(2157) ERROR: first condition must be MEMVAR type`	Messages 2157 through 2159 are generated at run time map messages that are written to the error log along with other detailed information to identify the exact map records that caused the error message. They occur if the Record and Field names for the map condition fields in the User Field/Element maps are not correct. Outbound maps can have map condition fields at both the Segment and Sequence level. At the Segment level of an outbound map, the first condition must be either blank, a MEMVAR or a RECFLD. At the Sequence map record level, an outbound map must be blank or have a MEMVAR as the first map condition field. Inbound maps do not have map condition fields at the Segment level. At the Sequence map record level, an inbound map must have a blank, a MEMVAR or a RECFLD as the first map condition.	Regardless of the level or map direction, if a first map condition field is specified, the second map condition field must be MEMVAR, RECFLD, or STRVAR.
`(2164) ERROR: on <READ/WRITE>, empty (M)andatory field- <field name>`	A run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It indicates that a field that has been defined as a mandatory User File field has a blank or zero value. For inbound maps, this message is generated when a record is read and a mandatory User File data field is blank. For outbound maps, this message is generated when a record is written and a mandatory User File data field is blank.	If the User File field does not need to be mandatory, the error can be corrected by simply changing the User File field's mandatory attribute status. If the field is truly a mandatory field, then for inbound maps correct the User data file that contains the blank field. For outbound maps, examine the mapping rules to determine a possible cause of the blank mandatory field. For outbound maps, it is the user defined map rules working with the User Field/Element map to place a non-blank value into a User record field before it is written.
`(2168) ERROR: must map to RECFLD or MEMVAR`	A run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It is caused by an inbound User Field/Element Map not having a RECFLD or MEMVAR defined in the Record field of a sequence record. For inbound maps, the Record field indicated where to store an inbound X12 transaction value.	Use the User Field/Element mapping option to correct the Record field name and regenerate the map.
`(2169) ERROR: empty value mapped to EDI mandatory field <record name> from <field name>`	A run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. It indicates that a field that has been defined as an mandatory EDI standard field has a blank or zero value. For inbound maps, this message is generated when an X12 record is read and a mandatory EDI field is blank. For outbound maps, this message is generated when a record is written to the X12 file and a mandatory X12 EDI field is blank.	For an inbound map, the inbound X12 transaction file needs to be corrected. For an outbound map, examine the error log, the user data file, the map rules and the User Field/Element map to determine and correct the cause of the blank EDI field value. If the error was caused by a missing or incorrect map rule or User Field/Element map, regenerate the map and run the map again.
`(2170) ERROR: Mandatory <defined length> EDI Len < Min: Value <minimum specified standards length>`	A mandatory EDI field is defined as less than the minimum length in the EDI standards.	Contact Trading Partner to update transaction to meet EDI specification
`(2171) ERROR: Invalid <segment name> Segment <code> code`	A run time map message that is written to the error log along with other detailed information to identify the exact cause of the message. For inbound maps, this message is generated when required information within the EDI elements such as the X12 version, are empty. In some cases, this message is generated for information only, and in most cases, processing continues.	Bad EDI file. Inform sender, or fix data.
`(2172) ERROR: Mapping To Numeric EDI Field with Non-Numeric Data: <field value >`	Occurs when mapping an alphanumeric field to a numeric EDI field. Inbound data received is not numeric.	Change the alphanumeric data to numeric or change the mapping specifications to meet the current data type or report the message to file sender regarding bad data.
`(2173) ERROR: Incoming EDI Numeric Field Has Non-Numeric Data: < field value >`	The EDI file read is invalid for this particular element.	The data for this element is bad. Report message to file sender.
`(2174) ERROR: Numeric Field Contains Non-Numeric Data < field value >`	User field specified as numeric has non-numeric data.	Change the definition of the user file field or modify incoming data.
`(2175) ERROR: Level <level number> Cond Check of Seg <segment name>, Non-Numeric Data: < >`	Segment specified as numeric has non-numeric data.	Change the Segment definition to accommodate numeric values or modify incoming data.
`(2176) ERROR: Level <level number> Cond Flow Check of Seg <segment name>, Non-Numeric Data: < >`	Level specified as numeric has non-numeric data.	Change the definition or modify incoming data.
`(2177) ERROR: Map Cond Check Numeric Field has Non-Numeric Data: < field value >`	Condition specified as numeric has non-numeric data.	Change the definition or modify incoming data.
`(2180) ERROR: Invalid Interchange Control Version Number: %s`	Added for ISA error checking.
`(2181) ERROR: Invalid Interchange Control Standards Identifier: %s`	Added for ISA error checking.