> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/ce/extensibility-and-integrations/integrations/sap-integration.md).

# SAP Integration

Emporix is designed to integrate seamlessly with systems like SAP ERP or SAP S/4HANA. To integrate SAP with Emporix, an integration layer (such as a middleware solution or API management platform) can be utilized to handle data exchange efficiently. This layer can collect and transform data into a suitable format and make the necessary API calls to Emporix. Options for integration include using an IPaaS platform or an API management layer that supports OData, REST API, or other protocols, enabling flexible and scalable integration tailored to the specific requirements of SAP and Emporix.

The guides below describe two SAP integration examples: master data replication with IDocs and sales and quote processes with OData services.

Both examples implement the integration process with SAP Integration Suite, which supports the SAP IDoc interface and modern integration technologies. Using the SAP IDoc interface is in line with SAP Clean Core Extensibility (Level B). For S/4HANA, SAP recommends modern integration technologies such as APIs, events, or OData services. As a result, an IDoc-based master data integration can co-exist with an OData-based sales order and quote integration for S/4HANA, while IDoc-based integrations are often preferred for SAP ERP. The SAP Sales and Quotes Integration describes an example integration process based on OData services available with S/4HANA.

{% hint style="warning" %}
Ready-to-use SAP integration content and related artifacts are delivered as part of the Emporix SAP integration package. To request the package, contact the [Emporix Support Team](mailto:support@emporix.com).
{% endhint %}

<table data-card-size="large" data-view="cards"><thead><tr><th align="center"></th><th align="center"></th><th align="center"></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td align="center"><i class="fa-arrows-rotate">:arrows-rotate:</i></td><td align="center"><strong>Master Data Replication with IDocs</strong></td><td align="center">Learn how master data is replicated between Emporix and SAP ERP or SAP S/4HANA using IDocs and SAP Integration Suite.</td><td></td><td></td><td><a href="/pages/COET5gQHq8Gd3bE7Icjx">/pages/COET5gQHq8Gd3bE7Icjx</a></td></tr><tr><td align="center"><i class="fa-message-quote">:message-quote:</i></td><td align="center"><strong>SAP Sales and Quotes Integration</strong></td><td align="center">Integrate transactional sales and quote processes between Emporix Commerce Engine and SAP S/4HANA using SAP Integration Suite.</td><td></td><td></td><td><a href="/pages/EDBxbzOEhlro3h34eVI8">/pages/EDBxbzOEhlro3h34eVI8</a></td></tr></tbody></table>

{% hint style="info" %}
To learn more about SAP Clean Core extensibility levels, see SAP's [ABAP Extensibility Guide — Clean Core for SAP S/4HANA Cloud (August 2025)](https://community.sap.com/t5/technology-blog-posts-by-sap/abap-extensibility-guide-clean-core-for-sap-s-4hana-cloud-august-2025/ba-p/14175399).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.emporix.io/ce/extensibility-and-integrations/integrations/sap-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.