Transition Paths to SAP S/4HANA...SAP S/4HANA Core SAP GUI AnyDB / SAP HANA SAP ERP Core Software...

Public

TEC114

Transition Paths to SAP S/4HANA

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

Speakers

Las Vegas, Oct 19 - 23

Frank Densborn

Barcelona, Nov 10 - 12

Dr. Jochen Freudenberg


Disclaimer

This presentation outlines our general product direction and should not be relied on in making a

purchase decision. This presentation is not subject to your license agreement or any other agreement

with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to

develop or release any functionality mentioned in this presentation. This presentation and SAP's

strategy and possible future developments are subject to change and may be changed by SAP at any

time for any reason without notice. This document 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. SAP assumes no responsibility for errors or omissions in this

document, except if such damages were caused by SAP intentionally or grossly negligent.


Agenda

SAP S/4HANA: New product

Deployment options of SAP S/4HANA: One codeline, different products

Transition to SAP S/4HANA: 3 scenarios

Major elements of transition process

New implementation

System conversion

Landscape transformation

Supporting services

Questions

Public

SAP S/4HANA: New product


SAP S/4HANAOur next-generation business suite

SAP S/4HANA Enterprise Management

is SAP’s next-generation Digital Core

Innovative in-memory database

New architecture and data models

Renewed applications

New UI technology

Cloud & on-premise deployment models

Natively integrated

SAP S/4HANA is a new product line.

The classical SAP Business Suite & SAP ERP is a separate product line and will still be available.

Public

Deployment options of SAP S/4HANA:

One codeline, different products


High level stack architecture SAP S/4HANALogical view

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

SAP S/4HANA Architecture

differs from the classical

Business Suite architecture

Data structures(Compatibility provided through Core Data

Services)

Application engines

Launchpad / SAP Fiori(SAPGUI for Windows still available for

compatibility reasons)

SA

P W

EB

DIS

PA

TC

HE

R

SA

P M

OB

ILE

PL

AT

FO

RM

SAP HANA

Database Tables

S/4HANA ABAP

Analytics

CDS View

SAP Gateway

Fiori Shell

Fiori Apps

(UI5)

Fiori Launchpad

(Homepage)Search

(Enterprise-)Search

planned

Transactional Logic

SAP Screen Personas

Web GUI for SAP

Web Dynpro

oDatahttps oData INA


SAP S/4HANAOne code line, different products

Following the “principle of one”, SAP S/4HANA will offer all main features* in different

deployment options

SAP S/4HANA

Development

Classical Suite

Selected

corrections

SAP S/4HANAOn-premise Edition

SAP S/4HANACloud Edition

*Detailed product features may differ in

different deployment options

Dev.

Consolidation

Public

Transition to SAP S/4HANA:

3 scenarios


Landscape

Transformation

ERP System - Region A -

ERP System - Region B -

ERP System - Region C -

Example: Complete conversion of an

existing SAP Business Suite system to SAP

S/4HANA

Example: Consolidation of current regional

SAP Business Suite landscape into one

global SAP S/4HANA system or selective

data migration

On-Premise

S/4Cloud

System

Conversion

SAP S/4HANA

Example: New or existing SAP customer

implementing a new SAP S/4HANA system

with initial data load

ERP System On-Premise

Transition to SAP S/4HANAThe 3 transition scenarios

New

Implementation

On-Premise

S/4Cloud

ERP System

Non-SAP System


Transition to SAP S/4HANAThe 3 transition scenarios (2)

The transition scenarios differ with

respect to amount & type of data

taken over

New installation: Master Data & selected

transactional data

System conversion: ‘entire’ repository

De

gre

e o

f

Sta

nd

ard

izati

on

Size of repository

to be kept

Cloud „Quadrant“

Rule of thumb:

Cloud deployment model when

simplification is ultimate goal

On-premise deployment model is

universally suited


Transition to SAP S/4HANA“Activation” of innovation

Generally, a transition to SAP

S/4HANA includes innovations in

business scenarios

SAP recommends to adopt these

innovations but provides

compatibility options

Core Data Services provide compatibility for

read access (e.g. custom code)

Classic SAP GUI transactions remain

available. Innovations consumed via Fiori UI

Integration to other systems remain

Inn

ova

tio

n

Time

Mandatory

adjustments

Mandatory

adjustments

HANA

optimization

of custom

code

Mandatory

adjustments

HANA

optimization

of custom

code

Adapting

new

Business

Processes

Possible SAP S/4HANA consumption

approach(within same version)

Public

Major elements of transition process


Transition to SAP S/4HANAMajor elements of deploy phase in transition process

1

Preparation

2

Technical Implementation

3

Semantical Adoption

Preparation steps on start release

Analysis of used business processes – mapping to

SAP S/4HANA innovations

Identify required integration scenarios of target state

Run pre-Transformation Checks on source system

Used functionality, supported industries, available

add-on, custom code …

Mandatory preparation steps to be executed on

source system.

“Installation” of SAP S/4HANA

o SAP HANA Database

o SAP S/4HANA application core

Customizing adjustment

Adjustment of technical infrastructure

Adapt custom code to comply with SAP

S/4HANA scope & data structure

Adapt business processes to leverage

new SAP S/4HANA innovation

functionality

Adapt integration (if applicable)

Implement SAP Fiori UIs

Introduce new SAP S/4HANA

innovation scenarios


Transition to SAP S/4HANAMajor elements of deploy phase in transition process (2)

1

Preparation

2

Technical

Implementation

3

Semantical

Adoption

Duration

(illustrative)

Configuration of (new)

Business Processes & Test

Rollout

Technical procedure

Planning & Preparation

Variable parts depending on

individual situation


SAP S/4HANA Preparation phase – Assessment options

Semantical assessment –

Simplification List

A Technical system assessment –

SAP S/4HANA transition pre-checks

B

Technical system assessment –

Custom Code Analysis

C


SAP S/4HANA – Custom code adaption

Simplification Database(delivered by SAP via SAP Service

Marketplace)

Lists of objects with incompatible

changes in SAP S/4HANA +

corresponding SAP notes describing how

to adapt to the changes.

SAP will provide tools, which allow customers before the conversion (upgrade) to SAP S/4HANA to assess the

impact of SAP S/4HANA simplifications on customer coding, as well as guidance how to adapt the coding.

Migration Analysis Tool

Customer system

before the conversion

to SAP S/4HANA

SAP Notes giving guidance for

each Simplification/type of change

how to adapt customer code.

Referring

to

Customer objects affected by the changes

(with Navigation to IDE)

Analyze customer code and extract

usage of SAP objects

Compare to lists of SAP objects with

incompatible changes in SAP

S/4HANA

Show customer objects affected by

the changes


Migration Phase

MUST-Do Tasks

WILL-Do Tasks

Automated Tasks

After Go–Live Phase

Preparation Phase

• Master Data: Activation of Business Partner Approach (Customer-Vendor Integration)

• Inventory Management: Switch from Inventory valuation to material ledger (activation of ML supported via dedicated report). Note: it is still possible to decide e.g. per material and plan whether Actual Costing shall be applied or not.

• Automated logic (triggered as part of the technical procedure within the Software Update Manager [SUM]) to transfer application-specific data (for example specific transactional data) from old data structure into new SAP S/4HANA data structure

• Logistics Information System (LIS): The LIS based analytics capabilities are considered as not strategic. The strategic analytics architecture within SAP S/4HANA is based on open CDS views.

• Logistics Information System (LIS): The LIS based analytics capabilities are considered as not strategic. The strategic analytics architecture within SAP S/4HANA is based on open CDS views.

SAP S/4HANA

Simplification list – Phase-wise sorting of items: Examples

Custom Code

related Tasks

• Execute Custom Code Check Analysis

• Custom Code optimizations (not SAP S/4HANA specific –following best practice guidelines)

• Custom Code Adaption to comply to SAP S/4HANA data structure and scope

• Additional Custom Code optimizations (for example: following SAP S/4HANA cloud guidelines)

Public

New implementation


Transition to SAP S/4HANAScenario 1 – New installation

Scenario description

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

customers migrating a legacy system.

Benefits for the customer

+ Reengineering and process simplification

based on ready-to-run business processes

and reference solution delivered with the

product

+ New implementation of industry-leading

Business Suite

+ Pre-defined migration objects & Best

Practices available in a guided process

Legacy

Any customers

legacy system

SAP Fiori

SAP HANA

SAP S/4HANA Core



What How

Install SAP

S/4HANASWPM (Software Provisioning Manager)

Initial data load from

source system

SAP Landscape Transformation• SAP source: system connection

• Legacy system: file upload;

SAP Data Services additionally supported

1

2

SAP ERP 6.0 or

higher

Option: Initial data

load from Legacy or

SAP system based

on SAP LTNon-SAP


Transition to SAP S/4HANAMigration cockpit

Data Migration • The data migration activities can be executed based on the cloud

implementation cockpit

• Based on the selected business scenarios relevant data migration

objects are proposed.

• Existing customer can connect their SAP Business Suite system.

For new customer a template based approach can be used


1

SAP Landscape TransformationSAP S/4HANA data migration / landscape transformation platform

Source Environment Target Environment

SAP MWB



LAN / WAN

Legacy

Any customers

legacy system

Non-SAP

Insert of data via

standard interfaces (BAPIs / Direct Input)

Insert of data via

standard interfaces and

table-based.

File

Uplo

ad

(new

imple

me

nta

tion)

Transformation & Analysis

Framework

Pro

cess C

ontr

ol

Transformation Engines (Migration, Conversion, Replication)

Object-based TransformationBusiness object based data transfer

Preconfigured transformation content

for SAP S/4HANA, cloud edition

Public

System conversion


SAP S/4HANA system conversionProcedure


Customers who want to change their current

system into a SAP S/4HANA system.

Database, SAP NetWeaver and

application transition in one step.

Benefits

+ Migration without reimplementation

+ No disruption for existing business

processes

+ Re-evaluation of customization and existing

process flows

(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/4HANA (all one step

migration, including SAP S/4HANA Finance

and SAP S/4HANA Logistics conversion)

using SUM with DMO

*

*


SAP S/4HANASystem conversion & SAP S/4HANA Finance

The road to SAP S/4HANA

• SAP S/4HANA Finance, on-premise edition is the first offering under the SAP

S/4HANA product family

• The decision to go for SAP S/4HANA Finance, on-premise edition should be based on the business benefits but is not a mandatory

prerequisite for any system conversion

Start Release

SAP ERP 6.0, EHP 0-7

SAP NetWeaver 7.0x

AnyDB or SAP HANA

SAP ERP 6.0

SAP NetWeaver 7.40 / EHP 7

SAP HANA

SAP S/4HANA Finance,

on-premise edition

SAP S/4HANA, on-premise edition 1511

SAP HANA

SAP S/4HANA Core(SAP S/4HANA Enterprise Management)

Technical Procedure

based on Software

Update Manager

(SUM) with its

Database Migration

Option (DMO)


SAP S/4HANA system conversionSUM phases

UptimeStart

Release

Target

Release

Shadow System

Downtime

Preparation Phase

Uptime

Post Processing Regular Uptime

Pre-Transformation

Checks

Application specific

adaptions on start

release

Downtime minimizing

steps using "switch

upgrade" technology

Table replacement

Kernel switch

AIM, XPRA …

t

Switch Upgrade Technology


SAP S/4HANA system conversion Example – Activities during the different phases in logistics

Pattern 1: Activity before

migration + downtime

Pattern 2: Activity before or

after migration

Pattern 3: Activity after

migration

Pattern 4: Technical migration

Inventory valuation not supported in SAP S/4HANA. Switch to

material ledger can be done before migration (activation of ML

supported via dedicated report) During downtime ML migration to

new logic.

Material Ledger

BOM-Determination

MM-IM

Simplification of

MRP areas

One logic for all storage location MRP-Logic. In case of using such

logic, program needed to create missing MRP-areas and MRP-File

before running MRP in SAP S/4HANA

Conversion of IM-Tables (MSEG) into new MATDOC

One Logic for BOM-Determination only via production version.

Conversion to new logic via report possible before and after

migration possible, has to run before starting MRP in SAP S/4HANA

Public

Landscape transformation



Customers who want to consolidate their

landscape or to selectively transform data

into a SAP S/4HANA system.

Benefits

+ Value-based migration: selective data

transformation allows a phased approach

focusing the first SAP S/4HANA migration

phase on parts of the business with highest

ROI and lowest TCI

+ Agility: stay on current business processes

but move gradually to SAP S/4HANA

innovations (Move to SAP S/4HANA at your

own pace!)

+ TCO reduction: system and landscape

consolidation with harmonized/ simplified

processes and unified master data lead to

lower cost of operations

(SAP GUI) / SAP Fiori

SAP HANA

SAP S/4HANA Core



Consolidation or selective

data transformation based

on SAP LT capabilities

Transition to SAP S/4HANAScenario 3 – Landscape transformation

What How

ConsolidationSAP Landscape TransformationConsolidate clients from different source systems into one new or

existing SAP S/4HANA system (build-up multiple client system)

Selective Data TransformationSAP Landscape Transformation• Migration of business units/single entities such as company code

• Migration of selected SAP applications (example: central Finance)

1

2


SAP S/4HANA landscape transformation scenarios – On premiseSAP LT enabled solutions

Consolidation Migration of Business Units

(Company Code)

Migration of selected applications

(centralFinance)

Pre

-co

nfi

gu

red

Tailored offerings for selective data migration requirements

(for example based on time slice, plant or other objects)

can be requested as project solution or service.

Public

Supporting services


SAP S/4HANA migration servicesOffering from SAP Active Global Support and Consulting

Migration

Planning

For the E2E Solution Per System / Change-Cluster

Technical Architecture & Infrastructure

SAP S/4HANA

Discovery

Workshop

Innovation Strategy & Roadmap

Business

Scenario

&

Solution

Mapping

Target

Architecture

&

Platform

Strategy

Strategic

Roadmap

&

Business

Case

Scenario

Implementation

Incl. Readiness

Check

SAP S/4HANA

Implementation Strategy

Prepare Realize/DeployExplore

Optional

Pre-Step

2

1

2a

3

4

New Implementation

System Conversion

Landscape

Transformation

Scenario Decision


SAP Best Practices for migration to SAP S/4HANA

New Implementation

System Conversion

Landscape Transformation*

Install new SAP S/4HANA,

On-Premise EditionPredefined SAP Data Services content including mapping and business

transformation rules based on pre-configuration.

SAP Data

Services

SCENARIO CONTENT TOOL

Migrate complete SAP ERP

system to SAP S/4HANA,

On-Premise Edition

Guidance and procedures for one-step migration projects (Upgrade & Migration) DMO for SUM


cloud edition: net new

customers (non-SAP

sources) or installed base

(SAP ERP source)

Predefined ABAP coding in SAP Landscape Transformation for extraction,

transformation and loading of data. Predefined mapping and business

transformation rules based on pre-configuration. Supports Cloud Project Services

and Enterprise Editions.

SAP

Landscape

Transformation


On-Premise EditionPredefined SAP Data Services content including mapping and business

transformation rules based on pre-configuration.

SAP Data

Services

Implement SAP S/4HANA,

Cloud Marketing Edition

Pre-defined content to load data for interactions, contacts and products from non-

SAP systems and for Social Media channels (Twitter and Facebook fan pages)

SAP HCI (PI)


cloud edition: net new

customers (non-SAP sources)

or installed base (SAP ERP)

Predefined ABAP coding in SAP Landscape Transformation for extraction,

transformation and loading of data. Predefined mapping and business

transformation rules based on pre-configuration. Supports Cloud Project Services

and Enterprise Editions.

SAP

Landscape

Transformation



(*) SAP S/4HANA, Cloud Marketing Edition possible scenario


New ImplementationSAP S/4 HANA on premise and cloud

Prepare Explore

New Install

Implement

additional

industry / LOB

packages+

Technical

Architecture

& Migration

Planning

All Implementation

Scenarios

Dependent on

Implementation

Scenarios

Strategy &

Roadmap

Value

Discovery

Workshop

Realize / Deploy

Migrate Existing

Landscape TransformationBusiness driven migration offerings

System ConversionTechnology driven migration offerings

SAP Support and

Premium Engagement (optional)

Transition to SAP S/4HANAService portfolio to support your journey to SAP S/4HANA

Implement new

innovations

Installation and data

transition for SAP

S/4HANA


Transition to SAP S/4HANAMore details

Please join the following SAP TechEd sessions for detailed information on the individual

scenarios

Deep dive into S/4HANA data migration

using a best practices approach

DMM213 (L1)

i

How to Plan and Execute the System

Conversion to SAP S/4HANA

ITM201 (L1)

iHow to Plan and Execute a Migration to

SAP HANA

ITM200 (L2)

i

Data Migration to SAP S/4HANA

with SAP Landscape Transformation

ITM230 (L1)

i

Public

Questions


SAP TechEd OnlineContinue your SAP TechEd education after the event!

http://sapteched.com/online

Access replays of keynotes, Demo Jam, SAP TechEd live interviews, select lecture sessions, and more!

Hands-on replays

http://sapteched.com/online


Further information

Related SAP TechEd sessions:

DMM213 – SAP S/4HANA Data Migration Deep Dive: The Right Path to SimpleITM200 –

ITM200 – How to Plan and Execute a Migration to SAP HANA

ITM201 – How to Plan and Execute the System Conversion to SAP S/4HANA

ITM230 – Data Migration to SAP S/4HANA with SAP Landscape Transformation

SAP Public Web

scn.sap.com

www.sap.com

SAP Education and Certification Opportunities

www.sap.com/education

Watch SAP TechEd Online

www.sapteched.com/online

http://scn.sap.com/welcome

http://www.sap.com/

http://www.sap.com/education

http://www.sapteched.com/online


Thank you

Contact information:

Dr. Jochen Freudenberg

SAP SE

[email protected]


© 2015 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.

http://global12.sap.com/corporate-en/legal/copyright/index.epx

Transition Paths to SAP S/4HANA...SAP S/4HANA Core SAP GUI AnyDB / SAP HANA SAP ERP Core Software...

Documents

Transcript of Transition Paths to SAP S/4HANA...SAP S/4HANA Core SAP GUI AnyDB / SAP HANA SAP ERP Core Software...