The vocabulary everyone keeps using (glossary)
What you'll learn
S/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.
- S/4HANA: SAP's current core business system. BTP: SAP's separate cloud platform for side-by-side extensions.
- RAP: the modern supported way to build extensions in-system. CDS: reusable, saved views of data.
- ATC: the automated quality checker. BAdI: an official hook for plugging in custom logic.
Clean Core conversations are full of acronyms. Here is a plain-language glossary. S/4HANA is SAP's current generation of its core business system. BTP (Business Technology Platform) is SAP's separate cloud platform where extensions can run beside the core. RAP (the ABAP RESTful Application Programming model) is SAP's modern, supported way for developers to build extensions inside the system.
A few more: CDS (Core Data Services) is a way of defining reusable views of data — essentially saved, shareable queries. ATC (ABAP Test Cockpit) is the automated quality checker that flags Clean Core problems. A BAdI (Business Add-In) is a pre-built, official 'hook' where custom logic can be plugged in without touching standard code. A released API is any connection point SAP has officially published and promised to keep stable.
And two that come up constantly: FPS (Feature Pack Stack) is a scheduled bundle of new features and fixes SAP ships — the thing you 'upgrade' to. Key-user extensibility is the set of in-app tools that let business power users adapt the system without a developer. You do not need to use these terms yourself, but recognising them lets you follow any Clean Core discussion.
Key points
- S/4HANA: SAP's current core business system. BTP: SAP's separate cloud platform for side-by-side extensions.
- RAP: the modern supported way to build extensions in-system. CDS: reusable, saved views of data.
- ATC: the automated quality checker. BAdI: an official hook for plugging in custom logic.
- Released 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.
Examples
'We'll use key-user extensibility for the field, a released API via RAP for the logic, run ATC before the next FPS, and read the data through a CDS view.' — every term above, in one real sentence.
Source notes: clean-core-curriculum (business synthesis)
Ask Claude
Build a prompt from this lesson + your question and open a fresh Claude chat with it pre-filled — handy for adapting a before/after pattern to your own object.