The Upgrade That Never Gets Easier
Every enterprise that customized ECC the same way learns the same lesson at RISE with SAP time: the upgrade isn't hard because S/4HANA is hard. It's hard because a decade of custom code, modified standard objects, and side-door integrations turned the core into something no vendor patch was ever tested against. Clean core isn't a purity exercise — it's the difference between an 18-month migration and a 6-month one.
What Clean Core Actually Means
Clean core means every extension lives outside the core: in the SAP BTP extension layer, via released APIs and CDS views, never through direct table access or core object modification. It's a discipline, not a product — SAP will sell you the tools, but no tool enforces the discipline for you.
The Three-Question Test
Before approving any customization request, three questions decide whether it belongs in the core or the extension layer: Does this run on every transaction, or only for an exception? Would we lose this capability entirely if we didn't build it, or is it a convenience? Can it be built on a released, upgrade-stable API? If the answer to the third question is no, the request needs an architecture review before it needs a developer.
The Part Nobody Budgets For
Clean-core discipline has a real cost: it's slower to ship the first version of anything, because the sanctioned path is rarely the fastest path. Enterprises that skip this step save three weeks on the first release and lose eight months on the next upgrade. The math only works if leadership protects the discipline when a business stakeholder is impatient for a shortcut — which is the actual failure point in most clean-core programs, not the technology.
What Good Looks Like
An enterprise doing this well can name every extension to its core, knows which SAP release cycle each one depends on, and treats its next S/4HANA or RISE upgrade as a scheduled event rather than a program. That's the real advantage — not a cleaner architecture diagram, but a modernization roadmap the business can put a date on.
Related Perspectives
Agentic Enterprise & AI ROI
From AI Pilots to P&L Impact
A pragmatic operating model for scaling AI beyond the pilot — who owns it, how it's funded, how it's measured.
Read perspective
Industry Playbooks
Warranty as a Revenue Line
How machinery OEMs turn field data and warranty automation into recurring aftersales revenue.
Read perspective
Data & AI Governance
Lineage Before Language Models
Why data lineage, not model choice, is the real blocker to trustworthy enterprise AI.
Read perspective