In brief
There is no single way to integrate with SAP. An old R/3 system can do different things from ECC 6.0, and S/4HANA differs from both. If you design an integration without knowing what the system supports, you build either something that does not work, or something outdated when a better standard was available. The solution: let the SAP system tell you itself what it can do first.
What determines the choice
- The version. Every SAP release adds capabilities. Function modules via RFC work almost everywhere. OData services require SAP Gateway, which is included as standard in newer versions. Modern ABAP, CDS views and the RAP model with OData V4 require more recent versions.
- The type of system. A purely technical SAP system has no business tables. An ERP system (ECC) does, and S/4HANA adds new ones, while some old ones work differently.
- What already exists. Which standard BAPIs, services and released APIs exist for this business object? If something already exists, you do not build anything new.
- The purpose. An app that displays and edits data needs something different from a nightly exchange of large volumes.
Reading out the system
An SAP system knows a lot about itself: which release and components are running, which tables and fields exist, and which business objects it knows with which BAPIs. Reading out that information gives you an objective picture of the possibilities, instead of assumptions.
No quick fixes
Under time pressure, people often reach for whatever works fast, such as a generic function for reading arbitrary tables. SAP itself states that such a function is not intended for external use. Integrations like that run into technical limits and break during upgrades. Better to use one specific object per data question.
Choosing from standards
With that picture, you choose from a limited set of SAP's standard integration types: the most modern one the system supports that fits the purpose. The result is integrations that SAP itself recommends, that survive upgrades and that fit the clean core principle.
How we do it
We are building an integration builder that starts with exactly this. It works with SAP systems from ECC to S/4HANA and reads out what the connected system is and can do: release, installed components and which technologies are present. For each integration type it shows whether it is available (can the system do it?) and whether it is permitted (does the organisation want it?). The choice then follows a decision model based on the release. What gets built is checked by the SAP system itself.
What to watch out for
- Record the choice and the reason. During an upgrade you then know which integrations can move to a more modern type.
- Look at the licence implications of integrations that create documents.
- Route the integration through an intermediate layer, so apps do not need to know anything about the SAP version behind it.
Would you like advice on SAP integration? Request a free advice conversation.
Updated on