972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

Guides

JD Edwards EDI integration guide: interface tables, Orchestrator and best practices

How EDI connects to JD Edwards EnterpriseOne through its EDI interface tables and newer Orchestrator services, and how to run it reliably.

2 min read · Updated October 19, 2026

The short answer

JD Edwards EnterpriseOne handles EDI through interface tables. A translator loads inbound documents into EDI staging tables, and batch programs such as the inbound EDI sales order edit/create program validate them and create transactions. Outbound programs extract ship notices and invoices into staging tables for translation. Orchestrator adds REST-based options for real-time integration.

How EDI flows through JD EdwardsSequence diagram for JD Edwards. The trading partner sends a 850 purchase order to the integration layer, which translates and validates it and load EDI order header and detail tables (F47011, F47012) through interface tables and the inbound edit/create program R47011. In JD Edwards, r47011 validates and creates sales orders; failed records stay in the tables for correction. Outbound programs extract ship notices and invoices into EDI interface tables, and the integration layer sends the 856 ship notice and 810 invoice to the partner.How EDI flows through JD EdwardsThe integration layer translates; JD Edwards keeps the business recordsTrading partnerIntegration layerJD Edwards850 purchase orderTranslate and validateCross-references turn partner codes into your items and locationsLoad EDI order header and detail tables(F47011, F47012)Through interface tables and the inboundedit/create program R47011R47011 validates and creates sales orders; failed records stay in thetables for correctionProcessing options control defaults per partner or versionOutbound programs extract ship noticesand invoices into EDI interface tables856 ship notice and 810 invoiceInterfaces and objects as described in this guide. Your version, licensing and partner requirements decide which ones apply.
How EDI flows through JD EdwardsSequence diagram for JD Edwards. The trading partner sends a 850 purchase order to the integration layer, which translates and validates it and load EDI order header and detail tables (F47011, F47012) through interface tables and the inbound edit/create program R47011. In JD Edwards, r47011 validates and creates sales orders; failed records stay in the tables for correction. Outbound programs extract ship notices and invoices into EDI interface tables, and the integration layer sends the 856 ship notice and 810 invoice to the partner.How EDI flows through JDEdwardsThe integration layer translates; JD Edwardskeeps the business recordsTradingpartnerIntegrationlayerJD Edwards850 purchase orderTranslate and validateCross-references turnpartner codes into youritems and locationsLoad EDI order headerand detail tables (F47011,F47012)Through interface tables andthe inbound edit/createprogram R47011R47011 validates andcreates sales orders;failed records stay inthe tables forcorrectionProcessing options controldefaults per partner orversionOutbound programsextract ship notices andinvoices into EDIinterface tables856 ship notice and 810invoiceInterfaces and objects as described in this guide.Your version, licensing and partner requirementsdecide which ones apply.

Read the diagram from top to bottom. JD Edwards does not exchange X12 itself in this design: the integration layer handles the partner connection and translation, and JD Edwards creates and posts the business records. Outbound documents are built from what JD Edwards actually recorded.

Expand diagram Download SVG

How EDI connects to JD Edwards

JD Edwards EnterpriseOne includes an EDI system built around interface tables. An EDI translator converts partner documents into flat records loaded into these tables; JD Edwards batch programs then validate and process them. Outbound, JD Edwards programs extract data into interface tables, which the translator converts into EDI documents.

Inbound flow: customer orders

  1. The translator converts an 850 purchase order into records for the EDI order header and detail tables (F47011 and F47012).
  2. The inbound EDI sales order edit/create program (R47011) validates the data and creates sales orders.
  3. Records that fail validation remain in the interface tables with errors for review and correction.

Outbound flow

Outbound documents such as order acknowledgments, ship notices and invoices are extracted by JD Edwards outbound programs into their EDI interface tables after the related business event, such as shipment confirmation or invoice printing, and then translated and sent.

Cross-references and partner data

  • Item cross-references map customer item numbers to JD Edwards items.
  • Customer and address book records store ship-to locations and partner identifiers.
  • Processing options on EDI programs control defaults and behavior per partner or version.

Missing cross-references are a leading cause of inbound order errors, so maintain them as part of partner onboarding.

Orchestrator and business services

Newer integrations can use JD Edwards Orchestrator, which exposes business processes as REST services, or business services for SOAP integration. These suit real-time scenarios, such as API orders from marketplaces, while interface tables remain efficient for traditional EDI batches.

Scheduling and monitoring

  • Schedule inbound and outbound batch programs often enough to meet partner timing requirements.
  • Review interface table errors daily and assign owners for business errors such as unknown items.
  • Monitor end to end, from receipt and acknowledgment through order creation, shipment and invoicing, not only batch job completion.

Best practices

  • Keep partner-specific mapping in the integration layer and use standard JD Edwards programs.
  • Use separate program versions and processing options for partners with different rules.
  • Purge processed interface records regularly to keep tables manageable.
  • Document custom extensions to EDI tables or programs.
  • Plan EDI early in upgrades and migrations. See the ERP migration checklist.
JD Edwards EnterpriseOne integration and implementationIntegration methods, document mappings and ECOM services for JD Edwards EnterpriseOne.

Frequently asked questions

What are JD Edwards EDI interface tables?

They are staging tables, sometimes called Z files, where inbound EDI data is loaded before processing and where outbound data is written for an EDI translator to pick up.

Which program processes inbound EDI sales orders in JD Edwards?

Inbound sales orders are loaded into the EDI order header and detail tables (F47011 and F47012) and processed by the inbound EDI sales order edit/create program, R47011.

Can JD Edwards integrate EDI in real time?

Yes, using Orchestrator, which exposes JD Edwards business logic as REST services. Interface tables remain common for batch EDI volumes.

Keep learning

Related

ERP

JD Edwards EnterpriseOne integration

EDI integration for JD Edwards EnterpriseOne through EDI interface tables, Orchestrator and business services.

 services

ERP Implementation

ERP implementation for SAP, Oracle, Microsoft, NetSuite, Infor, Epicor, QAD and Sage, with B2B integration built in.

 Guide

How to reduce EDI exceptions: a practical guide for EDI and operations teams

Where EDI exceptions come from, how to prevent the most common ones, and how to resolve the rest faster.

 Transaction guide

EDI 850 Purchase Order

The X12 document a buyer uses to order goods or services from a supplier. It starts most B2B order-to-cash cycles.

 ERP

Oracle E-Business Suite integration

EDI integration for Oracle E-Business Suite through e-Commerce Gateway, open interfaces and XML Gateway.

Have an EDI question we did not answer?

ECOM's integration specialists can review your partners, documents and systems and recommend next steps.

Request a Demo Contact us