Modernizing Legacy ABAP: When to Refactor, When to Wrap, and When to Replatform
Date Published
The Modern ABAP Engineering Decision Matrix
When modernizing complex legacy SAP estates, development leaders often face the dilemma of choosing between on-stack modern ABAP Cloud and side-by-side extensions on the SAP Business Technology Platform.
Our engineering framework categorizes existing custom code into three clear buckets: Core Standard Re-platforming (replacing Z-code with standard SAP functionality), On-Stack RAP Modernization (wrapping remaining core logic into RESTful Application Programming services with clean contracts), and Side-by-Side Innovation (migrating UI, integration, and third-party orchestration to SAP BTP).
By applying this triage methodology, organizations consistently achieve upgrade safety for upcoming S/4HANA releases while drastically lowering long-term maintenance overhead.