EEDIBlogs

EDI Mapping

How to translate data between internal formats (ERP, IDoc, JSON, CSV) and EDI structures, including field-level mapping patterns.

Featured articles

Intermediate11 min read

EDI Mapping Explained: From ERP Fields to X12 and EDIFACT Segments

A practical guide to how EDI mapping actually works — the concepts, common source formats, and a worked example translating SAP IDoc fields into an X12 850.

MappingSAP IDocX12
Marcus Webb2026-07-30

Advanced guides

Related transactions

850x12

Purchase Order

The X12 850 is the electronic purchase order a buyer sends to a supplier to request goods or services, replacing paper or PDF POs with a structured, machine-readable document.

856x12

Advance Ship Notice

The X12 856 (ASN) tells the buyer exactly what was shipped, how it was packed (pallet/case/item hierarchy), and when it will arrive — before the truck reaches the dock.

Related tools

Integration Platform (iPaaS)

Boomi Integration

Boomi

A cloud-native integration platform (iPaaS) with visual process-building tools, offering EDI connectivity alongside broader application and data integration.

X12EDIFACTJSON
Integration Platform (iPaaS)

MuleSoft Anypoint Platform

Salesforce (MuleSoft)

A general-purpose integration and API management platform that supports EDI connectivity through dedicated connectors and transformation modules (DataWeave).

X12EDIFACT (via EDI connectors/accelerators)JSON