On data and data manipulation

Many of these messages are map generation and map run time messages that occur because of invalid data, invalid Map Rules or incorrect Map Flow designs. Some of the error messages are the result of incomplete table look up databases. Some of the messages in this section are described as internal program errors. Internal program error messages are not expected to be displayed. If an internal error message occurs or if the suggested corrective action does not solve a problem, note the message number and any associated DBCIII error number and call support for assistance.

Table 1-7 lists the format, cause, and solution (if applicable) for the ECMap messages related to data and data manipulation, in numeric order by message number.

**Table 1-7: ECMap messages related to data and data manipulation**
Message	Cause	Solution
`(2000) ERROR: attempted to divide by zero`	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 indicates that a Map Rule division failed because the denominator field had a zero value.	Check both data in User Files and values assigned to variables in the Map Rules.
`(2001) ERROR: numeric overflow`	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 indicates that the numeric value was too large to be stored in the User File field, or too large to be stored in the standard X12 EDI transaction file field.	Compare User File numeric field sizes against the maximum size for the standard X12 Field.
`(2002) ERROR: ILLEGAL USE OF DATE FIELDS IN ARITHMETIC RULE`	Arithmetic operation requested on a date field cannot be performed. For example, adding a date field to a date field, or multiplying or dividing dates.	Use the “Define Rules” option to correct the rule. Allowable Date options are: Date = Date + number Date = Date - number Number = Date-Date
`(2028) ERROR: Level:<level number>- Loop count of exceeds maximum of <max loop occur>`	A compliance error caused this message. The loop specified occurs more than the maximum number allowed.	Solution:
`(2029) ERROR: Level<level number>, segment: <segment name> - occurred <number> times, exceeding maximum of <maximum segment occurrence>`	A compliance map error caused this message. The segment specified occurred more than the maximum number of occurrences for that particular instance.	Solution:
`(2030) ERROR: Segment <segment name> in loop <loop name> was Out-Of-Sequence.`	A compliance map error caused this message. A segment in a particular loop came in the incorrect order or sequence.	Solution:
`(2031) ERROR: Mandatory segment <segment name> in loop <loop name> was skipped.`	A compliance map error. A mandatory segment is missing.	Look in the Standards Guide and compare it to your map to see what mandatory segment was left out.
`(2032) ERROR: EDI Segment <segment name> not found in Transaction`	One of the segments listed in the transaction should be in this transaction.	Remove the segment that is not required according to the Standards Guide.
`(2033) ERROR: EDI Segment <segment name> level <level number> not found in database- <database name>`	Cause 1: An inbound run map message that is written to the error log. It occurs when the incoming X12 transaction file has a segment name that is not defined by the inbound Map at the indicated level. The run time result is that these incoming segments are ignored.	Solution 1: If that is desired, then no corrective action is necessary.
	Cause 2: The incoming X12 file has an invalid segment name. Also check the inbound Map Flow definition and the segment names that are defined for the Map. Perhaps some of the map segment names were incorrectly set to the IGNORE status, or some segment names need to be included in the map at additional levels.	Solution 2: Correct as indicated above and regenerate the map.
`(2034) ERROR: end-of-file reached, while searching for control Segment`	An inbound run map message that is written to the error log. This message occurs when the program reads the last record of the incoming X12 transaction file and the X12 transaction file does not have a correct ending control segment sequence, such as GE, IEA.	Examine the X12 incoming data file to check for valid control segments.
`(2044) ERROR: Record Type Read <record type> Does Not Match Any In File`	Occurs with a file with multiple record types. The message indicates that a record type is encountered in the data that does not match the file specifications.	Create a record for this record type and add it to your specifications.
`(2045) ERROR: Invalid Date Field: <date read> format <specified date format>`	An inbound run map message that indicates the date that was just read does not match the format specified.	Adjust format specification of change modify incoming data to meet specified format.
`(2046) ERROR: Date Value <date read> is greater than field size <specified field size>`	An inbound run map message that indicates the date that was just read exceeds the field size specified.	Define date field size and regenerate the map.
`(2047) WARNING: No Rule To Process Record Type <record type read>, Reading Forward`	An inbound run map message that indicates that the rules for reading files for multiple record types does not define the record type just read.	Add record type to the list of records. Ensure that an I/O rule has been created that causes a read of the specified record type.
`(2048) ERROR: Invalid Time Field: <record name> <field name>`	Time value passed is not valid	Correct value.
`(2049) ERROR: Invalid Field Value in SQL Where: <record name> <field name> <value>`	Value is not valid for the Field name in the Where Clause.	Correct the rule or the data populating the value in the Where Clause.
`(2050) ERROR: <record name> <field name> TimeStamp Missing Time`	The time parameter in the TimeStamp has no data.
`(2051) ERROR: Select '?' and # Parameter Mismatch`	Number of parameters and number of parameters passed do not match. This is usually because the SQL statement has been modified, but has not been recompiled.	Modify the SQL rule and recompile and store.
`(2052) ERROR: Invalid Test Indicator: <test indicator value read>`	An invalid test indicator was in the inbound data.	Look at the Test Indicator in the input data. The test indicator should be a P, T, or I in the ISA 15 section.
`(2053) ERROR: No Test Indicator`	An invalid test indicator was in the inbound data.	Look at the Test Indicator in the input data. The test indicator should be a P, T, or I in the ISA 15 section
`(2054) ERROR: Memory variable can not be defined as a time stamp`
`(2061) ERROR: Cannot switch between NCPDP Batch Versions`	Cannot switch between NCPDP Batch Versions
`(2062) ERROR: Cannot Switch between Real Time and Batch`	Cannot Switch between Real Time and Batch
`(2063) ERROR: NCPDP MAP Has No Transmission Segments Marked`	NCPDP MAP Has No Transmission Segments Marked
`(2064) ERROR: NCPDP MAP CANNOT USE DBC3 TP Files`	NCPDP must use ODBC trading partner.
`(2065) ERROR: Cannot Process NCPPD Data with Non-NCPDP Map`	Cannot Process NCPPD Data with Non-NCPDP Map