External

Clean core
extensibility for
SAP S/4HANA 
Cloud 
January 2025, version 2.0


SAP S/4HANA Cloud | Clean Core Extensibility

Table
of contents
1 Introduction 3

2 The clean core strategy 4

2.1 Clean core principles:

guidelines and benefits of extensibility 5

3 Extensibility of SAP S/4HANA Cloud 7

3.1 The extensibility model 7

3.2 Extensibility options: when to use what? 8

3.3 The public cloud extensibility model  16

3.4 The private cloud extensibility model  17

3.5 Launching a clean core certification

program for partner applications  19
3.6 APIs, events, and extension points 20

4 Extend SAP S/4HANA with SAP Build  21

5 Getting started 23

6 Summary 25

7 Appendix  26

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 2 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

1 Introduction
Software is designed with a scope in mind. While down upgrades or might even break them so
the breadth of scope covered by SAP applications that additional adjustment effort is required.
is an important factor for the adoption of SAP Therefore, the ultimate goal of every extension
solutions, these solutions cannot cover the distinct project should be to keep the core of a system
need of every customer to differentiate with a clean by minimizing these disturbing factors
competitive advantage. Therefore, SAP solutions while adhering to cloud standards.
can be extended to fit customers’ unique needs.
SAP introduced the revolutionary approach of The clean core strategy and the extensibility model
installing a system with standard functionality described in this paper support this objective:
(based on decades of best practices) along with enabling customers of SAP S/4HANA Cloud2 to
the ability to extend that functionality in a cost- extend where needed but still allowing for smooth
effective manner. This balanced approach has system upgrades and handling of system exten-
become one of the most important factors in the sions. Ultimately, the main goal is to keep the core
phenomenal success of the SAP ERP application. of the ERP system as close to the standard as
possible while extending the functional scope
To accommodate varying business needs and where needed.
preferences while adhering to cloud standards,
SAP introduced two different editions of SAP This paper gives details on the clean core strategy
S/4HANA Cloud: SAP S/4HANA Cloud Public Edi- in Chapter 2, followed by an in-depth description
tion and SAP S/4HANA Cloud Private Edition. of the extensibility of SAP S/4HANA Cloud in
For SAP S/4HANA Cloud Public Edition, as a SaaS Chapter 3. The extensibility model for both editions
solution, SAP makes sure the system is up to date of SAP S/4HANA Cloud, as well as the possible
and upgraded to the latest release for customers. options, are outlined with reasoning for when to
This allows them to leverage a standardized and use which. Chapter 4 highlights the evolution of
quick-to-deploy ERP solution that can be extended SAP Build solutions into a unified and AI-enabled
while keeping the core of the system unchanged, clean-core extensibility solution optimized both
that is, helping ensure smooth upgrade cycles by for cloud ERP and other cloud solutions from SAP.
not changing its base code line.1 Chapter 5 gives guidance on how to get started
on the journey toward achieving and keeping a
While upgrades in SAP S/4HANA Cloud Public clean core, followed by a summary in Chapter 6
­Edition are managed by SAP, SAP S/4HANA Cloud and a collection of relevant links in Chapter 7.
Private Edition follows a different approach.
It allows for more flexibility and control. SAP
takes care of system operations, but upgrades
are customer-managed projects that follow
the customer’s schedule. The higher degree of 1.  ublic cloud solutions from SAP for lines of business, such as
P
SAP SuccessFactors, SAP Concur, and SAP Fieldglass solutions, offer similar
flexibility and control can lead to costly and extension options adhering to the public cloud principle of keeping the core
time-consuming upgrade projects. One reason unchanged. What holds for SAP S/4HANA Public Cloud Edition and is
explained in Section 3.3 similarly holds for these solutions, that is, offering
for this is that extensibility options are much more extension options on the system stack as well as being decoupled from it
with SAP Business Technology Platform.
flexible – they can be decoupled from but also
2. I ncluding both SAP S/4HANA Cloud Private Edition and SAP S/4HANA Cloud
be modifying the core. The latter might slow Public Edition.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 3 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

2 The clean core strategy

“Clean core” is a concept and strategy to extend with lower total cost of ownership for SAP S/4HANA
SAP S/4HANA Cloud systems in an upgrade-safe Cloud while being agile enough to adapt to change
way. SAP S/4HANA Cloud Public Edition does when and where required.​A clean core is defined
and will continue to have a clean core, as SAP as an SAP S/4HANA Cloud solution that is up
technically enforces the guidelines of the public to date, documented, unmodified, consistent,
cloud extensibility model. To achieve or keep a efficient, and has custom extensions decoupled
clean core in SAP S/4HANA Cloud Private Edition, from SAP source code. The method for maintaining
certain recommendations and guidelines must this clean core while adapting SAP solutions to
be followed (see the paragraph on the private meet specific business needs is called clean core
cloud extensibility model). extensibility, which will be discussed in the following
paragraphs. Flexibility will continue to benefit
Extending SAP solutions to meet specific business customers in the future, provided that extensions
needs has always been a significant advantage for are built and utilized in adherence to clean core
SAP customers. Therefore, keeping a clean core, principles, the topic of the following section. 3
customers experience better maintainability, along

3. Find more information on the ERP clean core strategy.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 4 | 27
SAP S/4HANA Cloud | Clean Core Extensibility
Maximize upgrade stability by adhering
to these recommended clean core
guidelines:

_ I deally, adopt a policy of zero modifica-

tions of the core system.

_ Never clone SAP standard functionality.

_ Retire unused extensions.

2.1 Clean core principles: _ A

 dhere to general SAP code quality stan-
Guidelines and benefits of dards and best practices.4

extensibility _ Keep all extensions well documented.

Building extensions in adherence to clean core _ S

 et up a strong governance to follow the
principles achieves the balance between software clean core architecture (further described
flexibility with customer adjustments and system in the paragraph on the 3-tier extensibility
stability and availability in the cloud. The main model).
guideline to adhere to when building an extension
is to keep it strictly separate from the underlying _ D
 ecouple all extensions from the system’s
SAP applications. Extensions must access SAP core by leveraging public, released APIs.5
business objects only through well-defined,
upgrade-stable interfaces. Extensions calling, for _ L everage all extensibility options, that is,
instance, unreleased function modules or have all extensions running on stack, side
accessing the underlying database table directly by side on SAP Business Technology Plat-
can easily break as soon as the underlying sys- form (SAP BTP) or hybrid extensions resid-
tem code is changed and an upgrade is per- ing both on stack and side by side,
formed. The clean core approach, however, respectively.
results not only in faster software deployment
but also in easier adoption of software changes, _ C
 reate technical debt only as well-informed
since the core starts off clean and is kept that way decisions and only in cases where there is
using nondisruptive, regularly scheduled upgrades. no other possibility. Document these deci-
sions and revise the technical debt yearly
Clean core is a framework of best practices that – against new possibilities.
when followed – results in keeping both the SAP
S/4HANA Cloud solution and its extensions _ K
 eep the SAP software versions close to
upgrade stable. Let’s focus on how to achieve the latest release (current or n-1), feature
this. pack stack (FPS), and support pack stack
(SPS).

4.  or more detailed information see these blog posts on the Usage of ABAP
F _ W
 hen possible, use only partner solutions
Test Cockpit and ABAP Test Cockpit in the Cloud and the SAP BTP
Developer’s Guide. that are certified as clean core compliant.6
5.  ind public, released APIs to integrate and extend on SAP Business
F Discuss your clean core strategy with part-
Accelerator Hub.
ners and establish respective governance
6.  or more information, see an overview of implementation and certification
F
of ABAP Cloud add-ons for SAP Partners or this blog. For more information, for the partner solutions.
see “Extend SAP S/4HANA in the cloud and on premise with ABAP based
extensions,” SAP brochure, April 2024.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 5 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

What are the benefits when following

these guidelines?

Agility starts by having a solid foundation in the

cloud that leverages the previously mentioned
best practices and guidelines. Adopting them
brings benefits such as being able to quickly
react to changing environments that can include,
RISE with SAP Methodology for instance, a change in your company’s strategy
or processes, changing customer requirements,
RISE with SAP Methodology has been launched or sudden environmental or economic chal-
to drive these guidelines with customers and lenges. Having access to SAP’s innovations –
focus on the clean core principles. Customers being part of the latest release and, therefore,
using RISE with SAP should leverage this key enti- requiring an up-to-date core system – adds to
tlement to create a clean core project, establish a that agility. It allows customers to stay on top of
solution standardization board, and follow gover- new technologies and maximally leverage innova-
nance recommendations including regular report- tive services such as generative AI, low-code and
ing and execution of quality gates. pro-code application development, and process
automation.

System upgrade projects will be made signifi-

cantly easier when clean core extensions don’t
access the to-be-updated core in nonrecom-
mended ways. And when they do, if there simply
has been no other option available, customers
will know where to check because the upgrade
will be documented well. In addition, system
upgrades will eventually be both less complex
and costly, as there will be fewer outliers or cus-
tom extensions to potentially harm the upgrade
process adhering to the highest efficiency and
security standards. Moreover, the more regular
updates are run, the easier they will get, as best
practices will be established and well known and
proven project and test plans can be carried out.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 6 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

3 Extensibility of SAP S/4HANA Cloud

Whichever SAP S/4HANA Cloud solution custom- 3.1 The extensibility model
ers adopt, there must be ways in place that allow
for deviation from the standard offering where Independent of which cloud ERP solution you
needed to stay competitive and agile as per the choose, be it SAP S/4HANA Cloud Private Edition
customers’ unique business needs. The degree of or SAP S/4HANA Cloud Public Edition, it is stan-
freedom varies between SAP S/4HANA Cloud dard practice to support extensibility use cases
Public Edition and SAP S/4HANA Cloud Private with two different architectural approaches: on-
Edition, and the core concepts and differences stack extensibility, for extensions that are tightly
will be explained in this chapter. coupled with your ERP core, which means they
technically run on the same stack, and side-by-
SAP offers SAP S/4HANA Cloud Public Edition as side extensibility, for extensions that are loosely
a best-in-class public cloud ERP solution paired coupled with your ERP core and run on a sepa-
with a competitive cloud extensibility offering and rate extensibility platform. In the SAP context, this
an established robust partner ecosystem. This means that on-stack extensibility is used in case
public cloud ERP solution features developer your extension should be tightly coupled with
extensibility on the code level consuming Tier 1 your SAP S/4HANA Cloud solution, while side-by-
extensibility concepts. side extensibility is used when you want to
loosely couple your extension with your ERP sys-
Customers using SAP S/4HANA Cloud Private Edi- tem and run it on SAP BTP. Often, a combination
tion are supported on their transformation jour- of on-stack and side-by-side extensibility is
ney with a more flexible extensibility offering that needed to fulfill your business requirement.
enhances Tier 1 extensibility where it is of utmost When to use which extensibility pattern will be
importance with so-called Tier 2 and Tier 3 exten- detailed next.
sibility options. All these options, including the
role of SAP BTP in the extensibility context, will
be elaborated on further in this chapter.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 7 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

3.2 Extensibility options: when to use what?

The following guidelines and recommendations insights to help navigate the decision-making pro-
help to determine what part of the extension cess effectively, but it is not exhaustive. It is
should run on SAP S/4HANA as an on-stack important to analyze each extension use case
extension and what part of it should run on SAP and make an informed decision about which tech-
BTP as a side-by-side extension. The recommen- nologies work best for each case. For more infor-
dations apply to SAP S/4HANA Cloud Private Edi- mation and support, see SAP BTP Guidance
tion, SAP S/4HANA Cloud Public Edition, and SAP Framework and use SAP Application Extension
S/4HANA. Note that this guidance includes Methodology.

Figure 1: Extension use case patterns for SAP S/4HANA Cloud

Figure 1 depicts common extension use case patterns for SAP S/4HANA Cloud – both for on-stack
(to the left) and side-by-side (on the right) extensions. For more information, see the extension architec-
ture guide on extension use case patterns.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 8 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

A On-stack extensibility on SAP S/4HANA Cloud

On-stack extensions usually need to be tightly coupled, which means they need proximity to data,
­transactions, or applications in SAP S/4HANA Cloud.

 
Common on-stack use case
patterns are as follows:
 
The following are typical character-
istics of an on-stack extension:

Lj Adapt and extend standard applica- _ T

 ransactional consistency is required
tions: With this extensibility pattern, you when data from SAP standard tables
typically perform the following extension and fields and data from custom tables
tasks: and fields are changed jointly

_ Adapt a standard user interface (UI) _ C

 ustom integrations, for instance,
extensions of standard objects such as
_ Add a custom field to a standard UI APIs or services needed to enable
side-by-side extensions
_ Extend the SAP data model
_ R
 eading high data volumes, which
_ A
 dapt a standard business process requires complex Structured Query
with ­custom logic within a logical unit Language (SQL) queries and joins
of work by implementing the extension
point of an SAP application. _ F
 requent access and changes to data
from SAP standard tables and fields,
Lj  reate custom, full-stack applications:
C resulting in many roundtrips
This extensibility pattern enables you to
develop new applications that require  n-stack extensions on SAP S/4HANA Cloud will
O
proximity to SAP business objects and ser- be implemented with the ABAP Cloud develop-
vices according to the previously men- ment model.7 The benefits are described in the
tioned characteristics. Full-stack applica- following paragraph.
tions consist of a back- and front-end
implementation and, therefore, span the
full stack.

Lj Create and enable integration:

This extensibility pattern uses public local
APIs from SAP or events to build a custom
remote API or event, ­respectively, that can
be used for a side-­by-side extension on
SAP BTP. For more information on public
local APIs or events, see this page on
developer extensibility.

7.  or more information, see “Extend SAP S/4HANA in the cloud and on

F
premise with ABAP based extensions,” SAP brochure, April 2024.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 9 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

 The role and benefits of ABAP Cloud in the extension strategy

ABAP Cloud8 is the development model for developing cloud-ready business applications, services, and
extensions. It is available both on stack in SAP S/4HANA Cloud and also side by side on SAP BTP
­(see further benefits of creating extensions with ABAP Cloud in the context of SAP BTP in the following
paragraph). Some of its benefits are listed below.

ABAP Cloud provides one common develop- ABAP Cloud contains what you need to help ensure
ment model both on stack and side by side. It’s code quality, code documentation, and stable life-
available on SAP S/4HANA Cloud Public Edition, SAP cycle management of your custom extensions. It is
S/4HANA Cloud Private Edition, on premise, and on integrated into the development environment for
SAP BTP. It is used to develop customer and part- ABAP Cloud: ABAP development tools.
ner extensions as well as SaaS applications on
SAP BTP. It is the main development model used ABAP Cloud will benefit from the Joule copilot
by SAP itself to drive the development of SAP with ABAP development tools to increase devel-
S/4HANA Cloud. It allows leveraging existing oper efficiency. At the same time, an AI software
know-how of ABAP development tools for cloud- development kit for ABAP will offer a consumable
ready and clean extensibility. SAP standard library to conveniently use a gener-
ative AI hub on SAP BTP to leverage AI functional-
ABAP Cloud also helps ensure cloud readi- ity provided there in custom ABAP extensions.
ness and clean core compliance by default.
The new language version introduced with ABAP As mentioned, ABAP Cloud is also available on
Cloud allows the enforcement of cloud and clean SAP BTP to build side-by-side extensions, which
core rules by compiler and syntax checks. Using is explained next.
ABAP Cloud, these rules cannot be evaded.
8.  or more information on ABAP
F
Cloud, see the documentation
ABAP Cloud provides a model-driven archi- on the SAP Help Portal site.
tecture for online transactional processing
(OLTP), online analytical processing (OLAP), and
the development of new integrations and APIs by
the ABAP RESTful application programming model.
Moreover, strong transactional consistency is
enforced through the controlled logical unit of
work.

ABAP Cloud comes with a sound set of techni-

cal and business services (logging, change docu-
ments, number ranges, jobs, factory calendar, cur-
rency conversion, units of measure, and many more).
These services can be used without any additional
license and can reduce both total cost of develop-
ment and ownership for complex business applica-
tions. At the same time, they drive a high level of
standardization and supportability of custom exten-
sions. Last but not least, default configurations for
these services (calendars, countries, languages,
currencies, units, and so on) are delivered auto-
matically and are ready to use.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 10 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

B Side-by-side extensibility on SAP BTP

SAP BTP is an integrated offering comprising application development and automation, integration, data
and analytics, and AI services. The platform offers users the ability to turn data into business value, com-
pose and automate business processes, and build and – most important – extend applications in SAP
S/4HANA quickly. It provides integration capabilities to help ensure business processes are connected
across SAP and third-party solutions. SAP BTP is a platform for developing side-by-side extensions that
are loosely coupled with the core of SAP S/4HANA. Custom applications or extensions that run on
SAP BTP can interact with SAP S/4HANA using APIs and events while not modifying the core.9

9. For more information about available SAP standard APIs and events, see SAP Business Accelerator Hub.

 
Common use case patterns for side-by-side extensions are as follows:

Lj Create custom, full-stack applications: Lj  reate custom mobile apps: This exten-
C
sibility pattern provides mobile develop-
_ F
 ull-stack, single-tenant applications – ment capabilities. For an implementation
This extensibility pattern targets cus- example of this use case pattern, see the
tomers and implementation partners, mission on SAP Discovery Center.
enabling them to develop full-stack
apps on SAP BTP.

_ F
 ull-stack, multitenant SaaS applica- Lj  utomate tasks and processes across
A
tions for partners that are independent multiple systems: This extensibility pat-
software vendors (ISVs) – This extensi- tern provides low-code/no-code capabili-
bility pattern targets the ISV partner ties to automate processes. For an imple-
ecosystem, enabling them to develop mentation example of this use case
full-stack SaaS applications on SAP pattern, see the mission on SAP Discovery
BTP and to distribute the software to Center.
their customers. For an implementation
example of this use case pattern, see
the mission on the SAP Discovery Cen-
ter site.

_ H
 ub scenario of integrating with several
ERP systems and cloud services –
This extensibility pattern provides a
central hub on SAP BTP to collect and
distribute data from various systems.
For an implementation example of this
use case pattern, see the samples on
github.com.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 11 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

 
The following are typical characteristics and examples for side-by-side extensions:

_ S
 tand-alone applications or new business The services and technologies offered on SAP
process steps that can be decoupledData BTP to implement the previously mentioned
from custom tables and fields that isn’t extension patterns are described in more detail in
changed together with the following chapter. More detailed information
can be found in both the extension architecture
_ d
 ata from SAP standard tables and fields, guide and the SAP BTP Developer’s Guide.
therefore, no transaction consistency is The following paragraph summarizes the role and
required benefits of SAP BTP when it comes to extension
developments.
_ D
 emand to use a broad spectrum of different
development preferences, skill sets, and
languages such as Java, JavaScript, or ABAP
and freely available open-source libraries

_ A
 pplications for external users without a user
account for SAP S/4HANA and who will not
have direct access to an SAP S/4HANA
solution

_ B
 enefits of independent infrastructure, scal-
ability operations, and lifecycle with frequent
shipments and changes

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 12 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

 The role and benefits of SAP BTP in the extension strategy

SAP BTP supports two programming models: CAP services are developed and run on SAP BTP,
SAP Cloud Application Programming Model (CAP) Cloud Foundry runtime and SAP BTP, Kyma run-
to develop in JavaScript and TypeScript or Java, time. As mentioned, CAP allows implementation
and ABAP Cloud (described in the previous sec- in JavaScript (Node.js) and Java; it offers libraries
tion). Both development models are based on to implement and consume services, as well as
common concepts, and they are both centered generic provider implementations serving many
around core data services (CDS) – a modeling requests automatically; and it provides the option
language for domain models and service defini- of using open source libraries to create these ser-
tions. Both support creating services that work vices.10 Services and applications for ABAP Cloud
together especially well in conjunction with UI are developed and run in SAP BTP, ABAP environ-
frameworks such as SAPUI5 and SAP Fiori user ment. Here, ingredients for the development of
experience elements to create enterprise-grade applications, services, and integrations are
applications in a short amount of time. included and part of the SAP standard: SAP
HANA Cloud, model-driven development using
the ABAP RESTful application programming
model, technical services, and libraries such as
jobs, logs, printing, and XLSX processing.
10. Find more details on development on SAP BTP.

Encouraging innovation: By enabling side-by-side extensibility, SAP BTP encour-

ages innovation without disrupting the core SAP S/4HANA suite. Developers can
experiment with new features and applications on SAP BTP. Creating extensions, there
is a choice of a supported set of programming languages such as ABAP Cloud, JavaS-
cript, Java, or even Python (for instance, for AI use cases).
Open source libraries can be used within the extensions as well.

Reducing the total cost of ownership:

By using SAP BTP for side-by-side exten-
sions, the total cost of ownership can poten-
tially be reduced. This is because extensions
developed on SAP BTP are clean core com-
pliant and loosely coupled from SAP
S/4HANA. This will not interfere with upgrades,
thereby reducing the effort required for testing
and maintenance.

Supporting the transition to a clean core:

By providing a platform for side-by-side extensi-
bility, SAP BTP supports the transition toward a
clean core for the previously mentioned scenarios
and use cases. While extending side-by-side, the SAP
S/4HANA suite is kept unchanged, resulting in the clean core ben-
efits summarized earlier.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 13 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

The best of both worlds: on-stack and side-by-side extensions

Both on-stack and side-by-side extension options complement each other by providing a comprehensive
ecosystem for building, extending, and running enterprise applications. SAP BTP serves as an underlying
platform for cloud services and integration for extensions based on ABAP Cloud, CAP, and low-code/no-
code technologies coming with respective integrated development environments. In some scenarios,
pieces from all of these worlds might be needed. The following are a few examples.

Hybrid deployment Hybrid development Integration and

capabilities: practices: connectivity:

Extensibility for SAP S/4HANA SAP BTP promotes modern devel- SAP BTP provides robust inte-
often involves a hybrid deploy- opment practices such as gration capabilities for connect-
ment model, where some com- microservices architecture and ing SAP S/4HANA with other SAP
ponents remain on premise DevOps methodologies. Both and third-party systems. ABAP
while others are hosted in the CAP and ABAP Cloud align with Cloud integrates with SAP BTP’s
cloud. SAP BTP supports this these practices by offering cloud- integration
hybrid approach, allowing orga- native development capabilities services, enabling developers to
nizations to deploy extensions for Java, JavaScript, and ABAP orchestrate complex integration
in a manner that best suits their developers. On the ABAP side, scenarios involving extensions
needs. Both CAP and ABAP this synergy allows developers to and other cloud services based
Cloud facilitate cloud-based adopt modern development par- on ABAP. This integration helps
development and extension adigms while leveraging their ensure smooth data exchange
while integrating with on-premise existing ABAP skills, thereby and interoperability across the
SAP S/4HANA software, helping accelerating the extension pro- landscape.
to ensure a cohesive and inte- cess for SAP S/4HANA. Fusion
grated landscape. As described team development (as explained To summarize, both on-
previously, ABAP Cloud on top in the following chapter), might stack and side-by-side
gives the option of developer require developers of different technologies (and those
extensibility for tightly coupled skills to jointly develop an enter- available in both environ-
extension scenarios. prise application. The service ments) complement each
built for this might benefit from a other effectively in the
tight coupling to the core of SAP transformation journey to
S/4HANA, therefore, built using SAP S/4HANA. Together,
Tier 1 extension options on they empower organiza-
stack (that is, the ABAP develop- tions to extend and cus-
ment environment). Another tomize SAP S/4HANA effi-
developer might create a mobile ciently, adopting modern
UI based on that service with SAP ways of working and
Fiori tools in SAP Build Code – accommodating prefer-
maybe even making use of the ences, thereby meeting
available generative AI capabili- evolving business require-
ties enhancing productivity. The ments and driving digital
resulting full-stack application innovation.
will be hosted partly on stack
and partly side by side.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 14 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

The role and benefits of SAP BTP in the SAP BTP is an innovation layer next to a
context of SAP S/4HANA Cloud stable clean core and provides superior
benefits:
SAP BTP plays an essential role in the strategy for
SAP cloud ERP solutions. SAP S/4HANA Cloud and _ I t is deeply integrated and interwoven with
SAP BTP are inseparable, as SAP is developing your core ERP and understands and shares
major parts of its innovations as modular apps on the underlying meta and business model.
SAP BTP, such as SAP Green Ledger, SAP Digital
Manufacturing, SAP Advanced Financial Closing, _ S
 AP S/4HANA uses services for SAP BTP (for
sustainability management, and next-generation example, SAP HANA service for SAP BTP, SAP
industry solutions. SAP is following this strategy to Integration Suite, SAP Datasphere solution,
strengthen its clean core strategy: SAP AI Core infrastructure, and ABAP Cloud).

_ T
 he core holds the essential business pro- _ D
 eep integration – An extension wizard can
cesses that companies need, regardless of start directly from SAP S/4HANA, which allows
the industry they operate in (core processes). you to navigate to tools for extension creation
on SAP BTP (see Chapter 4) or to the service
_ D
 ifferentiating processes (edge, industry, center where we show APIs and business
innovative, next-generation, and more) are application programming interfaces, along
moved as modular apps toward SAP BTP, with remote function calls, as such.
establishing modular cloud ERP.
_ A
 BAP Cloud and CAP – Hyperscalers don’t
offer programming models that help create
Customers and partners should follow the business applications with that much built-
same strategy and establish two-layer IT: in functionality.

_ L
 ayer 1: A stable clean core holding essential _ S
 AP Business Accelerator Hub provides a vast
core processes that keep the business up amount of built-in, up-to-date content for our
and running, automating processes to lower applications, such as integrations, connectors,
the bottom line APIs, localization, and so on.

_ L
 ayer 2: An innovation layer with fast innova- _ A
 s mentioned in more detail in Chapter 4,
tions, flexibility, modularity, and nondisrup- Joule, SAP’s AI copilot, offers support spe-
tiveness to the core – providing processes cialized in SAP software–oriented develop-
that differentiate from competitors and give ment (both for ABAP Cloud and CAP).
competitive advantage, increasing the top line
(examples include sales-order automation,
just-in-time production, and customer loyalty)

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 15 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

3.3 The public cloud extensibility model

The previous paragraphs described different extension patterns and ways to approach these for both
on-stack and side-by-side extensibility. Now, let’s inspect how this is realized for SAP S/4HANA Cloud
Public Edition.

On-stack key user extensibility local APIs from SAP, such as CDS views, inter-
faces, business objects, and the like. Developers
This extensibility technique provides key users use ABAP development tools for Eclipse in their
(business experts) with the ability to do low- development projects and can make use of full-
code/no-code extensions directly on stack fledged development capabilities including
running on SAP S/4HANA Cloud Public Edition. profiling, debugging, and code checks. By using
To develop these extensions, key users can either only released public APIs, extensions developed
use dedicated SAP Fiori apps or make changes with ABAP Cloud are upgrade stable and have a
directly inside existing SAP business applications. clean core by default. The list of released APIs
can be found in ABAP development tools but
Examples include: also on SAP Business Accelerator Hub and in the
cloudification repository on GitHub. Further infor-
_ C
 hanging labels and positions in existing mation is provided on SAP Community.
SAP business applications or adding custom
fields to them
Side-by-side extensibility on SAP BTP
_ I mplementing business logic extensions at
well-defined locations inside the SAP business Side-by-side extensions are developed on
objects SAP BTP and have a clean core by default.
Communication with SAP S/4HANA Cloud solu-
_ C
 reating custom business objects or analyti- tions is possible through released remote APIs
cal queries specific to the business (such as OData APIs) and events, which can be
department found on SAP Business Accelerator Hub. The
portfolio of services, tools, frameworks, and run-
times for SAP BTP offer a lot of flexibility and tar-
On-stack developer extensibility get different development and technology prefer-
ences and personas. Tools are available that
Developer extensibility offers professional, com- address both key users (business experts) and
prehensive development of extensions, applica- developers. As mentioned previously, side-by-
tions, and integrations using the ABAP Cloud side extensibility on SAP BTP can be based on
development model. These extensions run two development models – either ABAP Cloud
on the stack for SAP S/4HANA and can leverage or CAP.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 16 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

3.4 The private cloud extensibility model

The public cloud extensibility model described API enablement technique exists in the private
above is reused in SAP S/4HANA Cloud Private cloud, referred to as Tier 2. Furthermore, the private
Edition. It is cloud enabled and has a clean core cloud allows for brownfield implementations and
by default and is, therefore, the go-to extensibility conversion from SAP ERP Central Component
model for the private cloud including key user, to SAP S/4HANA Cloud Private Edition and,
developer, and side-by-side extensibility. In the therefore, allows the takeover of classic extensions
context of the private cloud, these extensions for ABAP. These will be collected in Tier 3. The
are called Tier 1 extensions. One of the key interplay of these extensibility tiers is called
principles of Tier 1 extensions is the usage of the 3-tier extensibility model, shown in Figure 2
released APIs. If such an API is missing, a cloud below and explained in the next subsections.

Figure 2: The 3-tier extensibility model for SAP S/4HANA

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 17 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

3.4.1. Tier 1 3.4.3. Tier 3

Tier 1 extensions are developed using ABAP Tier 3 contains classic extensions for ABAP.
Cloud for on-stack extensions and all capabilities Hence, existing classic code in ABAP brought
offered by SAP BTP (see Chapter 4). Thereby, they into SAP S/4HANA Cloud Private Edition, for
are strictly decoupled from the SAP code through instance, from the conversion from SAP ERP Cen-
released APIs, events, and extensions points. This tral Component, will reside in this tier. There is no
is the go-to extensibility tier for new extensions. “magic button” that allows the transformation of
all existing extensions for ABAP to Tier 1 and Tier 2.
Moreover, there are cases where extensions cannot
3.4.2. Tier 2 be developed in Tier 1 due to technical limitations
(such as extensions to SAP business applications
There are cases where the required public APIs based on the SAP GUI interface). Hence, we recom-
for Tier 1 extensions are missing. To unblock this mend starting the journey to reach a clean core
situation, Tier 2 provides an API enablement by following three steps:
mechanism to make use of classic APIs instead.
This can be the case either because the public 1  etire all unused custom code and remove
R
APIs come with a higher release, or it can also it from the system. Perform a fit-to-standard
occur in areas where SAP does not actively invest analysis11 to check which existing extension
in new APIs (for example, classic HCM). In these can be replaced by SAP standard
cases, SAP nominates existing classic APIs. functionalities.

 2 
If there is a business case to renovate an
extension (for example, to make it future
ready for the cloud, make use of new tech-
nologies or mobile apps, and so on), bring it
step by step toward Tier 1 and Tier 2.

3  or the rest, ensure minimum quality and

F
upgrade stability by following best practices
to adapt your code. To do this, leverage
ABAP test cockpit and classic APIs.

For details and more information, please see the

extensibility guide for ABAP.

3.4.4. Recommendations for partners

Partners should follow the same recommenda-

tions for their partner solutions and add-ons as
customers, so the above guidelines also hold for
partners. Partner solutions and add-ons should
not break the clean core strategy of customers.
To this end, a clean core certification for partners
has been created. Customers can find certified
partner solutions for a clean core in the SAP Cer-
11. F
 or more information, see this premium engagement session on intelligent
custom code management or this support page on fit-to-standard workshops. tified Solutions Directory mobile app.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 18 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

3.5 Launching a clean-core certification program

for partner applications

SAP Integration and Certification Center (SAP ICC), When starting with SAP S/4HANA Cloud
part of the Partner Innovation Lifecycle Services in a greenfield approach, that is, without
group, announces the launch of a certification pro- an existing structure or processes, we rec-
gram for partner applications following the clean ommend you follow the previously men-
core criteria, with which it is possible to prove tioned guidelines and recommendations.
clean core compatibility to customers. That means using Tier 1 extensibility
where possible, Tier 2 extensibility when
With the clean core approach, SAP wants to make no publicly released SAP APIs are avail-
sure that partner applications follow the strategy able, and Tier 3 extensibility for your
in both the development and delivery of partner existing classic extensions for ABAP or
solutions to SAP customers. In the optimal case, when using Tier 1 and Tier 2 is not possible.
this is enabled by using SAP recommended exten- For existing classic extensions for ABAP, fol-
sion options only, as described in the extensibility low the described steps for Tier 3 to reach a
model for SAP S/4HANA Cloud. The following clean core step by step.
partner apps that previously adhered to the 3-tier
model outlined in this document can earn the
clean core designation:

 dd-ons for ABAP Cloud (Tier 1 or Tier 2) built for

A
SAP S/4HANA Cloud Private Edition12
Side-by-side solutions running on SAP BTP
(Tier 1) and integrating with SAP S/4HANA Cloud
Private Edition. Technical feasibility will be
checked and confirmed through P ­ artner applica-
tion on SAP BTP Certification. Further technical
details regarding the certification program can be
found in this presentation.

12. The certification scenario is generally available, and if you want to receive more details, please contact us at [email protected].

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 19 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

3.6 APIs, events, and extension points

Publicly released APIs, events, and extension On the SAP Road Map Explorer Web site, it is
points are the foundation for clean core extensi- possible to choose a certain product (for
bility both on stack and side by side, since they instance, SAP S/4HANA Cloud Public Edition) and
allow decoupling from SAP code. They can be select the focus topic filter Integration to learn
found on SAP Business Accelerator Hub. Custom- about upcoming APIs.
ers and partners can request new APIs, events,
and extension points through Customer Influence Now that the strategy and the reasoning behind
program channels as shown below. the clean core has been laid out, the following
chapter describes how to develop extensions
SAP S/4HANA Cloud Public Edition: achieving and keeping a clean core, that is, which
services support extension development accord-
ʯ  AP S/4HANA Cloud and SAP S/4HANA for
S ing to the clean core strategy and how best to
Integration leverage the benefits of the SAP Cloud Applica-
tion Programming Model and the ABAP RESTful
ʯ  AP S/4HANA Cloud and SAP S/4HANA for
S application programming model for both on-stack
Key User and Developer Extensibility and side-by-side extensions.

SAP S/4HANA Cloud Private Edition:

ʯ  AP S/4HANA Cloud Private Edition for

S
Extensibility and Integration (APIs)

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 20 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

4 Extend SAP S/4HANA with SAP Build

The go-to place following SAP-recommended best practices to create extensions optimized for SAP
software development is SAP Build. SAP Build includes powerful low-code, pro-code (ABAP, Java, JavaS-
cript), and generative AI capabilities, and enhanced interoperability with SAP S/4HANA to empower
developers and business experts to create extensions for SAP software with greater efficiency. It allows
customers to accelerate ERP modernization, foster innovation, and automate processes – all within a
single comprehensive suite of solutions.

Streamline extension of SAP S/4HANA Accelerate extension of SAP S/4HANA

with AI capabilities enabled by Joule
Through application development and process
automation with SAP Build, the previously described New levels of ERP efficiency can be unlocked
programming models CAP and ABAP Cloud can be with the latest AI capabilities enabled by Joule
leveraged, being aligned with clean core principles in SAP Build. Joule is SAP’s AI copilot offering
to create scalable, secure, and stable extensions. conversational interactions in the respective
business context. Uniquely trained on SAP data
and processes, it helps developers write code
and design workflows for SAP S/4HANA across
ABAP, Java, JavaScript, and low-code tools. As
an integral part of SAP Build, Joule is the copilot
for SAP development and makes developers
more efficient with their development tasks for
SAP S/4HANA.

Joule generates high-quality code and code

explanations aligned with SAP’s programming
models, thereby reducing development time
for both new and experienced developers and
accelerating migration to cloud ERP with a
clean core.

AI capabilities enabled by Joule can also be used

to extend ERP through low-code application
development. Joule assists with process auto-
mation, expediting the creation of workflows for
SAP S/4HANA and guiding workflow approvers
with automated recommendations.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 21 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

Fusion team development

SAP Build offers diverse, multiskilled teams with of the extension, the respective development
professional developers and business experts environment can be launched as, for instance, in
what they need to create enterprise extensions a complete application development pro-code
fostering collaboration, asset sharing, and seam- scenario, ABAP development tools for an on-
less technology bridges with built-in governance stack-extension or SAP Build Code development
and lifecycle management (see Figure 3). tools, or ABAP development tools for a side-by-
The lobby for SAP Build is the central place and side extension. The lobby provides many conve-
the starting point to begin an extension project nient features, such as monitoring capabilities and
with SAP Build – be it for side-by-side extension access to prebuilt content to supercharge devel-
development on SAP BTP or for on-stack exten- oper productivity.
sion development. Depending on the use case

Figure 3: SAP Build – what it comprises, how it can be used, and which solutions can benefit from it

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 22 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

5 Getting started
Your path to a clean core – as a step-by-step – whether in a greenfield or brownfield approach.
guide on how to get and stay clean – is similar for RISE with SAP Methodology embeds these into
both greenfield and brownfield implementations. the customer journey (greenfield or brownfield)
Whereas for greenfield the main task is to design through relevant tasks across project phases, in
a system utilizing as much standard functionality the form of a standardized framework, gover-
as possible and implement governance to keep nance, guidance, and use of a tool chain. Quality
this system clean (all steps except step 3 on the gates, as well as reports with recommendations
following page), a brownfield implementation – in and actions, help you stay on track during your
addition – entails a transformation journey that transformation journey, adhering to clean core
strives to make existing custom code clean (all principles. Whether through SAP-led or partner-
steps including step 3 on the next page). SAP rec- led engagements, you can get a clear path with
ommends anchoring the clean core principles in specific implementation stages and success
an organization’s IT strategy and follow clean core parameters to be able to take advantage of
guidelines as mandatory for new extensions speed, agility, and the benefits of the cloud.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 23 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

The six-step path to a clean core is as follows:

1
Start with the clean core concept and definition: This document is a perfect place to
start, as it provides explanations and recommendations, with links to learn more about and
understand the concept. Please refer to this document and to the SAP Learning Journey
“Applying the RISE with SAP Methodology” to help understand how you would apply these
concepts in your transformation journey in a tangible way.

2
Apply the concept and create your specific clean core strategy: The clean core con-
cept needs to be applied to the specific requirements of each customer and should be
reflected in all aspects of your IT strategy. This presentation provides further details to sup-
port this.

3
Analyze existing custom code (brownfield only): As discussed in Chapter 3, existing cus-
tom code needs to be analyzed. You should prioritize what to touch first, retire unused
objects, and create a list of objects to be redesigned or replatformed. Further tools to
help with this are described in this blog post and this overview.

4
Adopt extension guidelines and methodologies: Conduct a fit-gap analysis resulting
in a gap list. Ensure fit to standard, including validating gaps against future product road maps,
and design clean extensions following the SAP Application Extension Methodology and SAP Inte-
gration Solution Advisory Methodology according to the previously described guidelines. 13

5
Build extensions: Follow the 3-tier model described in Chapter 3 and use the services
described in Chapter 4 to develop on stack or side by side, keeping the core clean.

6
Establish clean core governance and operations: As mentioned previously, document
your technical debt, establish clean core governance, and embed your undertakings in your
business transformation journey..14 Clean core governance is key to success. Every deviation
from clean core principles (or your specific clean core strategy) should go through a gov-
ernance board that has to approve and document every exception. Clean core baselines
such as KPIs and thresholds should also be in place, as should periodic monitoring using
technical governance tools, such as mandatory checks from the ABAP test cockpit. The goal
is to minimize the number of business modifications and unclean and unused custom code
and maximize the share of code that is clean core compliant.

13. Find more information: Extensibility guide for ABAP, fit-to-standard analysis for SAP Signavio solutions, SAP BTP Guidance Framework, SAP Extensibility Explorer tool

14. SAP LeanIX solutions and the SAP Cloud ALM solution can help with this.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 24 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

6 Summary
Striving for a clean core comes with many bene- tomer needs during this transformation journey.
fits. However, it certainly poses several chal- We understand your requirements during your
lenges. We continue to try to solve these chal- transformation into the cloud, and our extensibil-
lenges. We do so by providing a rich extensibility ity offering will continue to improve to mirror this
offering for both SAP S/4HANA Cloud Public Edi- in the future. Be sure to stay up to date by check-
tion and SAP S/4HANA Cloud Private Edition, con- ing our packed road maps for future innovations
sidering each of their different backgrounds and to improve the clean core extensibility model for
requirements. We certainly take into account cus- SAP S/4HANA Cloud even further.

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 25 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

7 Appendix
Below is a list of relevant links that can support you on your journey toward a clean core.

Links Descriptions

Extension use case patterns Provides help to determine which part of the extension runs
on SAP S/4HANA as an on-stack extension and which part runs
on SAP BTP as a side-by-side extension

SAP Application Extension Describes a structured, technology-agnostic approach for cus-

Methodology tomers and partners to define an organization-specific extension
strategy

SAP BTP Developer’s Guide Helps to implement business applications on SAP BTP

SAP BTP Guidance Framework Provides a central access point for architects, developers, and
administrators to build and run enterprise-grade solutions on SAP
BTP

SAP Business Accelerator Hub Offers what customers need to accelerate integrations, exten-
sions, and innovations (APIs, events, CDS views, prebuilt auto-
mation content, and more)

Clean core on SAP.com Gives an overview of the ERP clean core strategy

RISE with SAP Methodology Represents a comprehensive framework designed to drive digital
transformation and intelligent operations within organizations,
leveraging advanced tools and strategies to streamline processes,
enhance efficiency, and accelerate innovation

From Classic ABAP to ABAP Gives an overview of implementation and certification for add-
Cloud and clean core ons for ABAP Cloud for SAP partners

Extend SAP S/4HANA in the Provides an overview on the extensibility options for ABAP-
cloud and on premise with based extensions on SAP S/4HANA in the cloud and on premise,
ABAP-based extensions along with guidelines for project managers, key users, and ABAP
developers

SAP Discovery Center Lets you explore missions, reference architectures, and services
for SAP BTP

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 26 | 27
SAP S/4HANA Cloud | Clean Core Extensibility

Links Descriptions

Extension architecture guide Shows how you can use the guide to determine which SAP tech-
nology should be applied in a given scenario

SAP BTP Developer’s Guide Shows how you can use the guide to improve the process of
implementing a business application on SAP BTP

ABAP Cloud Details a development model for ABAP to build cloud-ready busi-
ness apps, services, and extensions

SAP Cloud Application Helps you build cloud-native applications with maximized produc-
Programming Model tivity at minimized costs, based on proven best practices

Tutorials for SAP Build Apps Provides tutorials for SAP Build Apps

Tutorials for SAP Build Process Provides tutorials for SAP Build Process Automation
Automation

Tutorials for SAP Build Work Provides tutorials for SAP Build Work Zone
Zone

SAP Build Code Demo Showcases SAP Build Code development tools: AI code genera-
tion with Joule copilot, built on SAP BTP, that is optimized for
Java and JavaScript development; delivering a turnkey environ-
ment for coding, testing, integrations, and application lifecycle
management.

Watch the video to get an overview of SAP Build Code.

SAP BTP, ABAP environment on Informs about a platform-as-a-service offering that enables devel-
SAP Community opers to use their traditional on-premise knowledge of ABAP to
develop and run applications on SAP BTP

Hitachi High-Tech customer Shows how Hitachi High-Tech mastered side-by-side develop-
story ment techniques to innovate in a more agile and future-ready
way

SAP Innovation Awards 2024 Gives information about RISE with SAP and the clean core jour-
– Accenture ney of Accenture

© 2025 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material. 27 | 27