OData vs SOAP for S/4HANA integration
For S/4HANA integration, use OData APIs for synchronous, resource-oriented reads and updates, such as querying business partners or creating a sales order and getting an immediate result.
For S/4HANA integration, use OData APIs for synchronous, resource-oriented reads and updates, such as querying business partners or creating a sales order and getting an immediate result. Use SOAP APIs where SAP offers document-style or asynchronous services, often for high-volume business document exchange. In practice, choose the released API SAP provides for your process.
How do OData and SOAP compare for S/4HANA?
Quick answer: OData is RESTful and resource-oriented, ideal for synchronous access; SOAP is message- and document-oriented, and in S/4HANA many SOAP services are designed for asynchronous exchange.
| Criterion | OData | SOAP |
|---|---|---|
| Style | RESTful, resource-oriented (entities and operations) | Message-oriented, document-style |
| Typical interaction | Synchronous request and response | Synchronous or asynchronous; many S/4HANA services are asynchronous |
| Query capabilities | Filtering, selection, expansion, paging | Defined by the service operation |
| Batching | Batch requests with change sets | Per message |
| Payload | JSON or XML | XML defined by WSDL |
| Typical use | UIs, extensions, lookups, interactive create and update | Business document exchange between systems |
| Integration Suite adapter | OData adapter | SOAP adapter |
When should I choose OData?
Quick answer: choose OData when a caller needs data or a result now, and the interaction maps naturally to entities.
- Side-by-side extensions and apps reading and updating S/4HANA data.
- Lookups such as checking a business partner or product before processing.
- Creating or updating a document where the caller needs the result immediately.
Watch out for chatty designs: many small calls are slower and harder to monitor than a well-designed batch or a single coarse-grained request.
When should I choose SOAP?
Quick answer: choose SOAP when SAP provides a released SOAP service for the business document you are exchanging, especially asynchronous ones.
- System-to-system exchange of business documents, such as journal entries or supplier invoices, where SAP offers SOAP services.
- High-volume flows where asynchronous processing protects both sides.
- Partners and middleware already standardised on WSDL-based contracts.
Does the choice change error handling?
Quick answer: the principles are the same, but the failure signals differ.
For synchronous OData calls, the HTTP status and error body tell you immediately whether to retry or stop. For asynchronous SOAP, acceptance of the message is not the same as successful posting, so you also need to monitor processing inside S/4HANA and any confirmation messages. Either way, apply the same classification, retry and idempotency standards described in the error handling guide.
What is the practical rule?
Start from the business process, find the released interface on SAP Business Accelerator Hub, and use the style SAP provides for it. Where both exist, prefer OData for interactive, synchronous needs and SOAP or events for decoupled document flows. See the S/4HANA Public Cloud integration guide.
Key takeaways
- OData suits synchronous, RESTful reads and updates with filtering and batching.
- SOAP suits document-style and asynchronous business document exchange.
- Always start from the released API on SAP Business Accelerator Hub.
Questions
Does S/4HANA support both OData and SOAP?
Yes. SAP Business Accelerator Hub lists released OData (V2 and V4) and SOAP APIs for S/4HANA, along with business events.
Is OData always better than SOAP?
No. OData is convenient for synchronous, resource-oriented access, but many business processes are served by asynchronous SOAP services that are better suited to reliable document exchange.
Can Integration Suite call both?
Yes. Cloud Integration has OData and SOAP adapters, so the same flow standards for error handling and monitoring apply to either style.
Related reading
See what Spanovix would fix in your landscape
Bring your hardest interfaces. In a short working session we show where the agents cut failures, manual work and risk for your teams.