RISE PCE CAA Migration Options_wave4.pdf

INTERNAL – Authorized for Partners
Initial
Discovery
Technical Assessment
Readout
Technical
Analysis
Sizing and
Migration Planning
Signoff
Onboarding
RISE with SAP S/4HANA Cloud, private edition
Sales & Services Authorization Enablement
Migration Options & Process
You are
HERE
Cloud Architecture & Advisory Team (CAA), March 2023

2
© 2023 SAP SE or an SAP affiliate company. All rights reserved. | INTERNAL - SAP and Partners Only
RISE with SAP S/4HANA Cloud, private edition, will hereafter be referred to as “PCE”.
After finishing this course, you should know and be able to explain:
➢ The supported versions and migration scenarios
➢ The storage guidelines for migrations
➢ The high-level migration process flow
➢ The general system build timeline for migrations
Learning Objectives

3
Migration scenarios are also referred to as ‘brownfield’ scenarios.
Pure content migrations are not included, as they are based on new/’greenfield’ installations.
Partners and SAP will work hand-in-hand during the migration process.
Migration overview

4
Only releases that have at least 9 months of main maintenance left are supported.
Lower releases must be upgraded before a migration to PCE.
Customers must upgrade to the latest version of S/4HANA as per the dates agreed in the contract
and well before end of mainstream maintenance.
Supported releases General comments

5
Technical Qualification Criteria – Software Release Check
Summary of technical criteria for customers who are running S/4HANA on their premises to move to S/4HANA Private Cloud Edition (PCE).
Source Release
End of
Mainstream
Maintenance
End of
Extended
Maintenance
Possible Target
Releases under
PCE Contract
Migration Approach
SAP ERP 6.0, EHP 0 to EHP
5
31.12.2025 n/a S/4HANA 2022 SYSTEM CONVERSION: System conversion using SUM DMO
SAP ERP 6.0, EHP 6 onwards 31.12.2027 n/a S/4HANA 2022 SYSTEM CONVERSION: System conversion using SUM DMO
S/4Hana Finance 1605 31.12.2025 n/a S/4HANA 2022 SYSTEM CONVERSION: System conversion using SUM DMO
S/4HANA 1511 31.12.2020 n/a S/4HANA 2022 Supported under Limited Maintenance Policy
https://www.sap.com/about/agreements/policies/cloud-service-
specifications.html?sort=latest_desc&search=limited%20maintenance
S/4HANA 1610 31.12.2021 n/a S/4HANA 2022
S/4HANA 1709 31.12.2022 31.12.2025
S/4HANA 1709 SYSTEM COPY (backup/restore): This approach is possible till 2025
S/4HANA 2022 UPGRADE: Upgrade to latest release is recommended as part of the migration or at a later stage
S/4HANA 1809 31.12.2023 31.12.2025
S/4HANA 1909 31.12.2024 31.12.2025
S/4HANA 2020 31.12.2025 n/a
S/4HANA 2021 31.12.2026 n/a
S/4HANA 2021
SYSTEM COPY (backup/restore): Desired option as this release is under mainstream maintenance
until 2026
S/4HANA 2022 UPGRADE: Upgrade to latest release is optional
• Releases that have at least 9 months of maintenance (mainstream or extended as applicable) left are only supported. For lower release, an upgrade must be executed before the migration to
PCE. Customers must upgrade to the latest version of S/4HANA well before end of mainstream or extended maintenance.
• If a target release below 1909 is chosen, compatibility of subcomponents (such as additional SKUs deployed on top of S/4HANA) need to be manually verified.

6
Transition Options
Source Version Target Software Transition Method
ERP on any DB S/4HANA System Conversion
ERP on HANA S/4HANA
Perform system conversion on-prem
to S/4HANA followed by a system
copy to RISE infrastructure.
S/4HANA S/4HANA System Copy / Upgrade
RISE with SAP S/4HANA Cloud, private edition

7
Source ECC 6.0 Target S/4HANA in PCE
ECC 6.0 EhPxx
Any supported DB
Customer-specific
Infrastructure
Any supported OS
S/4HANA 20xx
HANA
Private Cloud
Infrastructure
SUSE Linux
System Conversion
System Conversion (SUM DMO with System Move) can be done by authorized partners ONLY
PCE Infrastructure

8
Source S/4HANA Target S/4HANA in PCE
S/4HANA
(1709, 1809, 1909, 20xx)
HANA
Customer-specific
Infrastructure
Any supported OS
Linux x86/Power
S/4HANA
(1709, 1809, 1909, 20xx
HANA
Private Cloud
Infrastructure
SUSE Linux
System Copy
System Copy can be done by authorized partners ONLY
PCE Infrastructure

9
A system is migrated using export/import or using SUM DMO with system move. In both cases the
source database is exported using SAP tools and imported into HANA in PCE.
For this approach the following additional storage needs to be contracted with the customer:
1. Storage needed for the export dump on the migration server. This needs to be analyzed and
calculated based on the database size of the source systems. As the migration server will be
reused for every system (DEV, QAS, PRD...), it should be calculated for the biggest source
database.
2. Storage needed on the HANA DB server for backups. Additional storage, twice the size of
HANA, should be calculated and considered. This storage will allow the migration team to
trigger local backups (at least two, therefore twice the HANA size) at different milestones during
the migration/conversion.
Storage guidelines migration/conversion

10
A system that is already on a supported S/4HANA release or running on the HANA database, and
export/import is not possible anymore. In this case, backup/restore is the method to be used.
For this approach, the following additional storage needs to be contracted with the customer:
Storage needed on the HANA DB server for the backup transferred. There should be additional
storage provisioned with size - one time the calculated HANA database size. The transferred
backup will be moved to this storage, so that the software provisioning manager (SWPM) can
perform the restore.
Storage guidelines system copy

11
For process-related details, review the latest guidance provided by solution management.
• Migration Execution
on the source system
• Migration Execution
on the target system
[details as per latest
migration guidance]
Partner
• CDM & TSM will
coordinate the
communication
between the partner
and ECS delivery.
ECS
Migration process flow

12
SAP INTERNAL. MAY BE SHARED WITH PARTNER UNDER NDA. SAP Roles
Partner
Roles
Milestone / Task & Activity Summary Summary Comment
Migration strategy workshops with customer implementation team C I R A
Workshops are in the responsibility of the partner. Dedicated time in project plan for quality
checks. SAP PL should make sure that partners are aware of SAP standard guidelines.
For Brownfield only: ECS participation in partner meeting I R A Overall responsibility with the partner.
For Brownfield only – HO (handover) for migration R A I I
Perform / confirm the post-migration steps before handing over to
SAP Cloud
I R A
Partner performs the post-processing steps as per documentation and shares the output with
SAP PL. Please keep in mind that the partner post steps for PCE migrations are divided into
two parts.
System HO (handover) from partner to Delivery for SAP Cloud
post-processing
C I R A Checklist for post-processing must be completed as part of the handover to SAP.
Perform the ECS post-processing and ECS migration checks R A C I C I
Responsibility of ECS to make the system as per ECS standard. Partners need to support in
fixing potential issues identified before handover to the customer.
Orchestrating migration support C I R A
Migration is the responsibility of the customer, typically outsourced to partner. Migration
support from SAP is provided only on a limited basis (e.g., to restart the DB if required).
Migration support / interface support (on exceptional basis) C I R A
Currently this is not a defined S/4HANA PCE service with a few exceptions. Additional charges
may apply.
Ensure adherence with all SAP Cloud Security aspects I R A In case of non-compliance always inform the SAP ECS Security officer.
System hand-over to customer R A I I
PL to trigger system handover process to customer. Recommendation to include partner in the
recipient list for system handover.
Customer sign-off (technical & commercial go-live) I C I Customer responsibility, partner to advise customer.
Technical resolution of the escalations during the delivery (system build) R A C I I
In parallel to standard incident escalation procedure, in case technical expertise is required.
Responsibility is with SAP onboarding team. Partners will be informed in case system handover
dates are endangered (if customer approval is given)
Migration-related tasks in the RACI
R = Responsible; A = Accountable; C = Consulted; I = Informed

13
The exact timeline depends on the solution. This example shows a timeline for the setup of a
skeleton S/4HANA system of up to 12 TB in size in the primary data center.
PCE ‘brownfield’ timeline with responsibilities
S2D
DEV/QAS/PRD
Network segment & Skeleton Systems
duration: ~9 WD
(CAS)
10 WD
Contract
Signature/
Upload
7 WD
[up to 14 WD, depending on the solution;
inquire for systems > 12 TB]
Contract
Start Date
(CDD)
Non-PROD
Post-Processing*
duration:
~3 WD
PROD
Post-Processing*
duration:
~12 hrs1
Export, Data Transport & Import
duration: customer-specific
* Dress rehearsal as chargeable service;
No cut over for Non-Prod over weekends
1 Prod post-processing time depends on system size (12hrs for < 3TB)
Partner with ECS support
ECS
ECS Resource
Assignment
Migration
Workshop
3 WD* / 12 h1
Partner Post-Processing
duration: customer-specific

14
Migration scenarios require close cooperation of partners and SAP
Migrations require additional storage to be provisioned – please follow the provided guidelines
Review the distribution of responsibilities in the RACI document
Follow the latest migration guidelines from the SAP solution management team
Verify the timelines—especially for larger landscapes and systems > 6 TB
Summary

Please reach out to your Regional SAP Partner CAA in case of any additional clarifications/questions
Thank you.

www.sap.com/contactsap
Follow us
© 2022 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.
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 docume
nt 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 platforms, 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 www.sap.com/trademark for additional trademark information and notices.

RISE PCE CAA Migration Options_wave4.pdf

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to RISE PCE CAA Migration Options_wave4.pdf

Similar to RISE PCE CAA Migration Options_wave4.pdf (20)

Recently uploaded

Recently uploaded (20)

RISE PCE CAA Migration Options_wave4.pdf