EDI, end to end. From the IDoc to the trading partner.
EDI touches the order in SAP, the map in the middle and the partner on the other end. When each part belongs to a different vendor, problems get passed around while orders sit blocked and chargebacks pile up. We cover all of it, so problems get fixed.
Most providers cover one or two. We cover all five.
| Layer | What's in it |
|---|---|
| Inside SAP | IDocs (orders, acknowledgements, ship notices, invoices, remittances), partner profiles, output setup in ECC and S/4HANA, customer and material mapping, blocked-document handling |
| Translation | X12 and EDIFACT maps to and from IDocs, on SAP Integration Suite (Integration Advisor), the PI/PO B2B add-on, or your EDI provider |
| Partner management | Trading partner agreements, identifiers, acknowledgements (997, CONTRL) and B2B monitoring in Trading Partner Management |
| Connectivity | AS2, SFTP, VANs, OFTP2, Peppol access points, and certificates that don't expire unnoticed |
| The trading partner | Onboarding and testing with each customer or supplier, retailer rules on ship notices and labels, and chargeback reduction |
Three things are forcing EDI changes.
PI/PO B2B is running out of road
PI/PO mainstream maintenance ends on 31 December 2027. EDI on the B2B add-on has to move, and every partner agreement must be set up again in Integration Suite.
PI/PO migration →S/4HANA changes the SAP side
Output management, business partner and IDoc changes mean EDI must be redesigned, and every trading partner retested before cutover.
ECC → S/4HANA →European e-invoicing deadlines
Belgium since January 2026, France from September 2026, Germany's sending requirement from January 2027. If you have EU entities, your invoices must change.
SAP deadlines →The right channel for every trading partner.
Big partners justify full EDI. Many smaller ones never will. We segment your partners and pick the channel that fits each one, then connect SAP once.
EDI or API
X12, EDIFACT or a partner's API, on Integration Suite or the EDI provider you keep.
Direct IDoc exchange
When both sides run SAP, IDocs go straight across over AS2 or SFTP, with no X12 or EDIFACT translation.
Supplier network
SAP Business Network: suppliers confirm orders, send ship notices and invoice in a browser, and SAP is connected once.
Full-service EDI provider
A provider owns the maps and every retailer's rule changes. We connect SAP to it cleanly.
Web forms
Small partners key documents into a web form that produces compliant EDI.
Peppol e-invoicing
Standard e-invoices from SAP through an access point, for entities under EU mandates.
Email and PDF, read by AI
Partners keep emailing PDFs. SAP extracts the data, pre-fills the order or invoice, and a person checks it.
Seven services.
| Service | What it is |
|---|---|
| EDI landscape assessment (fixed price) | Partner inventory, transaction sets, maps, platform, VAN costs, error rates, chargeback causes and the right channel for each partner, with a costed plan |
| PI/PO B2B → Integration Suite | EDI moved off the PI/PO B2B add-on to Trading Partner Management, partner by partner, with regression testing |
| EDI platform consolidation | Move from a third-party translator or VAN to Integration Suite, or connect SAP cleanly to the provider you keep |
| Trading partner onboarding | New customers and suppliers set up, mapped, tested and live, as a repeatable service |
| S/4HANA EDI readiness | Output management, IDoc and partner retesting built into the migration plan |
| E-invoicing compliance | Peppol and national formats for EU entities, using SAP Document and Reporting Compliance where it fits |
| EDI managed operations | Monitoring, failed-IDoc handling, partner changes and certificate renewals, monthly |
Where EDI hurts most.
Retail suppliers
Purchase order, acknowledgement, ship notice and invoice (850, 855, 856, 810), ship-notice timing and labels, and fewer chargebacks.
Retail →Manufacturing and automotive
Forecasts and delivery schedules (830, 862, DELFOR, DELJIT), VDA and Odette standards, OFTP2.
Manufacturing →Distribution and 3PL
Warehouse orders and confirmations (940, 945) and carrier status updates.
Supply Chain →The BOND Method, for EDI.
Blueprint
Partner inventory, channel decision per partner, target design and a costed plan.
Orchestrate
A pilot partner end to end to prove maps, connectivity, acknowledgements and monitoring.
Navigate
Partners moved in waves with regression testing, coordinated with each partner's test window.
Deliver
Cutover, old platform switched off, runbooks or managed operations.
Know every partner, map and failure point.
A fixed-price EDI landscape assessment shows what you run today, what it costs and the right channel for each trading partner.