Week 3 Unit 1: Planning - SAP

11
Week 3 Unit 1: Planning

Transcript of Week 3 Unit 1: Planning - SAP

Page 1: Week 3 Unit 1: Planning - SAP

Week 3 Unit 1: Planning

Page 2: Week 3 Unit 1: Planning - SAP

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

Discovery / Prepare Phase Realize Phase

tt2

Maintenance

PlannerPre-Checks

Custom Code

Migration Worklist

Software Update

Manager (SUM)

Application-Specific

Follow-On Activities

t3 t4 t5 t6

Simplification List

SAP S/4HANA On-Premise

Database Migration

Software Update

Data Conversion

System

Requirements

t1

PlanningSystem conversion: planning and system requirements

Page 3: Week 3 Unit 1: Planning - SAP

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

Example: Consolidation of current regional

SAP Business Suite landscape into one

global SAP S/4HANA system or selective

data migration

Example: New or existing SAP customer

implementing a new SAP S/4HANA system

with initial data load

PlanningThe 3 transition scenarios

Landscape

Transfor-

mation

ERP System

- Region A -

ERP System

- Region B -

ERP System

- Region C -

On-Premise

S/4Cloud

New

Implemen-

tation

On-Premise

S/4Cloud

ERP System

Non-SAP System

Example: Complete conversion of an

existing SAP Business Suite system to

SAP S/4HANA

System

Conversion

SAP S/4HANA

ERP System On-Premise

Page 4: Week 3 Unit 1: Planning - SAP

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

The S/4HANA Family and Migration Paths

SAP CRM

On-Premise

SAPBusiness

Suite AnyDBOn-Premise

SAP Business Suite(e.g. BS7i2013)

Suite on SAP HANA

SAP ERP

On-Premise

SAP S/4HANA familySAP

S/4HANACloud

System Conversion

PlanningSystem conversion towards the SAP S/4HANA family

SAP S/4HANAEnterprise

Management

SAP S/4HANAFinance

Page 5: Week 3 Unit 1: Planning - SAP

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

One-Step-procedure

PlanningTransition paths to move to SAP S/4HANA – Overview

AnyDB or SAP HANA

SAP ERP 6.0, EHPxx SAP HANA

SAP Simple Finance,

on-premise edition 1503

AnyDB

SAP HANA

SAP S/4HANA

Finance 1605

SAP HANA

SAP S/4HANA, on-

premise edition 1511

SAP HANA

SAP S/4HANA

1610

SAP Business Suite SAP S/4HANA family

System Conversion Paths (Basic)

From SAP Business Suite

(ERP 6.0, EHPxx, AnyDB, or

SAP HANA DB)

to SAP S/4HANA Finance

1 From SAP Business Suite

(ERP 6.0, EHPxx, AnyDB, or

SAP HANA DB)

to SAP S/4HANA

2

From SAP S/4HANA Finance

to SAP S/4HANA 3

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

the source system to already be on SAP HANA DB

• SAP S/4HANA Finance is 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

2

13

Note: One-step procedure to SAP S/4HANA product family supported for SAP ERP 6.0 EHPxx systems

(Unicode-only and AS ABAP-only system [no dual-stack system])

Page 6: Week 3 Unit 1: Planning - SAP

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

RemarksAvailabilityTarget

Release

Start Release

PlanningTransition paths to move to SAP S/4HANA – Details (1)

AnyDB or SAP HANA

SAP ERP 6.0, EHPxx

SAP HANA

SAP Simple Finance,

on-premise edition 1503

SAP HANA

SAP S/4HANA Finance

1605

SAP HANA

SAP S/4HANA, on-

premise edition 1511

SAP HANA

SAP S/4HANA

1610

SAP

Business

Suite

SAP S/4HANA

product family

1

2

3

4SAP ECC 6.0

EHP 0-7

SAP Simple Finance,

on-premise edition

1503

available since:

Q1/2015

Migration to SAP HANA DB

[if required], installation of

software [EHP7 + sFIN]) 1

SAP ECC 6.0

EHP 0-7

SAP S/4HANA

Finance 1605

available since:

Q2/2016

Migration to SAP HANA DB

[if required], installation of

software [EHP8 + sFIN]) 2

SAP ECC 6.0

EHP 0-7

SAP S/4HANA, on-

premise edition 1511 available since:

Q4/2015

Migration to SAP HANA DB

[if required], installation of

S4CORE software3

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 software4

System conversion from SAP S/4HANA Finance to SAP S/4HANA

Upgrade within the SAP S/4HANA product family

System conversion from SAP Business Suite to SAP S/4HANA

Page 7: Week 3 Unit 1: Planning - SAP

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

RemarksAvailabilityTarget

Release

Start

Release

PlanningTransition paths to move to SAP S/4HANA – Details (2)

SAP Simple Finance,

on-premise edition

1503

SAP S/4HANA, on-

premise edition 1511 available since:

Q4/2015

Installation of S4CORE

software5

SAP S/4HANA

Finance 1605SAP S/4HANA 1610

available since:

Q4/20166

SAP Simple Finance,

on-premise edition

1503

SAP S/4HANA 1610available since:

Q4/20167

SAP Simple Finance,

on-premise edition

1503

SAP S/4HANA

Finance 1605

available since:

Q2/20168

SAP S/4HANA, on-

premise edition 1511 SAP S/4HANA 1610 9

Installation of S4CORE

software

Installation of S4CORE

software

Installation of sFIN

software (upgrade)

available since:

Q4/2016

Installation

software (upgrade)

Not supported

System conversion from SAP S/4HANA Finance to SAP S/4HANA

Upgrade within the SAP S/4HANA product family

System conversion from SAP Business Suite to SAP S/4HANA

SAP

Business

Suite

SAP S/4HANA

product family

AnyDB or SAP HANA

SAP ERP 6.0, EHPxx

SAP HANA

SAP Simple Finance,

on-premise edition 1503

SAP HANA

SAP S/4HANA Finance

1605

SAP HANA

SAP S/4HANA, on-

premise edition 1511

SAP HANA

SAP S/4HANA

1610

8

9567

Page 8: Week 3 Unit 1: Planning - SAP

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

PlanningSize is important – Minimize source system size

Use SAP DVM: Data Volume Management Work Center in SAP Solution ManagerArchived data is still accessible after conversion; data conversion happens during access to archive

For System Conversion:

Focus on "relevant" tables

Trim down source

Archive data

Check data quality

Trim target operation

Consider data aging

Monitor data growth

ABAP sizing reports for move to SAP HANA

SAP Business Warehouse: SAP Note 1736976iMemory sizing report for SAP Business Suite

and SAP S/4HANA: SAP Note 1872170i

AnyDB

Page 9: Week 3 Unit 1: Planning - SAP

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

PlanningFind Your Path to SAP S/4HANA – Where to go for more information

Join the SAP S/4HANA Community

Discover SAP S/4HANA

SAP Learning Hub

SAP Help PortalSAP S/4HANA Trials

SAP S/4HANA

Cookbook

SAP S/4HANA Release Info

SAP S/4HANA FAQ

SAP S/4HANA Roadmaps

Choose Your Path to SAP S/4HANA

Page 10: Week 3 Unit 1: Planning - SAP

Thank you

Contact information:

[email protected]

Page 11: Week 3 Unit 1: Planning - SAP

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

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