Week 1 Unit 2:

Transition to SAP S/4HANA

Transition to SAP S/4HANA
Adoption journey highlights

Let’s watch a brief video explaining

the adoption journey.

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

Transition to SAP S/4HANA
The 3 transition scenarios

ERP System On-Premise  Example: New or existing SAP customer

New implementing a new SAP S/4HANA system
Implementation
Non-SAP System with initial data load
Cloud

 Example: Complete conversion of an

System On- existing SAP Business Suite system to SAP
ERP System
Conversion Premise
S/4HANA
SAP S/4HANA

ERP System
- Region A - On-Premise
 Examples: Consolidation of current regional
Landscape ERP System SAP Business Suite landscape or selective
Transformation - Region B - data transformation into one global SAP
ERP System S/4HANA system
Cloud
- Region C -

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 3

Transition to SAP S/4HANA New
Implemen-
ERP System
On-
Premise

tation
Scenario: New implementation Non-SAP System Cloud

Scenario description SAP S/4HANA SAP S/4HANA

SAP ERP 6.0 or
On-Premise Edition Cloud Edition
New implementation of SAP S/4HANA, e.g. for higher Option: Initial data
customers migrating a legacy system, also known load from legacy
as “greenfield” approach. or SAP system SAP Fiori

Non-SAP SAP S/4HANA Core

Benefits for the customer
Legacy SAP HANA
+ Reengineering and process simplification based
Any customers legacy
on ready-to-run business processes
system
+ Predefined migration objects & best practices
available with guided configuration
Steps How
+ Reduce time to value and customer total cost of
ownership
Install SAP S/4HANA Software Provisioning Manager
+ Rapid adoption of new innovations
• SAP source via direct system connection
Project duration parameters • Legacy system via file upload
Initial data load from
 Number of data migration objects (Material,
source system Tools used are:
Customer, Vendor, etc.)
• SAP Data Services (SAP DS) for On-Premise
 Volume and complexity per data migration object • SAP Landscape Transformation (SAP LT) for Cloud

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 4

Transition to SAP S/4HANA System
Conversion
ERP System
On-
Premise

Scenario: System conversion SAP S/4HANA

Scenario description SAP S/4HANA

On-Premise Edition
Customers who want to convert their current
system into an SAP S/4HANA system. Database,
SAP NetWeaver and application transition in one SAP GUI (SAP GUI) / SAP Fiori
step. SAP ERP Core SAP S/4HANA Core

Benefits AnyDB / SAP HANA SAP HANA

+ Migration without re-implementation

+ No disruption for existing business processes Steps How
+ Re-evaluation of customization and existing Check add-ons and Check add-ons, business functions, and industry solutions using the
process flows industries maintenance planner to ensure compatibility with SAP S/4HANA.
• Execute pre-checks for all software components to validate further
Project duration parameters Check components
prerequisites within the system
and code for
 Technical: Number of systems and source Optional step at any time:
SAP S/4HANA
database size • Custom code check tool identifies scope and data structure conflicts based
compatibility
 Functional: Number of company codes, ledgers, on the SAP S/4HANA Simplification Database content.
operating concerns, etc.
Run the actual conversion to SAP S/4HANA in one step using the database
Run the conversion
migration option of Software Update Manager (DMO of SUM).

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 5

 ERP System
Transition to SAP S/4HANA Landscape
Transfor-
- Region A -
ERP System
- Region B -
On-
Premise

Scenario: Landscape transformation mation ERP System

- Region C -
Cloud

Scenario description
SAP S/4HANA SAP S/4HANA
On-Premise Edition
Customers who want to consolidate their Consolidation or
Cloud Edition

landscape or to selectively transform data into an selective data

SAP S/4HANA system transformation based (SAP GUI) / SAP Fiori

on SAP Landscape SAP S/4HANA Core

Benefits
Transformation tool
+ Selective data transformation allows a phased SAP HANA
approach, focusing on parts of the business with
highest ROI and lowest TCI
+ System and landscape consolidation with
harmonized/simplified processes and unified Steps How
master data lead to lower TCO Consolidate clients from different source systems into one
Consolidation new or existing SAP S/4HANA system using the SAP
Project duration parameters Landscape Transformation (SAP LT) tool.

 General: Depending on the selected sub-scenario • Carve-out of single entities or processes

(System Consolidation, Selective Migration, • Migration of selected SAP applications (example: Central
Selective Data
Central Finance) Finance)
Transformation
 Specific: Number of systems to be consolidated, Tool used is:
volume of selected data • SAP Landscape Transformation (SAP LT)

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 6

Transition to SAP S/4HANA
Services path to SAP S/4HANA
Planning and safeguarding as part of each Premium Engagement for SAP S/4HANA
Discover Prepare / Explore Realize / Deploy

New Implementation
Innovation Strategy & Roadmap

S/4HANA Value New Implementation

Discovery On SAP S/4HANA
on-premise and cloud
S/4HANA Value & Implement
Implement
Implementation innovations
Readiness Check

additional
Strategy

Technical
Migrate Existing
Landscape Transformation Installation and
+ industry / LOB
packages
Architecture & Business-driven migration data transition for
Infrastructure offerings SAP S/4HANA

Migration System Conversion

Planning Technology-driven migration
offerings

Premium Engagements

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 7

Thank you

Contact information:

open@sap.com
© 2016 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.

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. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

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 SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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 platform 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, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 9