SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to...

40
CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE Germany June, 2017

Transcript of SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to...

Page 1: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

CUSTOMER

SAP S/4HANAKey adoption scenarios to considerChristian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE – Germany

June, 2017

Page 2: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

2Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

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.

Page 3: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

3Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Introduction

System Conversion

System Requirements

Simplification List Approach

SAP Readiness Check

Tools Overview

SAP Transformation Navigator

SAP Migration Cockpit

SAP Best Practice Explorer

Additional Information

Agenda

Page 4: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

Introduction

Page 5: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

5Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

SAP S/4HANA 1709Release strategy for 2017/2018 and definition of deliveries

FPS01*Feature Package Stack

(technically SPS 01)

FPS02*Feature Package Stack

(technically SPS 02)

SPS03*Support Package Stack

(technically SPS 03)

SAP S/4HANA 1709 SPS00*New release incl. new

technology stack

(NetWeaver AS ABAP 7.52 for S/4HANA,

SAP HANA 2.0 SP01)“

Support Package Stack for SAP S/4HANA 1709*

After general availability of SAP S/4HANA 1709, 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 Service Marketplace

Important SAP Notes

Release Information Note

Not available yet

Restriction Note

Not available yet

2017 2018

Q4 Q1 Q2 Q4Q3

SAP S/4HANA 1809

SPS00*New release incl. new

SAP NetWeaver Stack

Maintenance Line

2019

Q4 Q1 Q2 Q3 Q4

* This is the current state of planning and may be changed by SAP at any time without notice.

Page 6: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

6Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Adoption Paths

New

Implementation

System

Conversion

Landscape

Transformation

EXAMPLE:

New or existing SAP Customer

implementing a new SAP S/4HANA

system with initial data load

EXAMPLE:

Complete conversion of an existing

SAP Business Suite system or selective

EXAMPLE:

IT Consolidation: Merge of multiple source

systems into one new/existing S/4HANA

System

On-Premise

S/4HANA Cloud

On-Premise

On-Premise

S/4HANA Cloud

ERP System

ERP SystemRegion A

ERP SystemRegion B

ERP SystemRegion C

SAP S/4HANA

Third-partySystem

Page 7: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

7Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

SAP S/4HANA – TransitionScenario 1 – New Implementation

Scenario description

New implementation of SAP S/4HANA e.g. for

customers migrating a legacy system.

Legacy

Any customers

legacy system

Option: Initial

data load from

Legacy or SAP

System with

Migration

Cockpit

What How

Install S/4HANASWPM (Software

Provisioning Manager)

Initial data load

from source

system

SAP S/4HANA Migration

Cockpit

• Legacy system via file

upload

• optional: SAP Data Services

with predefined migration

content

1

2

(SAP GUI) / SAP Fiori

SAP HANA

SAP S/4HANA Core

Page 8: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

8Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

SAP S/4HANA – TransitionScenario 2 – System Conversion

Scenario description

Customers who want to change their

current system into a SAP S/4HANA

system.

Database, SAP NetWeaver and

Application transition in one step. (SAP GUI) / SAP Fiori

SAP HANA

SAP S/4HANA Core

SAP GUI

AnyDB / SAP HANA

SAP ERP Core

Software Update

Manager (SUM)

with Database

Migration Option

(DMO)

What How

Installation

and

migration

Rapid Database Migration of

SAP Business Suite to SAP

S/4 HANA (all one step

migration, including SAP

S/4HANA Finance /

S/4HANA “logistics

components” conversion)

using SUM with DMO

*

*

Page 9: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

9Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

SAP S/4HANA – TransitionScenario 3 – Landscape Transformation

Scenario description

Customers who want to consolidate their

landscape or carve out selected entities or

processes into an existing SAP S/4HANA

system.

Selective Data

Migration

service (SLO)

with SLT

What How

Install (and

configure)

S/4HANA

SWPM (Software

Provisioning Manager)

“Carve Out”

Selective Data Migration

service SLO (System

Landscape Optimization)

with SLT (SAP Landscape

Transformation)

Individual harmonization

project required

2

12

(SAP GUI) / SAP Fiori

SAP HANA

SAP S/4HANA Core

1

SAP GUI

AnyDB or SAP HANA

SAP ERP Core

SAP GUI

AnyDB or SAP HANA

SAP ERP Core

Page 10: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

10Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Choice of Deployment

On-Premise and Cloud share following characteristics for consistency

at every level of your enterprise:

Share same code line

Designed for in-memory

Same simplified data model

Improved use experience

Important considerations:

Scope of business functionality

Deployment times

Update frequency

Customizations

Regulatory, industry, and regional requirementsOn-Premise Cloud

Page 11: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

System ConversionSystem Requirements

Simplification List Approach

SAP Readiness Check

Page 12: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

12Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

SAP S/4HANASystem Conversion – Transition Paths Overview

AnyDB or SAP HANA

SAP ERP 6.0, EHP xxSAP HANA

SAP Simple Finance,

on-premise edition 1503

AnyDB

SAP HANA

SAP S/4HANA

Finance 1605

SAP HANA

SAP S/4HANA 1610

System Conversion Paths (basically)

From SAP Business Suite

(ERP6.0, EHP xx, AnyDB or SAP HANA DB)

to SAP S/4HANA Finance

From SAP S/4HANA Finance

to SAP S/4HANA 1610 FPS02

One-Step-Procedure

Note 1: For older SAP Business Suite releases or systems on Non-Unicode an additional

step to SAP ERP 6.0 EHPxx is required.

• The transition to SAP S/4HANA does not require

the source system to be already on SAP HANA

Database

• SAP S/4HANA Simple Finance, on-premise edition

1503 was the first offering under the

SAP S/4HANA product family

• The decision to go for SAP S/4HANA Finance should be based on the business benefits,

but is not a mandatory prerequisite for any

system conversion

1

2

3

1

2

3

Note 2: System has to be an AS ABAP-only system. Dual-stack systems (AS ABAP and AS Java combined in one system) are not

supported for the conversion. If your system is as dual-stack system, you have to split it before doing the conversion.

From SAP Business Suite

(ERP6.0, EHP xx, AnyDB or SAP HANA DB)

to SAP S/4HANA 1610 FPS02

Page 13: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

13Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

SAP S/4HANASystem Conversion – Transition Paths Overview (1/2)

AnyDB or SAP HANA

SAP ERP 6.0, EHP xx

SAP HANA

SAP Simple Finance,

on-premise edition 1503

SAP HANA

SAP HANA

SAP S/4HANA 1610 Start Release Target Release Availability Remarks

SAP ECC 6.0 EHP 0-7SAP Simple Finance,

on-premise edition 1503available since:

Q1/2015

Migration to SAP HANA DB [if required], Installation of

Software [EHP7 + sFIN])

SAP ECC 6.0 EHP 0-8SAP S/4HANAFinance 1605

available since: Q2/2016

Migration to SAP HANA DB [if required], Installation of

Software [EHP8 + sFIN])

SAP ECC 6.0 EHP 0-8 SAP S/4HANA 1610 available since:

Q4/2016

Migration to SAP HANA DB [if required], Installation of

S4CORE Software

System Conversion fromSAP S/4HANA Finance to SAP S/4HANA

Upgrade within theSAP S/4HANA product family

System Conversion fromSAP Business Suite to SAP S/4HANA

2

3

1

1

2

3

See SAP Note 2261242 and SAP Note 2185245 for more details

SAP S/4HANA

Finance 1605

Page 14: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

14Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

SAP S/4HANASystem Conversion – Transition Paths Overview (2/2)

SAP HANA

SAP Simple Finance,

on-premise edition 1503

SAP HANA

SAP HANA

SAP S/4HANA, on-

premise edition 1511

SAP HANA

SAP S/4HANA 1610

8

96

SAP S/4HANAFinance 1605

SAP S/4HANA 1610 available since: Q4/2016

SAP Simple Finance, on-premise edition

1503

SAP S/4HANA 1610 available since: Q4/2016

SAP Simple Finance, on-premise edition

1503

SAP S/4HANAFinance 1605

available since: Q2/2016

AnyDB or SAP HANA

SAP ERP 6.0, EHP xx

7

SAP S/4HANA, on-premise edition 1511

SAP S/4HANA 1610

Installation of S4CORE Software

Installation of S4CORE Software

Installation of sFINSoftware (Upgrade)

available since: Q4/2016

InstallationSoftware (Upgrade)

System Conversion fromSAP S/4HANA Finance to SAP S/4HANA

Upgrade within theSAP S/4HANA product family

System Conversion fromSAP Business Suite to SAP S/4HANA

Start Release Target Release Availability Remarks

6

7

8

9

NOT SUPPORTEDSAP S/4HANA

Finance 1605

Page 15: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

15Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Simplification List as Microsoft Excel File

Follow this link to SAP Note 2313884

Beside the Simplification List as PDF on the SAP Help Portal the

Simplification List is available additionally in XLS format as

attachment of SAP Note 2313884. In this note you can find

different Microsoft Excel Spreadsheets for the different SAP

S/4HANA releases. The Simplification List 1610 spreadsheet does

contain the following information:

» Simplification Items which are new with SAP S/4HANA 1610

» Simplification Items which are relevant for the upgrade from

SAP S/4HANA, on-premise edition 1511 to SAP S/4HANA 1610

» Simplification Items related to SAP Add-On Portfolio and

Project Management (PPM)

» Simplification Items which are as well relevant for customers

coming from SAP S/4HANA Finance 1605 or SAP Simple

Finance, on-premise edition 1503

Page 16: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

16Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Discovery / Prepare Phase Realize Phase

tt2

Maintenance Planner

Pre-ChecksCustom Code

Migration WorklistSoftware Update Manager (SUM)

Application specific follow-on activities

t5 t6

Simplification List SAP S/4HANA

System Conversion – SAP Readiness CheckBasic Sequence

Database Migration

Software Update

Data Conversion

System Requirements

t1

SAP Readiness Check

t3 t4

See SAP Note 2290622

Page 17: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

17Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Approach

1. Prepare source system– Minimum release: SAP ERP 6.x EhP0 on any database

– Help portal: https://help.sap.com/viewer/p/SAP_READINESS_CHECK

– SAP Readiness Check tool preparation note: SAP Note 2290622

2. Execute program SAP Readiness Check– Via your local SAP Solution Manager system (recommended)

– Via our direct cloud upload

3. Explore results to start Conversion project– Recommendations dashboard per system, sent via email as url link

– Engage SAP Digital Business Services or your preferred implementation partner

Page 18: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

18Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Demo: SAP Readiness Check

T-code: SE38

execute report: AGSRC_START_ANALYSIS

Result URL:

Page 19: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

19Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Active Business Functions

Page 20: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

20Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Custom Code Analysis

Page 21: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

ToolsSAP Transformation Navigator

Page 22: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

22Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

TomorrowQuestionsToday

Give me guidance, not choices!

Moving to an application landscape centered on SAP S/4HANA

Integration?

Value of

innovation?

Cost of new

solution?

Which solution to use in

which use case?

Cost of

migration?

?

Path to get

there?

Page 23: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

23Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Demo: SAP Transformation Navigator

Follow this link to SAP Transformation Navigator

Page 24: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

24Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Page 25: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

25Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Page 26: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

26Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Page 27: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

ToolsRoadmap Viewer

Page 28: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

28Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Transition to SAP S/4HANA

Follow this link to Roadmap Viewer

Page 29: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

ToolsMigration Cockpit

Page 30: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

30Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

SAP S/4HANA 1709Migration Cockpit*

Scenario description

New System Installation of SAP S/4HANA e.g.

for customers migrating a legacy system.

Legacy

Any customers

legacy system

Option: Initial

data load from

Legacy or SAP

System with

Migration

Cockpit

What How

Install S/4HANASWPM (Software

Provisioning Manager)

Initial data load

from source

system

SAP S/4HANA Migration

Cockpit

• Legacy system via file

upload

• optional: SAP Data

Services with predefined

migration content

1

2

SAP Fiori

SAP HANA

SAP S/4HANA Core

Migration Cockpit• Enhancement from the Migration Cockpit allow the data migration from SAP source

systems directly to SAP S/4HANA (via RFC connection).

• So customer does not need to extract the data into files but can directly load data from

Business Suite System to SAP S/4HANA.

* This is the current state of planning and may be changed by SAP at any time without notice.

Page 31: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

31Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

SAP S/4HANASAP S/4HANA Migration Object Modeler

The SAP S/4HANA Migration Object

Modeler is a design tool to enhance,

create or adjust migration objects used in

the Migration Cockpit. It is used to

integrate newly created objects and/or

customer specific enhancements to SAP

preconfigured migration objects.

You can adjust the source structures, get

an overview of the target structures

associated with the migration object, use

structure and field mapping.

It is available for the SAP S/4HANA 1610.

Page 32: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

ToolsSAP Best Practice Explorer

Page 33: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

33Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

SAP Best Practices Explorer

Follow this link to SAP Best Practice Explorer

Page 34: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

Additional Information

Page 35: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

35Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Product Page – SAP Help

You can find the “What’s New” and the “Feature Scope Description” with

the entire information concerning the SAP S/4HANA 1610 FPS02

delivery on the SAP HELP Page.

http://help.sap.com/s4hana

Page 36: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

36Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

SAP S/4HANACheck out the following links for more information

Follow this link to the Book

Page 37: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

37Customer© 2017 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Customer

Information about SAP S/4HANA 1709

Innovation Discovery SAP S/4HANA Road Maps

Page 39: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

Thank you.

Christian Vogler

SAP S/4HANA Product Management and Co-Innovation

[email protected]

Page 40: SAP S/4HANA Key adoption scenarios to consider...CUSTOMER SAP S/4HANA Key adoption scenarios to consider Christian Vogler, SAP S/4HANA Product Management & Co-Innovation, SAP SE –Germany

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 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,

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

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