On formats

The messages in this section are the result of either User File database fields defined incorrectly, or the data in an actual user file field not corresponding to the User File database definition.

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

Table 1-9: ECMap messages related to formats

Format

Cause

Solution

(2408) ERROR: length must be 4 or 8 for CD field type

An interactive data entry error that occurs during User File definition if a field's length is less than 4 and the field is specified to be a computational field (i.e. CD).

Either change the field type or change the field length to 4.

(2411) ERROR: Status MemVar Field Size too small for Err Code

Indicates that a Keyed I/O Map Rule has been defined to use a MEMVAR variable as an error code field and the MEMVAR length is less than 2. The MEMVAR length must be at least 2 in order for the MEMVAR to be large enough to hold the error code.

Use the User File definition option to redefine the MEMVAR field length. Or use the Map Rule definition option to select a different MEMVAR. If this message occurred during a map run, the map must be regenerated after the MEMVAR length has been corrected.

(2422) WARNING: field truncated

A map run or map generation message that is written to the error log along with other detailed information to identify the exact cause of the message. It could be the result of a map addition rule that results in a value too large to be stored in the designated field. This message can also occur for inbound maps when the data field mapped to the User File field exceeds the defined User File field length and the User Field/Element map for the field does not explicitly specify that field truncation is allowed. For an outbound map this message displays when the data field mapped to an EDI transaction field exceeds the maximum size defined EDI field length.

Use the User Files options to change the lengths or specify that truncation is allowed.

(2424) WARNING: <numeric type> overflow, <full number> truncated to <number>

A map run message that is written to the error log along with other detailed information to identify the exact cause of the message. It occurs when mapping a numeric field type results in truncation, and the field mapped to has not been specified as a field that can be truncated. Both the full number and the resulting truncated number are written as part of the message.

Use the User Files options to change the lengths or specify that truncation is allowed.

(2444) ERROR: Delimiter for < start position > Not Found in < field value >

Occurs when creating substring and/or concatenation rules. Rule is executed based on the presence of a specified delimiter, which cannot be found.

For substring errors: Delimiter for start position is not found in Source Field

Delimiter for Substring length is not found in Source Old

For Concatenate errors: Concatenate Delimiter for Destination is not found in LHS Variable

Check data for presence of delimiter.