8
Week 3 Unit 4: Executing the System Upgrade and Database Conversion

Week 3 Unit 4: Executing the System Upgrade and ... - SAP

  • Upload
    others

  • View
    3

  • Download
    0

Embed Size (px)

Citation preview

Week 3 Unit 4: Executing the System

Upgrade and Database Conversion

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

Executing the System Upgrade and Database ConversionSystem conversion: technical conversion

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

Database Migration

Software Update

Data Conversion

System

Requirements

t1

Simplification List

SAP S/4HANA On-Premise

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

Executing the System Upgrade and Database Conversion Simplification in SAP S/4HANA

Simplification of data model

New data model powered by SAP HANA

New tables and new applications (and new UI: SAP Fiori)

Conversion tasks for Software Update Manager (SUM):

Database migration: Provide SAP HANA database

Software update: Provide new applications and new tables

Data conversion: Conversion of table content to new data model

SUM

PAS Host

AnyDB

Source DB Host Target DB Host

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

Executing the System Upgrade and Database ConversionSUM is the tool for the technical conversion to SAP S/4HANA

Software Update Manager (SUM) 1.0

The tool for update, upgrade, combined update & migration, system conversion,…

Part of the Software Logistics Toolset 1.0 (see support.sap.com/sltoolset)

SUM 1.0 SP 18 is available (a new SP is provided ~ 3 times / year)

Database Migration Option (DMO)

Option in SUM to include the migration from AnyDB to SAP HANA DB

Available for migration to SAP Business Suite on SAP HANA and for system conversion

Source system is on SAP HANA database: simply use SUM

Source system is not on SAP HANA database: use DMO of SUM

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

Executing the System Upgrade and Database ConversionStandard approach (high level)

Discovery / Prepare Phase

t2

Maintenance

PlannerPre-Checks

Custom Code

Migration Worklist

t3 t4

System

Requirements

t1

Simplification List

SAP S/4HANA On-Premise

Uptime Processing

(dev lock)

Shadow System

Uptime Processing

Pre-transformation checks

Postprocessing Uptime

System update (SHD) DataConversion

System update

(application data)

Table replacement, kernel switch

AIM / XPRAS, SPAU

Data Migration

Downtime Processing

& migration

SPDD DataConversion

(FIN, ML)

Realize Phase

t

Software Update

Manager (SUM)

Application-Specific

Follow-On Activities

t5 t6

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

Executing the System Upgrade and Database ConversionFind 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

Thank you

Contact information:

[email protected]

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

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