The Governance Gap
Every SAP modernization program talks about clean core. Fewer programs define what it means in practice, and fewer still enforce it during delivery.
The result is a familiar pattern: the architecture review board approves a clean core strategy, the delivery teams build what they need to hit their deadlines, and twelve months later the landscape is no cleaner than it was before.
What Clean Core Actually Means in Delivery
Clean core is not a destination. It is a set of constraints applied to every decision that touches the core system.
In practical terms, clean core governance means answering three questions before any extension or modification is approved.
- Can this be done on BTP instead of in the core? If yes, it should be.
- If it must touch the core, does it use a supported extensibility mechanism? Key user extensibility, released APIs, or clean core-compatible BAdIs.
- Will this survive an upgrade without manual intervention? If the answer is uncertain, the design needs to change.
Why Speed and Governance Feel Opposed
Delivery teams resist governance because it feels like a bottleneck. And in many organizations, it is.
The problem is usually not the rules themselves but how they are applied. Governance that requires a committee review for every change request will always lose to deadline pressure. Governance that is embedded in the delivery workflow has a chance.
This means shifting from approval gates to automated checks. Instead of asking an architecture board whether an iFlow meets standards, check it programmatically before it reaches production.
A Model That Works
The programs where clean core governance actually holds share a few characteristics.
- Extension decisions are documented at design time, not retroactively. Every extension has a rationale that includes the clean core trade-off.
- Integration standards are enforced before deployment, not audited after incidents. Automated analysis catches naming violations, missing error handlers, and hardcoded credentials before they reach production.
- Governance metrics are visible to leadership. Not as compliance theater, but as a real-time view of how much of the landscape is upgrade-safe.
- Exceptions are allowed but tracked. Not every decision will be clean core-compliant, and that is acceptable as long as the deviation is explicit and time-bound.
Governance Is a Delivery Discipline
Clean core governance works when it is treated as a delivery discipline, not a policy document. It has to be fast enough that teams use it, specific enough that it catches real problems, and visible enough that leadership can see whether the landscape is getting cleaner or drifting.
The alternative is another modernization cycle in three years, fixing the same problems with a new set of slide decks.