Clean Core Orientation for Stakeholders

• QuestionWhat is "What is Clean Core? (plain language)"?Tap to revealAnswerClean Core means keeping SAP standard untouched and putting custom needs beside it on supported connection points, so the system stays easy to upgrade.
• QuestionIn "What is Clean Core? (plain language)", explain:Tap to revealAnswerKeep the SAP standard core untouched.
• QuestionIn "What is Clean Core? (plain language)", explain:Tap to revealAnswerPut custom needs beside it, on supported, stable connection points.
• QuestionIn "What is Clean Core? (plain language)", explain:Tap to revealAnswerThis keeps the system easy to upgrade.
• QuestionIn "What is Clean Core? (plain language)", explain:Tap to revealAnswerIt is about where customisation attaches — not a ban on customisation.
• QuestionAnalogy for "What is Clean Core? (plain language)":Tap to revealAnswerPlug into the wall socket rather than splicing into the wiring inside the wall — you can still rewire the house later.
• QuestionWhat is "The six Clean Core dimensions"?Tap to revealAnswerClean Core spans six dimensions — software stack, extensibility, integrations, processes, data, and operations — so it is end-to-end, not just about code.
• QuestionIn "The six Clean Core dimensions", explain:Tap to revealAnswerSix dimensions: software stack, extensibility, integrations, processes, data, operations.
• QuestionIn "The six Clean Core dimensions", explain:Tap to revealAnswerClean code on a distorted process or poor data is still not Clean Core.
• QuestionIn "The six Clean Core dimensions", explain:Tap to revealAnswerClean Core is end-to-end — a property of the whole solution.
• QuestionIn "The six Clean Core dimensions", explain:Tap to revealAnswerA genuinely 'Clean Core' project addresses all six, not just the code.
• QuestionAnalogy for "The six Clean Core dimensions":Tap to revealAnswerA building is only sound if structure, plumbing, wiring, foundations, and upkeep are all in order — not just one of them.
• QuestionWhat is "Why upgrades get easier"?Tap to revealAnswerBecause extensions use released, versioned contracts, SAP can change the core without breaking them — so upgrades bring fewer surprises and go faster.
• QuestionIn "Why upgrades get easier", explain:Tap to revealAnswerExtensions attach only through released (stable) and versioned (managed-change) contracts.
• QuestionIn "Why upgrades get easier", explain:Tap to revealAnswerSAP can change the core's internals without breaking those extensions.
• QuestionIn "Why upgrades get easier", explain:Tap to revealAnswerThe old way reached into internals, so every upgrade hunted for what broke.
• QuestionIn "Why upgrades get easier", explain:Tap to revealAnswerResult: fewer surprises and faster upgrades.
• QuestionAnalogy for "Why upgrades get easier":Tap to revealAnswerA standard plug fits every upgraded socket; a wire soldered directly into old fittings has to be redone every time the fittings change.
• QuestionWhat is "The vocabulary everyone keeps using (glossary)"?Tap to revealAnswerS/4HANA (the core system), BTP (SAP's cloud platform), RAP (modern in-system development), CDS (reusable data views), ATC (the quality checker), BAdI (an official hook), released API (a stable published connection), FPS (a scheduled feature bundle), and key-user extensibility (in-app tools) are the terms you will keep hearing.
• QuestionIn "The vocabulary everyone keeps using (glossary)", explain:Tap to revealAnswerS/4HANA: SAP's current core business system. BTP: SAP's separate cloud platform for side-by-side extensions.
• QuestionIn "The vocabulary everyone keeps using (glossary)", explain:Tap to revealAnswerRAP: the modern supported way to build extensions in-system. CDS: reusable, saved views of data.
• QuestionIn "The vocabulary everyone keeps using (glossary)", explain:Tap to revealAnswerATC: the automated quality checker. BAdI: an official hook for plugging in custom logic.
• QuestionIn "The vocabulary everyone keeps using (glossary)", explain:Tap to revealAnswerReleased API: an officially published, stable connection point. FPS: a scheduled bundle of features/fixes you upgrade to. Key-user extensibility: in-app tools for business users.
• QuestionAnalogy for "The vocabulary everyone keeps using (glossary)":Tap to revealAnswerIt is the cast list for the conversation — once you can recognise the names, you can follow the plot.
• QuestionWhat is "How to read a readiness report"?Tap to revealAnswerFindings are grouped by priority, a baseline marks accepted existing debt, and the trend — are new findings going down? — matters more than the absolute number.
• QuestionIn "How to read a readiness report", explain:Tap to revealAnswerFindings are grouped by priority — look at high-priority counts first, not the grand total.
• QuestionIn "How to read a readiness report", explain:Tap to revealAnswerA baseline marks accepted existing debt; watch for new findings on top of it.
• QuestionIn "How to read a readiness report", explain:Tap to revealAnswerA stable baseline with no new high-priority findings is healthy.
• QuestionIn "How to read a readiness report", explain:Tap to revealAnswerRead the trend, not the snapshot — 'which way is it moving?' beats 'how big is it?'
• QuestionAnalogy for "How to read a readiness report":Tap to revealAnswerLike a medical check-up: the direction your results are trending matters more than any one day's reading.

1. 1List the core idea

   Analyse~10 min

   In your own words, list the central idea of "What is Clean Core? (plain language)". Aim for one paragraph, no jargon you haven't earned.

   Done when: A non-expert could read your paragraph and explain it back to you.

   Re-read the source concept

2. 2Apply it to a real situation

   Apply~15 min

   Find a real situation from your own work / life where "How to read a readiness report" applies. Apply the idea — describe the situation, the move you'd make, and the alternative you considered first.

   Done when: You can name a specific situation (not a hypothetical), state your move, and explain the trade-off in one paragraph.

   Re-read the source concept

3. 3Teach it back

   Evaluate~5 min

   Pick someone (a colleague, a peer, a rubber duck) and explain the section to them in under 5 minutes. Use your own example, not the one from the lesson.

   Done when: Your listener can repeat the core idea + the trade-off back to you without prompting.

Why this matters. Reading + quizzing prove recall; applying it in a real situation is the only evidence of transfer. Treat at least one of these as non-negotiable before you move on.