ARCHITECTAdvanced
S/4HANA Clean Core
Master S/4HANA Clean Core with released APIs, extensibility options, ATC checks, custom code migration, side-by-side extensions and upgrade-safe ABAP design.
Overview
Master S/4HANA Clean Core with released APIs, extensibility options, ATC checks, custom code migration, side-by-side extensions and upgrade-safe ABAP design.
Lessons in this topic
- Classifying Custom Code for Clean CoreClassify custom code into keep, remediate, retire, replace or move side-by-side.
- Clean Core Risk: Modifications, Implicit Enhancements and Unreleased ObjectsIdentify the highest-risk custom code patterns that make upgrades difficult.
- Clean Core Governance and DocumentationUnderstand why Clean Core needs governance, review boards, exception tracking and lifecycle control.
- Clean Core and Extensibility TypesUnderstand key-user extensibility, developer extensibility and side-by-side extensibility.
- Side-by-Side Extension on BTPLearn when side-by-side extension is better than putting custom logic inside S/4HANA core.
- Clean Core Extension Decision FrameworkLearn how to choose between configuration, key-user extensibility, developer extensibility, BAdI, API and side-by-side extension.
- Released APIs vs Direct Table AccessUnderstand why Clean Core prefers released APIs over direct dependency on SAP internals.
Interview questions covered
- ATC shows usage of unreleased SAP objects in custom code. What would you do?
- A business requirement can be solved by configuration or a custom enhancement. What should you choose in Clean Core thinking?
- What does Clean Core mean in S/4HANA?
- How would you run a custom code cleanup during S/4HANA conversion?
- How do you sustain Clean Core after go-live?
- A team wants to add an implicit enhancement in S/4HANA because it is faster. How would you respond?
- How do you decide between in-app extension and side-by-side extension?