Connecting SAP to the applications around your ERP

An SAP integration lets your own application read data from SAP and write it back, so you don't have to rework SAP for a process that doesn't fit in it. Aziri has built five integrations with SAP, for example at Warsco, where units drawn in ArchiCAD automatically end up as quote lines in SAP.

What flows where

A typical integration. What exactly is exchanged is agreed together during the analysis.

  1. Drawing package (ArchiCAD)SAP

    Drawn objects become quote lines, after the application has checked the design

  2. SAPYour application

    Items with their unique number, so the app knows which code belongs to which object

  3. SAPYour application

    Customers and prices, as the basis for a calculation or quote

  4. Your applicationSAP

    Quotes or orders created in the app

How we approach an SAP integration

Items, customers and quotes stay in SAP, and the calculation or the drawing belongs in the application alongside it. That is the first thing we agree. At Warsco the objects in the ArchiCAD libraries already had a unique number in SAP, and that is exactly why a design could turn straight into a quote.

Then we set out which data flows in which direction and who is allowed to change it. That goes into the scope you approve, and we test with real items and quotes from your SAP before the integration goes live.

How do you connect SAP Business One, S/4HANA or ECC?

Each in its own way: Business One through the Service Layer, S/4HANA through OData APIs and ECC through function modules or IDocs. SAP is not one package, and how an application talks to it depends on the version you use. We look at that during the analysis together with your IT department or SAP partner.

SAP version Typical way to connect
SAP Business One The Service Layer, a REST API on the Business One server, or the older DI API.
SAP S/4HANA Published OData APIs, which SAP documents in the SAP Business Accelerator Hub.
SAP ECC Function modules (RFC/BAPI) or IDocs, often through a middleware layer your SAP partner manages.

Whichever route: we agree which user the integration runs under and which rights it gets, so the application only sees and changes what it needs.

Why an application alongside SAP?

Having a process built inside SAP itself is often a heavy project for something only one department uses. A separate application that talks to SAP is quicker to build and easier to change, while SAP stays the source. At Warsco a second application was added later, a transport calculation that used to live in Excel. You can read more about this kind of application under quote calculation and manufacturing.

Quotes from ArchiCAD straight into SAP

Warsco designs its units in ArchiCAD and then had to enter everything as quote lines in SAP by hand. A custom application now does that automatically.

Read the case
4 days
of training for the in-house team
2
applications in production

Frequently asked questions

Question not listed? Ask us directly.

Do we have to change SAP to connect to it?

Usually not. The application we build talks to SAP through the integration options of your SAP environment, and SAP remains the place where items, customers and quotes belong. Which access we need is something we discuss with your IT department or SAP partner.

Does SAP have an API?

Yes, but which one depends on your version. SAP Business One has the Service Layer, S/4HANA published OData APIs, and with ECC it goes through function modules or IDocs. During the analysis we look, together with your IT department or SAP partner, at which route is open.

Do you also do SAP implementations or migrations?

No. For that you need an SAP partner. We build the applications around SAP and the integration between them, for the process that is too specific for an SAP module and too important to keep doing by hand.

What does an SAP integration cost?

An SAP integration starts from €2,000. What it costs depends mostly on your SAP version and what your SAP partner opens up. If we build it together with the application that talks to SAP, it sits within that project’s fixed price; a first version for one process starts from €5,000. We prefer to give you one fixed price upfront, as soon as the scope is clear.

What if something changes in SAP?

Report it to our support team, and we find out where it goes wrong and talk to your SAP partner if needed. If the integration needs reworking because something changed on the SAP side, that falls outside regular support and we agree it with you beforehand.

Can a quote come straight from a drawing into SAP?

Yes, if the objects in your drawing package have a number that also exists in SAP. At Warsco the application turns the units from ArchiCAD into quote lines in SAP, so nobody has to create them by hand any more.

Tell us where things get stuck

Tell us briefly how your process works today. We’ll let you know whether custom software makes sense, roughly what a first version costs and how quickly it can be running.

We reply quickly.