Understanding the EDI Workflow

An EDI (Electronic Data Interchange) workflow is the automated process that enables businesses to exchange documents (like Purchase Orders, Invoices, ASNs, etc.) electronically, without manual intervention.

It defines how an EDI document:

1. Is generated

2. Is sent to a trading partner

3. Is received

4. Is processed by the receiving system (ERP or other)

---

Typical EDI Workflow (Step-by-Step)

1. Data Creation

• A user enters an order in their ERP system (like SAP, Oracle, etc.)

• This triggers the generation of an EDI document (e.g., 850 = Purchase Order)

2. Outbound EDI Mapping

• Internal ERP data is mapped to the EDI format (X12, EDIFACT, etc.)

• This mapping is handled by the EDI translator or middleware (like Cleo, IBM Sterling, BizTalk)

3. Transmission

• The EDI document is sent to the trading partner using a communication method like:

  • AS2

  • FTP/SFTP

  • VAN (Value-Added Network)

  • OFTP2

  • API (modern hybrid EDI)

4. Inbound Processing

• The trading partner receives the EDI document

• It’s translated into their internal format and processed into their ERP system

5. Acknowledgment (optional)

• An EDI 997 or CONTRL file is sent back to acknowledge receipt of the document

---

Tools That Manage EDI Workflows:

• Cleo Integration Cloud (CIC)

• IBM Sterling B2B Integrator

• OpenText

• MuleSoft

• Boomi

• SAP PI/PO (for SAP customers)