The following EDI Error Glossary provides information regarding EDI system errors that display on the following screens:
Please reference the screen name when communicating errors to Eclipse EDI Support.
For each program that produces error messages, the glossary shows:
The message as it appears on the terminal screen.
A definition of the message.
The recommended course of action.
The following errors display on the EDI Error Queue Maintenance screen.
CANNOT OPEN EDI.OUT.STATUS -E9PERR
The EDI.OUT.STATUS file does not exist, or permissions are incorrect. Contact Eclipse EDI Support for assistance.
5 - MAP SUBR -ECIERR:
Mapping subroutine defined in EDI Group Profile Maintenance for this trading partner and document does not exist or has not been compiled. Verify that the mapping subroutine that has been defined is correct. If it is not, correct it and requeue this document. If the routine is correct, contact Eclipse EDI Support so the mapper can be made available to you.
5 - NO MAPPING FOUND -ECIERR: XXX
A mapping subroutine is not defined on the EDI Group Profile Maintenance screen for this trading partner and document type. You must set up and define a mapper for this document on the EDI Group Profile Maintenance screen for this trading partner. Then requeue this document.
5 - Partner Sub-ID Not Found -ECIERR : XXXX-XXX
The bill-to or ship-to (N1-BT/N1-ST) data specified in the error message was not found in the EDI Group Profile Receive Code Info Table accessed from the EDI Group Profile Maintenance screen. You need to enter the bill-to or ship-to (N1-BT/N1-ST) data specified in the error message into the Receive Code Info Table screen for this trading partner. Use the Add Sub-ID hot key to enter the correct customer data and then requeue this document.
Doc Type Undefined -ECIERR: XXX
Received document is an invalid or undefined type. Verify that the document type being sent to you is correct and that it is defined for this trading partner. After verification, if the problem still exists, contact Eclipse EDI Support for assistance.
EDI Customer/Vendor : XXXX not on file -ECIERR
No customer or vendor account was found for the specified trading partner. The customer or vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document.
EDI Bill-To -ECLERR: XXXX not found
The account specified on the EDI Trading Partner Profile Maintenance screen cannot be found. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document.
EDI Customer : XXXX not on file -ECLERR
The account specified on the EDI Trading Partner Profile Maintenance screen cannot be found. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document.
EDI Customer Xref not found -ECLERR
No customer Xref account was found for the specified trading partner. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document.
EDI Pay-To : XXXX not found -ECLERR
The account specified on the EDI Trading Partner Profile Maintenance screen cannot be found. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then “requeue” this document.
EDI Vendor : XXXX not on file -ECLERR
No vendor account was found for the specified trading partner. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document.
Invalid Ship-From Br - ECLERR
The account specified on the EDI Trading Partner Profile Maintenance screen is not flagged as a ship-from account. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document.
No EDI items found -ECLERR
No valid line items were found on the received EDI order. The most likely cause for this error is that the individual line items on the incoming EDI document have a zero quantity or no part number. Determine if the problem is related to the quantity or part number and then contact your trading partner to have the problem corrected and the document resent.
Non Bill-To specified -ECLERR: XXXX
The account specified on the EDI Trading Partner Profile Maintenance screen is not flagged as a bill-to account. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document.
Non Pay-To specified -ECLERR
The account specified on the EDI Trading Partner Profile Maintenance screen is not flagged as a pay-to account. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document.
Non Ship-To specified -ECLERR: XXXX
The account specified on the EDI Trading Partner Profile Maintenance screen is not flagged as a ship-to account. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected. Then requeue this document.
*** Bad Qty : XX - Set to 1 -ECLERR ***
The received quantity specified in the quantity field of the line item is not a number. Contact your trading partner and have them correct the data that they are sending.
1 Entity ID not found. -OCLERR
The entity specified on the EDI Trading Partner Profile Maintenance screen was not found. Contact Eclipse EDI Support for assistance.
2 No Items found. -OCLERR (Zero Qty)
No items were found for which to create a ledger record. This is a possible mapper problem. Contact Eclipse EDI Support for assistance. After fixing the problem, you can requeue the document from the Inbound Document Archive.
3 Ledger Record not found. -OCLERR
The ledger record specified by the EDI document does not exist. Contact Eclipse EDI Support for assistance.
4 Ledger GEN not found. -OCLERR
The generation specified by the EDI document does not exist. Contact Eclipse EDI Support for assistance.
5 Ledger Record locked. -OCLERR
The requested ledger record is locked by another process and is not available. Contact Eclipse EDI Support for assistance.
6 Purchase Order # Wrong Format. -OCLERR
The purchase order number specified by the EDI document is not in the correct format to be received by Eclipse. The purchase order number that your trading partner is sending you, which should be in Eclipse format, is not in the correct format. Contact your trading partner and have them correct the data they are sending.
7 Purchase Order # Already Exists. -OCLERR
The purchase order number that the EDI document tried to create already exists on Eclipse. This could be caused by your trading partner trying to reuse a previously used purchase order number or resending a previously sent order. Contact your trading partner to have problem corrected.
1 - DOCUMENT TYPE XXX NOT FOUND -ECUERR
The document type specified by this document was not found on the EDI Trading Partner Profile Maintenance screen for this trading partner. Before you can process this type of document for this trading partner, you must define it on the EDI Group Profile Maintenance screen for this trading partner.
1 - FUNCTIONAL GROUP XX NOT FOUND -ECUERR
The functional group type received in the GS segment was not found in the EDI tables. Verify that your trading partner is sending a valid functional group type.
1 - NO TRADING PARTNER PROFILE FOUND -ECUERR: XXXX
No trading partner profile could be found for the given interchange ID. Set up a trading partner profile for the given interchange ID.
1 - NON-NUMERIC CONTROL NO -ECUERR: XXXX
The given control number cannot be updated because it is not in numeric format. Contact your trading partner and tell them that you can only accept numeric control numbers.
0 - BAD ISA -EUNERR
There was something other than ISA found where the interchange control header was expected to start. This typically indicates that your network is performing blocking and padding between ISA envelopes with spaces. Call your network and verify whether or not they have blocking turned on for your mailbox. If they do, have them turn it off. Harbinger does not do blocking. This error also indicates data corruption during transmission if all segments are not present. After determining and fixing the problem, have your trading partner resend the document.
2 - BAD GE SEGMENT -EUNERR
There was something other than GE found where the group footer was expected to start. This typically indicates the receipt of corrupted data from the network. The document must be resent by the trading partner or reprocessed by the VAN.
2 - BAD GS SEGMENT -EUNERR
There was something other than “GS” found where the group header was expected to start. This typically indicates the receipt of corrupted data from the network. The document must be resent by the trading partner or reprocessed by the VAN.
2 - BAD TS COUNT IN GE SEGMENT -EUNERR XXXX/
The number of transactions indicated in the “GE” segment does not match the number of transactions actually counted. This typically indicates the receipt of corrupted data from the network. The document must be resent by the trading partner or reprocessed by the VAN.
2 - GROUP CONTROL# MISMATCH GS/GE -EUNERR:
The control number in the group header does not match the control number that was last received from your trading partner. This may indicate that you have missed a transmission from your trading partner. It often indicates that your trading partner does not send control numbers sequentially. Verify with your trading partner whether or not they send sequentially numbered control numbers, and proceed from there.
3 - NO SE FOUND -EUNERR
There was no transaction footer found. This typically indicates the receipt of corrupted data from the network. The document must be resent by the trading partner or reprocessed by the VAN.
3 - NO ST FOUND -EUNERR
There was no transaction header found. This typically indicates the receipt of corrupted data from the network. The document must be resent by the trading partner or reprocessed by the VAN.
3 - SEG COUNT MISMATCH IN SE -EUNERR:
The number of segments indicated in the “SE” segment does not match the number of segments actually counted. This typically indicates the receipt of corrupted data from the network. The document must be resent by the trading partner or reprocessed by the VAN.
3 - TS CONTROL# MISMATCH ST/SE -EUNERR: XXXX/XXXX
The control number in the transaction header does not match the control number that is in the transaction footer. This typically indicates the receipt of corrupted data from the network. The document must be resent by the trading partner or reprocessed by the VAN.
4 - Duplicate Recv Doc -EUNERR: XXX
Duplicate control numbers have been received from a particular trading partner for a specific document type. Contact your trading partner and tell them which control numbers have been received in duplicate. Then ask them to verify whether or not it is a duplicate. If the document that was sent was not a duplicate, they must resend it with control numbers that have not yet been used.
IEA FG COUNT # GROUP COUNT -EUNERR: XXXX-XXXX
The number of functional groups indicated in the “IEA” segment does not match the number of functional groups actually counted. This typically indicates the receipt of corrupted data from the network. The document must be resent by the trading partner or reprocessed by the VAN.
Interchange Control# ISA/ISE mismatch -EUNERR: XXXX/XXX
The control number in the interchange control header does not match the control number that is in the interchange control footer. This typically indicates the receipt of corrupted data from the network. The document must be resent by the trading partner or reprocessed by the VAN.
No IEA Segment found !!! -EUNERR
There was no interchange control footer found. This typically indicates the receipt of corrupted data from the network. The document must be resent by the trading partner or reprocessed by the VAN.
Unexpected File Name
The system did not recognize the file as an EDI file for processing.
The following errors display on the EDI Activity Log Viewing screen.
Mapping Subroutine not Cataloged -ECDERR
The mapping subroutine specified on the EDI Group Profile Maintenance screen does not exist or has not been compiled. Recheck the mapping subroutine you are using on the EDI Group Profile Maintenance screen. Make sure each zero and letter O is in the right place.
No Mapping Defined -ECDERR
No mapping subroutine entered for the specified EDI document on the EDI Group Profile Maintenance screen. Enter the appropriate mapping subroutine on the EDI Group Profile Maintenance screen for the trading partner.
No Trading Partner Profile Defined -ECDERR
A trading partner profile has not been set up on the EDI Trading Partner Profile Maintenance screen. Set up a trading partner profile for this trading partner.
Trade Partner : XXXX not on file -ECDERR
The trading partner does not exist on Eclipse. The customer/vendor who is defined on the EDI Trading Partner Profile Maintenance screen for this trading partner must be corrected.
Error in 852 Transmission -EP8ERR: XXX
An error occurred while creating the 852 document. Contact Eclipse EDI Support for assistance.
The following errors display on the Status screen of Sales Order Entry or Purchase Order Entry after changing the status to E and pressing Esc.
Ledger Record not found -ECOERR: XXXXXXX
The ledger record specified by EDI does not exist on Eclipse. Contact Eclipse EDI Support for assistance.
Mapping Subroutine not Cataloged -ECOERR
The mapping subroutine specified on the EDI Group Profile Maintenance screen for this trading partner does not exist or has not been compiled. Recheck the mapping subroutine you have entered on the EDI Group Profile Maintenance screen. Make sure each zero and letter O is in the right place.
No Mapping Defined -ECOERR
No mapping subroutine has been defined on the EDI Group Profile Maintenance screen for the specified trading partner. Enter the appropriate mapping subroutine on the EDI Group Profile Maintenance screen for the trading partner.
No Trading Partner Profile Defined -ECOERR
No trading partner profile has been found in Trading Partner Profile Maintenance for the account specified on this order. Set up a trading partner profile for this trading partner.
Transmission Aborted!!! -ECOERR
The system returns this message if No is the response to the following prompt: This document has already been Transmitted - Continue (Y/N). No action is necessary.
No Document specified -EDSERR
No document type has been specified for the attempted transaction. Enter the appropriate document type on the EDI Group Profile Maintenance screen for the trading partner.
No Mapping Defined -EDSERR
No mapping subroutine has been defined on the EDI Group Profile Maintenance screen for the specified trading partner. Enter the appropriate mapping subroutine on the EDI Group Profile Maintenance screen for the trading partner.
No Trading Partner Profile Defined -EDSERR
No trading partner profile has been found in Trading Partner Profile Maintenance for the account specified on this order. Set up a trading partner profile for this trading partner.
CANNOT OPEN EDI.STND.DE -EPDERR
The EDI.STND.DE file does not exist, or permissions are incorrect. This file contains ANSI data element information. Contact Eclipse EDI Support for assistance.
CANNOT OPEN EDI.STND.SEG -EPDERR
The EDI.STND.SEG file does not exist, or permissions are incorrect. This file contains ANSI segment information. Contact Eclipse EDI Support for assistance.
CANNOT OPEN EDI.STND.TS -EPDERR
The EDI.STND.TS file does not exist, or permissions are incorrect. This file contains ANSI transaction set information. Contact Eclipse EDI Support for assistance.
Branch EDI Group ID is not Defined -ESDERR
The “GS” interchange ID is not defined in the EDI OUTGOING ID record in Control File Maintenance for the specified branch. Set up the interchange ID for the specified branch in Control File Maintenance under EDI OUTGOING ID.
Branch EDI ISA ID is not Defined -ESDERR
ISA interchange ID is not defined in Control File Maintenance under EDI OUTGOING ID for the specified branch. Set up the interchange ID for the specified branch in Control File Maintenance under EDI OUTGOING ID.
Trading Partner not found -ESDERR: XXXX
No trading partner profile was found in Trading Partner Profile Maintenance for the account specified on this order. Set up a trading partner profile for this trading partner.
The following errors display on the EDI Trading Partner Profile Maintenance screen.
Ascii decimal value must be 255 or less
The three digit decimal value entered in the Separator/Sub-Separator field cannot be greater than 255. Re-enter the separator or sub-separator in the correct format.
Entity already assigned to EDI group
An entity can only be assigned to one EDI group. Enter a different entity or find the current trading partner profile that is linked to that entity and delete it.
Multiples Entities Are Only Allowed For Vendors
Customers cannot have multiple entities set up for a single group. Do not enter multiple entities for Customers.
Single character or 3 digit decimal value for ascii character
The value placed in the Separator/Sub-Separator field must be either the character used as the separator or its three-digit decimal-value ascii equivalent. Re-enter the separator or sub-separator in the correct format.
There Are Still Active Groups. Delete Them First
You cannot delete a trading partner profile until all groups belonging to that profile have been deleted. Go to the EDI Group Profile Maintenance screen and delete all groups. Then go back to the EDI Trading Partner Profile Maintenance screen and delete the profile.
Wrong Format. Use Qualifier Tilde ID. ex 01~12345
The trading partner ID number must be entered in this format. Enter the trading partner ID number in the correct format.
You Must Delete Through Group Maintenance. Press <Enter>
A group cannot be deleted from the EDI Trading Partner Profile Maintenance screen. Go to the EDI Group Profile Maintenance screen to delete the group.
Group is not in file.
When using the Copy Profile command, the group profile you are attempting to copy must exist. Verify that the group ID you are entering exists in a trading partner profile.
ISA ID is not in file.
When using the Copy Profile command, the ISA ID you are attempting to copy must exist. Verify that the ISA ID you are entering exists in a trading partner profile.
You cannot copy a group from itself
When using the Copy Profile command, you must enter the group whose profile you are copying, not the group receiving the profile. Verify the source group and target group.
Duplicate <Press Enter>
The entity being entered has already been entered. Enter a different entity.
Entity already assigned to EDI group
An entity can only be assigned to one EDI group. Enter a different entity.
See Also: