SAP Integration: Connect Your Shop, Portal and Apps to SAP

The effort depends mainly on which SAP system you use, which services are already available and how many business transactions are mapped. Clearly scoped connections can usually be implemented in the Professional package from €8,000; extensive integrations of several systems fall under the Enterprise package with individual quoting. The exact quote follows after the free initial consultation and a brief system analysis.

First, we clarify the integration scenario and interface technology with your SAP team. Then we develop against your test system, test real business cases with the business departments and go live after your sign-off. The duration depends heavily on approvals and coordination on the SAP side, which is why we plan for them from the start.

Common ones are OData or REST services that SAP S/4HANA provides via SAP Gateway, classic BAPIs that are called via RFC, and IDocs for exchanging business documents. SAP Business One offers its own REST interface with the Service Layer. Which variant fits depends on your system, the data volume and the requirements of your SAP department.

For settings in the SAP system itself, usually yes – for example for authorizations, the activation of services or IDoc partner agreements. We take care of the integration logic and the connected applications and coordinate directly with your consulting partner. That way each side works in its own area of expertise.

Yes. Orders from the shop can be passed to SAP as sales orders, while prices, stock levels and delivery status flow back. For high traffic we recommend a cache so that the shop stays fast and SAP is not queried on every page view.

When switching from SAP ECC to S/4HANA, data structures and available services partly change. Middleware that decouples your applications from SAP makes this step easier: mainly the connection to SAP is then adapted, not every single application. That's why we factor planned migrations into the concept from the start.