The messages in this section focus on interactive User Field/Element mapping errors and interactive Map Flow errors. Many of these errors are caused by differences between EDI field definitions and User File field definitions.
The format, cause, and solution (if applicable) for the ECMap messages related to mapping are listed below, in numeric order by message number.
Table 1-10 lists the format, cause, and solution (if applicable) for the ECMap messages related to mapping, in numeric order by message number.
Message |
Cause |
Solution |
|---|---|---|
|
An abort transaction was executed either by the user or because of bad map information. User data was backed out. |
If it does occur because of bad data, fix data and rerun the map. If abort transaction was erroneous placed in map flow, remove the command, and regenerate map. |
|
A conditional store was defined for an element or sub-element with conditions applied. |
From the mapping window, modify the element and remove the conditional aspect for the conditional store or change the element from a conditional store element. |
|
||
|
