Clean Core Overview

Vivien Boche, Senior Director

PUBLIC
What we cover…

• What is the clean core?

• What are the benefits?
• How to get to a clean core?
• Myth and Facts
• Information on where to get started

© 2024 SAP SE or an SAP affiliate company. All rights reserved.. 2

How often do you upgrade your ERP system per year?

Show with your hands …

1x per year 2x per year Let’s not talk

about it ...
How familiar are you with what Clean Core is?

Show with your hands …

Adapted
Heard about it Fully Clean
some areas
What I often year

“BTP is the only means of

making and keeping the core
clean”
“Clean Core is only about
Custom Code and Extensibility.”
“Fit-to-standard is the only
means of making and keeping
the core clean”
“Clean Core is only about TCO”

5
 modern approaches to design:

What is
clean
core?

PUBLIC 7
 Keep the
extensions clean 1 Extensibility

Keep the
data clean 2 Data

Keep the
integrations clean 3 Integrations

Keep the
processes clean 4 Processes

Keep the operations

effective and efficient 5 Operations

PUBLIC 8
 What is
clean
core?

CLEAN CORE
Clean means up-to-date, The core describes the main aspects of an ERP
transparent, unmodified, system landscape, namely extensibility,
consistent, efficient, and cloud processes, data, integration, and operation.
compliant. Capabilities of the core depend on the
implemented software stack.

PUBLIC 9
 SAP BTP
Unleash digital innovation
across business functions

Create personalized experiences Build faster with business context Run with confidence on a trusted,
that instantly work with SAP applications to meet change with agility enterprise-grade platform

App Dev Automation Integration Data and Analytics AI

Build and innovate Optimize and automate Connect and simplify Give data purpose Infuse intelligence

PUBLIC 10
 “A new public cloud system is clean
per the definition.”

PUBLIC
 1. Agility and flexibility

2. The ability to leverage the

Benefits latest innovations (stay
current)
of clean
core 3. Efficient and more secure
operations

4. Data to value

PUBLIC 12
 Following a clean core strategy means:

• Reducing data and process inconsistencies

• Establishing suitable housekeeping processes and

governance structures
How to
clean • Maximizing the use of standard functionality and
core its ROI

• Building cloud-compliant extensions that are

integrated using stable interfaces

• Minimizing customization complexity

PUBLIC 13
 Keep the
extensions clean 1 Extensibility

Keep the
data clean 2 Data

Keep the
Integrations clean 3 Integrations

Keep the
processes clean 4 Processes

Keep the operations

effective and efficient 5 Operations

PUBLIC 14
 Keep the extensions clean

Keep the
extensions clean 1 Extensibility

Main Aspects:
Keep the
Extensions should be avoided when data clean 2 Data
possible
Create cloud compliant Extensions, Keep the
Integrations clean 3 Integrations
Custom extensions do not break an
upgrade and upgrades do not break an
extension Keep the
processes clean 4 Processes
Leverage 1: on the stack & 2. side-by-side
with SAP BTP
Keep the operations
effective and efficient 5 Operations

PUBLIC 15
 What makes
extensions clean core How to achieve
• Establish a governance model – a clearly defined process with high demands to approve any

compliant? extension.
– Prefer standard over custom development by leveraging fit-to-standard best practices.
– Avoid custom code where possible. Don’t extend for rarely needed use cases.
What is a “good” extension? – Prefer “clean” extension options over “unclean” ones.
Main aspects – Use SAP Application Extension Methodology and extensibility guidance to identify the best
path in your landscape.
• Avoid extensions when possible
• Set up a strong governance to create • If you need to extend, a clear separation is key.
decoupled extensions in a way that they – Only access standard objects through released and stable APIs (either remote or locally;
would work in the cloud (three-tier access for reading and changing access possible).
model) – Choose only “clean” tools or environments and extensibility options (in SAP S/4HANA: key
user, developer, or side-by-side extensions).
• Separate extensions by leveraging
released APIs – custom extensions do • Choose extension domain based on requirements only.
not break an upgrade and upgrades do – SAP BTP automatically decouples extension but is not the only “clean” approach.
not break an extension* – Do not extend in the core simply because “we always do so.”
• Leverage the full capabilities of
extensibility on the stack as well as side • Enable awareness.
– In on-premise installations, you can actively decide to develop some extensions not clean
by side with
core, as long as they are documented and informed decisions (use cases: copy routines; API
SAP BTP not available, and more).
• Create technical debts only as – Mitigate missing APIs in private cloud or on premise by using wrappers as described in
informed decision ABAP Cloud API Enablement Guidelines for SAP S/4HANA Cloud, private edition, and
SAP S/4HANA.
*Ensuring upgrade stability can be a short-term workaround for – Create requests for APIs using a customer influence tool (for public or private cloud
transforming a whole application from traditionally developed code into
cloud-compliant (Tier 1) extensions. editions).

PUBLIC 16
 Extensibility Options in S/4HANA
App Dev – Why and how to achieve a Clean Core?
• InApp = In-App Extensibility
• DE = Developer Extensibility

On Premise S/4 Transformation Clean Core with Platform

EC

S/

S/
InApp-2

1 2 2

4
C

4
3 4
DE-5
5 5

6 7 6
BT
P

Custom Process Standard Process

Custom Process on BTP

Extensibility Options

In-App Extensibility Developer Extensibility Side-by-Side Extensibility

1 S/4HANA 2 S/4HANA 3 SAP BTP

© SAP SE OR AN SAP AFFILIATE COMPANY. ALL RIGHTS RESERVED. | CONFIDENTIAL 17

 Clean Core Extensibility Options for SAP S/4HANA
Core Solution Extensions Side-by-Side Extensions
Low Code

SAP S/4HANA
Cloud SAP Build
Key User Tools

SAP S/4HANA Cloud “clean”

SAP BTP
“clean” Seamless
On-Stack integration Side-by-Side
Extensibility Extensibility
SAP S/4HANA SAP Build
Cloud ABAP Code
Pro Code

Environment

Classic BTP ABAP

“clean” Extensibility 1 “clean”
Environment

“unclean”
“clean”

INTERNAL – SAP and Partners Only 1 SAP S/4HANA Cloud Private Edition and on premise only; not “clean core” 18
When to use use which tool?
Extensibility Options Today
In-App Extensions Cloud Extensions

Adopt new Refresh & mobilize

user interface user experience

Create custom Cloud native for

analytics B2C & B2B

Secured Process
Expose data SAP S/4HANA SAP BTP innovation
connectivity
Cloud User Interface
On-Stack Rules / Workflow Side-by-side
Data marts &
Create forms / Extensibility Process / Events extensibility analytics
email templates
Data Replication

Add Data science &

application intelligence
logic

Add database IoT & big data

fields / objects

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | PUBLIC 1 as part of product roadmap | may be changed by SAP at any time without prior notice 2 SAP S/4HANA on premise only 20
When to use use which tool?

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | PUBLIC 21

What if no API is available?
3-tier extensibility model for SAP S/4HANA
private cloud and on-premise
SAP S/4HANA SAP Business Technology Platform TIER 1 – Cloud extensibility model
Development of cloud-ready and upgrade-stable applications
TIER 1 ON-STACK and extensions
TIER 1 SIDE-BY-SIDE
ABAP Cloud development Cloud development Same development model as used in SAP S/4HANA Cloud,
Key user extensibility (All runtimes – Java / Node.js / ABAP) public edition
Default for new extensions and custom apps

TIER 2
Cloud API enablement
TIER 2 – Cloud API enablement
RENOVATE OR
Extends and enables tier 1 for private cloud and on-premise
INNOVATE Mitigates missing public SAP APIs or extension points:
• Develop custom wrapper objects for not released SAP
objects to be used in tier 1
• Retire wrapper once a released SAP API is available

TIER 3
Classical ABAP development TIER 3 – Classic ABAP extensions
Legacy/existing custom ABAP code or new on-stack extensions
RETIRE code that cannot follow the rules of tier 1 and 2
Avoid and reduce the content in tier 3
ADAPT

ON-STACK - tightly coupled SIDE-BY-SIDE - loosely coupled

INTERNAL – SAP and Partners Only 24

 Local APIs – Current Status and Future Direction
Available APIs

§ Success of all Extension Projects depends

on a rich set of local APIs 4130 + 101 + 6975
Read APIs Write APIs Other artefacts

Upcoming New APIs

§ SAP continuously delivers § Customers can request APIs

new local APIs with high via dedicated Customer
priority Influence Session
Additional § Shipment of API via Continuous
Local APIs Feature Delivery (CFD) or with
next Release

INTERNAL – SAP and Partners Only 25

Key User Extensibility

PUBLIC
 In-App Extensibility
(Key user)

UI Adaptation Mode – Adaptation mode with Custom Fields SAP Fiori App Custom Business Logic SAP Fiori App
drag & drop configuration

Custom Business Objects SAP Fiori App Custom CDS Views SAP Fiori App Custom Analytical Queries SAP Fiori App

© 2022 SAP SE or an SAP affiliate company. All rights reserved. | PUBLIC 27

Application development and automation on SAP BTP
Integrated solutions enabled by generative AI

LOW-CODE PRO-CODE

ABAP
SAP Build SAP Build Code
Environment

Drag-and-drop simplicity Optimized for Java and JavaScript apps Optimized for ABAP apps

Generative AI-powered developer productivity

SAP Integration Suite SAP Datasphere

Enterprise Resource Customer Relationship Human Capital

Spend Management Business Network
Management Management Management

© 2023 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 SAP Materials for general audiences.
SAP Build

SAP Build enables everyone no matter their skill level to create and augment
enterprise applications, process automations and business sites
with drag-and-drop simplicity.

SAP Build Apps SAP Build Process Automation SAP Build Work Zone

Build visually
Integrate seamlessly
Collaborate in fusion teams
Public 29
SAP Build Apps
Build full-stack enterprise-apps in minutes - absolutely zero coding required

Drag-and-drop the user interface

Access a pallet of user interface
controls, drag them into place, and
preview the final result in real time.

Create any logic without code

Drag-and-drop any logic function –
sensors, file operations, data
functions, animations, and more –
onto a canvas.

Easily integrate data

Easily add your own data integrations
or get started with some of ours.

Public 30
 Pif Paf Alimentos
A mobile application
for maintenance
technicians using
SAP Build Apps

© 2024 SAP SE or an SAP affiliate company. All rights reserved.. 31

 Pif Paf Alimentos
A mobile application
for maintenance
technicians using
SAP Build Apps

3 weeks 30% 10%

To go-live with a Reduction in time and cost Reduction in
mobile application of technician data entry paper waste
© 2024 SAP SE or an SAP affiliate company. All rights reserved.. 32
Pif Paf Alimentos
Architecture details

© 2024 SAP SE or an SAP affiliate company. All rights reserved.. 33

Automate visually
Simplify process and task automation

Automate processes and tasks with

drag-and-drop simplicity

Workflow management, robotic

process automation (RPA), and
embedded AI in a single solution

Leverage process expertise without

coding

SAP Build Process Automation

© 2024 SAP SE or an SAP affiliate company. All rights reserved.. 34

Build simpler and faster – Empower everyone to
build and personalize business sites visually

Build branded sites, pages and

workspaces without writing any code

Personalize sites and target content

to users based on profile information
(location, department, role)

Quickly add new users and

deploy business site updates

SAP Work Zone

Public 35
Application development and automation on SAP BTP
Integrated solutions enabled by generative AI

LOW-CODE PRO-CODE

ABAP
SAP Build SAP Build Code
Environment

Drag-and-drop simplicity Optimized for Java and JavaScript apps Optimized for ABAP apps

Generative AI-powered developer productivity

SAP Integration Suite SAP Datasphere

Enterprise Resource Customer Relationship Human Capital

Spend Management Business Network
Management Management Management

© 2023 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 SAP Materials for general audiences.
SAP BUILD CODE

PUBLIC
SAP Build Code

Public 38
SAP Build Code
Application development for all key extension use cases in SAP environments

Extend SAP Solutions Build Fiori web apps with Build and run
SAPUI5 and SAP Fiori elements mobile apps

Develop SAP HANA Build multi-tenant

Native applications SaaS applications

Public 39
SAP BTP,
ABAP Environment

PUBLIC
SAP S/4HANA, private cloud and on-premise editions
ABAP language version and public SAP APIs

ABAP cloud development in the private cloud and on-premise editions of SAP S/4HANA
§ Switch ABAP language version for development object or package
§ Inspect the “Release state” for used APIs and objects

Switch from classic ABAP extensibility (standard ABAP) to ABAP cloud (ABAP for cloud SAP released the CDS view for ABAP cloud development
development)

Public This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. 42
ABAP Cloud – IDE and API examples
Custom ABAP on
SAP S/4HANA Cloud
ABAP development tools in Eclipse
Cloud-optimized ABAP language
Proven ABAP transport management

Access to public SAP APIs ONLY

– otherwise, syntax error!
No access to old Dynpro APIs
No direct select on the MARA table
from SAP

Local APIs from SAP S/4HANA

SELECT products from
SAP S/4HANA tables using the public
I_Product CDS view

Public 43
SAP Application Extension Methodology

SAP Application Extension

Methodology

To access scan this code

or click the link on top

The SAP Application Extension

Methodology helps you to define,
document and execute an
enterprise extension strategy for
your organization.

Public 44
 Keep the
extensions clean 1 Extensibility

Keep the
data clean 2 Data

Keep the
Integrations clean 3 Integrations

Keep the
processes clean 4 Processes

Keep the operations

effective and efficient 5 Operations

PUBLIC 45
 Keep the data clean

Keep the
extensions clean 1 Extensibility

Main Aspects: Keep the

data clean 2 Data
Modern data requirements
Data volume Keep the
Integrations clean 3 Integrations
Outdated, unused or redundant
information
Keep the
processes clean 4 Processes
Personal master data

Keep the operations

effective and efficient 5 Operations

PUBLIC 46
 What makes data How to achieve
clean core compliant? For data quality:
• Analyze and define data quality measures for critical data objects. SAP
provides data quality measures for several standard data objects.
What is “clean” data? – If necessary, involve SAP or third-party vendors (such as CDQ) for getting
Benefits
further help and advice.
• Establish a “get clean” process. Reliable results when
– Define a tool-based, reusable data cleansing process (such as through using data in processes
Main aspects the and analytical
SAP Master Data Governance application [consolidation], SAP applications (data to
Data quality
Information Steward software, SAP Data Intelligence solution, quality value)
(Configuration, master, and transactional data)* services for SAP BTP, or other third-party tools) for deduplication,
• Accuracy • Timeliness generation of best records, and more. Business process
• Completeness • Validity • Establish a continuous “keep clean” process. efficiency to improve
• Consistency • Uniqueness stability and quality of
– Define a validation rule framework, approval process, and automated
business process steps
Data volume efficiency distribution framework to connected receiver systems for newly created,
changed, or deleted data records (such as using SAP Master Data Reduced TCO due to
(Master and transactional data) Governance or SAP Master Data Integration service).
• Optimized memory and disk consumption efficient data volume
– Define continuous data monitoring. management
• No outdated, unused, or redundant information • Adhere to SAP One Domain Model (universal language across SAP
• Data lifecycle management (creation, updates, systems) and SAP Data and Analytics Advisory Methodology. Improved data
end of life) exchangeability
For data volume efficiency (from creation until end of life): between different
Data privacy compliance • Enable efficient continuous analysis and monitoring of the database by solutions
• Storing and processing personal master data reducing outdated, unused, or redundant data.
only with justifiable purposes Lower risk of breaching
• Define archiving or deletion of data-tiering processes to improve efficiency
data privacy
of the database (for example, using the SAP Information Lifecycle protection regulations
Management component).
*Configuration data: General data that defines the organization‘s structure
and is of static nature (such as company code, plants, purchase organisations,
controlling area, or sales area); Master data: Consistent and uniform set of
For data privacy compliance:
identifiers and extended attributes that describe the core entities of the • Analyze data usage to clarify business purposes of collecting and
enterprise, such as customers, vendors, products and general ledger processing personal master data.
accounts; Transactional data: Information directly derived as a result of • Establish policies to govern personal master data lifecycle (using SAP
transactions, this data always has a time dimension, a numerical value, and
refers to one or more (master data) objects
Information Lifecycle Management).
PUBLIC 48
SAP Master Data Governance

Consolidation

Central governance

Data quality & process

Analytics

PUBLIC 49
SAP DATASPHERE

PUBLIC
SAP Datasphere is the foundation for a business data fabric architecture

Self-service data access | Virtual data products

Data discovery | Business content, data marketplace, recommendations

Orchestration | Data transformation and data ops

Processing and persistency | Warehousing, business semantics
(analytic/relational models), knowledge graph

Data governance | Metadata management, catalog, lineage, privacy, quality

Data ingestion | Data replication, data federation, real-time, application integration

PUBLIC 53
 Keep the
extensions clean 1 Extensibility

Keep the
data clean 2 Data

Keep the
Integrations clean 3 Integrations

Keep the
processes clean 4 Processes

Keep the operations

effective and efficient 5 Operations

PUBLIC 54
 Keep the integrations clean

Keep the
extensions clean 1 Extensibility

Main Aspects:
Keep the
Integrations: standard API’s data clean 2 Data

Loosely coupled integrations: Event-

Driven Design Keep the
Integrations clean 3 Integrations
Avoid traditional API’s (RFC and
IDoc)
Keep the
SAP Application Interface processes clean 4 Processes
Framework
Keep the operations
effective and efficient 5 Operations

PUBLIC 55
What makes
integrations clean
How to achieve
core compliant? • Establish a clearly defined integration strategy with SAP Integration Solution Advisory
Methodology:
What is “clean” integration? – The central access point to discover integration artifacts like standard APIs, events, and
integration flows is SAP Business Accelerator Hub.
Main aspects – If mediation is required, use SAP Integration Suite to benefit from the tight integration
• Base integrations on standard APIs with other SAP BTP capabilities.
(OData and SOAP)
• Define a one-time “get-clean” process:
• Aim for side-by-side extensibility with – Create an integration repository (included in SAP Solution Manager) to identify existing
API integration or even SAP Cloud SDK integrations and the technology or protocol on which they are based.
by utilizing the tight coupling with – Establish “get clean” service inside the company to evaluate how utilized traditional
SAP Integration Suite APIs (RFC and IDoc) as well as their classical extensions could be converted into
• Realize loosely coupled integrations in an standard interfaces (fit to standard).
event-driven design based on standard • Establish a continuous “keep clean” process (governance model):
events* – Define central governance functionality for evaluation of new interface requirements or
• Avoid traditional APIs (RFC and IDoc) and any interface adjustment based on defined SAP Integration Solution Advisory
their related classical extension options Methodology characteristics. The Integration Assessment capability could be used as
an accelerator.
• Ensure proper monitoring and error – Apply a “keep clean” process for the most important and critical integrations.
resolution capabilities using SAP
Application Interface Framework

*Event: A data record expressing a significant change in state (for example, change of a business partner) and consisting of data representing the occurrence and context metadata. It is sent to an event provider
such as the SAP Event Mesh capability, where consumers can subscribe to it. The business object data needs to be pulled by each consumer individually by using standard APIs.

PUBLIC 56
Connect the
disconnected

SAP Integration Suite

Connect apps & processes with
prebuilt tools & content across SAP
& non-SAP.

PUBLIC 57
SAP Integration Suite
SAP’s hybrid integration platform for the Intelligent Enterprise

Slack Salesforce
Workday ServiceNow
Splunk Kafka
Google
SAP Business Accelerator Hub Third- Azure AWS
Governments 3,400+ prebuilt integrations | 3,900+ APIs | 600+ business events |
250+ connectors to SAP and third-party cloud apps party And many more connectors . . .
apps
Capabilities within SAP Integration Suite
Integration Assessment
Define and govern your integration technology strategy
SAP Concur UN/EDIFACT
SAP Ariba Cloud Integration Open Connectors ASC X12 Odette
End-to-end process integration Accelerate connectivity to third-party applications
Odette EDIFACT
SAP Customer B2B
API Management | Graph Integration Advisor | VDA EDIFACT
Experience partners
SAP apps Expose your data as APIs, Trading Partner Management
manage the end-to-end lifecycle Manage B2B scenarios and AI-based integration
GS1 EANCOM
SAP S/4HANA
SAP Integration Suite, Migration Assessment cXML JAIF EDIFACT
SAP SuccessFactors advanced event mesh1 Migrate and elevate integrations from
Sense and respond to business events SAP Process Orchestration software to the cloud
SAP Fieldglass

1 Optional separate license | 2 Part of the road map, subject to change | 3 Private landscape corresponds to on premise or private cloud

PUBLIC 58
SAP Integration Suite
SAP’s hybrid integration platform for the Intelligent Enterprise

Slack Salesforce
Workday ServiceNow
Splunk Kafka
Google
SAP Business Accelerator Hub Third- Azure AWS
Governments 3,400+ prebuilt integrations | 3,900+ APIs | 600+ business events |
250+ connectors to SAP and third-party cloud apps party And many more connectors . . .
apps
Capabilities within SAP Integration Suite
Integration Assessment
Define and govern your integration technology strategy
SAP Concur UN/EDIFACT
SAP Ariba Cloud Integration Open Connectors ASC X12 Odette
End-to-end process integration Accelerate connectivity to third-party applications
Odette EDIFACT
SAP Customer B2B
API Management | Graph Integration Advisor | VDA EDIFACT
Experience partners
SAP apps Expose your data as APIs, Trading Partner Management
manage the end-to-end lifecycle Manage B2B scenarios and AI-based integration
GS1 EANCOM
SAP S/4HANA
SAP Integration Suite, Migration Assessment cXML JAIF EDIFACT
SAP SuccessFactors advanced event mesh1 Migrate and elevate integrations from
Sense and respond to business events SAP Process Orchestration software to the cloud
SAP Fieldglass

Microsoft Azure Google Cloud Platform Edge Integration Cell

Next-generation integration runtime for local integrations

Vendor-managed
AWS Alibaba Cloud Microsoft AKS Amazon EKS PostgreSQL, Private
multi-cloud offering landscape3
SUSE Rancher Red Hat OpenShift2 Redis

1 Optional separate license | 2 Part of the road map, subject to change | 3 Private landscape corresponds to on premise or private cloud

PUBLIC 59
PUBLIC 60
 Keep the
extensions clean 1 Extensibility

Keep the
data clean 2 Data

Keep the
Integrations clean 3 Integrations

Keep the
processes clean 4 Processes

Keep the operations

effective and efficient 5 Operations

PUBLIC 61
Keep competitiveness while reducing complexity

Keep the
extensions clean 1 Extensibility

Main aspects
Keep the
State-of-the-art process data clean 2 Data

governance
Keep the
Application architecture
Integrations clean 3 Integrations
SAP Best Practices packages
Keep the
Business process design
processes clean 4 Processes
Established process management
Keep the operations
effective and efficient 5 Operations

PUBLIC 62
 What makes business How to achieve

processes clean • Governance model and organizational structures:

– Proper requirement management includes a solution standardization board or a similar deciding structure, a
suitable methodology (for example, SAP Application Extension Methodology – see slide “Clean extensions”),
core compliant? and proper documentation and tooling support such as the SAP Cloud ALM solution or the Focus Build
solution for SAP Solution Manager.

What is a “clean” process? – A business process management structure is established and transparent across relevant organizations,
including process owners and related contact persons.

• The solution architecture can be based on the SAP Enterprise Architecture Framework methodology. Supporting
resources can be leveraged using the SAP Transformation Navigator tool, SAP Signavio Process Explorer
Main aspects solution, SAP Signavio Process Manager solution, SAP Signavio Process Collaboration Hub, and the partner
solution LeanIX.
• Establish state-of-the-art business
process governance, including proper • SAP Best Practices can, in general, be compared to SAP Signavio Process Explorer, the SAP Signavio Process
requirement management and transparent Navigator solution, SAP Signavio Process Manager, or SAP Signavio Process Collaboration Hub. Find more
organizational structures general guidance in the Administration Guide to Implementation of SAP S/4HANA with SAP Best Practices.
• Use recommended SAP Reference • For individual implementation projects, the SAP Activate innovation adoption process and the related road map
Solution Architecture to leverage SAP viewer can be leveraged. Further preconfiguration is provided through the enterprise management layer for SAP
solutions such as SAP S/4HANA and others S/4HANA. Industry-specific best practices can be requested through SAP standard content activation service.
• Implement respective SAP Best Practices • The solution design is focused on the following principles:
where available and applicable – For nondifferentiating processes, SAP standard is strictly applied; for differentiating processes, SAP standard
• Tailor or enhance standard solutions solutions are tailored to business needs and enhanced where needed.
from SAP only where competitive – A focus on mandatory and key process variants helps avoid unnecessary customizing and process complexity.
advantages can be created – For required extensions the recommendations for “clean extensions” are followed.
• Achieve business process management
• Business process management excellence covers the following three aspects:
excellence by documenting processes and – Customer-specific process design is documented (SAP Signavio Process Manager and SAP Signavio Process
continuously monitoring process flow as Collaboration Hub).
well as process performance and efficiency – As-is process execution can be measured (SAP Signavio Process Insights, SAP Signavio Process Intelligence,
and using the plug and gain approach).
– Business processes are efficiently executed based on measurable process performance indicators (SAP
Signavio Process Insights and SAP Signavio Process Intelligence).
PUBLIC 63
PUBLIC 64
SAP Signavio
Process Insights &
Process Intelligence

PUBLIC
SAP Signavio
Process Insights & Business Process
Process Intelligence
Management

Process Mining and

recommendations

Process best practices

PUBLIC
 Keep the
extensions clean 1 Extensibility

Keep the
data clean 2 Data

Keep the
Integrations clean 3 Integrations

Keep the
processes clean 4 Processes

Keep the operations

effective and efficient 5 Operations

PUBLIC 67
 Keep operations effective and efficient

Keep the
extensions clean 1 Extensibility

Main aspects
Keep the
End-to-end concept for operations. data clean 2 Data

Release management
Keep the
Housekeeping activities that are in line Integrations clean 3 Integrations
with SAP Best Practices
Keep the
processes clean 4 Processes

Keep the operations

effective and efficient 5 Operations

PUBLIC 68
 What makes
operations clean How to achieve
• Establish keeping the core clean as an integral part of the end-to-end operations concept:
core compliant? – Consider “keep clean” as an IT service to add business value and establish IT as a service
provider to own the end-to-end view and end-to-end processes.
What are “clean” operations? – Integrate monitoring and alerting of a “keep clean” process into the overall concept for
operations to have an integrated view on KPIs for affected areas that define a clean core
(integration, extensibility, processes, data).
Main aspects
– Establish procedures for event management and escalations that are in line with the
• The paradigm of keeping the core clean is established governance models for integration, extensibility, processes, and data. Consider
integrated into the end-to-end concept using SAP’s operations platforms to achieve this – SAP Cloud ALM or SAP Solution Manager.
for operations.
• Release management is based on two core principles:
• Release management is an established
– CMPs create preapproved monthly maintenance windows that are agreed by all involved
foundation for a clean core; the latest
parties and adequately documented.
release should always be targeted.
– Only in exceptional rare cases, it is requested to skip maintenance windows ("opt out").
• Housekeeping activities that are in line
with SAP Best Practices are pursued, and • Regular housekeeping is established and supports keeping the core clean, for example:
the distribution of roles and – Background job management (including approval, documentation, monitoring, and
responsibilities that are agreed with SAP improvement) is implemented to contribute to an efficient utilization of infrastructure.
are followed. – The usage of file interfaces for importing or exporting data from or into the system is avoided to
strengthen security, maintainability, and consistency.
• It is agreed that SAP performs
– End-user authorizations are reviewed and adapted on a regular basis. Unneeded authorizations
maintenance for technology within the
are unassigned from users and discontinued.
preapproved CMPs.

PUBLIC 69
 SAP Cloud Application Lifecycle Management

PUBLIC 70
 HITACHI

Leveraging SAP Business

Technology Platform to
accelerate move to the
cloud and keeping the
core clean

Watch the video

Read the Story

Reduced custom ERP add-ons Accelerated S/4HANA Cloud upgrade cycles

94% fewer 1 month

SAP ERP add-ons Time spent on upgrading
decreased from over 9,000 ERP versions cut from one
to 520 and a half years to approx. one month

PUBLIC 73
MYTHS & FACTS

74
 “BTP is the only means of
making and keeping the core
clean”
“Clean Core is only about
Custom Code and Extensibility.”

“Fit-to-standard is the only

means of making and keeping
the core clean”
“Clean Core is only about TCO”

PUBLIC 75
MYTHS & FACTS
“BTP is the only means of A Clean Core can be achieved
making and keeping the core by:
clean” 1. On-stack (key-user &
developer extensibility)
2. Side-by-side extensibility
(BTP)
3. Fitting processes to
standard or
4. A mix of all of the above

76
MYTHS & FACTS
“Clean Core is only about Clean Core affects:
Custom Code and Extensibility.” • Custom Code i.e.
Extensibility as well as
• Data,
• Processes,
• Integration and
• Operations

77
MYTHS & FACTS
“Clean Core is only about TCO” Clean Core not only
contributes to a TCO
reduction:
• It also enables the
consumption of the latest
innovations
• A mindset and paradigm
shift from OnPrem to Cloud
• Provides you with more
flexibility in your business
78
MYTHS & FACTS
“Fit-to-standard is the only • Although a fit-to-standard
means of making and keeping system is probably mostly
the core clean” clean
• the usage of “on-stack” and
”Side-by-side” extensibility
options also make and keep
the core clean.

79
How to
start from
here?

81
SAP BTP Guidance Framework

SAP BTP Guidance Framework

To access scan this code

or click the link on top

The SAP BTP Guidance

Framework provides a central
access point for architects,
developers and administrators to
build and run enterprise-grade
solutions on SAP BTP.
 Key SAP Services Offerings for Clean Core
Typical customer situations (1/2)

Typical Customer Situation Key Service Offerings … and in addition

Discovery Workshop for SAP S/4HANA Value and Implementation Strategy (VIS)
Customer wants to get a first Overview Sessions by E-CSPs
Follows customer’s business priorities to define the
1 understanding about Clean Core with On-site workshop provides guidance about the
benefits and transformation paths of adopting
target landscape and identify key innovations
to benefit most from SAP S/4HANA, including clean
External L0 / L1 Deck
SAP (1) SAP S/4HANA in a clean core compliant way core guidelines. Evaluates the best-fitting Definition Deck + Document
transformation path

IT strategy and enterprise architecture road map Migration and Upgrade Planning Workshop
service (MPW) Clean Core Assessment as part of
Customer would like to get a deep dive Supports planning the conversion to SAP S/4HANA Preferred Success
2 on Clean Core and to understand “what While defining our customer’s IT strategy &
enterprise architecture, this service provides
with a system-level transition roadmap and
milestone plan, clarifying the conversion Clean Core Business Scenario as part of
does Clean Core mean for me” (1) advisory on the clean core paradigm readiness and the functional and technical Max Attention (preparation for Move to
scope in compliance with clean core S/4HANA)

Application development planning service on

SAP BTP Capabilities Empowerment
SAP BTP
Customer would like to understand how
Supports the customer in upfront discovery and Supports an understanding of SAP Integration Suite Extensibility Strategy Workshop for Max
3 to start a journey with regard to “clean assessment of his SAP BTP development project, and SAP BTP extensibility capabilities to build
Attention Customers
including side-by-side extensibility in a clean state-of-the-art cloud applications in a clean
extensibility”? core compliant way core compliant manner

Cloud Service Development evaluation Intelligent Custom Code Management Analysis

Supports the analysis of existing custom code.

Customer would like to understand how Uses Design Thinking and user-centered tools & Intelligent Custom Code Management
4 to act on existing custom code?
methods to create a vision & scope document and
Custom code objects and references are clustered
and prioritized. Suitable follow-up activities are Transformation
come to a proposal for the customer how to
recommended to increase clean core compliant
leverage BTP for their custom code
extensions

(1)
for customers planning a journey to SAP S/4HANA. If the customer is already on SAP S/4HANA, start from situations 3-7.

Services available Professional Services customers

PUBLIC Services available only for Premium Engagement customers 83

 Key SAP Services Offerings for Clean Core
Typical customer situations (2/2)

Typical Customer Situation Key Service Offerings … and in addition

SAP Standard Content activation services Fit to Standard Analysis / Design

Customer wants to understand how he Accelerated process discovery service
F2S workshops validate the predefined content and
5 can stick to Clean Core from a business Pre-defined Industry and LoB content which can
be used in the context of fit-to-standard or fit/gap
identify delta requirements with advice on best with SAP Signavio and other SAP Signavio
processes perspective? analysis workshops
solutions considering SAP standard, SAP’s Services
latest technologies, and the clean core concept

Integration planning service Integration Design Workshop

Customer would like to understand how
Conducts comprehensive information analysis and Supports customers with best practices and industry
6 Clean Core affects the topic of workshops in order to create a customer-specific standards on how to design critical interfaces in Integration implementation service
implementation/upgrade plan for an optimal, clean core compliant manner, and
integration? SAP Integration Suite gives guidance on using SAP Integration Suite

Data Quality Service Data Management Design

Provides a detailed overview of how aspects of SAP Data Volume Management (PE: Scoping,
Customer would like to understand how Planning, PS: Optimization )
7 Clean Core affects the topic of data?
Assesses and improves the quality of data and
provides action plan for data management to
solutions for data management can be
implemented based on design principles of
get and keep data clean scalability & performance, transition to Financial Data Quality Analysis
operations, and SAP best practices

Services available Professional Services customers

Services available only for Premium Engagement customers

PUBLIC 84
 Custom code analysis with Custom Code Migration
app

SOLUTION OVERVIEW
Available in an SAP S/4HANA >=1809 system or in SAP BTP ABAP Environment
Technically based on remote ABAP test cockpit
Analysis of custom code for SAP S/4HANA, SAP BTP, ABAP Cloud, classic ATC use cases
Simplified custom code remediation
Obsolete custom code removal based on usage data
Identification of custom code candidates for back-to-standard and redesign
Evaluation of custom code for semi-automated adaptation
(quick fixes in ABAP development tools for Eclipse)

HIGH LEVEL FEATURES

SCOPING ANALYSIS

PUBLIC 85
 Self Service – Transparency - Clean Core Dashboard

Ver Ve
sio Lab rsion
Li v n 1 pre 2
e vie
w
ž A

§ Available for productive SAP S/4HANA Cloud, private edition systems in SAP for Me (Systems & Provisioning area)
§ Gives a technical overview on the “clean core compliance” of your SAP S/4HANA Cloud, private edition systems
§ Includes link to guides, services and tools (SAP and partner) that help to get closer to a clean core.

PUBLIC 86
Thank you

Vivien Boche
Senior Director – SAP Business Technology Platform
Vivien.boche@sap.com

Let’s connect