Q13E-Commerce and ERP
Question
4 marks
Describe the architecture of Electronic Data Interchange (EDI).
Answer
A rigorous technical exposition of the Electronic Data Interchange (EDI) architecture. Explains the strict translation software, communication networks (VANs), and rigid formatting standards required for autonomous B2B data exchange.
EDI is completely invisible to consumers but absolutely runs the global B2B supply chain. It is the strict computer-to-computer exchange of business documents (Purchase Orders, Invoices, ASNs) in a standard, mathematical electronic format.
The EDI Architectural Pipeline
The process of translating a human-readable invoice into an EDI packet involves strict architectural layers:
- 1. Internal Database Extraction: The buying corporation's ERP system generates a raw, proprietary Purchase Order (PO) in its internal database.
- 2. The EDI Translator (Mapping Software): The absolute core of the architecture. The Translator software violently strips away the proprietary formatting and mathematically forces the data into a rigid, globally recognized syntax (like ANSI X12 or UN/EDIFACT). It ensures the "Date" field is exactly 8 characters and the "Price" field is formatted perfectly.
- 3. The Communications Layer: The translated EDI file cannot just be emailed. It is violently blasted across the network using highly secure, trackable protocols like AS2 (Applicability Statement 2) over HTTPS, or through a dedicated Value-Added Network (VAN).
- 4. The Value-Added Network (VAN): A highly secure, private, third-party network acting as a digital post office. It mathematically guarantees delivery, provides undeniable audit trails, and routes the EDI packet to the exact supplier's mailbox.
- 5. Reverse Translation: The supplier's EDI Translator receives the X12 file, violently unpacks it, and injects the PO directly into the supplier's ERP database, instantly triggering the manufacturing process without a single human ever typing a key.