How Cleo Integration Cloud (SAP connector) connects to SAP S/4HANA
Prebuilt SAP connector with IDocs
Inbound 850 orders map to the ORDERS05 IDoc to create sales orders. Outbound 856 ASNs are generated from DESADV and 810 invoices from INVOIC. This works on ECC and on S/4HANA.
S/4HANA APIs
On S/4HANA, the connector can also use SAP APIs rather than IDocs for some scenarios. Which method fits depends on release, volume and your SAP team's preference.
What data moves
| From | To | Data | When |
|---|---|---|---|
| Trading partner | SAP (ORDERS05) | 850 purchase orders become sales orders | EDI file or message received |
| SAP (DESADV) | Trading partner | 856 advance ship notices | Outbound delivery goods issue |
| SAP (INVOIC) | Trading partner | 810 invoices | Billing document release |
| Cleo | Trading partner | 997 functional acknowledgments | Document received |
Setting it up
- 1Collect each partner's implementation guideRetail and automotive partners differ in segments, qualifiers and timing. The guide is the contract.
- 2Configure SAP partner profiles and portsCreate IDoc partner profiles, ports and message types for ORDERS05, DESADV and INVOIC, or enable the APIs.
- 3Set customer and material cross-referencesMap partner item numbers and ship-to codes to SAP customers, materials and partner functions.
- 4Build the maps in CleoStart from the order-to-cash accelerator and adjust to each partner's rules.
- 5Test with partner sandboxesExchange test documents, resolve rejections, and get partner sign-off.
- 6Monitor after go-liveWatch IDoc status (WE02), the Cleo dashboard and acknowledgments daily at first.
What usually breaks
- !Missing customer or material cross-reference leaving the IDoc in error with no sales order.
- !ASN sent before the delivery is final or packed, causing partner chargebacks.
- !Unit of measure mismatch between partner and SAP.
- !Duplicate 850s creating duplicate sales orders without a duplicate check on PO number.
- !IDoc processing stuck on locked objects or missing authorizations.
A private AI layer across both systems
EDI exception triage
A private assistant reads failed IDocs and Cleo errors, explains the cause such as an unmapped ship-to, and drafts the master data fix for approval.
Order-to-ASN reconciliation
Compare received 850s, sales orders, deliveries and sent 856s and 810s to find missing documents before partners complain.
Plain-language partner questions
Ask which orders from a partner are open or rejected this week, answered from SAP and EDI logs on your infrastructure.
Try it here, free
IDoc to EDI X12 Mapping Worksheet (INVOIC to 810)
An editable mapping sheet that pairs IDoc segments and fields with X12 segments and elements, with rules and open questions, exported as an Excel spec.
When something else fits better
- SAP Integration Suite or SAP's EDI options, if you already license them and have skills.
- Another EDI service or VAN with SAP adapters, if partner-managed mapping suits you better.
- Direct API or portal integration for a single partner with low volume.
Frequently asked questions
Which EDI documents does the Cleo SAP connector cover?
Cleo describes two-way integration for 850 orders, 856 ASNs and 810 invoices, using IDocs ORDERS05, DESADV and INVOIC, plus an order-to-cash accelerator. Other documents, such as 860 changes, may need extra mapping, so confirm scope.
Does it work with ECC and S/4HANA on-prem?
Cleo lists SAP S/4HANA, S/4HANA Cloud and ECC. The IDoc pattern is long established on ECC and S/4HANA on-premise. Check the connector requirements for your release and where the integration runtime will sit.
How can AI reduce EDI errors?
A private assistant on your servers can read IDoc errors, master data and partner rules to explain failures and draft fixes. A person approves any master data change, so the assistant never writes to SAP unattended.
Pairing documented at www.cleo.com/solutions/application-connectors/sap . Cleo Integration Cloud (SAP connector) is a product of Cleo; Netray is independent and not affiliated with either vendor.