S/4HANA Clean Core
Clean Core is SAP's principle that customer extensions should not modify SAP standard objects and should live on stable, released extensibility layers so upgrades and cloud migrations remain low-risk. Consultants must know the extensibility options (KUX, developer extensibility, side-by-side on BTP), released APIs, and how to detect and remediate custom code that violates Clean Core.
Overview
Clean Core is SAP's principle that customer extensions should not modify SAP standard objects and should live on stable, released extensibility layers so upgrades and cloud migrations remain low-risk. Consultants must know the extensibility options (KUX, developer extensibility, side-by-side on BTP), released APIs, and how to detect and remediate custom code that violates Clean Core.
Lessons in this topic
- What Clean Core Means and WhyDefinition, benefits and risks of violations.
- ATC Cloudification and Custom Code MigrationHow to measure Clean Core adherence.
Interview questions covered
- Enhancement broke after upgrade. Clean Core lens?
- Customer has 200 user exits and wants S/4 conversion. Plan?
- What is S/4HANA Clean Core?
- What are the three extensibility options?
- How do you build a Clean Core governance model?
- New custom code introduced without Clean Core review. Response?
- A customer wants to modify a standard S/4HANA transaction. How do you keep the core clean?
- What are released APIs?
- Customer wants a new field on sales order. Approach?