The problem
In SAP, functions are bundled into groups. That is convenient, because related functions sit together. But it has a downside: if one function contains an error, the whole group can no longer be used. Every integration that relies on that group fails at the same time. And the repair sometimes requires manual work in SAP itself.
Why this happens more often with generated code
If you have code produced automatically or with AI, new functions are deployed faster and more often. Every deployment is a chance for an error. Without separation, one small mistake becomes an outage in several integrations at once.
Our approach
- One function per container. An error affects only that one function.
- Check before deploying. All code first goes through SAP's syntax check. If there is an error, nothing is deployed, and the error comes back with its line and word.
- Roll out in layers. First a small foundation, then the rest. The next layer starts only when the previous one is fully in place.
A lesson from practice
We learned this the hard way, while developing our own integration builder: one error in one function made an entire function group unusable. Since then, isolation has been a fixed rule, including in the instructions for the AI that helps build.
What to watch out for
- Limit the damage of an error to the smallest possible component.
- Let SAP check the code before anything is saved, not after.
- Record lessons like this as rules, so they do not have to be learned again.
Would you like advice on SAP development? Request a free advice conversation.
Updated on