Connect SAP to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between SAP and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with SAP EDI
XEDI connects SAP environments with EDI trading partners, helping enterprise teams manage partner-specific EDI requirements while integrating document flows with SAP order, fulfilment and finance processes.
One managed platform, no custom code
XEDI maps SAP to your trading partners and validates every document, so data flows straight into the systems your teams already use.
EDI and SAP speak different dialects of the same idea
SAP already thinks in structured documents. The work in an SAP EDI integration is not persuading it to accept one, it is translating between the partner's EDIFACT, TRADACOMS or X12 message and the IDoc type SAP expects: ORDERS05 for an inbound order, DELVRY for a despatch advice, INVOIC02 for an invoice.
That translation is rarely one-to-one. A retailer's order carries fields SAP has no home for, and SAP requires fields the retailer never sends. Deciding where each of those is sourced or defaulted is the substance of the project.
Partner profiles are where it usually stalls
Every trading partner needs a partner profile in SAP with the right message types, ports and process codes. Get one wrong and the IDoc is created but never leaves, or arrives and sits in status 51 with an error nobody is watching.
Sold-to and ship-to determination is the other recurring issue. Retailers identify delivery points by GLN, SAP by customer and partner function, and the two have to reconcile for every depot a partner operates.
What your team sees day to day
You get an EDI mailbox and a portal that works like an inbox, so orders can be received and acted on independently of what the SAP interfaces are doing.
Documents build on each other: the order becomes the despatch advice, amended where the delivery differs, with SSCC labels for the pallets, then the invoice on delivery. SAP receives the same documents as IDocs. Delivery of that invoice is confirmed in the dashboard, independently of IDoc status.
The integration sits over that workflow and automates it, so documents post as IDocs and outbound flows are raised from SAP rather than confirmed by hand. The portal is for teams without an SAP dependency; our API is for enterprises wanting finer granularity than documents. For an SAP estate the integration is usually the right middle ground.
Documents you can exchange
- Purchase orders
- Order acknowledgements
- Despatch advice and ASN messages
- Invoices
- Inventory and product data where required
Built for SAP teams
Whoever owns SAP in your business, XEDI keeps EDI accurate and hands-off.
- Enterprise suppliers
- SAP administrators
- EDI teams
- Supply chain operations
- Finance teams
SAP EDI document types
The message set differs by partner and by SAP release, but these are the flows most SAP supplier programmes are built from.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Inbound retailer demand, translated to an ORDERS IDoc and creating a sales order against the right sold-to and ship-to. | Partner to SAP |
| Order acknowledgements | Confirmation of accepted, amended and rejected lines back to the partner. | SAP to partner |
| Advanced shipping notices | Despatch advice raised from the SAP delivery, including handling unit and pallet structure where required. | SAP to partner |
| Invoices | Billing documents translated out of SAP and referenced to the order and delivery. | SAP to partner |
| Credit notes | Credits and adjustments carried on the invoice message with the appropriate document code. | SAP to partner |
| Delivery forecasts | Scheduled demand from partners that plan ahead rather than ordering line by line. | Partner to SAP |
How to connect SAP with EDI using XEDI
SAP connections are usually staged partner by partner rather than switched on at once, so a mapping problem affects one relationship instead of all of them.
-
01
We scope the SAP modules, interfaces and trading partners in play.
-
02
We build the mapping between each partner's message and the IDoc types SAP expects.
-
03
We configure partner profiles, ports and process codes alongside validation that runs before an IDoc is created.
-
04
We prove each document flow against what the partner requires, checking IDoc status at every step until it is clean.
-
05
You get flows we monitor ourselves, so a stalled document is our problem before it is yours.
Ready to connect SAP?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about SAP EDI
Common requirements
- SAP interface method and access details
- Customer, material, plant and tax references
- Trading partner identifiers
- ASN, packaging and delivery rules
- Invoice and finance validation requirements
What we need from you to build it
Only the things we cannot hold for you. Each partner's requirements are already ours; the IDoc configuration and mapping are ours to build.
- IDoc types and partner profiles
- The message types in scope per partner, with ports and process codes configured, and someone who can change them when a partner adds a document.
- Customer and partner functions
- Each trading partner mapped to a sold-to, and each delivery point mapped to a ship-to with the GLN the partner uses.
- Material master and units
- GTINs at each packaging level, the partner's ordering unit, and the conversion to the base unit held in SAP.
- Output determination
- Conditions that decide when a despatch advice or invoice is generated, so documents are not sent early or missed entirely.
- Pricing and tax
- Condition types and tax codes that reconcile with what the partner expects, since price variance is a common rejection reason.
Why suppliers choose XEDI for SAP
- Your retailers are almost certainly connected already, which is why an SAP programme does not have to wait on partner onboarding.
- Partner rules are validated before an IDoc is generated, so errors surface in the document rather than in the SAP error queue.
- A new trading partner is not an ABAP change and a release cycle. We configure and test it, and it arrives working.
- Every message is traceable end to end, which matters when a retailer disputes an invoice months later.
- The same connection carries EDIFACT, TRADACOMS and X12, so a partner in another region does not mean another project.
- Partners raise problems with us, not with your team. We are notified on your behalf and resolve them before they reach anyone internally.
Can XEDI integrate EDI with SAP?
Yes. XEDI can map partner EDI documents to SAP workflows and manage the partner-specific validation and connection requirements.
Plan your SAP EDI setup
Everything you need to scope, map and go live with SAP, in one place.