- The document discusses an Expert Guided Implementation session to help organizations plan their SAP S/4HANA conversion project. - Over the course of 4 days, SAP experts will provide lessons in the morning on key topics like transition scenarios and planning elements. Participants will then execute demonstrated steps in their own systems with remote support from experts. - The goal is to leverage accelerators and best practices to efficiently plan the SAP S/4HANA conversion project.

1. INTERNAL – SAP and Customers Only
Sabrina Autier, SAP
Expert Guided Implementation – Day 1
Plan Your System Conversion – SAP S/4HANA
Expert Guided Implementation powered by SAP Enterprise Support Academy*
e-mail: sabrina.autier@sap.com

2. 2
INTERNAL – SAP and Customers Only
Disclaimer
▪ The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP. Except
for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service or
subscription agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related
document, or to develop or release any functionality mentioned therein.
▪ This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and
functionality are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this
presentation is not a commitment, promise or legal obligation to deliver any material, code or functionality. This presentation is provided
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a
particular purpose, or non-infringement. This presentation is for informational purposes and may not be incorporated into a contract. SAP
assumes no responsibility for errors or omissions in this presentation, except if such damages were caused by SAP’s intentional or gross
negligence.
▪ 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, which speak only as of their dates,
and they should not be relied upon in making purchasing decisions.

3. 3
INTERNAL – SAP and Customers Only
Your organization is at the beginning of the digital
transformation and is planning to adopt SAP S/4HANA or
SAP S/4HANA Cloud, Private Edition through a conversion
scenario.
This Expert-Guided Implementation session will help you
prepare for your project. The delivery demonstrates how to
leverage key accelerators and best practices to plan an SAP
S/4HANA conversion project. It will provide references and
tools that are stored in various places.
Expert Guided Implementation
Plan Your Conversion To SAP S/4HANA

4. 4
INTERNAL – SAP and Customers Only
Expert Guided Implementation
Expert Guided Implementation
is a new optimized, short-term
setup service to configure basic
scenarios without long-term, in-
house consulting
Customer Readiness
❑ Desire/requirement to convert an existing SAP
ERP Solution to SAP S/4HANA
❑ SAP S-User to ensure access to resources
❑ Planning to start an SAP S/4HANA
conversion project in the next 2 years
Target Group:
❑ Project Management
❑ Functional Experts
❑ Technical Experts
Customer Requirements
Execution
Execution
Empowering Execution Expertise on
Demand
Demand
Web session, 1-2 hours each
morning
SAP expert explains step-by-
step configuration using
training materials
2-3 hours on the same day
Participants execute
demonstrated steps within their
own project, on their own SAP
environment
✓ ✓ ✓
During Execution
Participants have direct access
to an SAP expert who directly
supports them remotely, if
necessary, during the execution
Execution Expertise on Demand
Empowering
Training, practical experience, remote consulting

5. 5
INTERNAL – SAP and Customers Only
Expert Guided Implementation Schedule
Schedule: SAP S/4HANA Plan Your System Conversion
Day 1 Day 2 Day 3 Day 4
Empowering lesson
Introduction to SAP S/4HANA
• Why is SAP S/4HANA different?
• How is it different?
SAP S/4HANA Release Strategy
SAP S/4HANA Transition Scenarios
Key activities of an SAP S/4HANA
conversion project
Planning elements of an SAP S/4HANA
conversion project
(Web session, 1-2 h. in the morning)
Empowering lesson
SAP Readiness Check overview
Simplification Item Check Overview
Functional preparation: Finance
Functional preparation: Customer and
vendors
(Web session, 1-2 h. in the morning)
Empowering lesson
Maintenance planner
Custom code activities
Introduction to SAP Fiori
Introduction to SAP S/4HANA embedded
analytics
(Web session, 1-2 h. in the morning)
Empowering lesson
SUM and DMO of SUM
Downtime minimization approaches
SAP HANA 2.0
Sizing
(Web session, 1-2 h. in the morning)
Execution by customer
Customers will understand the transition
scenarios and have a high level
understanding of the end to end system
conversion pathway
(Remote support in the afternoon)
Execution by customer
Customers will understand the different
checks that can be run on the source SAP
ECC system and can start implementing
the prerequisites
(Remote support in the afternoon)
Execution by customer
Customers will understand the
different checks that can be run on the
source SAP ECC system for custom
code, and can start discussing
internally to check that SAP Fiori and
SAP S/4HANA embedded analytics
are in the scope of the project
(Remote support in the afternoon)
Execution by customer
Customers will understand how to run the
Sizing tool, and can start to implement it on
the system
(Remote support in the afternoon)
Goal of the day
◼ Understand how the differences
between SAP ECC and SAP S/4HANA
will influence the conversion project.
Goal of the day
◼ Understand how the simplification
aspects will influence the conversion
project, and which check can be run
before or early in the project, in order to
avoid unplanned issues within the
project
Goal of the day
◼ Understand how the simplification
aspects will influence impact custom
code during the conversion project, and
why SAP Fiori and SAP S/4HANA
embedded analytics should be included
(at least an initial scope) in the project
Goal of the day
◼ Understand how to use SUM and DMO
of SUM and the toolset for system
conversion

6. 6
INTERNAL – SAP and Customers Only
Agenda – DAY 1
▪ Learning Objectives
▪ SAP S/4HANA Introduction
o Why is SAP S/4HANA different from SAP ECC
o How is it different from SAP ECC
▪ Three transition scenarios
▪ Conversion
▪ Selective Data Transition
▪ New implementation
▪ Key activities of an SAP S/4HANA conversion project
▪ How do SAP S/4HANA differences impact the project
▪ Overview of some key activities
▪ Conversion project planning elements
▪ Key accelerators to help with project planning
▪ Planning elements
▪ Key Takeaways
▪ Additional documentation

7. SAP S/4HANA – Why is it different?

8. 8
INTERNAL – SAP and Customers Only
Embedded analytics for
simulation, prediction &
insight-to-action
Machine learning for
automated processing &
decision support
On any device, use
role based cockpits
with digital assistant
Sales Order fulfillment Issues
Capacity Plan Simulation
Monitor GR/IR Account Reconciliation
Overdue Materials - Stock in Transit
Slow or Non-Moving Materials
Why is SAP S/4HANA different?
SAP S/4HANA and SAP S/4HANA Cloud are designed to run your business different than before

9. 9
INTERNAL – SAP and Customers Only
Out-of-the-box
integration
Artificial
Intelligence
Technologies
NEW Business
Processes
Embedded in
SAP S/4HANA
Real-time Insights
Why is SAP S/4HANA different?
SAP S/4HANA and SAP S/4HANA Cloud are designed to run your business different than before
Intelligent
Suite

10. SAP S/4HANA – How is it different from
SAP ECC?

11. 12
INTERNAL – SAP and Customers Only
How is SAP S/4HANA different from SAP ECC?
Overview of key new features per Line of Business
Central Procurement
MRP live & MRP Cockpit
U-GL & Prediction
Product Compliance
Customer 360˚
Service Management
Enterprise Contract Mgmt.
Rep. & Repair Malfunction
AI/iRPA scenario
NEW Business
Emb. in S/4HANA
Real-time Insights Integration
Key Industry function
embedded inside
(e.g. Automotive, Consumer,
Retail, Mill, Prof. Services:
Commercial Project Mgmt.…)
SAP Cloud Platform
SAP Analytics Cloud
SAP AIN
Procurement Overview
Image based buying Intell. product proposal
International Trade
Del. insights enabl. by IoT
Direct Delivery
Embedded EWM & TM
Ext. Service Parts Planning
Predictive MRP
Prod Engineering & Ops
PPDS with Optimizer
Portfolio & Proj. Mgmt.
Recipe Management
Cash App
Orch. Financial Close
Compliance Framework
Group Reporting
Multi-C. Interact. Center
Maintenance Overview*
Asset Mgmt. for resource
scheduling
IoT Integration
GDPR Tools
Re-architecture &
improved functions
(e.g. Chemicals, A&D, Oil Gas,
Utilities…)
Details &restrictions…
Real-time Inventory & TM
Overview
Contract proposals
SAP Field Service Mgmt.
SAP Cloud for Service
Sales Force Support
Demand Driven MRP
Quot. of Product Bundles
Emb. Supplier Evaluation
Geographical Framework
GR/IR Monitor
Responsibility Mgmt.
PROCUREMENT MANUFACTURING
SUPPLY CHAIN R&D
FINANCE
SALES
SERVICE CROSS
ASSET MGMT. INDUSTRIES
Prod. Order Conversion*
SAP DMC
SAP IBP SAP EPD
SAP Customer Experience
BRIM
RPA scenarios
Service Ticket Autom.
Software Mgmt.
New VC Engine w. Simul.
Settlement Mgmt.
Post Goods Movement*
Int. Approval Workflow
Abnormal Liquidity
Situation Handling
Advanced ATP
Solution portfolio
Service Overview

12. 13
INTERNAL – SAP and Customers Only
How is SAP S/4HANA different from SAP ECC?
Some functionalities spread on different SAP Business Suite products are available in SAP S/4HANA
SAP Business Suite and non-SAP solutions
Complex landscape with integration and
lifecycle management challenges
SAP Business Suite
Functionality
now in SAP S/4HANA
Commercial Project Management
Project & Portfolio Management
Central Purchasing (SRM)
Supplier Lifecycle Management (SRM)
Ext. Warehouse Management (SCM)
Transportation Management (SCM)
Production Planning & Detailed
Scheduling (SCM)
Sales Force Support (CRM)
Multi-Channel Interaction Center (CRM)
Production Planning Optimizer (SCM)
SAP Event Management (SCM)
New Functionality
replacing SAP Business Suite
functionality in SAP S/4HANA
Advanced ATP
SAP S/4HANA Service
International Trade
Extended Service Parts
Management
SAP Direct Delivery - Last Mile
Distribution
New Functionality
with no predecessor in Suite
Legal Content Management
Demand-Driven and Predictive MRP
Intelligent Apps
Responsibility Management
Situation Handling
SAP HANA DB
CDS Views ML Foundation
Predictive Analytics Integrator (PAI)
SAP S/4HANA 2021
(SAP Business Suite is a group of several on-premise products :SAP ECC,
SAP CRM, SAP SRM, SAP SCM, SAP EWM)

13. 14
INTERNAL – SAP and Customers Only
How is SAP S/4HANA different from SAP ECC?
SAP S/4HANA is available in different deployment options
functional scope
business engagement
SAP Product
Release Cycles
Minimum Upgrade Frequency
UX
Deployment Types
SAP Best Practices
Configuration Options
Custom Code
Modification of SAP code
3rd
Party Add-ons
Infrastructure
Upgrades
Compatibility Scope
Licensing
SAP S/4HANA Cloud
Twice per year (e.g. 2208)
SAP Fiori
new implementation
yes
Self-Service and Expert Configuration
no
no
certified Public Cloud add-ons allowed
SAP, Alibaba, AWS,. ect. (SAP decision)
included and mandatory
n/a
SAP S/4HANA
annually, plus quarterly Feature/Support Packs (e.g. 2022)*
5 years* (to stay in mainstream maintenance)
SAP Fiori and SAP GUI
new Implementation, System Conversion, Selective Data Transition
optional (for New Implementation)
Implementation Guide (IMG)
optional
optional
allowed unless operating system access required
SAP, AWS, Azure, GCP, (customer preference)
customer owned, installation on request
mostly allowed – see note 2269324
allowed
customer preferred infrastructure
not included
allowed
SAP S/4HANA Cloud, public edition SAP S/4HANA Cloud, private edition SAP S/4HANA
subscription perpetual
* with 2023 Release and Maintenance Announcement changed to by yearly release + 4 years standard maintenance

14. 15
INTERNAL – SAP and Customers Only
How is SAP S/4HANA different from SAP ECC?
On premise versus SAP S/4HANA Cloud, Private Edition
Traditional
Advisory &
Implementation
Services
Application
Management
Services
Software
+ Support
Technical
Managed
Services
Infrastructure
Management
SAP S/4HANA
Cloud, private
edition
+
Advisory &
Implementation
Services
Application
Management
Services
Software
+ Support
Technical
Managed
Services
Infrastructure
Management
+

15. 16
INTERNAL – SAP and Customers Only
How is SAP S/4HANA different from SAP ECC?
SAP S/4HANA runs on ABAP Platform and not anymore on SAP NetWeaver
• The first SAP S/4HANA versions (1511, 1610, 1709) were developed on top of AS ABAP, but had some important
changes:
• SAP S/4HANA 1709 runs on top of AS ABAP 7.52 and contains the SW component SAP ABAP 7.5C
• Starting from SAP S/4HANA 1809, SAP S/4HANA is built on top of ABAP Platform, which is the evolution of the
SAP NetWeaver platform and replaces it in SAP S/4HANA. The ABAP platform:
• Contains the SAP ABAP software component (not the classic SAP ABAP 7.50, but the new SAP ABAP 7.5D,
E, F, etc. as needed for SAP S/4HANA), SAP S/4HANA 2021 is on SAP ABAP 7.5G
• Is based on a new Kernel line (7.7x or higher instead of 7.53 used for old SAP NetWeaver)
• Will not be released as a standalone product (like the old SAP NetWeaver), but only as foundation of the
corresponding SAP S/4HANA system

16. 17
INTERNAL – SAP and Customers Only
How is SAP S/4HANA different from SAP ECC?
It allows multiple new techniques for extensibility
End-to-end security/End-to-end lifecycle management
Secured Connectivity
User Interface
Rules/Workflow
Process/Events
Data Replication
SAP S/4HANA
In-App Extensibility
Adopt existing or create
new user interface
Create custom
analytics
Expose data
Create forms/
email templates
Add application
logic
Create custom fields or
custom business objects
Classic
Extensibility
SAP Business
Technology Platform
Side-by-Side Extensibility
Refresh & mobilize
user experience
Cloud native
for B2C & B2B
Process
innovation
Data Marts
and Analytics
Data Science
and Intelligence
IoT and Big data
User Interface Layer Application Layer Database Layer

17. 18
INTERNAL – SAP and Customers Only
FPS01*
Feature Package Stack
(technically SPS01)
FPS02*
Feature Package Stack
(technically SPS02)
SPS03*
Support Package Stack
(technically SPS03)
SAP S/4HANA 2021
Support Package Stack for SAP S/4HANA 2021*
After general availability of SAP S/4HANA 2021, Feature Package Stacks (FPS)
and Support Package Stacks (SPS) contains stabilizations bundled with
corrections and legal changes. Customers benefit from this functionality as part of
their maintenance fee. First SPS of a new release can contain selected features
and are labelled Feature Package Stack (FPS) accordingly.
Support Package Stacks are compiled periodically and made available in the
SAP Support Portal
Q4 Q1 Q2 Q4
Q3
SAP S/4HANA 2022*
New release incl. new
technology stack
Maintenance Line
2023
Important Links
Restrictions and recommendations
regarding specific revisions of the SAP
HANA database for use in SAP S/4HANA
Release and maintenance strategy for
SAP S/4HANA
New release incl. new Technology Stack
(ABAP Platform 2021 and SAP HANA 2.0 SPS05
will be defined as minimal version for customers)
SAP S/4HANA 2021 - Restriction Note
2021 2022
Q4 Q1 Q2 Q3 Q4
OCT 13, 2021
2040
SAP S/4HANA release strategy
Release strategy for 2021 / 2022 and definition of deliveries
SAP S/4HANA Maintenance Commitment 2040:
SAP Business Suite 7 Maintenance Commitment 2027/2030:
Announcement on news.sap.com

18. 19
INTERNAL – SAP and Customers Only
• Starting with SAP S/4HANA 2023
• Stable two-year release cycle
• Three easy-to-adopt innovation shipments via Feature Packs every 6
months
• Mainstream maintenance duration for each release is expanded from 5 to 7
years
Taking the next evolutionary step towards a release strategy, which
better supports our customer base.
Since 2015, eight SAP S/4HANA releases have been delivered
Next level of product maturity: SAP S/4HANA 2023
Delivering completeness on Compatibility Scope alternatives and
concluding major overhauls.
SAP S/4HANA Has Reached Its Next Stage

19. SAP S/4HANA – Three transition scenarios

20. 21
INTERNAL – SAP and Customers Only
Type Approach Available for Purpose
System
conversion
(Tool: Software Update Manager)
New
implementation
(Tool: SAP S/4HANA migration
cockpit)
Selective Data
Transition
(Customer-tailored
(service/consulting offering)
Reusing
by
in-place
conversion
Bringing your business processes to the new
platform
 A complete technical in-place conversion of an existing ERP
software system in SAP Business Suite to SAP S/4HANA
 Adoption of new innovations at your speed
New implementation/reimplementation
 Reengineering and process simplification based on latest innovations
 Implementing innovative business processes with preconfigured
content on a new platform
 Performing initial data load
 Retiring old landscape
Value-driven data migration to the new platform
 You need more than master data and open items, i.e. transactional
data, complete or selected,
 migrate a selection of data (i.e. by organizational units),
 migrate data from more than one system, or
 migrate application related data into a S/4HANAbased solution
landscape
Standardized
Customer
tailored
Reengineering
with
data
migration
SAP ERP
SAP ERP or
third-party
system(s)
SAP S/4HANA
SAP ERP or
third-party
system(s)
Recap of the three transition scenarios
Overview of the different approaches to move to SAP S/4HANA
SAP S/4HANA
SAP S/4HANA
SAP S/4HANA
Cloud, private
SAP S/4HANA
Cloud, private
SAP S/4HANA
Cloud, private

21. 22
INTERNAL – SAP and Customers Only
Recap of the three transition scenarios
Scenario 1 – System Conversion
Scenario description
• A complete technical in-place conversion
of an existing SAP ERP system to
SAP S/4HANA (Database, SAP
NetWeaver and Application transition in
one step).
Why would you choose this Option?
• Bring your existing business processes to
the new platform.
• Keep your investments in custom specific
processes and developments
• Keep your complete data
• Mitigate the risk and investment of a big
bang conversion project by reducing the
scope of the transition project to a pure
technical conversion project, and adopt
new innovations at your speed at a later
point of time and in a phased approach.
(SAP GUI) / SAP Fiori
SAP HANA 2.0
SAP S/4HANA Core
SAP GUI
AnyDB / SAP HANA
SAP ERP Core
Software Update
Manager (SUM)
with Database
Migration Option
(DMO)
What How
In-place technical
conversion
tool-based technical conversion process of a SAP Business
Suite ERP system to SAP S/4 HANA using SAP Software
Update manager (SUM);
Downtime minimizing options available
*
*
SCN Blog: SAP S/4HANA System Conversion – At a glance
SAP ERP 6.0 (any EHP level)

22. 23
INTERNAL – SAP and Customers Only
Recap of the three transition scenarios
Scenario 2 – New Implementation
Scenario description
New implementation of SAP S/4HANA, e.g. for
customers migrating a legacy system, also known
as “greenfield” approach.
Why would you choose this Option?
Customers planning to
• re-design their SAP ERP solution based
processes on SAP pre-configured best practices
• migrate a non-SAP / 3rd-part legacy system,
• migrate an SAP ERP System on releases lower
than SAP ERP 6.0 not meeting the technical
prerequisites for a system conversion
Benefits for the customer are
• Reengineering and process simplification
based on pre-configured business processes
• Rapid adoption of new innovations in a
standardized manner
Steps How
Install SAP S/4HANA Software Provisioning Manager
Initial data load from
source system
• SAP S/4HANA Migration Cockpit
• SAP Data Services (SAP DS)
both with best practice migration content

23. 24
INTERNAL – SAP and Customers Only
A Selective Data Transition to SAP S/4HANA goes beyond a standard
new implementation or conversion. It includes a host of options, related
to the handling of software & data provisioning, requiring additional
expert services and tools to accomplish.
SAP strongly advises you to engage SAP Digital Business
Services or specialized SAP Partners equipped with the necessary
tools and experience with such an approach.
Reasons for selecting a Selective Data Transition approach:
• Large, multi-national corporation
• Multi-SAP ERP instance environment
• Business requirement to harmonize or to do just a partial redesign / leverage
partly today’s ECC installation
• Necessity to retain historic data in productive system
• Often effort intense & complex to load historical data
• Increased risk vs. other options
Recap of the three transition scenarios
Scenario 3 – Selective Data Transition
Download the Selective Data Transition Engagement whitepaper

24. 25
INTERNAL – SAP and Customers Only
Transition to SAP S/4HANA
Considerations when determining your transition path
Do current business processes support your long-term strategy?
Strategic redesign of business processes suggests a new implementation.
Can you adopt SAP Best Practices or will you retain past customizations?
A move to standardization brings agility, suggesting a new implementation.
Is your move to SAP S/4HANA driven by the business or IT?
IT sponsored projects are typically conversions to SAP S/4HANA, which lay the foundation for incremental
innovation projects driven by the business.
Can you convert from SAP ERP to SAP S/4HANA in a single step?
Single-step conversion is possible for SAP ERP 6.x (any enhancement pack) single stack, Unicode systems.
According to SAP statistics, a majority of our customers fulfill this criterion.
Do you require previous transactional data in the new system?
The requirement to retain all data in the system is a very strong indication for conversion. Alternatively, consider a new implementation if re-platforming your current ECC
data on commodity hardware or leveraging data retention solutions.
Is landscape consolidation and process harmonization a key value driver?
Consider a new implementation and consolidate the required configuration and data into that new system.
High or low number of interfaces to other systems (SAP and third-party)?
The higher the number of interfaces, the stronger is the case for conversion
Can your company sustain a multi-year innovation plan with incremental innovations?
If an incremental innovation is part of the company’s philosophy, a system conversion followed by innovative projects will lead to the desired outcome. If you are
uncertain whether a multi-year innovation plan can be sustained, a new installation is the only chance to harvest the full value.

25. SAP S/4HANA – Conversion project
Overview on some key activities

26. 27
INTERNAL – SAP and Customers Only
• Data model is simplified, some tables are not existing anymore
• Industries are “back to core”
• Some formerly included products are out of the core
• Some “old” features/transactions/reports have been
decommissioned or rebuilt
• Some features are now mandatory (Material ledger, Business
Partner..)
• Some formerly separated products are embedded in the core
• New architecture based on ABAP Platform
• New User Interface (SAP Fiori)
• New capabilities (Machine Learning, embedded analytics..)
• New processes
SAP S/4HANA – Conversion project – Overview on some key activities
How will the SAP S/4HANA differences impact the project?
Innovation =
Optional workload to bring
differentiating value
Simplification items =
Mandatory Workload
required to be live, which can
be, or not at same time
innovation

27. 28
INTERNAL – SAP and Customers Only
SAP S/4HANA – Conversion project – Overview on some key activities
Example of a simplification item
Example: The change of the MM-IM data
model - Attachment of SAP Note 2206980

28. 29
INTERNAL – SAP and Customers Only
The following activities are some key specific activities of a conversion project. For each of these activities,
there can be one or several tools, mandatory or optional.
Management of simplification item
impacts on components or applications
Downtime management
Customer/Vendor and finance data
consistency
Software and database change
Adaptation of custom code due to
simplification item impacts and move
to SAP HANA database
Management of the Business Partner
simplification Item
Reduction of custom code
Keep source and project landscape in
sync where needed
SAP S/4HANA – Conversion project – Overview on some key activities
Overview of the activities

29. 30
INTERNAL – SAP and Customers Only
time
Start Release: SAP ERP 6.0x
Manage simplification Item impacts and configure system
Identify and resolve inconsistencies (in each environment)
Run detailed (manual) Simplification Item (SI) Check
Retire unused custom code
Adapt custom code due to simplification item and SAP HANA
Clarify add-on status
Manage Business Partner
2nd SUM SI Check Analyze Transactional data
Customizing Checks
1st SUM SI Check
SUM Uptime SUM Downtime
Post conversion activities
on SAP S/4HANA
Preparation
and Migration
of Customizing
Data
Migration
Activities After
Migration
Conversion of Accounting
Target Release: SAP S/4HANA
SAP S/4HANA – Conversion project – Overview on some key activities
How is SAP S/4HANA different and how does this impact the project?
Preparation phase on SAP ECC

30. 31
INTERNAL – SAP and Customers Only
The SAP Roadmap Viewer gives you access to the
implementation, conversion or upgrade methodology for
multiple SAP products including SAP S/4HANA. It contains
many accelerators, organized by phases and streams,
including the pre-project phase
SAP S/4HANA Conversion project - planning elements
The SAP Roadmap Viewer Accelerator example: SAP S/4HANA sample
project plan

31. 32
INTERNAL – SAP and Customers Only
Project Mgmt.
Solution
Adoption
Application
Design and
Configuration
Data Management
Extensibility
Integration
Analytics
Testing
Technical
Architecture and
Infrastructure
Operations &
Support
Run
Realize Deploy
Explore
Prepare
SAP S/4HANA – Conversion project – Overview of recommended activities
Discover
Sizing & Scalability Verification
IT Infrastructure Setup
Trial
System
Provisioning
Execution / Monitoring / Controlling
Organizational Change Management (OCM)
Project
Initiation
Analytics Configuration
Integration Implementation
QAS Setup/Conversion
Data Migration & Verification
CC. Quality
Closing
Go
Live
Stop
Start
Strategic
Planning
Production
Cutover
Dress
Rehearsal
Hyper
Care
Transition
Planning
Transition
Preparation
Prototype
Handover
to
Support
Organization
Operate
Solution
Cutover
Preparation
Test Preparation & Execution
Configuration
Fit-to-Standard
Analysis / Design
Activate Solution
Application
Value
and
Scoping
Product Enhancements
Gap Validation
Security Design
Improve
&
Innovate
Solution
Learning Design Learning Realization
Security Implementation
UX Activation and Design
Team Enablement
DVM Design DVM Configuration & Execution
Integration Validation
Design Review
Sizing
Technical Design
Tech. Architecture and
Infrastructure Definition
Operations Impact Evaluation Operations Implementation
Custom Code Impact
Analytics Design
Test Planning
DEV Setup/Conversion
Integration Design
Data Migration Design
Operations
Readiness
Sandbox Setup/Conversion
Quality Gates Task / Activity
QG2 QG4
QG3 QG5
QG1

32. SAP S/4HANA Conversion project -
planning elements

33. 34
INTERNAL – SAP and Customers Only
SAP S/4HANA Conversion project - planning elements
The “Mapping Your Journey to SAP S/4HANA - A Practical Guide for senior IT Leadership” guide
This guide is a practical,
condensed, down-to-earth
handbook for executives,
project managers, decision-
makers, and senior IT
leaders. It summarizes our
combined experience from
over 5,000 SAP S/4HANA
migration projects we’ve
seen so far.
Download it from this link.

34. 35
INTERNAL – SAP and Customers Only
SAP S/4HANA Conversion project - planning elements
Typical duration of SAP S/4HANA transition to date: 11 months
Majority of S/4HANA customers went
live in 8-14 months
Duration of projects is largely determined by customer complexity (degree
of change) and implementing partner preferences / tools / methodologies
SAP S/4HANA transitions: the “outliers”
Duration of very large and complex S/4HANA implementations
Simple S/4HANA Finance
implementations
Typical S/4HANA
system conversion
Typical S/4HANA (full suite)
implementations
As short as As long as
Average
(Median)
3months 11months 7months
4months 12months 8months
6months 15months 11months
Complex S/4HANA (full
suite) implementations at
the largest customers
10months 36months 18months
Months to implement SAP S/4HANA (Illustration)

35. 36
INTERNAL – SAP and Customers Only
SAP S/4HANA Conversion project - planning elements
Actual findings from customer projects & recommendations
• For SAP ERP on any DB customers a two step approach via SAP ERP on SAP HANA has in general no significant benefits.
Individual exceptions may make sense in case of for non-Unicode systems & for SAP ERP Systems releases < SAP ERP 6.0)
• System conversion projects are in average shorter and cost less than new implementation projects
→ Many customers choose system conversion for doing a ‚technical uplift‘ to SAP S/4HANA. intensive adoption of new SAP
S/4HANA applications and Fiori UI Technology is often addressed in follow-up projects.
• SAP S/4HANA Finance and SAP S/4HANA projects have pretty much the same project duration
→ In general a two steps approach by moving to SAP S/4HANA via SAP S/4HANA Finance does not make sense
• Two steps approach with Central Finance
→ For those companies in which a central financial department is a key component of the current or future business architecture,
SAP recommends starting with SAP S/4HANA for central finance and planning for the system conversions of each of the source
SAP ERP instances later on.
→ However, the perception of SAP S/4HANA for central finance as a “first stepping-stone” in a transition to SAP S/4HANA in just any
landscape is misleading. In particular, companies with a single SAP ERP instance should retain their landscape design and focus
on the standard options.

36. 37
INTERNAL – SAP and Customers Only
Transition Project
Further Business
Process
Transformation
Technical Migration
Initial Business
Process
Transformation
SAP S/4HANA Conversion project - planning elements
Deciding when Business Process Transformation should occur
System Conversion + Selective Innovation
System Conversion with additional / full scope of Business Process Transformation (aka‘Big Bang‘)
Separate, single implementation projects
(i.e. Business Process redesign, new
Applications, Fiori UX, Analytics etc.)
Mandatory Simplifications (i.e. in FI,
SD, MM, .. area) plus some focused,
selected innovations
Go-Live
✓ In the transition project, not only Mandatory Simplification but Business Process Transformation should be included to
some extent.
✓ Further Business Process Transformations should be conducted gradually after Go-Live to enjoy new innovations.
Project
preparation
37
System Conversion

37. 38
INTERNAL – SAP and Customers Only
SAP S/4HANA Conversion project – planning elements
Suggested pre-project activities (if not done before, start as soon as possible within)
Sandbox / Trial
Project
start
Custom code worklist
Workload assessment
Budgeting
Partner
selection
Internal
team and
Partner
available
Simplification items impacts evaluation
Landscape impacts
SAP
Readiness
Check
CVI / SIC
Maint. Planner
Add-ons
Source system pre-req.
Target system preparation
Inconsistencies fixing
SUM & Fin
Conversion
ATC installation &
config
Custom code impact workload
assessment

38. 39
INTERNAL – SAP and Customers Only
Conversion 2
SAP S/4HANA Conversion project - planning elements
The conversion process will occur multiple times during the project
QA Conversion
Purposes
• Convert the QA
environment to SAP
S/4HANA
• Enhance cookbook
• Test Integration
• Functional regression
• Operational readiness
• User acceptance
DEV Conversion
Purposes
 Convert the DEV
environment to SAP
S/4HANA
 Refine cookbook
 Perform mandatory
code adaptations and
simple code
optimizations
 Perform post-
conversion steps to
adapt business
processes
 Configure new
processes and
features
Copy of production
Purposes
• Test conversion steps
with copy from
production
• Familiarize with
process before
working on DEV/QA
and production
• Estimate downtime
• Identify finance issues
which are not
appearing in the
consistency checks,
but detected during
finance conversion
(post SUM)
• Initiate conversion
cookbook
Test Conversion
(1 to n times)
Conversion 1
PRD Conversion
Purposes
 Convert the PRD
environment to SAP
S/4HANA
Note
 Execute end-to-end
conversion precisely
as defined within
cutover plan and
cookbook
Conversion 3
Copy of production
Purposes
 Finalize & validate
cutover plan
 Finalize & validate
cookbook
 Validate the total
downtime duration
and optimize if
needed
 Test environment:
− Infrastructure testing
− Post-cutover
operational
performance testing
Dress Rehearsal
(1 to n times)
Data consistency issues identified, for correction in production
Corrections implemented before system copy, task is reduced in next runs based on copy of production

39. SAP S/4HANA Conversion Project – RISE
with SAP

40. 41
INTERNAL – SAP and Customers Only
Building YOUR Intelligent Enterprise
 Take your next step towards an intelligent enterprise:
Resilience and low TCO with infrastructure of choice
• SAP Data Center
• IaaS Provider Infrastructure
• Customer Data Center
• Scalability option based on the growth of your
business
• Technical operations excellence by SAP
◼ Single point of contact
◼ One set of SLAs
Business
process
intelligence
(BPI) &
Signavio
SAP
Business
Technology
Platform
SAP Business
Network
Starter Pack
SAP S/4HANA Cloud
(Public or Private)
Flexibility to
choose
infrastructure
provider
Premier Value
Simplified
Engagement
Guided Journey
SAP Launchpad Service & Mobile Start App,
Custom Code Migration,
SAP Readiness Check,
SAP Cloud ALM,
SAP Enable Now,
SAP Learning Hub
Driving business
innovation together
RISE with SAP

41. 42
INTERNAL – SAP and Customers Only
SAP S/4HANA - Deployment Options
High level picture of SAP S/4HANA consumption
Customers who desire:
• A complete, modern, native SaaS ERP
solution with the full benefits of
public cloud
• The fastest path to innovation and
the lowest TCO
• A clean Cloud ERP solution without
converting old/legacy ERP processes
and configurations.
• To reimagine business processes and
take advantage of standardized best
practices
Customers who desire:
• A rapid conversion of their existing
ERP/ECC environments to a Cloud-based
architecture
• The flexibility of a traditional on-premise
application as well as subscription-based,
cloud economics
• Gradual transformation to a pure SaaS
landscape at their own pace
• Full, extensive, ERP functionality including
partner add-ons with the ability to extend
and enhance
Customers who require:
• Complete control and ownership of
their application and data landscape
• The ability to manage unique, customer-
specific needs which cannot be
addressed by public cloud or private
cloud offerings
• The utilization of their existing IT
departments, infrastructure, budget,
and IaaS vendor agreements
• Specific compliance with industry- and
country-specific regulatory requirements
SAP S/4HANA Public Cloud SAP S/4HANA Private Cloud SAP S/4HANA On-Premise
RISE with SAP
To learn more about cloud deployment, listen to the session:
The Path to SAP S/4HANA, Choosing the Right Cloud
Deployment for Your Business

42. 43
INTERNAL – SAP and Customers Only
• SAP S/4HANA is a new product, which is very different from SAP ECC/ERP, and this will influence
your conversion project in many aspects
• Starting a given list of activities prior to the project, or at the beginning of the project, will save
significant time and can avoid some showstoppers.
• It is very important to decide if the project will include innovation in some aspects (technical and/or
functional) since this will change the workload of your project.
• Conversion will occur multiple times during the project. It is recommended with a trial conversion
based on a copy of production, or even several trials.
• The “Mapping Your Journey to SAP S/4HANA - A Practical Guide for senior IT Leadership” guide is a
key document to better understand key elements of a transition to SAP S/4HANA, while the SAP
Roadmap Viewer helps you to understand the most common tasks for each workstream
• SAP S/4HANA conversion transition path is available for both SAP S/4HANA On-Premise or SAP
S/4HANA Cloud, Private Edition.
Key takeaways

43. Thank you.
Contact information:
© 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.
Sabrina Autier
mailto:sabrina.autier@sap.com

44. Additional resources

45. 47
INTERNAL – SAP and Customers Only
SAP S/4HANA reality – Comparison of SAP ECC on HANA and SAP S/4HANA
Project durations are very similar indicating high
importance of customer specific factors for project
management, not product features.
Top reasons why you should skip SAP ECC on
SAP on HANA and go directly to SAP S/4HANA:
• SAP ECC on SAP HANA project almost
doubles your effort
• SAP S/4HANA makes operational reporting
easier than SAP ECC on SAP HANA
• SAP S/4HANA has been re-architected for
SAP HANA while SAP ECC on SAP HANA is
not
➔ SAP ECC on SAP HANA is not a head start for SAP S/4HANA

46. 49
INTERNAL – SAP and Customers Only
SAP S/4HANA 2021 Fully Activated Appliance
The Software Appliance Concept
Software
Configuration
Walk-
throughs
Create your own pre-configured system
in a fraction of the usual setup time
SAP S/4HANA 2021 &
additional components
SAP Best Practices &
technical settings
Sample data &
demo scenarios
More information:
• Overview blog
• Demo scenarios
• Try out as S/4HANA 30-day trial
• Detailed How-To videos
*SAP S/4HANA 2021 SP00 version is planned for end of Q4 2021.
Until then the most recent appliance release (SAP S/4HANA 2020 FPS02) can be used.
In 1-2 hours via SAP Cloud Appliance Library
(SAP CAL), hosted in AWS / MS Azure / GCP
In 2-3 days when deploying on own physical
hardware
Use cases:
Trial / Sandbox / PoC / Scoping
Open to customers, partners, public users, and
SAP employees
SAP S/4HANA 2021*,
Fully-Activated Appliance