The integration problem nobody talks about honestly
Most EDIFACT implementation projects that run over time and budget do not fail because of EDIFACT. They fail because of SAP.
SAP is extraordinarily flexible, which means every company's SAP configuration is different. The purchase order structure in your SAP MM module reflects years of decisions made by your team — custom fields, partner functions, pricing conditions, plant assignments. When an EDIFACT ORDERS message arrives from a trading partner, it needs to map to that specific configuration. And the mapping is almost never simple.
The four integration points in SAP that cause the most problems
1. Partner function mapping
EDIFACT messages carry multiple party identifiers — the buyer, the seller, the ship-to party, the invoice-to party. SAP's partner function model has its own set of roles. Getting these to align correctly, especially when a single EDIFACT message involves parties that SAP treats as different accounts, is one of the most common sources of mapping errors.
2. Material number translation
Your trading partner sends their own article number in the EDIFACT ORDERS message. Your SAP system uses your internal material number. The mapping table between these two — what SAP calls the "info record" — needs to be maintained for every material, for every trading partner. When a trading partner adds a new product or changes their article numbering, the mapping breaks until it is updated.
3. Pricing conditions
EDIFACT ORDERS messages often include price information. SAP's pricing condition structure is highly configurable. Whether you want to accept the price from the EDIFACT message or derive it from your SAP condition records, you need a clear decision and a mapping rule that enforces it consistently. Ambiguity here leads to invoice discrepancies downstream.
4. Delivery schedule handling for DELFOR/DELJIT
For manufacturing companies receiving delivery forecasts and JIT call-offs, the EDIFACT DELFOR and DELJIT messages need to map to SAP's scheduling agreement structure. The tolerance windows, rounding rules, and horizon handling in SAP scheduling agreements need to match what your trading partner expects — and these often need to be negotiated as part of the onboarding process.
The mapping rule that survives supplier changes
The most common mapping failure mode is building a direct, brittle translation between the EDIFACT message structure and the SAP field structure. When either side changes — a new EDIFACT message version, a SAP configuration change, a new trading partner with slightly different conventions — the mapping breaks.
The pattern that works is a three-layer architecture:
- Parse layer — convert the raw EDIFACT message into a canonical internal format, validating against the message specification
- Enrich layer — look up and resolve all identifiers (partner numbers, material numbers, plant codes) using reference data maintained separately from the mapping logic
- Transform layer — convert the enriched canonical format into SAP IDoc or BAPI calls
Testing strategy that catches problems before go-live
The testing phase of an EDIFACT/SAP integration is where most of the time should go — and where most projects cut corners.
A proper test cycle covers:
- Positive path testing — standard messages that should process cleanly
- Edge case testing — messages with optional segments present or absent, messages at quantity and value boundaries
- Error path testing — deliberately malformed messages to verify that error handling works and bad data does not corrupt SAP
- Regression testing — after any SAP change or mapping update, re-run the full test suite
The honest assessment
SAP EDIFACT integration is not difficult if you have done it before. It is very difficult if you have not. The combination of SAP configuration knowledge, EDIFACT message expertise, and middleware experience is rare. When a project brings in a team that is strong in one area but weak in the others, the integration works in the test environment and breaks in production.
Ask any potential vendor to show you a reference of a live SAP EDIFACT integration they have running. Then call the reference.
Related reading
If you are new to EDIFACT, start with our plain-language guide to EDIFACT before diving into SAP-specific implementation.
For retail-specific EDI automation with SAP, see our article on DESADV and RECADV in Bulgarian retail.
Have questions about your SAP EDIFACT setup? Book a free discovery call with our integration team.