Skip to content
  • There are no suggestions because the search field is empty.

Common EDI errors and how to fix them

This article is for suppliers and retailers that exchange EDI documents through Logicbroker. It covers the EDI errors that Support sees most often, what each one means and how to fix it. For failures that apply to every format, including API and portal documents, see Failed Document Summary.

In this article:

How to find the error

Logicbroker records each error as an event on the document that failed. Start there.

  1. Click Reporting › Failed Documents. Failed documents are grouped by failure reason. Click View Documents on a row. Then click View to open a document, or Details to read its error.
  2. On the document, click the text next to Most recent event to read the full error.
  3. Expand Events for the document's history. Check Attachments for its EDI files. A Functional Acknowledgement attachment is a 997 that Logicbroker received for the document.
  4. To see the EDI file with its envelope and group control numbers, click More Actions › View EDI.

To look across all your documents, click Reporting › Events and filter by Partner or Severity. If you manage your EDI settings, the EDI Transmission Failures table under Connections › EDI lists EDI files that Logicbroker couldn't send or process.

To get an email when a 997 rejects one of your documents, turn on EDI document rejected under My Profile › Notifications.

If the most recent event is "Error transmitting EDI", Logicbroker couldn't deliver the file to the receiving connection. See Failed Document Summary. If an order never reached your system and shows no error, see Missing orders.

A document failed with "EDI 850 rejected"

Who this applies to. Retailers whose orders go to suppliers by EDI, and suppliers who receive orders by EDI. The same error appears for other documents that Logicbroker sends by EDI, as "EDI 855 rejected", "EDI 856 rejected" or "EDI 810 rejected". For example, a supplier's shipment shows "EDI 856 rejected" when the retailer's system rejects it.

What it means. The receiving system sent back a 997 functional acknowledgement that rejected the file. Logicbroker then marks the document Failed. The event details say "Your EDI 850 document was rejected by the receiving party." They include a link to download the full rejection message.

These are the causes Support finds most often:

  • A value is longer than the receiving system accepts. Examples are the ship-to name, an address line (N3), the city, state and ZIP line (N4), the unit of measure or a note.
  • A value isn't valid in the receiving system. Examples are a unit of measure written as "100/Case" instead of a code such as "CS", a state code in lowercase, or a state of "0".
  • Data the receiving system requires is missing, such as the ship-to address.
  • The file's structure doesn't follow X12 or the retailer's specification. Examples on shipments are a missing HL01 in a loop, a TD5 segment with an empty element, or a reference (REF) segment that the retailer requires.
  • The EDI version doesn't match (see A qualifier is rejected as invalid, or the EDI version doesn't match).

What to check:

  1. Open the document and click EDI 850 rejected (or the matching error) next to Most recent event. Download the full rejection message from the link in the details.
  2. Find the segment and value that the receiving system rejected. Suppliers can ask their EDI provider, whose translator log usually names the field and the value.
  3. Compare that value with the document in Logicbroker and with the retailer's specification.

How to fix a rejected order (850). Choose the case that matches:

  • One value on the order is wrong or too long. Some accounts can change the fields on a failed order. If you can, correct the value and click Save Changes. Logicbroker resubmits the order. If the fields are locked, contact Support with the field and the value you need. Support can edit the order and send it again.
  • The retailer's order is missing data, such as the ship-to address. Logicbroker can only send the data that the retailer sent. Only the retailer can send a corrected or new order. Suppliers should contact the retailer.
  • The receiving system rejected the file for a reason on its own side, and the order is correct. An example is a setting at the supplier's EDI provider that rejects every order. The supplier fixes it first. Then click More Actions › Retry on the order, then Yes. Retry sends the same data again, so it fails again if the problem is in the order. To retry several orders at once, see Retry a failed order.
  • The supplier already corrected the file in its own system and loaded the order. A later 997 that accepts the file doesn't clear the Failed status in Logicbroker. Contact Support and say which status the order should have, for example Ready to Ship.

How to fix a rejected 855, 856 or 810 that you sent. The rejected values come from your file, so the fix is in your system or at your EDI provider. Correct the document there. Then move the failed document to Ignored. To do this, click More Actions › Ignore. If your account shows Change Status instead, click More Actions › Change Status and choose Ignored. Send the corrected document to Logicbroker the same way you sent the first one. For a shipment, use a new shipment number in BSN02, because Logicbroker doesn't process an exact copy of a shipment it already has (see My corrected shipment is treated as a duplicate).

How to check it worked. The document no longer shows Failed and moves on. A resent order moves to a status such as Ready to Acknowledge. A corrected shipment or invoice shows Complete. If the receiving system sends 997s, a new Functional Acknowledgement attachment appears and no new rejection event is added.

When to contact Support. Contact Support if you can't change the order's fields, if the same rejection returns after a correction, or if the order needs a status that your More Actions menu doesn't offer. See What to send Support.

Your system says a value is "too large - truncated"

Who this applies to. Suppliers who receive orders by EDI and whose translator or ERP limits the length of some fields.

What it means. The order contains a value that is longer than your system accepts. The message comes from your own translator or ERP, not from Logicbroker. It usually names the field and the value, as in "The value assigned to the Field ... is too large - truncated." Depending on your setup, your system either sends back a 997 that rejects the order, or accepts the file and holds the order in an error queue.

What to check:

  1. Note the field and the value from your system's error.
  2. Find the order in Logicbroker. If it shows Failed with "EDI 850 rejected", follow A document failed with "EDI 850 rejected". If it shows Ready to Acknowledge or a later status, Logicbroker has usually already sent it to you.
  3. Check the field's maximum length in your retailer's specification. Values that fit the specification can still be longer than your system allows.
  4. Check that the order isn't already in your system under the same PO number, including any error or exception queue. A resend could create a duplicate.

The fix. Contact Support with the PO number, the field name and the value from the error. Support can shorten the value and send the order to you again. The same error returns whenever an order has a value of that length, so tell your EDI provider which field failed.

How to check it worked. The order loads into your system without the error.

A qualifier is rejected as invalid, or the EDI version doesn't match

Who this applies to. Suppliers and retailers on EDI. Each connection uses an X12 version, such as 4010 or 4060. The version can differ by retailer and by document type.

What it means. The version in the file's envelope is not the version the receiving system expects. The receiving system may reject the whole file. It may also report a qualifier code as invalid or unknown, because a code that is valid in one version can be unknown in another.

What to check:

  1. Open the document and click More Actions › View EDI. The GS segment ends with the version, for example 004010 or 004060.
  2. Check which version your retailer's specification uses.
  3. If you manage your EDI settings, open Connections › EDI. Check whether My Custom Document Settings has a Version for that partner and document type.

The fix. Contact Support to confirm which version the connection should use. Support can correct the version and send the affected documents again. If you changed the Version setting yourself, for example for testing, set it back to the version in your retailer's specification.

How to check it worked. New documents show the expected version in the GS segment, and the receiving system accepts them.

An 855, 856 or 810 doesn't appear or doesn't link to the order

Who this applies to. Suppliers who send acknowledgements, shipments or invoices by EDI, and retailers who send documents to Logicbroker by EDI.

What it means. There are three different causes.

  • Logicbroker couldn't tell who sent the file. Logicbroker identifies the sender and the receiver from the ISA qualifier and ID, or the GS ID. Both must match identifiers set up in Logicbroker, and the two companies must be trading partners. If they don't match, Logicbroker can't process the file. It sends no 997 back, and the document doesn't appear in your portal. Support often finds the retailer's ID in the sender field instead of your own, or a receiver ID that isn't the retailer's.
  • Logicbroker matched the sender but couldn't read the file. Logicbroker records an "Error receiving EDI" event, which you can find under Reporting › Events. Its details start with "Failed to process inbound EDI" and give the file's control number. Correct the file and send it again.
  • Logicbroker received the document but couldn't find its order. Logicbroker links the document to an order by its PO number. The PO number is in BAK03 on an 855, PRF01 on an 856 and BIG04 on an 810. A shipment then fails with "Original Order Not Found". Other documents can fail with "Order not found" and the details "This document cannot be linked to an existing order."

Logicbroker creates its 997 as soon as it matches the sender and the receiver, before it checks the document. It waits up to 15 minutes before it sends the 997. An accepted 997 from Logicbroker means that Logicbroker received the file. The document can still fail afterwards, so check Reporting › Failed Documents.

What to check:

  1. Check whether you received a 997 from Logicbroker for the file. If none arrived within 15 minutes, plus the time your connection takes to deliver files to you, check the identifiers in steps 2 and 3.
  2. Open Connections › EDI. Compare the sender qualifier and ID in your file's ISA segment (ISA05 and ISA06) with your entry in My EDI Identifiers. If you can't see Connections › EDI, ask your account administrator.
  3. Compare the receiver qualifier and ID (ISA07 and ISA08) with the retailer's Qualifier:Identifier in Your Partner's EDI Connection Details.
  4. Check that you sent the file to the right environment. Stage and production have separate EDI connections.
  5. If the document appears but failed, compare its PO number character by character with the order. See Shipment failed with "Original Order Not Found".
  6. If you also have a Stage connection, search for the PO number in the Stage portal. An order that a retailer sent while testing in Stage doesn't exist in production.

The fix. Choose the case that matches:

  • The identifiers are wrong. Correct them in your system, or ask your EDI provider to. Then send the file again.
  • The PO number is wrong. Send a new document with the PO number exactly as it is on the order. Move the failed one to Ignored.
  • The order was a Stage test order. Production has no such order, so move the failed document to Ignored. Ask the retailer about its testing. If you no longer want orders from Stage, sign in to Stage and turn off Enabled on your EDI connection under Connections › EDI, if your connection shows it. Otherwise, ask Support to turn it off.

How to check it worked. You receive a 997 from Logicbroker. The document appears under Related Documents on the order, and it doesn't show Failed.

When to contact Support. Contact Support if the identifiers and the PO number match and the document still doesn't appear or link. Include the file's control number (ISA13), the date and time you sent it and the raw EDI file.

An 856 or 810 failed because it was sent out of order

Who this applies to. Suppliers on any connection. The rules depend on the retailer.

What it means. Some retailers require an acknowledgement before a shipment or invoice. Some retailers require items to ship before you invoice them. If a document arrives before Logicbroker has processed the one it depends on, it fails. An early invoice fails with "Cannot Invoice Unshipped Items", and the details list each short line, for example "Tried to invoice 1 but there are 0 shipped."

What to check:

  1. Open the failed document and scroll down to Related Documents.
  2. Check that the acknowledgement or shipment it depends on is listed and isn't Failed.
  3. If the shipment isn't listed although you sent it, Logicbroker may not have received it. See An 855, 856 or 810 doesn't appear or doesn't link to the order.
  4. Check that your 856 ships the full quantity you invoice. Logicbroker doesn't mark the order fully shipped until your shipments cover the ordered quantities.

The fix. Send or fix the missing document first and wait until it shows Complete. Then open the failed document and click More Actions › Retry. For the full steps, see Retrying after fixing the cause and Invoice failed before the shipment completed. To avoid the failure, send the 855, then the 856, then the 810, and let each one finish first (see Sending documents in the right order).

How to check it worked. The retried document no longer shows Failed and moves on, normally to Complete.

When to contact Support. Contact Support if the document still fails after the document it depends on is Complete.

How to read a retailer's EDI specification

Logicbroker's standard specifications describe the standard schema. The EDI segment for each field is listed next to it. See Acknowledgement Specification, Shipment Specifications and Invoice Specification. Some retailers have their own EDI specification. If yours does, follow the retailer's specification.

  • Where to find it. Under Connections › EDI, the Your Partner's EDI Connection Details table lists each retailer's Qualifier:Identifier. Click View in the Specifications column to open that retailer's specification. You can also check Partners › Document Standards.
  • "User Req" and "Req Des." columns. Some retailer specifications have both. "User Req" is what the retailer requires. "Req Des." is the X12 standard designation. Follow "User Req".
  • Optional segments. A retailer may send an optional segment on some orders and not on others, and new optional segments can be added. If your map limits how many times a segment can repeat, an extra optional segment can make an order fail in your system. You can ignore an optional segment that you don't use.
  • Where values go. The retailer's specification says where to put values such as the tracking number on the 856. Use it when your data doesn't appear where the retailer expects it.
  • Who answers which question. Questions about the retailer's own data go to the retailer. Examples are its location codes, which optional values it sends in production, and its test scenarios. Logicbroker Support can help with how Logicbroker maps a field and with errors on your documents.

What to send Support

When you contact Support about an EDI error, include:

  • your company name and the retailer's name
  • the PO number and the Logicbroker document ID
  • the exact error, from the event details or from your translator
  • the control number (ISA13) and the date and time the file was sent, if the problem is with a file
  • the raw EDI file in .EDI or .TXT format, if Support asks for it or Logicbroker doesn't show the document
  • what you already tried, and whether you want a document sent again or only checked

In the portal, go to Help › Submit a ticket, or email support@logicbroker.com.

Related articles

We're updating this article. Some steps and screenshots may not match the portal yet. If anything is unclear, contact support@logicbroker.com.