Akshay writes about the practical side of SAP modernization — clearing the issues flagged by ATC (SAP’s code-quality checker), moving reports onto SAP’s modern stack (CDS and RAP), retiring brittle screen-automation (BDC), and getting a custom codebase ready for ABAP Cloud without halting the business that runs on it.
Going live on S/4HANA isn't the finish line for Clean Core — it's the start. Why converted systems drift out of compliance, and how continuous governance keeps every upgrade a non-event.
SAP ECC mainstream maintenance ends in 2027. Here's a custom-code migration plan for small and mid-size teams that de-risks the move to S/4HANA — incrementally, without rewriting everything.
The handful of code issues most likely to block your SAP cloud move — flagged by ATC, SAP's code-quality checker — and the official, upgrade-safe replacement for each.
Stop integrations breaking on every screen change. BDC screen-automation (CALL TRANSACTION, batch input) is brittle and not cloud-safe — here's a decision tree for replacing it with official APIs (BAPI, RAP or OData).
Give the business a modern web screen in hours, not months. Turn an old table-maintenance view or report into a Fiori app (SAP's modern web UI), scaffolded from the table on the modern stack (CDS, RAP).
Make a stalled migration feel manageable. An ATC baseline (a snapshot from SAP's code-quality checker) turns an overwhelming wall of findings into a prioritized backlog you burn down at your own pace.
The single biggest performance lever in S/4HANA is doing the work in the database. A practical guide to code pushdown with CDS and AMDP.
Stop emailing spreadsheets. A clean, governed way to give the business live SAP data in Power BI or Datasphere — built on released CDS and OData.
