Clean core extensibility for SAP S/4HANA Cloud
Learn how the clean core strategy and the extensibility model described in this paper support this objective: Enabling customers of SAP S/4HANA Cloud to extend where needed, but still allowing for smooth system upgrades and handling of system extensions. Stáhnout dokument
Creating scalable, upgrade-ready
extensions for the Autonomous
Enterprise
WHITE PAPER
Clean core extensibility
extensions for the Autonomous
Enterprise
WHITE PAPER
Clean core extensibility
Table of contents
Preface: Autonomous Enterprise 3
and clean core
Executive summary 5
1 Introduction 7
2 Why a clean core is important 9
2.1 Overcoming obstacles and
unlocking innovation 9
3 What a clean core means for 10
extensibility
3.1 Extensibility as part of the 5 guiding 10
principles of clean core
3.2 Extensibility options: On-stack 11
and side-by-side
3.2.1 On-stack: SAP Build (through ABAP 12
Cloud) or classic extensibility
3.2.2 Side-by-side with SAP Build 14
and Joule Studio
3.2.3 The best of both worlds: on-stack 17
and side-by-side extensions
3.3 SAP’s clean core extensibility model 19
and the clean core level concept
3.3.1 The clean core level concept 19
3.3.2 Evolution of 3-tier extensibility 20
to level concept
3.3.3 Overview of clean core levels 21
3.3.4 Why, what and how—Under- 22
standing the new clean core levels
3.4 Partner add-ons and clean core 26
3.4.1 SAP Solution Extensions 26
3.4.2 Clean core APIs from partners 26
4 How to achieve a clean core 27
for extensibility?
4.1 RISE with SAP Methodology 27
4.1.1 Governance and maturity— 28
An approach to assessing
clean core governance
4.1.2 Clean core measurement 29
framework
4.1.3 Measurability: Extensibility KPIs 30
4.2 Reaching clean core with
“Stay Clean” and “Get Clean” 33
4.3 Stay Clean: How to create 34
clean extensions
4.3.1 Functional requirements 34
4.3.2 Extension architecture 38
4.3.3 Extension implementation 40
4.3.4 Extension deployment 42
4.4 Get Clean: How to measure the 44
current state of clean core?
4.4.1 RISE with SAP Methodology 44
dashboard
4.4.2 Assessing clean core KPIs 45
individually
4.5 How to achieve a clean core 46
4.5.1 Key steps and recommendations 47
for your path to clean core
5 F.A.Q. 49
6 Appendix 50
2 | 53Clean core extensibility
Preface: Autonomous Enterprise 3
and clean core
Executive summary 5
1 Introduction 7
2 Why a clean core is important 9
2.1 Overcoming obstacles and
unlocking innovation 9
3 What a clean core means for 10
extensibility
3.1 Extensibility as part of the 5 guiding 10
principles of clean core
3.2 Extensibility options: On-stack 11
and side-by-side
3.2.1 On-stack: SAP Build (through ABAP 12
Cloud) or classic extensibility
3.2.2 Side-by-side with SAP Build 14
and Joule Studio
3.2.3 The best of both worlds: on-stack 17
and side-by-side extensions
3.3 SAP’s clean core extensibility model 19
and the clean core level concept
3.3.1 The clean core level concept 19
3.3.2 Evolution of 3-tier extensibility 20
to level concept
3.3.3 Overview of clean core levels 21
3.3.4 Why, what and how—Under- 22
standing the new clean core levels
3.4 Partner add-ons and clean core 26
3.4.1 SAP Solution Extensions 26
3.4.2 Clean core APIs from partners 26
4 How to achieve a clean core 27
for extensibility?
4.1 RISE with SAP Methodology 27
4.1.1 Governance and maturity— 28
An approach to assessing
clean core governance
4.1.2 Clean core measurement 29
framework
4.1.3 Measurability: Extensibility KPIs 30
4.2 Reaching clean core with
“Stay Clean” and “Get Clean” 33
4.3 Stay Clean: How to create 34
clean extensions
4.3.1 Functional requirements 34
4.3.2 Extension architecture 38
4.3.3 Extension implementation 40
4.3.4 Extension deployment 42
4.4 Get Clean: How to measure the 44
current state of clean core?
4.4.1 RISE with SAP Methodology 44
dashboard
4.4.2 Assessing clean core KPIs 45
individually
4.5 How to achieve a clean core 46
4.5.1 Key steps and recommendations 47
for your path to clean core
5 F.A.Q. 49
6 Appendix 50
2 | 53Clean core extensibility