# XEDI EDI Integration with Infor LN (ION BODs) > Source: https://netray.co/stack/xedi-infor-edi-bod-infor-ln > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Stack ## Short answer XEDI is an EDI translation and mapping service that converts trading partner messages (X12, EDIFACT, TRADACOMS) into Infor BODs and routes them through Infor ION. The same approach is described for CloudSuite Industrial (SyteLine) and M3, so one EDI provider can serve several Infor ERPs. ## Erp Infor LN ## Erp Key infor-ln ## On Prem true ## Product XEDI Infor EDI integration ## Vendor XEDI ## Category EDI ## Integration **Method:** BOD exchange through Infor ION **Detail:** Inbound partner documents are translated to BODs such as sales order or shipment related documents and delivered into ION, which routes them to the ERP. Outbound BODs from the ERP are translated back to partner formats. Exactly which BODs are mapped for your transactions must be confirmed in the project scope. **Method:** Partner connectivity: AS2, SFTP, API, mailbox **Detail:** On the trading partner side, the service supports common transports such as AS2, SFTP, API and mailbox. Your IT team still has to open the right firewall rules and manage certificates and keys. ## Data Flows **From:** Trading partner **To:** Infor LN **Data:** Purchase orders (850 style) translated to a sales order BOD **Trigger:** Partner sends the document **From:** Infor LN **To:** Trading partner **Data:** Order acknowledgments (855 style) **Trigger:** Sales order confirmed in LN **From:** Infor LN **To:** Trading partner **Data:** Advance ship notices (856 style) and shipment data **Trigger:** Shipment confirmed in LN **From:** Infor LN **To:** Trading partner **Data:** Invoices (810 style) **Trigger:** Invoice posted in LN **From:** Trading partner **To:** Infor LN **Data:** Forecasts and releases (830/862 style) for scheduling **Trigger:** Partner schedule update ## Setup ### Collect trading partner requirements **Detail:** Get each partner's implementation guide: document types, versions, qualifiers, label and ASN rules, and test requirements. ### Confirm ION is in place **Detail:** Make sure ION connectivity to LN is configured with the document flows and an ION API or messaging connection point the EDI provider can reach. ### Map partner fields to LN **Detail:** Map partner item numbers, ship-to locations, units and payment terms to LN business partners, items and addresses. Cross reference tables are usually the bulk of the work. ### Set up transport **Detail:** Exchange AS2 certificates or SFTP keys with each partner and test connectivity before sending documents. ### Run partner test cycles **Detail:** Send test orders end to end: PO in, acknowledgment out, ASN, invoice. Partners usually have their own certification step. ### Monitor BOD errors **Detail:** Assign an owner for failed BODs in ION and for translation errors on the EDI side, with a daily check. ### Go live per partner **Detail:** Cut over partners one at a time and keep manual processing as a fallback during the first weeks. ## Pitfalls - Partner item numbers and ship-to codes that are missing from the cross reference cause BODs to fail on the ERP side. - Unit of measure and pack size differences between partner documents and LN items produce wrong quantities. - ASN rules such as SSCC labels and hierarchical structure are stricter than the ERP shipment data supports without customization. - Duplicate documents when a partner resends and nothing checks the purchase order number and revision. - Expired AS2 certificates or changed SFTP keys silently stop traffic until a partner calls. - BODs delivered but rejected in LN sit in an ION error queue that nobody watches. ## Ai Layer ### Failed document triage **Description:** An assistant that reads EDI error logs, ION BOD errors and LN master data can explain in plain language why an order failed, for example an unmapped ship-to, and draft the cross reference fix for approval. ### Order reconciliation **Description:** Compare what partners sent against what became sales orders in LN, and list missing or changed lines each morning. ### Chargeback and late ASN analysis **Description:** Ask which partners had late or incorrect ASNs this month and trace each back to the shipment event that caused it. ## Alternatives - A traditional VAN plus a mapping tool you run yourself, if you already have EDI skills in house and few partners. - Another Infor-aware EDI provider or the Infor Marketplace options, if your partners require a specific network. - Web portals provided by large customers can cover one or two low-volume partners without a full EDI project. ## Faq ### Does XEDI work with Infor LN or only with Infor cloud products? **Answer:** The vendor describes translation to Infor BODs routed through ION for CloudSuite Industrial, M3 and LN. Because ION is part of the architecture, the approach is not tied to cloud hosting, but confirm your LN version and ION setup with the provider. ### What is a BOD? **Answer:** A Business Object Document is the XML message format Infor uses in ION to exchange business data between applications. EDI translation here means converting partner formats such as X12 or EDIFACT into BODs that LN understands, and the reverse for outbound documents. ### Which transports are supported with partners? **Answer:** The vendor lists AS2, SFTP, API and mailbox. Which one you use is dictated by each trading partner, so collect their connectivity requirements early and plan certificate and key exchange as part of the test cycle. ## Source https://xedi.com/integrations/infor-edi ## Search terms infor ln edi ion bod integration, infor ln edi, xedi infor, infor ion bod edi translation, syteline edi ion, infor m3 edi integration --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json