The problem
In many SAP landscapes nobody knows exactly which integration functions are in place, which version is active, and whether someone once made a "quick" manual change. When there is an outage or an upgrade, the first step is a search.
The register
The solution is a central register: one place where every object put into SAP is described, with its interface and content. Every change produces a new version. Our system supports version control with Git. You can go back to an earlier version.
Comparing design and reality
A register is only valuable if it matches what is actually in SAP. That is why we compare the register with the system after every rollout, and regularly after that:
- identical: what is there is what was intended;
- older version: a known earlier version is running;
- different: something was changed outside the register;
- missing: the object is not there (any more).
This way a manual change stands out, and you can see whether production matched the design at the time of the check.
What it gives you
- During an outage you see straight away what has changed.
- During an upgrade or migration you know exactly what has to move.
- During an audit you can show what is in the system and why.
How we do it
Our integration builder works this way. In spring 2026 it already managed dozens of functions with more than three hundred recorded versions, each checked by SAP itself before it was placed.
Would you like advice on managing your SAP custom code? Request a free advice conversation.
Updated on