The problem
Almost every SAP system has its own custom development: Z-programs, modifications and enhancements built over the years. Some of it is essential, some of it is never used any more, and for much of it nobody remembers why it is there. With every upgrade, and certainly with the move to S/4HANA, all that custom code has to be checked and often adapted.
Why it keeps coming back
- Custom code is quick to build and rarely cleaned up.
- The people who built it have left; documentation is missing.
- Modifications to the SAP standard itself turn every new version into a project.
That is why SAP steers towards a clean core: modify the standard as little as possible, and extend it through released interfaces or alongside the system.
Our approach
- Measure what is used. Which programs, functions and reports actually run? What is not used can usually go.
- Separate valuable custom code. What stays, we build on released SAP interfaces or as a separate application alongside SAP, for example in a dedicated application or on a low-code platform.
- AI as an accelerator, with checks. An AI model can help read and convert old code. We have every result checked by the SAP system itself and by a senior developer.
- Record it. Every piece of custom code that stays gets an owner and a reason.
What to watch out for
- Cleaning up before a migration is cheaper than after: every line of code that is gone does not have to be converted.
- A clean core is not a goal in itself; the point is lower costs at every subsequent upgrade.
- Record which interfaces depend on the custom code before you remove anything.
Would you like advice on cleaning up SAP custom code? Request a free advice conversation.
Sources
Updated on