Architecture of EDI
The architecture for EDI (Electronic Data Interchange) is designed to enable the secure, standardized, and automated exchange of business documents between organizations. Here's a breakdown of a typical EDI architecture, including all key components:
π§ 1. Internal Systems (ERP / Business Applications)
- Examples: SAP
- Purpose: These systems generate and consume business documents (like Purchase Orders, Invoices, ASN, etc.).
- Documents are exported/imported in flat files, IDocs, XML, etc.
π 2. EDI Interface / Middleware Layer
This layer maps internal data formats to standardized EDI formats.
Components:
-
Mapping Tool: Translates ERP data formats (e.g., IDoc) to EDI standards (e.g., ANSI X12).
-
Transformation Engine: Converts business data to EDI format and vice versa.
-
Validation Engine: Ensures data integrity and compliance with EDI standards.
Examples: SAP PI/PO, Boomi, MuleSoft, IBM Sterling Integrator, Microsoft BizTalk
π 3. EDI Translator
- Converts documents between human-readable (ERP) and EDI formats.
- Examples of EDI formats: ANSI X12
π‘ 4. Communication AS2
This is how the EDI documents are securely exchanged between trading partners.
Options:
-
VAN (Value Added Network): Third-party network that manages EDI routing, translation, and storage (e.g., OpenText, GXS)
-
AS2: Secure point-to-point EDI communication over the Internet
-
SFTP/FTP/HTTPS/REST APIs: Other common transfer protocols
-
OFTP / OFTP2: Used often in automotive or European sectors
π₯ 5. Trading Partners
- Your customers, suppliers, or logistics partners
- Each partner may have specific EDI requirements (document types, mapping rules, communication protocol)
π 6. EDI Process Flow (Example)
Letβs take an Order-to-Invoice flow:
-
ERP creates a Purchase Order β internal IDoc
-
Middleware maps IDoc to EDI 850 (PO)
-
EDI Translator converts PO to correct format
-
Communication Layer sends 850 to the supplier via AS2 or VAN
- Supplier processes the order and sends back:
- 855 (Order Acknowledgment)
- 856 (ASN)
- 810 (Invoice)
- Your system receives these via EDI β translated β imported into ERP
