SAP Integration

We first agree which data moves in which direction and how often, and review your SAP release and the services available. SAP Business One is usually integrated through the Service Layer or the DI API, and S/4HANA and ECC through OData services, BAPI/RFC or IDocs. In S/4HANA and ECC, sales organisation, pricing conditions and document types also shape the design, so we work through them with your SAP team.

Yes. We don't sell SAP licences or take over SAP implementation and support; that stays with your team or partner. We build the systems that connect to SAP and the integration between them, and agree the interfaces with your SAP team.

Usually not; SAP's standard services and BAPIs are often enough. If a field or rule has no standard equivalent and a custom OData service or function module is needed, we define it with your SAP team or partner and leave the development inside SAP to them.

We connect your channels to SAP through an integration layer rather than directly. When you move from ECC to S/4HANA, only the SAP side of that layer is adapted to the new system's services and data model, so changes to your online store, B2B portal and field apps are kept to a minimum.

That depends on your SAP contract. Documents created in SAP by external systems can fall under SAP's indirect or digital access licensing rules, so we recommend clarifying this with your SAP account manager or partner at the start of the project.

It depends on your SAP release, the number of channels to connect and the interfaces involved. After a discovery call we share a clear timeline and a transparent quote, as a fixed project price or a monthly retainer; you can also outline your needs in our project planner.