Clean Core Isn't Optional Anymore — Here's What It Means for Upstream

Every upstream operator we work with has the same quiet liability sitting in their SAP system: years of custom code, written by people who have long since moved on, doing things the standard system can now do on its own. It worked. It still works. And it's exactly what makes every upgrade slower, riskier, and more expensive than it needs to be.

That's the problem clean core is meant to solve.

What "clean core" actually means

Clean core is SAP's principle that your customizations should live alongside the standard system through approved extension points — not inside it by modifying standard objects. A clean core system stays close to standard, which means upgrades become routine instead of a project.

It comes down to a few ideas:

• Keep the standard standard. Don't modify SAP's own objects.
• Extend through side-by-side and on-stack extensibility, not core modifications.
• Use released APIs, not direct table access that breaks when the data model changes.
• Retire custom code that standard functionality now covers.

Why upstream feels this more than most

Upstream oil & gas runs some of the most heavily customized SAP landscapes in any industry. PRA, JVA, complex AFE and partner-billing logic — much of it was built before standard functionality matured. The result is a thick layer of custom code that's deeply entangled with the core.

When you carry that into an S/4HANA upgrade or a move to SAP RISE, every modification becomes something to test, fix, or rebuild. We've seen upgrades double in timeline purely because of code nobody had remediated.

Do the remediation before the upgrade

The mistake we see most often is treating clean core as something to sort out during the upgrade. By then, it's the critical path — and the most expensive time to discover a custom program that no longer compiles.

The better sequence is straightforward:

1. Analyze. Inventory custom code and classify it: keep, remediate, or retire.
2. Retire aggressively. A surprising amount of custom code is dead or now redundant with standard.
3. Remediate what stays to released APIs and approved extension points.
4. Then upgrade — into a landscape that's ready for it.

Done this way, clean core stops being a tax on the upgrade and becomes the thing that makes the upgrade fast.

The payoff

A clean core landscape upgrades in a fraction of the time, adopts new SAP capabilities like Joule and Fiori without a fight, and stops accumulating the technical debt that made the last upgrade hurt. For upstream operators planning a move to S/4HANA or RISE, it's the highest-leverage work you can do — and it's best done first.

If you're staring down an upgrade and aren't sure what's hiding in your custom code, that's exactly the assessment we do. Let's talk.