Migration Scenarios
RISE with SAP S/4HANA Cloud, Private Edition, base option
INTERNAL
02 Oct 2022
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.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
2
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/Extended
Maintenance*
Possible Target Releases
under PCE Contract
SAP ERP 6.0, EHP xx
31.12.2027
S/4HANA 2021
SYSTEM CONVERSION: System conversion using SUM DMO
S/4HANA 1511
31.12.2020
S/4HANA 2021
S/4HANA 1610
31.12.2021
S/4HANA 2021
Supported under Limited Maintenance Policy https://www.sap.com/about/agreements/policies/cloud-servicespecifications.html?sort=latest_desc&search=RISE+with+edition&pdf-asset=10151ebc-f07d-0010-bca6c68f7e60039b&page=1&source=social-atw-mailto
S/4HANA 1709
31.12.2022/
31.12.2025*
S/4HANA 1709
S/4HANA 1809
31.12.2023/
31.12.2025*
S/4HANA 1909
31.12.2024/
31.12.2025*
S/4HANA 2020
31.12.2025
S/4HANA 2021
31.12.2026
Migration Approach
SYSTEM COPY (backup/restore): This approach is possible till 2025
UPGRADE: Upgrade to latest release is desired as part of the migration
S/4HANA 1809
SYSTEM COPY (backup/restore): This approach is possible till 2025
S/4HANA 2021
UPGRADE: Upgrade to latest release is desired as part of the migration
S/4HANA 1909
SYSTEM COPY (backup/restore): Desired option as this release is under maintenance until 2025
S/4HANA 2021
UPGRADE: Upgrade to latest release is optional
S/4HANA 2020
SYSTEM COPY (backup/restore): Desired option as this release is under maintenance until 2025
S/4HANA 2021
UPGRADE: Upgrade to latest release is optional
S/4Hana 2021
SYSTEM COPY (backup/restore)
• Releases that have at least 9 months of maintenance 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 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.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
3
S/4HANA 1511 & 1610 – Limited Maintenance Policy
Supported under Limited Maintenance Policy
https://www.sap.com/about/agreements/policies/cloud-servicespecifications.html?sort=latest_desc&search=limited%20maintenance
Highlights of this policy :
•
Non PRD systems (on old S/4HANA releases) can be migrated to PCE
•
Before the migration of PRD system, the Non PRD systems have to be upgraded to latest S/4HANA versions
•
After the migration of PRD system(old S/4HANA release), it has to be upgraded to latest S/4HANA version
within 2 weeks
•
The migration of the systems can be done by Partners and Upgrade (Technical Tasks) will be done by C4C as
per PCE R&R.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
4
Limited Maintenance Policy – Who does what
Scenario
Migration from
On-Prem to
PCE
Where Migration Partner can do
Partner is
involved
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
Go-live 1
Upgrade to latest Go-live 2
S/4Hana Version
Go-live done by Only C4C can do
partner, post go- (as per R&R)
live Handover to
C4C
C4C
5
RISE with SAP Transition Options
RISE with SAP S/4HANA Cloud, Private Edition, base option
Source Version
Target Version
Transition Method
ERP on anyDB
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
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
6
Source Release – ECC 6.0 on anyDB (non-HANA)
Target – RISE with SAP S/4HANA Cloud, Private Edition, base option
SAP S/4HANA, private cloud edition infrastructure
ECC 6.0 EhPxx
S/4HANA 2021
Any supported DB
HANA
System Conversion
•
Any supported OS
Suse Linux
Customer specific
Infrastructure
Private Cloud
Infrastructure
S/4HANA Conversion (SUM DMO with System Move) can be done by authorized Partner with support from C4C Delivery
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
7
Source Release – ECC 6.0 on HANA
Target – RISE with SAP S/4HANA Cloud, Private Edition, base option
There is no direct transition method from ECC 6.0 on HANA to S/4HANA. There could be different options to handle such customers
Option 1: [Recommended]
Step 1 – S/4HANA conversion at on-premise [Customer will have to consider any OS upgrade/Hana 2.0 upgrade etc]
Step 2 – Copy S/4HANA from on-prem to Private Cloud
Both the steps can be done by partner in one downtime. Downtime will be less as compared to Option 2
Option 2: [Not Recommended]
Step 1 – Copy ECC on Hana from On-prem to Private Cloud
Step 2 – S/4HANA conversion
Both the steps can be done together by partner in one downtime. Drawback is it will require very long downtime (of days) and hence this might
not meet any customer’s requirement.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
8
Source Release – S/4HANA
Target – RISE with SAP S/4HANA Cloud, Private Edition, base option
SAP S/4HANA, private cloud edition infrastructure
S/4HANA
S/4HANA
(1709 to 2021)
(1709 to 2021)
HANA
HANA
System Copy
Any supported OS
Linux x86/Power
Customer specific
Infrastructure
•
Suse Linux
Private Cloud
Infrastructure
System Copy can be done by authorized Partner
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
9
Additional Costs to be included in Base Costs
Deployment
Block Storage
(Storage on Hana DB)
Storage for Export Dump
(Cloud4C)
Not Included
(Needs to be priced using
Additional Storage SKU)
Not Included
(Needs to be priced using
Additional Storage SKU)
(applicable for migration or S/4
Conversion)
For both Block storage (storage on the DB server) and storage on the Application server, PCA will need to price
the storage using SKU SAP Additional Storage, private cloud edition – 8008794 (This is only for Migration
Scenario).
Storage for Export Dump will move from DEV to QAS to PRD S/4HANA Application Server for sequential
migration scenario so you can price as per the largest Export dump size.
The storage for backup during conversion will be moved from DEV to QAS to PRD S/4HANA Database server for
sequential migration scenario so you can price as per the largest DB size.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
10
Handling Additional Storage in PQA
The additional storage which is part of PQA/DED should be maintained with usage details as well.
If the storage is for Migration purpose then please maintain under usage details as “/migration” so that block
device would be provided as /migration mount point.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
11
Storage Guidelines
Approach 1 : Migration/Conversion
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 the S/4HANA cloud, private edition, base option.
For this approach the following additional storage needs to be contracted with the customer:
1. Storage needed for the export dump on the Application Server. This needs to be analyzed and calculated depending on the source
systems database size. As the Application Server will be different 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 (also known as Block Storage). There should be additional storage twice the
HANA size calculated. This storage will allow the Migration Team to trigger local backups (at least two, therefore twice the HANA size)
at milestones during the migration/conversion
Approach 2 : System Copy
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:
1. Storage needed on the HANA DB server for the backup transferred (also known as Block Storage). There should be additional
storage one time the HANA size calculated. To this storage the transferred backup will be moved so SWPM can trigger the restore.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
12
RISE with SAP Transition Options - Storage Requirements
RISE with SAP S/4HANA Cloud, Private Edition, base option
Source Version
1. ERP on anyDB
2. ERP on HANA
3. S/4HANA
(1709 & above)
Target Version
Transition Method
Storage Requirement (Not included in Base cost)
S/4HANA
System Conversion (DMO w System
MOVE)
1. Storage for Export dump on S/4HANA Application server
2. Storage for taking Backup on database server (at least twice of
HANA DB size)
S/4HANA
System Copy (backup / restore) – step 1
System Conversion (SUM) – step 2
Step 1
1. Storage for copying source database Backup on ERP on HANA
database server (same size as HANA DB)
Step 2
1. Storage for executing Backup on database server (at least twice of
HANA DB size)
S/4HANA
System Copy (backup / restore) – step 1
S/4HANA upgrade (optional) – step 2
Step 1
1. Storage for storing source database Backup on S/4HANA
database server (same size as HANA DB)
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
13
Backups during Migration
To avoid any issues due to different teams (Cloud4C and SI) connecting at OS level during the migration,
Local Backups during migration of the system will need to be taken by the migration (SI) team. Cloud4C can
take any backup’s post the migration team handing over the system to Cloud4C for post migration activities.
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
14
Migration Dump is Higher Than Estimation
R3load (DMO with System Move /SWPM) based migration dump is
higher than expected, what could be the reason ?
•
Source DB size compression (Full DB, set of tables, index only,
etc.)
•
Large Cluster tables (CDCLS, RFBLG, EDI40, KOCLU etc.) If the
cluster tables are large in your database, then it will impact the
overall estimated compression factor
•
Source DB statistics not up to date
•
Large LOBs and Hybrid LOBS - Large Object is a data type used
to store large record (e.g. tables SOFFCONT1, DBTABLOG)
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
15
How to estimate migration dump size ?
1.
Source: Suite on HANA Sizing Report
•
Migration Dump Estimation = 25% of Column store data + Hybrid LOBs
Migration Dump Estimation = 535.75 + 2056 = 2591.75 GB
2.
•
SoH HANA DB Backup Size = 4384.2 GB
•
Migration Dump Estimation = 25% of Column store data + Hybrid LOBs
Source: S/4HANA Sizing Report
Migration Dump Estimation = 1767.25 + 1084 = 2851.25 GB
•
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL
S/4HANA HANA DB Backup Size = 8993 GB
16
Thank you
Follow us
www.sap.com/contactsap
© 2021 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 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 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/copyright for additional trademark information and notices.