Clean Core for Key & End Users

• QuestionWhat is "What Clean Core means for you"?Tap to revealAnswerIf you extend SAP through the supported in-app tools, your changes survive upgrades; shadow spreadsheets and off-system workarounds do not.
• QuestionIn "What Clean Core means for you", explain:Tap to revealAnswerChanges made through supported in-app tools survive upgrades.
• QuestionIn "What Clean Core means for you", explain:Tap to revealAnswerShadow spreadsheets and off-system steps are invisible and break silently.
• QuestionIn "What Clean Core means for you", explain:Tap to revealAnswerWorkarounds carry no audit trail and no upgrade protection.
• QuestionIn "What Clean Core means for you", explain:Tap to revealAnswerClean Core is a promise of durability, not a restriction on what you can ask for.
• QuestionAnalogy for "What Clean Core means for you":Tap to revealAnswerIt is the difference between writing on the whiteboard everyone shares and keeping notes on a sticky pad in your own drawer.
• QuestionWhat is "Key-user (in-app) extensibility"?Tap to revealAnswerThe in-app (key-user) tools let business users add fields, views, and simple logic through released, supported extension points — no classic development.
• QuestionIn "Key-user (in-app) extensibility", explain:Tap to revealAnswerKey-user tools are built into the Fiori apps — changes are made through screens, not code.
• QuestionIn "Key-user (in-app) extensibility", explain:Tap to revealAnswerYou can add custom fields, custom views of data, and simple custom logic.
• QuestionIn "Key-user (in-app) extensibility", explain:Tap to revealAnswerYou only ever extend at released (SAP-supported, stable) extension points.
• QuestionIn "Key-user (in-app) extensibility", explain:Tap to revealAnswerBecause the hooks are released, the changes are upgrade-safe by design.
• QuestionAnalogy for "Key-user (in-app) extensibility":Tap to revealAnswerIt is like the official settings panel of an app: powerful options the maker put there on purpose, not a hack into the source code.
• QuestionWhat is "Custom fields & logic without a developer"?Tap to revealAnswerAdding a field, showing it on a form or report, and setting a simple validation are things you can self-serve through the in-app tools, and they stay upgrade-safe.
• QuestionIn "Custom fields & logic without a developer", explain:Tap to revealAnswerSelf-service staples: add a field, show it on a form or report, add a simple validation.
• QuestionIn "Custom fields & logic without a developer", explain:Tap to revealAnswerThe tools store your change as configuration the upgrade carries forward — not a code edit.
• QuestionIn "Custom fields & logic without a developer", explain:Tap to revealAnswerDefault question: 'can the in-app tool do this?' before going outside the system.
• QuestionIn "Custom fields & logic without a developer", explain:Tap to revealAnswerIn-app changes are shared and audited, unlike a personal workaround.
• QuestionAnalogy for "Custom fields & logic without a developer":Tap to revealAnswerIt is like adding a custom column to a shared spreadsheet template that everyone inherits — except the system remembers it through every update.
• QuestionWhat is "When to involve a developer (and what to ask for)"?Tap to revealAnswerWhen the in-app tools fall short, ask a developer for a solution on released APIs or RAP — never a modification to SAP standard.
• QuestionIn "When to involve a developer (and what to ask for)", explain:Tap to revealAnswerInvolve a developer when the in-app tools cannot meet the need.
• QuestionIn "When to involve a developer (and what to ask for)", explain:Tap to revealAnswerAsk for a solution on released APIs or the modern RAP model — 'build it the Clean Core way.'
• QuestionIn "When to involve a developer (and what to ask for)", explain:Tap to revealAnswerNever accept a modification to SAP standard, even as a quick fix.
• QuestionIn "When to involve a developer (and what to ask for)", explain:Tap to revealAnswerDescribe the outcome; insist it is upgrade-safe; let the developer pick the method.
• QuestionAnalogy for "When to involve a developer (and what to ask for)":Tap to revealAnswerAsk a licensed electrician to add a proper new outlet — do not let anyone splice into the wiring inside the wall.
• QuestionWhat is "Staying upgrade-safe"?Tap to revealAnswerKeep extensions inside the governed tools, avoid undocumented integrations and config drift, and report needs instead of building shadow processes.
• QuestionIn "Staying upgrade-safe", explain:Tap to revealAnswerKeep extensions inside the governed in-app tools so the system carries them forward.
• QuestionIn "Staying upgrade-safe", explain:Tap to revealAnswerAvoid undocumented integrations — they break silently and without warning.
• QuestionIn "Staying upgrade-safe", explain:Tap to revealAnswerAvoid configuration drift — uncontrolled manual settings nobody can reconstruct.
• QuestionIn "Staying upgrade-safe", explain:Tap to revealAnswerReport needs rather than building private shadow processes.
• QuestionAnalogy for "Staying upgrade-safe":Tap to revealAnswerUse the building's official maintenance request line instead of running your own wires through the ceiling.

1. 1Map the core idea

   Analyse~10 min

   In your own words, map the central idea of "What Clean Core means for you". 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. 2Use it to a real situation

   Apply~15 min

   Find a real situation from your own work / life where "Staying upgrade-safe" applies. Use 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.