Specifics of a System Conversion to

SAP S/4HANA Cloud, private edition

October 2022

Public
Knowledge Transfer for SAP User Groups - SAP CLM Webcast Series (extract)
https://webinars.sap.com/sap-user-groups-k4u/en/upcoming

Extract of session list from Cloud & Lifecycle Management (CLM) in 2022 – dates subject to change
Public 2
Conversion to SAP S/4HANA Cloud, private edition (RISE with SAP)

System Conversion
▪ Transition of one SAP ERP system to SAP S/4HANA (on-prem)

RISE with SAP

▪ A comprehensive SAP offering with one contract
▪ Supports you on the transition to an intelligent enterprise
▪ Bundles services for data migration, cloud infrastructure of choice, process redesign, …

SAP S/4HANA Cloud, private edition

▪ A deployment model as part of the RISE with SAP offering
▪ SAP S/4HANA (on-prem) software operated by SAP
▪ Functional differences to SAP S/4HANA are related to features from Compatibility Scope Matrix
(see SAP Note 2269324 - Compatibility Scope Matrix for SAP S/4HANA, part 1 Universal Compatibility Packs)

Public 3
Release Strategy of SAP S/4HANA Cloud, private edition

SAP S/4HANA Cloud, private edition follows the SAP S/4HANA 2022 release strategy.
Consequently, release dates, maintenance durations and upgrade paths are identical.

Reference: SAP Note 3061124 - SAP S/4HANA Cloud, private edition - Release Information
Public 4
Use of a migration server as intermediate target

➢ SAP S/4HANA cloud regulations: Migration

no OS level access on AppServer- assisted
and DB host for partners service SAP S/4HANA
Application server
SAP ERP virtual machine (VM)

➢ Migration Server is provided in the Application server

target landscape during project,
decommissioned afterwards DMO with SAP HANA
system move DB server VM
Source DB
➢ Partner installs AppServer on it,
DB server
target for DMO with system move
➢ SAP ECS reconfigures system
after hand-over from partner Migration
Server
➢ No migration server is required
SAP S/4HANA Cloud, private
in case that SAP Services Customer data center
edition
(on premise)
execute the conversion

Public 5
DMO with system move
Parallel mode reduces downtime

▪ Source and target SUM run in parallel. Source PAS Host Target PAS Host

▪ Long running shadow system activities on target SUM SUM

like SPDD, SGEN are executed in uptime.
Any
▪ 3 sync points are required: DB Convert
− Phase HOSTCHANGE_MOVE_SOT
Source DB host Target DB host
− Downtime dialog
− Phase HOSTCHANGE_STOP

▪ With continuous synchronization, even export

and import processes run parallel.

https://blogs.sap.com/2020/10/22/dmo-with-system-move-with-shd-rep-on-target-db/

Public 6
 DMO with System Move (parallel mode, 3 manual sync points)
Source Target

Shadow system activities:

EU_IMPORT / EU_CLONE_EXT
1) HOSTCHANGE_MOVE_SOT 1 ACT_UPG / SPDD
SHD_IMPORT
2) MAIN_DTTRANS 2 SGEN
Uptime …

Downtime
Export
application
tables

3) HOSTCHANGE_STOP 3 Import
application
tables

Public 7
 Parallel mode: wait on downtime dialog until target SUM runs import phase

SUM on source:
downtime dialog

SUM on target:
Runs phase EU_CLONE_MIG_DT_IMP
Public 8
DMO Conversion to Hyperscaler
Use Software Update Manager (SUM) for a one-step conversion and transition to Hyperscaler

One-Step conversion & transition of your on-premise SAP ECC to SAP S/4HANA Cloud, private edition

▪ Simplified approach for this use case

▪ Proven SUM technology
▪ Option to use downtime-optimized features
▪ Applicable for SAP ECC on non-SAP HANA DB
▪ Pilot phase, registration required via incident
Convert & Transition

The approach simplifies the technical

conversion and transition to a hyperscaler;
the application specific preparation and post
activities are similar to a standard conversion

Pilot program “DMO conversion to hyperscaler”:

https://blogs.sap.com/2021/12/02/dmo-to-azure-combine-sap-s-4hana-conversion-with-the-move-to-azure-without-dmo-with-system-move/
Public 9
Third-Party Add-Ons for SAP S/4HANA Cloud, private edition

▪ Similar to SAP S/4HANA on-premise

▪ Not allowed to install Add-Ons that require OS access

▪ Add-Ons validated and approved by SAP ECS are listed in SAP Note 3029231
“SAP S/4HANA Cloud, private edition : Compatible partner products”

▪ Additional Add-Ons are listed in the following SAP Notes

− 2974663 SAP S/4HANA, on-premise edition 2020: Compatible partner products
− 3094994 SAP S/4HANA, on-premise edition 2021: Compatible partner products

▪ Installation of uncertified Add-Ons: at customers own risk,

impact on future upgrade feasibility and on system performance to be considered
https://blogs.sap.com/2022/08/05/third-party-solutions-usage-in-rise-with-sap-s-4hana-cloud-private-edition/
November 2022: new openSAP course S4CPE1 on SAP S/4HANA Cloud, private edition (announced soon)

Public 10
SAP FIORI

▪ SAP will set-up the technical landscape required for Fiori app usage
− Embedded Deployment of SAP FIORI Frontend Server
− Deployment of SAP Web Dispatcher
− => you must be aware of the options and tasks to expose SAP FIORI to public internet
(like Load Balancer for SAP FIORI Launchpad, installation of SSL certificates on first access point)

▪ SAP will configure test SAP FIORI app versions to verify set-up
− Additional technical SAP FIORI app enablement possible via optional services
− Checklist and guides available for SAP FIORI enablement
like SAP FIORI rapid activation, custom catalog creations, unit & integration tests

SAP Fiori for SAP S/4HANA – 5 Steps to Fiori Bootcamp for Customers
https://blogs.sap.com/2021/09/27/sap-fiori-for-sap-s-4hana-5-steps-to-fiori-bootcamp-for-customers/

Public 11
Thank you.
Contact information:

Boris Rubarth
boris.rubarth@sap.com

© 2022 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to SAP Materials for general audiences.