OpenSAP S4cpe1 ALL SLIDES Presentation

Gain Technical Knowledge on SAP S/4HANA Cloud, Private Edition
Unit 1: Introduction to the Course and Course

Overview
Introduction to the course and course overview
Question 1
“What are you going to learn

in this course?”
© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Course introduction | Overview

Unit 1
Unit 2
Responsibilities and communication
Unit 3
Preparing for your SAP S/4HANA Cloud, private edition project
Unit 4
Migration scenarios for moving an existing system into the cloud
Unit 5
Network and security considerations
Unit 6
Important tooling
Unit 7
What you need to know about SAP Fiori
Unit 8
Extensibility options
Unit 9
Downtime optimization considerations
Unit 10
Go-live preparation and running the system
1. Introduction to the course and course 6. Important tooling

overview
2. Responsibilities and communication 7. What you need to know about SAP Fiori
3. Preparing for your SAP S/4HANA 8. Extensibility options

Cloud, private edition project
4. Migration scenarios for moving an 9. Downtime optimization considerations

existing system into the cloud
5. Network and security considerations 10. Go-live preparation and running the system

Key takeaways
▪ You understand the course content

▪ Enjoy the course!

Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2022 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of
SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its
distributors contain proprietary software components of other software vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or
warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.
The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty
statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names
mentioned are the trademarks of their respective companies.
See www.sap.com/trademark for additional trademark information and notices.
Unit 2: Responsibilities and Communication
Question 1
What are the key roles in the

phases of a RISE with
SAP S/4HANA Cloud, private
edition engagement?

Key roles
Sales Phase Deployment Phase Operations Phase

▪ / Partner: Sales team ▪ / Partner: Cloud architect ▪ : Customer Engagement team
▪ / Partner: Cloud Architect ▪ : Project lead (service management)
▪ Partner/Customer: Technical expert ▪ Partner/Customer: Project manager ▪ Partner/Customer: Service
manager
▪ Customer: Business contact(s) ▪ ( / Partner: Transition expert)
▪ : Operations team
▪ : Customer Engagement team
(service management) ▪ Partner/Customer: Technical expert

Question 2
What is the overall governance

model in an SAP S/4HANA
Cloud, private edition
engagement and what is the
relation to the full RISE with
SAP bundle?

Governance overview – Setting the scene
Enterprise
Applications Further SAP Public
Cloud Solutions
SAP S/4HANA SAP Business
Cloud, Technology LBNAIN
Security private edition Platform
SAP Public Cloud –
Infrastructure and SAP Basis
Networks
Cloud Managed Services
Services
RISE with SAP S/4HANA Cloud, private edition – complete bundle
SAP Cloud
3rd Level Support/Product Support/Product Development SAP

Question 3
Who is responsible for which

task in an SAP S/4HANA Cloud,
private edition engagement?

Included and optional services
Application Infrastructure
Cloud Operations
Infrastructure Infrastructure Operation
Base Infrastructure Infrastructure | Network | Technical Basis Ops | OS & SAP HANA DB Ops
Basic Operations
Service Change
Database (SAP HANA) Security
Management Control
Infrastructure
Potential partner services or cloud application services (CAS)
Additional Technical Services Application Managed Services & Implementation
See also Cloud Services Specifications for S/4H PCE on SAP Agreements
Roles and Responsibilities document
The Roles and Responsibilities document

can be found on the SAP Agreements
website under Agreements/Cloud Service
Agreements. Standard Services
It is part of the contract between customer

and SAP, acts as a service catalog, Optional Services
describes the governance, and is non-

negotiable.
Additional Services
Cloud Application Services

(“CAS”). Can be performed by
customer.
Excluded Tasks

Demo
Understanding and handling the Roles and

Responsibilities document
Roles and Responsibilities on SAP Agreements

Question 4
What does the communication

flow look like?

Communication
Customer
Customer IT Interaction Leveraged global service
Integrated
+ Center delivery organization providing
Unified Support
Partner Services Framework 24x7 services with follow-the-
Support SAP
Teams sun operations
Point of contacts for SAP

▪ Level 1 support ongoing service and
Teams
▪ Tasks outside of support
SAP per R&R
▪ Optional services
SAP One Support Portal
▪ Creation of service Service Request Management
request or incident Incident Management
Security Patch Management

Question 5
What is the value of added

services and configurations
that can be done by the
customer, or bought as a
service from a partner or SAP
Cloud Application Services
team?

Additional or optional services and their value
Strategic
Task Run by Details
View
Transform Customer, Envision Business Transformation
Solution partner, or Enable Manage the Intelligent Enterprise
Plan Business Improvement / IT Operations Improvement
Improve Customer,
Solution partner, or Deployment Management / Application Change Management / Test
Change
Management
Release Version Management / Advanced Security and Compliance /
Customer, Proactive
Run Solution Managed Operations Control Center
Value
partner, or
Basic Reactive Application Management / Continuous Application Operations
Advanced Technical Operations / High Availability and Business
Proactive
and partially Continuity
Run Systems by partners
Basic Technical System Operations
(transition)
Commodity Technical Landscape Deployment / Technical Transitions
Run
Commodity Infrastructure Services
Infrastructure
Question 6
Is there anything else to

consider in case of a transition
(brownfield) project?

Transition to SAP S/4HANA Cloud, private edition
Source on-
premise
SAP Partner
▪ Executes all required preparation and
▪ Provides a target for the source data execution steps in the source system Source
activities
and guidance for the transfer
▪ Transfers the required files to SAP
S/4HANA Cloud, private edition target
▪ Provides an empty virtual server to be following the guidance shared by SAP
used for import activities – the
Transfer data
migration server
▪ Executes the necessary transition
steps on the migration server SAP S/4HANA
Cloud, private
▪ Starts up SAP application server in ▪ Informs SAP that the technical steps edition
SAP S/4HANA Cloud have been completed successfully

Import
▪ Executes post activities before
▪ Executes all the post transition steps
handover to customer, including
and activities in the target private cloud Post-
monitoring tools, backup schedule, and Processing
system
validation
Transition partner
Source on-
premise
The right transition partner must have knowledge on SAP S/4HANA Cloud,
private edition-specific tasks: Source
activities
▪ Differences compared to a transition done on-premise (with or without targeting a
different data center or Infrastructure as a Service cloud provider)
▪ Communication and handover points with SAP’s teams
▪ Using migration server and/or in certain cases migration assisted services
Transfer data
▪ Partner is fully responsible for the overall transition
SAP S/4HANA
An SAP partner can gain knowledge on SAP S/4HANA Cloud, private edition Cloud, private
edition
transition tasks either in the Sell or Service authorization on SAP Partner
Portal*, or by participating in the 10Steps2S4 to PCE* program (regional
Import
offering).
* Above links are only accessible to registered SAP partners Post-
Processing

Key takeaways
▪ Be aware of the key roles in an SAP S/4HANA Cloud,

private edition engagement
▪ In terms of roles and responsibilities, we are talking about
the private cloud part of the RISE with SAP S/4HANA
Cloud, private edition offering
▪ Get to know the Roles and Responsibilities document
– SAP takes care of technical operations (“keeps the
lights on”)
– Customers and partners can add services on top
▪ Main communication channel is SAP One Support Portal
▪ Make sure that an enabled partner is selected to perform
the transition project

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 3: Preparing for Your SAP S/4HANA Cloud,
Private Edition Project
Question 1
How are you planning to

transition to SAP S/4HANA?

Preparing for your SAP S/4HANA Cloud, private edition project Illustration
Transition paths to SAP S/4HANA
Greenfield Implementation
Current environment Private edition environment
Sandbox Development Quality Production

SAPThird
ERP
Party SAP S/4HANA SAP S/4HANA SAP S/4HANA SAP S/4HANA
Brownfield Implementation
Current environment Private edition environment
SAP S/4HANA Development Quality Production

SAP ERP Conversion &
migration SAP S/4HANA SAP S/4HANA SAP S/4HANA

SAP Readiness Check for SAP ERP usage and data profiling
Overview What functionality is used today in

my SAP ERP 6.0 system?
The tool assesses functional aspects of SAP
ERP 6.0 to deliver valuable profiles about the
key topic areas:
▪ Detailed Data Profile How much data would be required to
▪ SAP ERP Solution Usage Profile be migrated to a new SAP S/4HANA
implementation?
▪ Initial Data Migration Profile
▪ Organizational Structure Profile
What is the volume of data associated
▪ For detailed information about the setup and with a specific function that is active in
run of the analysis, including an FAQ section the existing SAP ERP solution?
and an overview of all data collectors, see How complex is the leveraged
SAP Note 3112362 data model within the existing
SAP ERP 6.0 implementation?
How can I identify, measure, and categorize the
transactional and master data in a productive
SAP ERP 6.0 system easily and with minimal
effort?
Demo
SAP Readiness Check for SAP ERP usage and

data profiling
▪ A few examples of how to check SAP ERP current
data and usage information

Question 2
What are the options to

accelerate the transition to
SAP S/4HANA?

Implementation accelerators | Greenfield implementation
Enterprise Management Layer SAP Best Practices
Note: This is a paid service provided by SAP.

Note: You will need to check the version for SAP S/4HANA
Blog: Enterprise Management Layer for SAP S/4HANA – FAQs (on-premise) and not the one for SAP S/4HANA Cloud.

Question 3
What needs to be considered

when using SAP Best
Practices content?

SAP Best Practices
▪ SAP Best Practices content for SAP S/4HANA Cloud, private

edition is the same content as for SAP S/4HANA (on-premise!)
▪ Test drive of SAP Best Practices content and understand the
available business processes.
− Using an SAP CAL (fully activated appliance) is an option.
▪ Import the content into the SAP S/4HANA system
− SAP Best Practices content only, in the Best Practices client.
− SAP Best Practices content merged with client 000 content.
▪ Implementing content after adding manual configuration or
having transactional data in the system setup is not possible.
− You would need to create a new client if you want to change
the initial SAP Best Practices content.
▪ You need to fill out the form to request best practices content.
For more details see SAP Note 3039705
▪ Only the first activation is included in the subscription.
Implementation options with SAP Best Practices
Legend
= System Status Use client copy Adjust
optional
Client with C- Adaptation of
Considerations
= Activity profile “SAP_Cust”
▪ Check if the
/G-tables filled
language from best
best practices
= Involved Role files to be practices content in
Reduced Copy
installed content IMG standard content
from Client 000
Create best
provides good
Client with SAP Note
SAP Best
practice strongly
reduced
2272406 coverage
client* Client with
Practices
content
(configuration
content of C-
/G-tables from Download
Activate best complete ▪ Evaluate how much
by table client 000 most content of C- “Merged"
provides yes recent best
practices /G-tables from
customizing additional
/FTI/T_NOCLN content client 000,
good practices adapted by project in IMG configuration might
000) (/n/SMB/BBI)
coverage content best practices
regarding no Full Copy from content be required
customer Client 000
requirements Client with "Classical" ▪ Check if a “sandbox”
Create complete
?
"classic" content of C-
customizing system might help or
/G-tables from project in IMG
client client 000 consider using an
SAP CAL system.
Application Consultant Technology Technology Consultant Application Consultant

(Customer and/or Partner) Consultant
(*) Further Details: http://help.sap.com/s4hana → SAP S/4HANA Edition … → Link "About administrating SAP S/4HANA solution implementation“ → PREREQUISITE
settings → Setting up a new best practice client

Question 4

when implementing add-ons /
3rd party solutions?

Add-ons and 3rd party solutions
▪ Solution Extensions (SAP branded partner solutions sold by SAP)

− Are generally allowed and managed by SAP (technical upgrade, subscription,
support).
− Relevant SAP Notes:
3029231 –
SAP S/4HANA Cloud, private edition: Partner Products compatible with S/4HANA 2020
3148843 –
SAP S/4HANA Cloud, private edition: Partner Products compatible with S/4HANA 2021
▪ Third Party Solutions (sold by a partner or independent software
vendor)
− Are generally allowed and managed by customer.
− SAP may execute technical tasks that are not accessible to the customer
(e.g. SAINT installation).
− Must not require the installation of any customer/partner/3rd party software
outside the ABAP stack
(e.g. shell-scripts, executables, agents, …) onto any servers managed by SAP.
− If a dedicated infrastructure is required, it may be delivered via an IaaS
subscription from SAP or a hyperscaler, or even on-premise.
Add-ons and 3rd party solutions
▪ Third Party Solutions Certification

− Although a certification issued by SAP Integration and
Certification Center is highly recommended, it is not
mandatory.
− Nevertheless SAP Cloud team may require additional
technical/architectural feasibility and security checks for
previously unknown third-party solutions before allowing their
use.
▪ Recommendation for customers/partners
− Execute a complete evaluation of necessary third-party
solutions (especially in brownfield scenarios).
− Check not only for ABAP add-ons but also agents, libraries, or
any 3rd party software.
− Share this information with SAP ideally at an early stage of the
SAP S/4HANA Cloud, private edition engagement/sales cycle.

Question 5

when planning your project?

Considerations
SAP S/4HANA Cloud, private edition project

▪ SAP will be managing the infrastructure of your
SAP S/4HANA system.
▪ Requests will need to be made via service
requests.
− Make sure to plan ahead.
− The handling of the service request is an
additional step compared to traditional on-
premise approaches.
− Provide complete and clear instructions in
your request to avoid issues.
▪ Unplanned technical situations can be
addressed through an incident to SAP ECS
team
▪ Please review your specific R&R
Google Cloud AWS Azure
▪ SAP product issues should still be addressed
as an incident to SAP Product Support

Key takeaways
▪ Decide which transition path is right for you.

▪ Evaluate the required setup for your system
landscape.
▪ Consider options for accelerating your
implementation.
▪ Carefully check third-party solution(s) needs and
share with SAP Enterprise Cloud Services team at
an early stage of your engagement
▪ Understand the working model with SAP and ensure
this is reflected in your project plan.

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 4: Migration Scenarios for Moving an
Existing System into the Cloud
Question 1
What are the possible transition

paths for on-premise customers
to move to SAP S/4HANA Cloud,
private edition?

Transition paths to SAP S/4HANA Cloud, private edition
New Implementation
SAP R/3 or 3rd Party System
New Implementation
System Conversion
Selective Data Transition
SAP ERP
(New Implementation) SAP S/4HANA Cloud,

Lift & Shift private edition
SAP S/4HANA (on-prem) –
with 9+ months remaining mainstream
maintenance
(New Implementation)
Lift & Shift & Upgrade –

SAP S/4HANA (on-prem) – as described in the Limited
with no or less than 9 months
remaining mainstream maintenance Maintenance Policy
Source release – SAP ERP 6.0 on any database/target – SAP S/4HANA Cloud, private edition
SAP S/4HANA Cloud,

private edition
infrastructure
SAP ERP 6.0 EHPxx SAP S/4HANA

System conversion
(DMO with system move)
Any supported DB SAP HANA DB
Any supported OS Suse Linux
On-premise SAP S/4HANA Cloud, private edition

Source release – SAP ERP 6.0 on SAP HANA DB/target – SAP S/4HANA Cloud, private edition
Option 1:
System
SAP Cloud
conversion to
infrastructure
SAP S/4HANA
SAP ERP 6.0 EHPxx SAP S/4HANA

System Copy
Consider SAP HANA
SAP HANA DB
DB upgrade, if required
Consider OS upgrade,
Suse Linux
if required

Source release – SAP ERP 6.0 on SAP HANA DB/target – SAP S/4HANA Cloud, private edition
Option 2:
System
SAP Cloud
conversion to
infrastructure
SAP S/4HANA
SAP ERP 6.0 EHPxx SAP ERP 6.0 EHPxx

Copy SAP ERP from on-
Any supported SAP prem to private cloud
SAP HANA DB
HANA DB version
Any supported OS Suse Linux

Source release – SAP S/4HANA (on-premise)/target – SAP S/4HANA Cloud, private edition
System
SAP Cloud
upgrade to
infrastructure
latest release
SAP S/4HANA SAP S/4HANA

(1809, 1909, 20XX) (1809, 1909, 20XX)
System Copy
SAP HANA DB SAP HANA DB
Any supported OS
Suse Linux
Linux x86/Power

Note:
For SAP S/4HANA 1809
▪ SYSTEM COPY (backup/restore): This approach is allowed until March 2023. After March 2023, Limited Maintenance Policy will apply.
▪ Upgrade: Upgrade to latest release is desired as part of the migration.
Question 2
What are the steps required for SAP

and the partner to get the customer
system into SAP S/4HANA Cloud,
private edition?

Source release – SAP S/4HANA target – RISE with SAP S/4HANA Cloud, private edition
System Copy
SAP Partner
SAP S/4HANA (on-premise)
▪ Executes all required preparation
System copy preparation activities
activities ▪ Performs a full offline backup of the
SAP HANA database
Full offline SAP HANA ▪ Provides a target for the source data
database backup and guidance for the transfer ▪ Transfers the backup files to SAP
S/4HANA Cloud, private edition target
following guidance shared by SAP
Transfer backup files ▪ Provides an empty virtual server to be
used for import activities – a migration
server
SAP S/4HANA, ▪ Moves provided backup onto the SAP
private cloud edition HANA server
▪ Executes SWPM on the provided
migration server to trigger the restore
Database restore ▪ Start up SAP application server in and post steps
SAP S/4HANA Cloud
SWPM process for system
copy ▪ SAP executes post activities before ▪ Executes all the post system copy
handover to customer, including steps and activities in the target private
SWPM post activities monitoring tools, backup schedule, and cloud system
(SAP GUI) validation

Source release – System copy
SAP S/4HANA Cloud,

1. Prepare migration server Customer (on-prem) private edition
(copy SAP tools)
2. Perform offline backup
3. Copy backup cloud storage no root
S/4H S/4H
HANA HANA access
4. Backup will be transferred to APP APP
SAP HANA server by SAP
5. Run SWPM (Software
Provisioning Manager). In
5. SWPM/
the system copy scenario) to 2. Backup Restore
trigger the restore and run
post-processing
1. Prepare
− Switch to final application
server Migration
local storage Server
− Finalize post-processing storage 3. Copy
Object Storage with root
access
Source release – SAP S/4HANA target – RISE with SAP S/4HANA Cloud, private edition
System Conversion
SAP Partner
(on-premise)
▪ Executes all required preparation and
execution steps in the source system
Conversion uptime + export
executed by the partner in the ▪ Transfers the required files to SAP
source system S/4HANA Cloud, private edition target
▪ Provides a target for the source data following guidance shared by SAP
and guidance for the transfer
▪ Transfers all tools needed for
Transfer files ▪ Provides an empty virtual server to be conversion (SUM/SWPM/SAP Kernel)
used for import activities – a migration to the provided migration server
server
▪ Installs a temporary PAS on the
SAP S/4HANA,
migration server and executes all the
private cloud edition technical conversion steps
Import + conversion ▪ Informs SAP that the technical steps

▪ Start up SAP application server in have been completed successfully.
downtime SAP S/4HANA Cloud Stops all SAP processes on the
temporary PAS
▪ SAP executes post activities before
Conversion post-activities handover to customer, including ▪ Executes all the post-conversion steps
monitoring tools, backup schedule, and and activities in the target private cloud
(SAP GUI)
validation system

Source release – System conversion
SAP S/4HANA Cloud,

1. Prepare migration server Customer (on-prem) private edition
2. Export on-prem ERP
3. Copy export data to migration
server no root
ERP S/4H
DB HANA access
4. Perform import/conversion APP APP
5. Post-processing part 1
6. Switch to final application
server
7. Finalize post-processing 2. Export 4. Import
part 2
Migration with root
1. Prepare Server access
local storage
storage 3. Copy

Conversion to Microsoft Azure – DMO without system move (pilot)
One-step conversion and transition of your on-premise SAP ERP to SAP S/4HANA on MS Azure
▪ Simplified approach for this use case Customer data center Microsoft Azure
on premise
▪ Proven SUM technology Application server Application server VM
▪ Option to use downtime-optimized features
▪ Applicable for SAP ERP on non-SAP HANA DB SAP ERP SAP S/4HANA
▪ Pilot phase, registration required via incident
Migrate and convert

Note: The procedure has been verified with MS Azure,
Database server Database VM
but should equally work with other hyperscalers
Source database SAP HANA
Blog: “DMO to Azure”: combine SAP S/4HANA conversion with the move to Azure (without “DMO with System Move”)
Whitepaper: Converting from SAP® ERP on Premise to SAP S/4HANA® on Microsoft Azure
Question 3
What should I do if there are

less than 9 months of
mainstream maintenance
remaining for my SAP
S/4HANA release?

Source release – SAP S/4HANA 1511, 1610, and 1709
Summary of technical criteria for customers who are running old SAP S/4HANA releases on their premises to move
to SAP S/4HANA Cloud, private edition
Source Release End of Mainstream Description
Maintenance
SAP S/4HANA 1511 31.12.2020 Supported under limited maintenance policy
SAP S/4HANA 1610 31.12.2021 Supported under limited maintenance policy SAP S/4HANA (on-prem) –
with no or less than 9 months
SAP S/4HANA 1709 31.12.2022 Supported under limited maintenance policy remaining mainstream
(applicable since 01.04.2022) maintenance
Lift & Shift & Upgrade – as described in the Limited Maintenance Policy:
https://www.sap.com/about/agreements/policies/cloud-service-specifications.html?sort=latest_desc&search=limited%20maintenance
Highlights of this policy:
▪ Non-PRD systems (on old SAP S/4HANA releases) can be migrated to SAP S/4HANA Cloud, private edition
▪ Before the migration of PRD system, the non-PRD systems have to be upgraded to the latest SAP S/4HANA versions
▪ After the migration of PRD system, it has to be upgraded to the latest SAP S/4HANA version within 2 weeks
▪ The migration of the systems can be done by partners and the upgrade (technical tasks) will be done by SAP ECS as per roles &
responsibilities matrix. Note that the implementation partner and customer still need to perform regression testing and other upgrade
preparation tasks.
Note: If the customer release is an older version such as 1511, 1610, or 1709, please clarify with your responsible SAP sales account team.
Migration Assisted Services
The assisted migration services are included when the customer needs to
migrate components not based on SAP S/4HANA or SAP HANA database, e.g.:
▪ SAP ASE as target database
▪ SAP Content Server
▪ SAP NetWeaver Java-based systems
Scope of SAP team:
▪ SAP BusinessObject platform
▪ Trigger SUM/SWPM (Software Update
Manager/Software Provisioning Manager) tool on OS level
Scope of partner team (engaged by the customer) ▪ Monitor service request reported by the partner.
▪ Complete responsibility and accountability of migration Coordinate with SAP server management and DB teams.
is with migration partner ▪ Execute any OS command with root or <SID>adm as
▪ Follow up and fix issues related to migration requested by partner.
▪ Open support ticket and/or change request for operating ▪ Share SUM/SWPM logs to partner on request, where
system (OS) and database (DB) parameters, if needed jailed user (“custuser1”) is too restricted
▪ Close alignment with SAP team assigned to customer ▪ Copy files to locations that customer/partner has no
access to

Technical assessment – Sizing
Customer transitioning to SAP S/4HANA
New SAP S/4HANA Customer Existing SAP ERP system converted to SAP S/4HANA
(Greenfield Sizing) (Conversion Sizing) * SAP HANA server only
SAP Quick Sizer SAP Readiness Check
Additional storage requirement Consider inclusion of any temporary resource

▪ System conversion ▪ Additional storage for temporary files
▪ System copy ▪ Additional sandbox servers
▪ Additional app servers
Note:
▪ Additional sizing should be executed for embedded analytics and SAP Fiori requirements
▪ SAP Fiori migration and SAP S/4HANA migration/conversion are two different topics. You can plan them both
for the same downtime window, but the downtime duration will increase. This is not a one-step approach, it is
a two-step approach.
Demo
Run the ABAP on SAP HANA

Sizing Report

Demo

Key takeaways
▪ Additional storage needed for export data and to be

able to perform DB backups during the conversion
▪ Validate that you reach the cloud systems using the
customer’s cloud connection
▪ Validate that the contractually ordered system sizes
are sufficient to run the systems after the conversion
▪ Download all necessary tools (SWPM/SUM, SAP
Kernel, etc..) and copy them to the migration server
▪ SAP uses a default set of parameters for cloud
systems. Align with the SAP team if additional
parameters or modified values are needed.
Deviations need to be documented in a ticket.

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 5: Network and Security Considerations
Question 1
What is the customer /

SAP shared security
responsibility model?

Shared security responsibility model (high level)
CUSTOMER
▪ Platform architecture RISE with SAP ▪ On-premise to IaaS providers connectivity
▪ IaaS provider subscription and landscape S/4HANA Cloud, ▪ User identity and authentication and
▪ Backup and restore Private Edition authorization management
▪ Building secure VMs including OS, Shared Security ▪ Customer data ownership
SAP HANA DB, and SAP applications ▪ Compliance with government regulations
▪ Basis and other technical support ▪ Security audit logging
▪ SLA services ▪ Integration and extensions
▪ Security, threat, and patch management ▪ Custom developments and configuration
▪ Security audits and compliance of the ▪ Application change management
platforms ▪ In transit data encryption between on-prem
and RISE
▪ Physical data centre security

▪ Network connectivity, regions, availability zones
IaaS
AWS Azure Google Cloud ▪ Physical, virtual infrastructure and hypervisor
Provider
▪ Network availability
▪ Audit, security, and compliance on IaaS

Question 2
What does the SAP private

managed environment for
the customer look like?

SAP private managed environment
Customer 1 Customer 2 Customer 3

Application Instances Application Instances Application Instances
Separate Subscription/
SAP HANA Instances SAP HANA Instances SAP HANA Instances
Project/Account
Project/Account
Project/Account
Operating Instances Operating Instances Operating Instances
Compute Compute Compute
Storage Storage Storage
Connectivity Connectivity Connectivity
Subnets Subnets Subnets
VPC/VNET VPC/VNET VPC/VNET
Azure AWS Google Cloud IaaS Provider – Azure, AWS, and Google Cloud
Regional
Admin VPC
Regional Admin | Infrastructure | Secure Admin Connectivity | Jump Hosts
SAP Global Monitoring & Alerting | Provisioning & Automation | SIEM | Asset & Lifecycle Management |
Security VAPT & Security Patch Management | Endpoint Protection & Response | Capacity
Operations Management | Admin Access Management
Question 3
What does the

SAP S/4HANA Cloud,
private edition deployment
architecture look like?

SAP S/4HANA Cloud, private edition deployment architecture (1/2)
SAP S/4HANA Cloud, Private Edition/Azure – IaaS Provider
Region 1 Region 2
Subscription 1 – Primary Subscription 2 – Disaster Recovery
VNET #1 VNET#2
Network Services
SAP Application and
Network Services
Database Servers DR
Gateways
Customer
VNET
Gateways
Customer
Subnet
Subnet
PROD
Peering SAP DR Application and
Databases
QAS (Disaster Recovery – Data

Replicated from Primary)
Disaster Recovery
DEV
Application Subnet
Application Gateway
Production Subnet Gateway
WAF Subnet
WAF Subnet
IaaS Provider (Azure) – Security Group/Network Security Group or Firewall

SAP S/4HANA Cloud, private edition deployment architecture (2/2 – high level)
Browser SAP GUI Mobile Integration Cloud NOTE: Internet shall include only HTTPS
On-Premise
Private connectivity
SAP S/4HANA Cloud, private edition Web Application Firewall

Dedicated virtual network for customer Cloud Connector
Web Dispatcher
AWS Azure Google Cloud
Additional
environment if
required by customer
DEV QAS PRD
DNS Zone: SAP S/4HANA Cloud, private edition<customer internal domain>

Question 4
How is data encrypted

both in transit and at rest?

Encryptions and ciphers (1/2)
SAP HANA DB
SAP HANA
Encryption for
Data at Rest

Encryptions and ciphers (2/2)
SAP GUI
Browser SAP GUI Integration Customer
Network
Private Network
TLS 1.2 TLS 1.2
SAP
Access
SNC
Dedicated
TLS 1.2 TLS 1.2
AES-256- AES-256-
Customer
SAP Web Dispatcher GCM GCM Landscape
AES-256- SAP Application Server

GCM
NOTE: AES-256-GCM is only
fixed for data at rest encryption, SAP S/4HANA
for TLS it is auto-negotiated.
SAP HANA in-memory database

AES-256-
CBC
Secure Storage
AES-256-
GCM
Question 5
How is the customer account

boundary configured?

Customer account boundary (high level)
Central SAP
Master Account Hyperscaler
Customer Landscape
Account
SAP-hec-cust-001
Account Service VNET created within each

Administrator Administrator customer subscription
SAP Master Root Account (SAP SE)
SAP Enterprise Cloud Services (ECS) Security Policy

Inheritance
Customer Subscriptions

Question 6
Which security and

compliance topics are part
of the SAP S/4HANA Cloud,
private edition offering?

SAP S/4HANA Cloud, private edition – Security
✓ Isolated Landscapes, Security Monitoring ✓ 24 x 7 Security Monitoring Center

Security Hardened Systems Real-time visibility and decision making ✓ 24 x 7 Incident Response
✓ Network Filtering ✓ Advanced Forensics
✓ Web Application Firewall
✓ DDoS Protection
✓ Vulnerability Scanning
✓ 2 Factor Authentication Vulnerability ✓ Vulnerability Advisory
Management
Network Security ✓ Penetration Testing
State of the art risk-
Advanced IT security impact vulnerability ✓ Hacking Simulations
architecture prioritization ✓ Security Patch
Management
✓ Endpoint Detection &

Cloud Security Posture Response (EDR)
Threat Protection
Management ✓ Security Orchestration
Advanced malware
Protect data, control analysis Automation and
access, and detect Response (SOAR)
threats ✓ Malware Management
✓ Cloud Security &
Compliance Umbrella
✓ Security Compliance ✓ Identity & Access Management
Scanning ✓ Privileged Identity Management
✓ Security Secure Operations ✓ Asset & Change Management
Configuration Checks User and process-level security across hybrid ✓ Security Awareness
landscapes
Question 7
Which single sign-on

options are available for
SAP S/4HANA Cloud,
private edition?

Single sign-on options
Browser Based
Application No, SAP GUI
Yes is still used
Kerberos
Yes Sufficient?
Yes No
SAP Identity Authentication service Basic SSO included in SAP Extended SSO SAP S/4HANA
SAP S/4HANA Cloud, private edition Cloud, private edition
SAML Kerberos X.509
X.509 2FA Kerberos 2FA
SAP BTP services, license included
with RISE License included with RISE License not included
System Demo: Single Sign-On example
Single Sign-On example

with IAS Integration

Hyperscaler
End User SAP Business Technology Platform
Subaccount
Service Provider
(SAP S/4HANA
Application Cloud, private
Client
Business edition)
Application Studio
iOS
Launchpad Connectivity
service
Android
trust
Cloud
Windows Identity
IAS to BTP (1) connector
Authentication trust
Service
IAS to SAP S/4HANA (3)
Desktop
trust
IAS to IDP (2) Corporate Identity

Provider
1. Identity Authentication service and SAP BTP

2. Identity Authentication service and Corporate Identity Provider
(in our example Azure AD)
3. Identity Authentication service and SAP S/4HANA

Question 8
Where can I find more

information about hyperscalers,
cloud architecture, and
edition?

openSAP course on hyperscalers
SAP on Hyperscalers – Strategy, Architecture and Deployment

Blogs and external content
Refer to the following excellent blogs for further

information on hyperscalers, cloud architecture, and
SAP S/4HANA Cloud, private edition:
▪ Secure RISE with SAP
▪ RISE with SAP: Multi-layer Defense in Depth Architecture
of SAP S/4HANA Cloud, Private Edition
▪ RISE with SAP: Adopting to Zero Trust Architecture
Principles with SAP Cloud Services

Question 9
Which tasks in the context

of security is it important
that the customer does?

Which tasks in the context of security is it important that the customer does? (1/2)
▪ WAN (on-premise to IaaS Providers) and Dedicated Private Connectivity (AWS Direct Connect)
The customer needs to arrange a dedicated network connectivity with their hyperscaler using one of the following
options:
– AWS Direct Connect
– Azure Express Route
– Google Interconnect
▪ Customer needs to get permission to cross-connect to the Hyperscaler router. SAP only performs a software
configuration with SAP S/4HANA Cloud, private edition; the physical connectivity is the customer’s responsibility.
Refer to Private connectivity to SAP HANA Enterprise Cloud via AWS Direct Connect for further details.
▪ User Identity Management and Authentication
All technical user accounts (“Service Principals”) have to be requested via IT direct ticket
▪ User Authentication and Authorization Management
Choose the Identity Authentication service, basic or extended Single Sign-On options, and perform SSO
config/setup.
▪ Customer Data Ownership
SAP does not have access to customer data unless explicitly authorized by the customer. SAP only processes the
customer data. The customer should fully understand Role-Based Access Control (authorizations). The customer
is also responsible for the authentication function. Refer to Data Processing Agreement for SAP Services.
Which tasks in the context of security is it important that the customer does? (2/2)
▪ Compliance with Government Regulations

SAP complies with data protection law(s) wherever SAP cloud services are
operated (e.g. GDPR in EU countries)
▪ Security Audit Logging
SAP provide infrastructure logs using Splunk (a log management solution).
Customer is responsible for the application and security logs
▪ Integration and Extensions, Custom Applications Development
This is the same as in on-premise environments
▪ Configuration of the Customer Business Processes
▪ Application Change Management

Key takeaways
▪ Approach to Multi-Layer Defense in Depth

Architecture: SAP S/4HANA Cloud, private edition is
a “single tenanted” managed private environment for
customers where SAP creates a separate account
(AWS) or subscription (Azure) or project (GCP) for
each customer.
▪ The applications and database virtual instances are
solely dedicated to a single customer. Security by
Design and Security by Default are deeply
embedded into the multi-layer architecture.

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 6: Important Tooling
Important tooling
Question 1
What are important tools

that will help with the
transition to SAP S/4HANA?

Important tooling
Important tools/notes supporting your transition to SAP S/4HANA
Planning phase Preparation phase Realization phase

Application-
System Maintenance Custom code Software Update
Pre-checks specific follow-
requirements planner preparation Manager (SUM) up activities
Cross-application and
application-specific preparation activities
System
Conversion
Tools
SUM
Transformation Maintenance Simplification ABAP Test SUM – Software ABAP Test
Prerequisite
Navigator Planner Check Report Cockpit Update Manager Cockpit
Check
Product ABAP
Roadmap Simplification
Availability Development
Viewer Item Catalog
Matrix Tools
SAP Readiness
SUM 2.0
Check for SAP
Notes
S/4HANA
Version
Process
Interoperability
Discovery
2251604

Important tooling
Question 2
What can you plan for during

the Discovery phase?

Important tooling
SAP Transformation Navigator
Build your own custom transformation guide
Step 1: Transform your landscape
Step 2: Extend your business
Step 3: Review benefits
Step 4: Set your priorities
Step 5: Generate your documents
Step 6: Share your map

http://www.sap.com/TransformationNavigator

Important tooling
Demo

▪ Tool access link:
– http://www.sap.com/TransformationNavigator

Important tooling
Roadmap Viewer
Provide key content you can use to drive a successful SAP S/4HANA deployment
▪ Browse implementation guidance for

your digital transformation
▪ Access SAP Activate methodology
assets and accelerators
▪ A comprehensive document and
service collection
▪ Supports all transition scenarios
▪ Offers a project plan template
Roadmap Viewer
https://go.support.sap.com/roadmapviewer/

Important tooling For conversion customers only,
minimum source release is SAP ERP 6.x
SAP Readiness Check 2.0
Available for all customers free of charge, customers can initiate their ERP system analysis, covering the most important
aspects of an SAP S/4HANA system conversion. Minimum source release is SAP ERP 6.0 EHP 0, any database – Unicode
is not required
• Add-Ons & Business Functions

• SAP S/4HANA Sizing
• Simplification Items
• Custom Code & Custom Dev
• SAP Fiori Recommendations
• Integration
• Business Process Discovery
Customers who have already generated an analysis in the past, the only additional setup is to implement the data volume management SAP Note 2612179 as well as the latest version of SAP
Notes 2913617 and 2290622.

Important tooling
Simplification item catalog
Provides customers with a description of all relevant changes that might have an impact
when converting from SAP ERP to SAP S/4HANA
▪ Collection of simplification items,
which describe the difference
between functions in SAP Business
Suite and SAP S/4HANA.
▪ Each simplification item contains a
description of impact for customers,
corresponding SAP Notes, and
mitigation possibilities.
▪ Simplification list is used by SAP
Readiness Check and simplification
item checks (SAP Note 2502552) –
both return relevant simplification
items for your system.
Simplification item catalog

https://launchpad.support.sap.com/#sic

Important tooling
Process Discovery
Executive summary
Starting point to build a case Process Discovery Solution
for SAP S/4HANA
Online application
Easy to share including (currently named Spotlight)
direct links to Process Discovery Process
solution Discovery
for SAP S/4HANA Deep-dive into process performance
Audience: Transformation and efficiency
Business executives
Identification of areas for improvement
Process Discovery Summary and automation potential
Interactive PDF document Tool-based support to identify

(Evolution of SAP Business Scenario Recommendations)
standardization opportunities
Process Discovery free of charge for customers on SAP Maintenance

Important tooling
Question 3
Which tools can help

during the Prepare phase?

Important tooling
Simplification items check
Run manually in advance / will be run by SUM at least twice during the conversion procedure.
If serious issues exist in the system, it could cause the system conversion to fail.
▪ Relevance check determines
which simplification items are
relevant for your specific system.
Consistency check checks for
data inconsistencies or missing
mandatory preparation activities
before your conversion.
▪ It is necessary to freeze the check content of the simplification item catalog (SIC) once you are past the DEV system
conversion (Download Local SIC → Switch Source → SIC)
− Relevance Check – Review all items in “Yellow”. Most of the time “Green” can be skipped.
− Consistency Check – Resolve all “Red” via notes or SUM will fail in RUN_S4H_SIF_CHECK_EXEC
− Exemption – Resolve all “Red” if possible and only apply exemption as needed
Prerequisites
▪ SAP Note 2399707 and SAP Note 2502552.
▪ Also see the following blog.
Important tooling
Maintenance planner
Maintenance planner enables easy and efficient planning of all changes in your SAP system
landscape.
▪ Maintenance scenarios
− Release upgrade, update
− Conversion to SAP S/4HANA,
SAP BW/4HANA
− Apply HR packages, Java patches,
− Plan add-on uninstallation for ABAP
▪ Integrated processes and utilities
− Seamless planning for SAP Fiori apps
− Integration with SAP Transformation
Navigator, innovation discovery
− Side effects reports, security notes, copy
stack XML
▪ Advanced capabilities
− Up-to-date installation
Maintenance planner − System tracks
https://maintenanceplanner.cfapps.eu10.hana.ondemand.com/ Correction of system information
Important tooling
Question 4
Now that you have reached

the Explore phase, which
other tools can be useful?

Important tooling
SAP Cloud Appliance Library (CAL)
▪ SAP Cloud Appliance Library (CAL): Repository of latest, preconfigured SAP solutions that can be instantly consumed in
the cloud. Includes RIG landscape for practicing conversions with documentation, search for “System Conversion
Landscape SAP ERP to SAP S/4HANA”
▪ Familiarize key users with the new interfaces and SAP Fiori apps
▪ Use one of the best practice clients for the Fit/Gap Analysis in the subsequent phases
SAP S/4HANA Fully-Activated Appliance
(1) (2) (3) (4)

SAP S/4HANA SAP NW JAVA/ADS Remote Desktop BI Platform
ABAP Server Java Server Windows Remote Desktop SBOP BOE
SAP S/4HANA SAP Fiori
Adobe Document SAP GUI SBOP BI Platform
Core / Gateway
Services ABAP Dev Tools / SAP BI Best Practices Content
Cloud
SAP BASIS SAP NetWeaver Java HANA Studio
Connector
SAP Best Practices SAP Lumira (Discovery &
Designer)
SAP HANA SAP Sybase ASE

Remote desktop & BI Platform only via SAP CAL*
* Note: BI Platform and remote desktop are optional in CAL (will decrease hosting fee if you opt out). Both are included by default but you can opt-out in the
Advanced Mode of instance creation. This cannot be undone unless you create a new instance that has them in again.

Important tooling
ABAP test cockpit
▪ Simplification use cases

SAP S/4HANA checks
− Functionality no longer available
− Data model changes
− Data type changes
▪ SAP HANA use cases
− Use of DB vendor specifics (native SQL)
− DB operations on pool/cluster tables SAP HANA checks
− SELECT/OPEN CURSOR statements without
ORDER BY
▪ Use check variant
S4HANA_READINESS_REMOTE
S4HANA_READINESS_REMOTE includes
SAP S/4HANA and SAP HANA checks
Important tooling
Question 5
Which tools can help you

during the Realize phase?

Planning Preparation Realization
Important tooling Software
System Maintenance SI Custom code Follow-on
Software Update Manager (SUM) requirements planner checks prep
Update
Manager
activities
▪ Software update PAS Host

1
Provide new applications and new tables Software
Update
▪ Data conversion Manager
Convert table content to new data model
▪ Database migration
Migrate to SAP HANA database (if required) Source = Target DB Host
3 DMO with system move

2 PAS Host Source PAS Host Target PAS Host
Software Software
Software
Update Update
Update Manager
Manager Manager
Any Any
DB DB Convert
Source DB host Target DB host Source DB host Target DB host

Important tooling
Technical Downtime Optimization app
More information available in SAP Note

2881515: Introduction to the Technical
Downtime Optimization App
Technical Downtime Optimization app

https://launchpad.support.sap.com/#/downtimeoptimization
Important tooling
Question 6
What are the important tools

do consider for the Deploy
phase?

Important tooling
Migration cockpit
SAP Fiori app Process & content Data load

Migrate Your Data
API-based
MS_Logistics
SAP S/4HANA
Cloud
Staging tables
SAP S/4HANA
Cloud, private
Excel XML template files
edition
or other tools of choice
SAP S/4HANA 2021: 176+
SAP
Migration objects S/4HANA
Important tooling
Question 7
After go-live, which other tools

should be considered to keep
the system up-to-date during
the Run phase?

Important tooling
nZDM tool
▪ Maintenance events like applying updates or upgrades of ABAP-based solutions cause a technical
downtime
▪ near-Zero Downtime Maintenance moves time-consuming upgrade activities like the import of new table
content and table conversions partly into uptime. The Record & Replay framework ensures the consistency
of business transactions
Uptime Downtime
Shadow Operation
Extended Shadow
Operations
▪ SAP Note 1678564 – Restrictions, Database-specific Settings, and Troubleshooting of nZDM for SUM
▪ SAP Note 1678565 – Prerequisites, Terms and Conditions for nZDM/SUM
Important tooling
Key takeaways
▪ Make use of all available tools to be ready for transition

to SAP S/4HANA Cloud.
▪ Run SAP Readiness Check early to get an overview
and create a planning baseline on important topics, plan
related efforts and required skills.
▪ Run the simplification items checks as soon as
possible, as some business process adaptions may be
complex and require more time than expected. Become
familiar with the simplification items for your target
release. Sufficient time for workshops and training
(change management) has to be included in your
project plan.
▪ Check your custom coding with ABAP test cockpit to
make sure it is compatible and optimized for
SAP S/4HANA Cloud.

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 7: What You Need to Know About SAP Fiori
Question 1
What does SAP provide as a

starting point for SAP Fiori?

SAP Fiori starting point in SAP S/4HANA Cloud, private edition
SAP Fiori architecture installed SAP Fiori launchpad foundation Plus a limited selection of apps
▪ SAP Fiori front-end server installed activated activated
in embedded mode, by default ▪ Selected standard SAP Fiori ▪ For example, to confirm main UI
features activated technologies and main floorplans
▪ SAP Fiori foundation roles are technically working
generated – administrator role +
user role
▪ Review what has been activated in
© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
transaction STC02 3
SAP Activate guidance for User Experience
Choose SAP Activate roadmap: On the Content and Accelerators Task Content and Accelerators
SAP Activate methodology for tabs, select the tag: are provided to guide your
RISE with SAP S/4HANA User Experience scoping, fit evaluation,
Cloud, private edition extensions, transport, and
deployment activities for User
Experience

SAP Activate – Major decision steps for User Experience adoption
Business
WHO will change

1. Scope your target business roles
2. Get to know your users
WHAT will change

3. Envision the future
Technical
HOW to change
4. Explore and fit
5. Lay it out for me

SAP Activate – Decide WHAT to change by aligning User Experience to business outcomes
Be more MOBILE GUIDE me better RESPOND faster
COLLABORATE better Be more INSIGHTFUL REACT faster
Be more AUTOMATED Be more PROACTIVE Be more ADAPTABLE
More Information: SAP Activate – Introducing UX Value Goals for your UX adoption roadmap
SAP Activate – Deciding WHEN to change by planning your UX adoption roadmap
EXAMPLE
NOW NEXT LATER
Procurement Officer
Be more
REACT PROACTIVE
faster
Be more Be more
AUTOMATED ADAPTABLE
GUIDE me
RESPOND
better
faster
Customer Call
Center
Be more Be more
MOBILE INSIGHTFUL
Retail Staff Member Finance Specialist Others

Question 2
What do we need to do before

exploring SAP Fiori?

How to deploy SAP Fiori for SAP S/4HANA efficiently
Scope and Prepare Activate and Explore Refine and Support

Sandbox Development
then move to
Quality Assurance & Production
Initial scoping Rapid activation of your Adjust launchpad content and

Identify business roles selected business roles layouts to meet your needs

Scope the business roles you want to explore
Scope and Prepare

Select your SAP business role templates from either/or:
▪ SAP Best Practices Explorer scope items
▪ SAP Fiori apps reference library
Include the SAP recommended business roles for configuration,
adaptation, and extension
▪ Administrator
Initial scoping ▪ Analytics Specialist
Identify business roles ▪ Business Process Specialist
▪ Configuration Expert – Business Process Configuration
For highest value intelligent use cases refer to:

▪ Situation Handling in the SAP Help Portal section “Use Cases for Situation
Handling”
▪ Machine learning scenarios in SAP Best Practice Explorer scope items or
in the SAP Fiori app F4469 Intelligent Scenarios
▪ Robotic process automation use cases in the SAP Intelligent Robotic
© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC
Process Automation Store 10
Activate the business roles you want to explore
Scope and Prepare Activate and Explore

Sandbox Activate SAP business roles using
transaction STC01 task list
SAP_FIORI_CONTENT_ACTIVATION
▪ Optionally generate test users
▪ IMPORTANT: Requires FES embedded
mode
Initial scoping Rapid activation of your

Identify business roles selected business roles Assign the Key User role to selected
users
▪ Explore hidden fields/features of your
apps and other in-built key user
extensions
▪ For example, by assigning role
SAP_UI_FLEX_KEY_USER

Question 3
How do we configure SAP Fiori

for our needs?

Refining your SAP Fiori User Experience for SAP S/4HANA
Refine and Support

Copy SAP business roles to create your own custom Development
business roles using the Launchpad Content Manager then move to
Quality Assurance & Production
Refine launchpad content in your custom business roles
▪ Activate via task list SAP_FIORI_FCM_CONTENT_ACTIVATION
▪ Refine data authorizations as needed
Apply key user extensions identified in fit evaluation, for
example: Adjust launchpad content and
layouts to meet your needs
▪ Custom fields
▪ Custom analytics
Add additional launchpad content using the Launchpad
App Manager, for example:
▪ App variants created using Adapt UI
Adjust launchpad layouts for your custom business roles
using SAP Fiori apps Manage Launchpad Spaces/Pages
Demo – Quick tour of where to find the tools you need
▪ Scoping tools and references

– SAP Fiori apps reference library
– SAP Best Practices Explorer
– SAP Help Portal
▪ Activation tools
– Task lists – run and review
▪ Configuration tools – SAP Fiori Administration Role
– Launchpad Content Manager & Launchpad App Manager
– Manage Launchpad Spaces & Manage Launchpad Pages
▪ Extension tools
– Adapt UI
– Special roles, e.g., Analytics Specialist, Administrator,
Configuration Expert – Business Process Configuration
▪ Support tools for every user
– About and App Support
Understand your extension options for SAP Fiori apps
ADAPT EXTEND BUILD
Standard built-in adjustment options Breakout options for the Build your own custom apps and
via in-app extensibility tools for the Developer include your own intelligent use
Key User* cases for the Developer
Example: Make hidden fields visible Example: Extension project by Example: SAP Fiori elements app
using Adapt UI; add custom field in developer – side-by-side built side-by-side on SAP BTP
SAP Fiori app Custom Fields (preferred) or classic
EASY MODERATE COMPLEX
* Key User = whoever you authorize to make changes on behalf of other users
Optimize your launchpad features
Centrally configure SAP Fiori features:

▪ Launchpad configuration parameters via
SAP GUI transaction /UI2/FLP_CUS_CONF
▪ Launchpad plug-ins via SAP GUI
transactions /UI2/FLP_CONF_DEF and
/UI2/FLP_CUS_CONF
Refer to the SAP Fiori launchpad guide

for your SAP S/4HANA release in the
SAP Help Portal for:
▪ Available launchpad configuration
parameters and their values
▪ How to develop and activate launchpad
plug-ins
Question 4
How do we support and

troubleshoot SAP Fiori?

How do we support and troubleshoot SAP Fiori?
Educate users on providing support information

▪ via the About and App Support features in the SAP Fiori
launchpad User Actions menu
Educate your support team on available tools

▪ Refer to blog post Support Best Practice Recommendations
▪ Check the further advice in blog post Performance
Optimization and Best Practice – Part 1 Tools and Tracing
When reporting incidents to SAP...

▪ Include the technical app ID from About and/or App Support
▪ Assign the application component of the app from About and
App Support

Question 5
What else should we consider

before going live with SAP Fiori?

Before you go live, make sure you...
Transport your UX Optimize end-to-end Test your solution thoroughly

▪ Through your system landscape performance ▪ On multiple device types
▪ Plus make a run sheet of any one- ▪ Performance tuning is a customer ▪ Especially test any peak system
off manual “per system” activities responsibility scenarios such as high volume
▪ SAP provides optional analytics, mass uploads, and
performance optimization printing
services on request

Question 6
Where can we find resources

to help us?

Resources to help your SAP Fiori journey in SAP S/4HANA
From the SAP Help Portal SAP Community topic OpenSAP Microlearning
product page for SAP S/4HANA SAP Fiori for SAP S/4HANA ▪ https://microlearning.opensap.com
▪ https://help.sap.com/s4hana_op ▪ https://community.sap.com/topics/ – SAP S/4HANA User Experience
includes: fiori/s4hana ▪ How-to videos for SAP S/4HANA
– SAP Fiori launchpad guide for ▪ Blogs, videos, links to official User Experience
administrator, developer, and user references, links to crossover
– SAP Fiori Overview guide topics
– SAP Security guide
Key takeaways
▪ Your SAP Fiori installation, architecture, and

launchpad are delivered ready-to-use
▪ Scope and activate the SAP business roles you want
to explore
▪ Refine your custom business roles and apply your
extensions where needed
▪ Prepare for go-live and business-as-usual support

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 8: Extensibility Options
Outline
Talk about extensibility – Why change or why consider new

approaches? → Intro
Golden rules apply to RISE (use/mention note – solution

standardization roadmap in activate) → up to customer to use,
not mandatory but best practice → Reuse 5Stepsdemo
Custom code analysis for clean core (take specific stuff to

ABAP on BTP) → Create Demo of CCA for ABAP on BTP
Additional offerings: BTP entitlements → LPD, SPA

(refer to previous RIG technical course)
▪ Haven’t found details on available entitlements, mentioned
in base contract but deleted from most contracts
▪ Ask Sales contact RISE: Kevin Richardson (Australia)
k.richardson@sap.com

Question 1
Why do we need extensibility

options in our project?

Extensibility needs
Presentation Tier Application Tier Data Tier
User Interface Create Custom Form and Business Logic Data Model
Extension User Interface Template Extension Extension
Realize business
Adapt the
Create a custom requirements by
standard user Store additional
user interface in implementing
interface of the information by
addition to or as a Adapt existing or additional
core solution by extending the
replacement for a create new forms business logic and
adding, removing, entities of an
standard UI and e-mail add, exchange, or
and changing UI existing data
catering for templates re-wire a process
elements like model or define a
specific usability by creating
labels, buttons, new data model
needs additional process
and input fields
steps

Question 2
Why do we need new

extensibility approaches?

New extensibility approaches
Reduce TCO Bring Speed and Innovation Be Cloud-Ready
By making upgrades eventually Allow you to absorb innovation New development paradigms
non-events from a custom code delivered by SAP at a faster rate allow you to lay the foundation
point of view today to move to the cloud from
a custom extension perspective
▪ Reduce test efforts for ▪ React faster on changing ▪ RAP vs CAP development –
business users business requirements one complements the other
▪ Reduce adaption efforts for ▪ React faster on adoption of ▪ Restricted ABAP is used in
developers new technologies (SPA, Event ABAP cloud
Mesh, …) ▪ Released APIs are leveraged
▪ IT department able to offer
upgrade projects at a for integrations with multiple
reliable fixed schedule SAP products

Question 3
Are the new extensibility

approaches related to the
clean core concept?

Moving to new extensibility approaches enables the clean core
Clean Core:
Stay as close as possible to standard – without losing the flexibility to quickly adapt the business
processes to your needs.
Upgrade Relocate
Stick to Document
Stable Your
Standard Deviations
Extensions Extensions
Adopt a zero Extensions should Leverage SAP BTP Monitor deviations
modification policy not break upgrades for side-by-side or and prepare to move
and vice versa hybrid patterns to clean core when
possible

How to clean the core?
Retire
Back to standard
Get transparency Re-design to SAP BTP Repeat

or on-stack refactoring
Be aware of the technical debt

Demo
Re-platform to SAP BTP, ABAP Environment

Question 4
What’s the difference

between classic
enhancements and new
extensibility concepts?

Moving away from typical extension to clean core extensions
Custom Extension
BAdI Implementation CustomUI
Custom UI
SAP Standard Transaction Dynpro,Dynpro

WDA, UI5
Classic Extensibility
BAPI Custom Logic

ABAP Classes, Function
(unreleased) Function Modules Modules, Reports
SAP
SAP Standard
S/4HANA
SAP
SAP S/4HANA
S/4HANA
Table / Object
Applications
Applications
Applications Direct Access to SAP Tables Custom Table
Finance,
Finance, procure,
procure,
Finance, procure,
produce,
produce, sales SE11 defined
produce,sales
sales
Append / Customer Include
SAP S/4HANA SYSTEM
SAP Standard Object Classic Extension Technology Extension Object

Custom Extension
CustomBAdI
Business
Implementation
Logic (Key User) CustomUI
Custom UI
SAP Standard Transaction Dynpro

SAP UI5 with Fiori Elements
Dynpro-Exit
Released Objects
BAPI/ Remote APIs Custom Logic
(unreleased) Function Modules Language of choice,

e.g. JavaScript in CAP model
SAP
SAP Standard
S/4HANA
SAP
SAP S/4HANA
S/4HANA
Table / Object
Applications
Applications
Applications Custom Table
Finance,
Finance, procure,
procure,
Finance,
produce, procure,
sales Direct Access to SAP Tables Data model based on CAP
produce,
produce,sales
sales
in e.g. SAP HANA Cloud
Create
Append
Custom
/ Customer
Field (Key
Include
User)
SAP S/4HANA SYSTEM SAP Business Technology Platform
SAP Standard Object Clean Core Extension Technology Extension Object

Custom Extension
CustomBAdI
Business
Implementation
Logic (Key User) CustomUI
Custom UI

Released Objects

SAP
SAP Standard
S/4HANA
SAP
SAP S/4HANA
S/4HANA
Table / Object
Applications
Applications
Finance,
Finance, procure,
procure,
Finance,
produce, procure,
produce,
produce,sales
sales
Create Custom Field (Key User)

Custom Extension
Custom Business Logic (Key User) CustomUI

Custom UI

Released Objects

SAP
SAP Standard
S/4HANA
SAP
SAP S/4HANA
S/4HANA
Table / Object
Applications
Applications
Finance,
Finance, procure,
procure,
Finance,
produce, procure,
produce,
produce,sales
sales

Custom Extension

Custom UI

Released Objects / Remote APIs Custom Logic

SAP
SAP Standard
S/4HANA
SAP
SAP S/4HANA
S/4HANA
Table / Object
Applications
Applications
Finance,
Finance, procure,
procure,
Finance,
produce, procure,
produce,
produce,sales
sales

Custom Extension

Custom UI

Released Objects / Remote APIs Custom Logic

Language of choice,
SAP
SAP Standard
S/4HANA
SAP
SAP S/4HANA
S/4HANA Custom Class to prepare data
Table / Object
Applications
Applications
Finance,
Finance, procure,
procure,
Finance, procure,
produce,
produce, sales Data model based on CAP
produce,sales
sales

Question 5
What are the available

extensibility options?

Key-user extensibility
EXAMPLE: FIELD EXTENSIBILITY

SAP S/4HANA Create and maintain custom fields that can be used to enhance
extensibility
SAP
SAP S/4HANA applications and APIs
SAPS/4HANA
Applications
S/4HANA
In-app
Applications
Applications
Applications Choose different data types (e.g. Number, Text)
Finance,
Finance,Procure,
procure,
Finance,
Finance,procure,
procure,
Produce,
produce, Sales
produce,sales
sales Custom fields can be used in applications and their UIs, reports,
produce, sales
KEY-USER e-mail templates, form templates, OData APIs and other
EXTENSIONS
Low-code / No-code
tools
SAP S/4HANA
ABAP Foundation
SAP HANA

Examples
UI adaptation mode – adaptation mode Custom Fields SAP Fiori app Custom Business Logic SAP Fiori app
with drag-and-drop configuration
Custom Business Objects SAP Fiori app Custom CDS Views SAP Fiori app Custom Analytical Queries SAP Fiori app
Demo
Key-User Extensibility

Extensibility Options
Scenario
Transport
Asset
Record asset Print Form Check Check
In-App In-App
location inventory inventory
change and sign and sign
release reception
Extend Process using In-App and Side-By-Side extensibility

Side-by-side extensibility
SIDE-BY-SIDE
EXTENSIBILITY
SAP S/4HANA
SAP
SAP S/4HANA
SAPS/4HANA
Applications
S/4HANA
Applications
Applications
Applications Custom code
Finance,
Finance,Procure,
procure,
Finance,
Finance,procure,
procure, Events
Produce,
produce,Sales
produce, sales
sales
produce, sales
Remote API Partner extension
Programming language
Java
SAP S/4HANA ABAP
ABAP Foundation
Node.js
SAP BTP

Demo
Side-by-Side Extensibility

Extensibility Options
Scenario
Transport
Asset
Record asset Print Form Side-by- Check Check
side In-App In-App
location inventory inventory
change and sign and sign
release reception
Extend Process using In-App and Side-By-Side extensibility

Key takeaways
▪ As a customer, you require extensibility options in multiple

tiers (presentation, application, data) in an SAP system
▪ Using new extensibility approaches allows you to:
– Reduce TCO
– Absorb innovation at a faster rate
– Be cloud-ready and reach the ultimate goal of having a
“clean core”
▪ Moving from classic enhancements to new extensibility
concepts might require a complete redesign of your
custom coding as you will need to adapt to the new
services, tools, and development paradigms.

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 9: Downtime Optimization Considerations
Question 1
What is different with regard to

downtime duration between
a transition project to SAP
S/4HANA in the same data
center and a project moving to
edition?

Downtime-relevant aspects for targeting SAP S/4HANA Cloud, private edition
General differences:
▪ Two different system locations:
Data transfer time to be considered
▪ Tight interaction of customer,
partner, and SAP:
Be aware of process and
communication paths
Some approach-specific aspects:

▪ New implementation: Migration cockpit performs initial data load
▪ Selective data transition: Initial data load (much depending on technique used by SAP or partner)
▪ Lift & Shift: Backup and restore becomes “backup, transfer, and restore”, so data transfer is relevant as well
▪ System conversion: See following slides

Question 2
What is the architecture

difference for a system
conversion to SAP S/4HANA
Cloud, private edition?

Conversion tasks of Software Update Manager
▪ Software update PAS Host

1
Provide new applications and new tables Software
Update
▪ Data conversion Manager
Convert table content to new data model
▪ Database migration
Migrate to SAP HANA database (if required) Source = Target DB Host
3 DMO with system move

2 PAS Host Source PAS Host Target PAS Host
Software Software
Software
Update Update
Update Manager
Manager Manager
Any Any
DB DB Convert
Source DB Host Target DB Host Source DB Host Target DB Host

Question 3
How can I speed up the

standard approach
“DMO with system move”
to reduce downtime?

“DMO with system move”: the SUM option which is generally available
Source Target
▪ Parallel mode reduces downtime: Uptime Shadow system activities:
source & target SUM run in parallel. 1. HOSTCHANGE_MOVE_SOT EU_IMPORT / EU_CLONE_EXT
▪ Long-running shadow system activities 1 ACT_UPG / SPDD
SHD_IMPORT
on target like SPDD, SGEN are only SGEN
2. MAIN_DTTRANS 2
then executed in uptime. …
▪ 3 sync points are required: Downtime Export
− Phase HOSTCHANGE_MOVE_SOT application
− Downtime dialog tables
Import
− Phase HOSTCHANGE_STOP 3. HOSTCHANGE_STOP 3 application
▪ With continuous synchronization, even tables
export and import processes run in
parallel.
▪ “DMO with system move” does not time
support downtime-optimization
techniques (like doDMO)
https://blogs.sap.com/2020/10/22/dmo-with-system-move-with-shd-rep-on-target-db/
Question 4
What could be a future

approach for the combined
move and conversion to
SAP S/4HANA Cloud,
private edition?

Guided system conversion to Microsoft Azure using Software Update Manager (pilot)
One-step conversion and transition of your on-premise SAP ERP to SAP S/4HANA on MS Azure
▪ Simplified approach for this use case Customer data center Microsoft
on-prem Azure
▪ Proven SUM technology Application server App server VM
▪ Option to use downtime-optimized features
▪ Applicable for SAP ERP on non-SAP-HANA DB SAP ERP SAP S/4HANA
▪ Pilot phase, registration required via incident
Convert & Transition

The approach simplifies the technical DB server Database VM
conversion and transition to a hyperscaler;
the application-specific preparation and post Source DB SAP HANA
activities are similar to a standard conversion
Blog: “DMO to Azure”: combine SAP S/4HANA conversion with the move to Azure (without “DMO with System Move”)
Whitepaper: Converting from SAP® ERP on Premise to SAP S/4HANA® on Microsoft Azure
Demo
Checking the SUM dialog for “DMO with system move”

Key takeaways
▪ Downtime optimization depends on both

organizational and technical aspects
▪ The move to hyperscalers can be done via
“DMO with system move”
▪ SAP is currently evaluating “plain DMO” as a pilot
project approach

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 10: Go-Live Preparation and Running the System
Question 1
How do you prepare for a

successful go-live for
edition?

Go-live check service for greenfield implementation
▪ Maintain Business Go-Live field in controlling system

Greenfield Implementation
▪ Submit JIRA ticket for ECS back office
▪ Coordinate CQC for implementation* & perform go-live checks &
provide report
▪ Request to view findings
▪ Classify alerts between customer or ECS scope and review with
customer SAP
▪ Create ticket to implement changes S/4HANA
▪ Cutover executions
▪ Maintain actual Business Go-Live field in controlling system
▪ Send go-live announcement at the end SAP S/4HANA Cloud, Private Edition
* The continuous quality check (CQC) for implementation has been part of SAP Enterprise Support for many years.
CQC OS/DB migration check and/or CQC for upgrade for brownfield implementation
▪ Maintain Business Go-Live field in controlling system

Brownfield Implementation
▪ Submit JIRA ticket for ECS back office
▪ Submit ticket for CQC OS/DB migration and/or
CQC for upgrade SAP Lift & Shift
1
(Inc. Upgrade)
▪ Coordinate and perform services & provide report S/4HANA
▪ Request to view findings
▪ Classify alerts between customer or SAP
ECS scope and review with customer 2 System Conversion
S/4HANA
▪ Create ticket to implement changes SAP ERP Selective Data
3
▪ Cutover executions Transition
▪ Maintain actual Business Go-Live field in controlling
system
On-premise SAP S/4HANA Cloud, Private Edition
▪ Send go-live announcement at the end
* Continuous quality check (CQC) OS/DB migration check applies for changed operation system or changed database such as
from non-SAP-HANA to SAP HANA database. CQC for upgrade applies when you perform system upgrade or conversion.

Question 2
How do I plan for upgrades to

keep the system up to date?

SAP S/4HANA release strategy
2021 2022 2023
Q4 Q1 Q2 Q3 Q4
Maintenance Line
SAP S/4HANA 2021 FPS01* FPS02* SPS03*

New release incl. new technology Feature Package Stack Feature Package Stack Support Package Stack
stack (ABAP Platform 2021 and SAP (technically SPS01) (technically SPS02) (technically SPS03)
HANA 2.0 SPS05 will be defined as
minimum version for customers)
Support Package Stack for SAP S/4HANA 2021* SAP S/4HANA 2022*
New release incl.
new technology stack
* This is the current state of planning and may be changed by SAP at any time without notice.
SAP Readiness Check for SAP S/4HANA upgrades
Discover Prepare Explore Realize Deploy Run
SAP Readiness Check for SAP S/4HANA upgrades ▪ A holistic system analysis is the
foundation for further planning
steps toward a successful and
smooth upgrade between
SAP S/4HANA product versions.
▪ SAP Readiness Check for

SAP S/4HANA upgrades
summarizes the most
important aspects of the
upgrade in an easily
consumable way.

SAP Readiness Check for SAP S/4HANA upgrades – Demo

SAP Readiness Check for SAP S/4HANA upgrades – Demo

SAP’s technical upgrade process
Overview of the upgrade process:
Prepare Phase Realize Phase
t1 t2 t3 t4 t5 t6
System Maintenance SI- Custom Code Software Update Application-Specific

Requirements Planner Checks Migration Manager (SUM) Follow-On Activities
Application-Specific Preparation
Activities
Simplification Item Methods

Catalog Standard
nZDM
ZDO
Upgrade to SAP S/4HANA: Sequence
Question 3
What are customer responsibilities

when preparing for an upgrade?

Support from SAP Enterprise Cloud Services
Leveraged global service delivery organization

providing 24x7 services with follow-the-sun operations
Customer Interaction Teams

Center
Customer IT Integrated
+ Support
Unified Framework ECS Office of the CTO
Partner Services
Support
Teams ECS Cross Delivery and Automation
Primary points of contact for ECS Customer Office

▪ Level 1 support
▪ Tasks outside of SAP ongoing service and support
Request Fulfilment (Initial Build)
per R&R (example requirements of the customer
management in during the customer lifecycle Event (Alert Management) & Backup COE
business client) Incident and Outage Management
▪ There are optional
services that can be Service Request Management Availability Management (Zero Outage)
requested to SAP Incident Management
Security Patch Management Request Fulfillment (Standard and Non-Standard)
through CAS services
for an additional cost Customer-Specific Projects, Hypercare
▪ Creation of SR or INC
Cloud Application Services – optional service

Customer responsibilities when preparing for an upgrade
▪ Create tickets (assisted service request) for system upgrade

(service request)
▪ Create SAP system users for Basis consultant (ABAP/Fiori)
▪ Application-related – Prep. activities
▪ Suspend jobs from customer and isolate the system
▪ SPDD/SPAU (T_CODE used for SAP Dictionary objects and
repository objects adjustments)
▪ Resume jobs from customer and connect the system
▪ Application-related – Post. activities
▪ Custom code adjustments
▪ Change management during system upgrade
▪ Testing after upgrade including unit test, integration test, and user
acceptance test etc.

Key takeaways
▪ Decide and choose CQC services based on

greenfield or brownfield implementation scenarios
▪ Execute and evaluate the SAP Readiness Check
report for planning every SAP S/4HANA upgrade
▪ Create your own strategy and planning for an
SAP S/4HANA release upgrade
▪ Have a clear definition and clarification on roles and
responsibilities between different teams during the
project

Thank you.
open@sap.com
Follow all of SAP

warranty.

OpenSAP S4cpe1 ALL SLIDES Presentation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenSAP S4cpe1 ALL SLIDES Presentation

Uploaded by

Copyright:

Available Formats

Gain Technical Knowledge on SAP S/4HANA Cloud, Private Edition

Unit 1: Introduction to the Course and Course

“What are you going to learn

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

1. Introduction to the course and course 6. Important tooling

3. Preparing for your SAP S/4HANA 8. Extensibility options

4. Migration scenarios for moving an 9. Downtime optimization considerations

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

▪ You understand the course content

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 15

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

What are the key roles in the

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Sales Phase Deployment Phase Operations Phase

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

What is the overall governance

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

RISE with SAP S/4HANA Cloud, private edition – complete bundle

3rd Level Support/Product Support/Product Development SAP

Who is responsible for which

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Potential partner services or cloud application services (CAS)

Additional Technical Services Application Managed Services & Implementation

The Roles and Responsibilities document

It is part of the contract between customer

describes the governance, and is non-

Cloud Application Services

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

Understanding and handling the Roles and

Roles and Responsibilities on SAP Agreements

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

What does the communication

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

Point of contacts for SAP

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11

What is the value of added

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

Is there anything else to

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 14

SAP S/4HANA Cloud have been completed successfully

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 16

▪ Be aware of the key roles in an SAP S/4HANA Cloud,

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 17

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

How are you planning to

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Sandbox Development Quality Production

SAP S/4HANA Development Quality Production

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Overview What functionality is used today in

SAP Readiness Check for SAP ERP usage and

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

What are the options to

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Enterprise Management Layer SAP Best Practices

Note: This is a paid service provided by SAP.

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

What needs to be considered

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

▪ SAP Best Practices content for SAP S/4HANA Cloud, private

Application Consultant Technology Technology Consultant Application Consultant

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 11