The Clean Core Strategy: The Hardest (But Most Critical) Choice in Cloud ERP

Clean Core might sound like a marketing buzzword. However, it represents the most difficult cultural challenge that an organization could face during its digital transformation journey.

For many years, if a process didn’t fit or users needed functionality that wasn’t native to the system, developers wrote ABAP code to change the system. This created a tailored suit that fit perfectly—until you needed an upgrade. Then this customization became a straitjacket. Upgrades became multimillion-dollar nightmares because every line of custom code had to be checked and fixed.

Decluttering the Core

SAP’s Clean Core strategy fundamentally rejects this approach. As detailed in the SAP Customer Evolution program, the goal is to keep the ERP core standard without modifications. The innovation moves to SAP’s clean core model focusing on level A or level B extensions. These levels represent the cleanest extensions that use only released APIs or extension points or classic APIs and frameworks from the Cloudification Repository.

This is because, in a Cloud ERP world, updates happen automatically and frequently. If the organization’s core is cluttered with custom code, those updates will break the system. By decoupling the core using SAP BTP, organizations get the best of both worlds: a stable, easily upgradeable system and the ability to build extensions that give the business a competitive edge.

The SAP Customer Evolution program updates webinar highlighted that this is often a shock to internal developers and business users who are used to hearing yes to every customization request. The new answer is yes, but on the platform, not in the core. This discipline can make the difference between a successful Cloud ERP deployment and a failed one.

What This Means for SAPinsiders

Implementing a Clean Core strategy is 10% technology and 90% discipline. Here is how SAPinsiders can enforce it:

Establish a Clean Core governance board. SAPinsiders should create a review body that includes both business and IT leaders. Any request to modify the core ERP code must go through this board which fully understands the cost and impact of implementing any customizations. The default answer should be no, and the requestor must demonstrate why standard functionality will not work and why the customization cannot be built using the cleanest definitions of extensibility.

Retrain the organization’s ABAP team. Internal developers are likely experts in modifying the core. However, they need to pivot in a Cloud ERP world. Organizations should invest in training them on the different extensibility levels available to maintain a clean core approach. This will turn them from core modifiers into app builders. It will also empower them to drive innovation without endangering the system’s stability.

Run the Custom Code Migration app. Use the tools SAP provides through the SAP Customer Evolution program to scan the organization’s current SAP ECC system. These will tell SAPinsiders exactly how much they have in the way of customizations and, crucially, how much of it is never used. SAPinsiders should use this data to ruthlessly retire technical debt before they even start their migration journey.