Frequently Asked Questions
SAP Core Enablement: Frequently Asked Questions
Everything you need to know about SAP Core Enablement engagements with MYGO Consulting.
What does SAP Clean Core mean?
SAP Clean Core is an approach to implementing S/4HANA that emphasizes standardization and minimization of customization in the core system. Instead of modifying SAP's standard code with Z and Y namespace objects, custom functionality is built as side-by-side extensions on SAP BTP. This keeps the core upgrade-safe, reduces maintenance costs, and enables faster adoption of SAP innovations.
How do you decide what custom code to keep vs. retire vs. move to BTP?
We use a structured disposition framework. Each custom object is evaluated on two axes: business criticality (is this actively used and needed?) and technical fit (can this run as a BTP extension?). Objects that are unused get retired. Objects that duplicate standard S/4HANA functionality get replaced. Objects with genuine unique business logic get re-platformed to BTP as side-by-side extensions.
Will our users notice any difference after moving to a clean core?
The goal is to maintain or improve the user experience while eliminating technical debt behind the scenes. Custom Fiori apps and BTP extensions can provide the same or better functionality than Z-transactions. In many cases, users gain access to modern SAP Fiori interfaces that replace legacy custom transactions. We involve business users in functional gap analysis to ensure no critical capability is lost.
How long does a clean core transformation take?
A clean core assessment and remediation program typically runs 3-6 months for the initial analysis and first wave of remediation. Organizations with large custom code portfolios (5,000+ objects) may need 6-12 months for full remediation. We phase the work by business criticality, addressing high-impact customizations first.
Can we do clean core as part of an S/4HANA migration?
Yes, and we recommend it. The migration to S/4HANA is the ideal time to implement clean core principles because you are already addressing custom code during the conversion process. We run the clean core analysis in parallel with the migration assessment so that custom code remediation serves both the migration and the clean core objectives simultaneously.
What is the relationship between clean core and SAP BTP?
BTP is the technology platform that makes clean core possible. When custom functionality needs to move out of the S/4HANA core, BTP provides the runtime environment for side-by-side extensions, the integration layer for connecting extensions to S/4HANA, and the development tools for building modern applications. Clean core is the strategy; BTP is the execution platform.
Does SAP require a clean core approach for S/4HANA Cloud?
S/4HANA Cloud Public Edition enforces clean core by design; you cannot modify the core. S/4HANA Cloud Private Edition and on-premise allow core modifications but SAP strongly recommends the clean core approach for upgrade safety and long-term maintainability. MYGO helps organizations adopt clean core principles regardless of their S/4HANA deployment model.
Still Have Questions?
Talk to our SAP experts and get answers to your specific questions directly.