EDI 850 Import Fails: Ship-to Code Cannot Be Found in the Related Table (Ship-to Address)
The field Ship-to Code of table Sales Header contains a value (xxxx) that cannot be found in the related table (Ship-to Address).What It Means
A trading partner sends a purchase order (EDI 850) for a store or distribution center. Business Central cannot create the sales order, because the ship-to location code on the order does not exist for that customer. The PO stays in error in Transaction Manager. This is common when a retailer opens a new store or DC.
Root Cause
Sales Header "Ship-to Code" must match a Ship-to Address record on the customer card. The trading partner sends its own location code. If no Ship-to Address has that code, and no translation maps it to one that exists, Business Central rejects the value with a table-relation error.
Step-by-Step Fix
- Note the value in brackets in the error. This is the ship-to code that the trading partner sent.
- In Business Central, open the customer card for the trading partner and choose Ship-to Addresses. Check whether that location exists.
- If the location does not exist, create a Ship-to Address with the address from the 850 (TrueCommerce's 'Configuring Ship To Codes' article covers the setup).
- If the location exists under a different code, leave Business Central as it is. In Transaction Manager go to Trading Partners, select the partner, open Translations → Address List, and add a record: EDI Code = the partner's ship-to code (including the trading partner number), Bus Sys Code = the Business Central Ship-to Code.
- Reprocess the 850.
Verification Steps
Sources & References
Early Access · 30-Day Sandbox Pilot
Stop Order Sync Failures Before Customers Notice
The Order Flow Doctor monitors Microsoft Dynamics 365 Business Central order flows across Shopify, EDI (TrueCommerce, SPS), 3PLs, and carriers. Get automated root-cause diagnosis and one-click fixes.