RISEwithSAP PrivateCloudEdition BrownField Migrations Partner Overview

RISE with SAP
Brownfield Migrations
Partner Overview
SAP S/4HANA Cloud
Private Edition
Brendan Ryan
Enterprise Cloud Services (ECS) Strategic Partner Management
October 2023, SAP
INTERNAL – SAP and Partners Only

Agenda
01
• RISE with SAP Onboarding Essentials
02
• Migration Strategy & Approach
03
• Key Project Handover Points
04
• Project Planning & Resourcing
05
• Sample Project Structure
06
• Managing the Change Process
07
• Typical Project Issues & Mitigations
08
• Monitoring Overview
09
• Security Overview
10
• Conclusions
INTERNAL – SAP and Partners Only

© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL – SAP and Partners Only
RISE with SAP
Onboarding
Essentials
One Commercial Construct: ERP, Infrastructure, and Technical Services
Advisory & Application

Implementation Management
Services Services
Advisory & Application
Implementation Management
Services Services
SAP S/4HANA
Software Traditional Technical
Managed Private Cloud
+ Support
Services
Software Technical
+ Support Managed
Services
Infrastructure Infrastructure
Management + Management +
SAP S/4HANA, private cloud edition – Key benefits and values
Business Benefits Strategic Benefits Technical Benefits Operational Benefits

• Full scope of SAP S/4HANA • Simplified system conversions • Access to S/4HANA • Resilience and TCO of
scope incl. LOB and industry and brownfield migrations into Extensibility Framework hyperscaler infrastructure
processes, supporting 25 the cloud • Side-by-side and In-App • Technical operations done
industries • Application and technical extensions by SAP
• Wide range of partner operations from one vendor • Code enhancement & • Upgrade installation on
add-ons allowed • Safeguarded prior code modifications allowed customer request
• 64 Country/Region investments into • Expert configuration
versions in 39 languages new SAP systems (full IMG access)
• SAP concierge service • Scalable platform
to simplify move to the cloud
Mandatory Partner Certification Criteria
Partners must get Sell or Service authorisation to work on S/4HANA
Cloud, Private Edition projects. SELL Authorisation Requirements
1 X Customer
Specific numbers of employees in your organisation need to pass Engagement 1 X Sales 1 X Presales
relevant certifications depending on the sales motion. Executive Consultant
Executive
• SELL partners engage in customer sales through their own
contracts (resell model), operating as co-sell partners. Sell 1 X Cloud 3 X Solution
partners can also provide services and deliver projects Architect Consultant
• SERVICE partners provide various customer services, operating

as co-sell partners.
SERVICE Authorisation Requirements
The Partner Finder tool lets customers find and acknowledge a
partner's skills, experience, and expertise. The competency 1 X Project 3 X Solution
Manager Consultant
framework helps partners stand out by showcasing your expertise
and specialisation, and setting you apart from competitors.
Partner Enablement
The Digital Partner Platform provides a blended training via SAP
Partner Portal and Learning Hub. It serves as a central location that *One person can handle Sales Executive, Presales Consultant, and
Customer Engagement Executive roles. However, for Solution
offers links and streamlines your enablement journey. Consultants, you need three individuals, each with a distinct
certification
SAP S/4HANA Cloud, Private Edition
Brownfield Partner Led Onboarding Journey
Contract Signature RISE Onboarding Migration to RISE Post Processing Run with RISE
• Customer signs the Rise contract with • 10 WD after contract signed • Partner performs system • After post processing & customer • Rise cloud SLAs are
agreed Committed Delivery Date Sales to Delivery (S2D) migration &/ conversion of validation, systems are now applicable.
(CDD) for new Cloud systems. session is completed. customer’s on-premise SAP considered as operational
• Application of CQC, EW
• Partner returns onboarding technical systems to S/4HANA Cloud • Once ECS post processing is
• SAP stands up the private parameter
checklist, Pre-Provisioning Form Private Edition. completed, the system is made
cloud environment based on recommendations by ECS
(PPF) and the Connectivity the customer input. • Partner works closely with live and handed over to
• Continuous monitoring,
Questionnaire within 5 working SAP ECS cloud delivery team Customer.
• Skeleton systems are built optimisation, and
days (WD) of contract signing. to complete Migration
and handed over to Partner maintenance to ensure
• SAP Project Lead (PL), SAP Client after 7 WD. smooth operations and
Delivery Manager (CDM – big deals) • Customer establishes the
efficient performance
and SAP Technical Service Manager connectivity to the ECS • Customer can raise SRs
(TSM) or SAP Digital cloud. and Incidents going forward
Customer Engagement Manager
(dCEM – small deals) are assigned to
manage service delivery.
Notes Build Timeline

• CDD is the product start date indicated in the cloud order
form
ECS • Simple Landscape build takes ~17 business days from contract
signature
• Any delay in return of PPF by partner will impact CDD • [Standard Delivery (No DR)] S2D (10 WD) + System
•
•
ECS system build begins after S2D session completed
Service Requests can take up to 24 hours to process Delivery •
Build (7 WD) [no DR]
Disaster Recovery system delivery takes additional effort
• 20 additional days for long distance DR
• 3 additional days for short distance DR
• Larger HANA systems (> 6TB) may take additional business days
S/4HANA Cloud, Private Edition
Greenfield Partner Led Onboarding Journey
Best Practices Scoping Contract Signed Rise Onboarding System Handover Run with RISE System Configuration
PCE Assessment • Customer signs the Rise contract with
• 10 WD after contract signed Sales to • Systems are handed over according to • Rise cloud SLAs are now applicable. • Partner leads implementation project
• Partner Cloud Application Architect (CAA) agreed Committed Delivery Date (CDD) the contracted CDD
Delivery (S2D) session is delivered. on S/4HANA Cloud, Private Edition
conducts comprehensive assessment for new Cloud systems. • Application of CQC, EW parameter
• (IF BP IN SCOPE) CDD Standard systems
• SAP ECS stands up the private cloud recommendations by ECS
• Determine if Best Practice (BP) activation is • Partner returns onboarding technical delivery is extended by an additional 2
environment based on the customer
necessary checklist, Pre-Provisioning Form (PPF), WD. ECS will also need to perform a BP • Continuous monitoring, optimisation, and
inputs.
• Share Best Practices Questionnaire with Connectivity Questionnaire & (IF BP IN scope import activation which takes an maintenance to ensure smooth
SCOPE), the completed BP • New S/4HANA systems are built, operations and efficient performance
Customer additional 5 WD after CDD, this may be
Questionnaire, providing details on patched and configured i.e., Dev, QA
extended depending on number of • Customer can raise SRs and Incidents
Best Practices Not in Scope system requirements, countries, & PRD deployed from standard image,
scope items. going forward
• Customer undecided on employing SAP BP currencies, additional languages, client client, Fiori, ADS, TMS, Languages
configuration, and Business Function import are setup & (IF BP IN SCOPE), • Once ECS post processing is
in sales cycle
requirements, including HANA Plugins, BP activation tasks are executed completed, the systems are made live
• ECS will Utilise standard fast PCE and handed over to Customer.
within 5 Working Days (WD) of signing • Customer establishes the connectivity
deployment procedure for greenfield systems
the contract. to the ECS cloud.
• Additional BP activation requests can be
• SAP Project Lead (PL), SAP Client
handled via service request after system
Delivery Manager (CDM – big deals)
build but will incur delays and also loss of
and SAP Technical Service Manager
system/client data
(TSM) or SAP Digital
Best Practices in Scope Customer Engagement Manager
• Customer certain about employing SAP BP (dCEM – small deals) are assigned to
with tight project timeline manage service delivery.
• Partner CAA confirms via email SAP BP in

scope
• BP tech preparation steps will be included in
the initial build before handover
Notes Build Timeline

•
•
•
CDD is the product start date indicated in the cloud order form
Any delay in return of PPF by partner will impact CDD
ECS system build begins after S2D session completed
ECS • Simple Landscape build takes ~23 Working Days (WD) from contract signature
•
•
[Standard Delivery (No DR, No BP)] S2D (10 WD) + System Build (13 WD)
[BP in scope] System Build (+2 WD) & BP scope activation after CDD (+5 WD), can take longer
• Disaster Recovery system delivery takes additional effort
• Service Requests can take up to 24 hours to process
Delivery •
•
•
20 additional WD for long distance DR
3 additional WD for short distance DR
Larger HANA systems (> 6TB) may take additional business days
Customer Onboarding Preparation Tasks
Customer Connectivity
Questionnaire
Pre Provisioning
Form
Connectivity Setup
• Connectivity Option Customer selects desired connectivity for S/4HANA Cloud,
Private Edition.
Requested Landscape Setup Detail • Connectivity Questionnaire SAP provides a questionnaire for collecting technical
parameters. Customer details VPN devices, endpoints, Edge location, and related
• S-User Credentials Provide super user at contract signing. Use it to create and parameters.
share a new user for SAP Service Marketplace. • Connectivity Setup SAP Network engineers collaborate with the customer to
• Language Setup Specify SAP system languages. establish and test the required connectivity.
• SID and ABAP Share SAP System Identifiers (SID) and ABAP Client details. • Internet DNS Entries and TLS 1.2 Certificates
• Private IP Ranges Define non-overlapping /22 ranges for virtual networks; add • Customer prepares required entries and certificates (details discussed with SAP
/22 if subscribing to Disaster Recovery. during onboarding).
• DNS Domain Specify domain for S/4HANA Private Cloud; provide DNS zone
transfer IPs.
• Contact Details Supply name, email, and number for S/4HANA Private Cloud
system.
Roles and Responsibilities
• SAP ECS runs in Factory mode. PCE Roles & Responsibilities
• Partners must familiarise themselves with the Roles and
Responsibility (R&R) matrix specified in their RISE agreement with
SAP prior to project commencement.
• Partners handle advisory and project implementation tasks.
• Partners handle the application specific upgrade activities, with CAS

helping if needed.
• Partners access the application layer of the ECS hosted system

through SAPGUI.
• Partners don't have full access to the operating system (OS) of the
ECS hosted systems.
• In case of migration issues, SAP may provide partners with a 'Jailed'

user account (no create, change, and deletion privileges) on the
ECS hosted Primary Application Server. This read-only account
enables partners to investigate issues, navigate the operating
system, and check log files. It is granted only if access to the
operating system is required during the migration and it involves the
central instance directly, (specially in case of JAVA systems).
Customer access requests are reviewed and approved by the SAP
security officer before granting access.
• To facilitate the migration process, SAP offers a Migration Server

hosted with ECS environment with root access as a workaround for
the root access restrictions . Partners utilise this server for the
duration of the migration procedure to set up a temporary application
server for the migration process and data migration
• Responsibilities of ECS are as stated in the R&R. Additional service

requests will be reviewed and if approved by ECS can be ordered at
an additional cost. i.e., additional security services
• SAP CAS completes tasks as outlined in the R&R, completing them * Note: Customer/Partners maintain responsibility for standard database instance administration tasks, i.e., user
upon request and is contingent upon contractual discussions. creation, role assignment, SQL tuning while the specific technical aspects such as server provisioning, backup,
patching etc are managed by SAP ECS.
Service Categories
The 'Roles and Responsibilities Matrix' shows who

should do the different tasks during PCE transition
projects, either SAP or the Customer. The tasks are
generally split by service categories
• Standard Services covered by the PCE contract

are completed automatically by ECS team.
• For tasks under the Cloud Application Services
(CAS) scope, customers can choose either the
SAP ECS Team (extra cost) or a Partner team
they hire to complete.
• Optional non standard services and Additional
unique services, however, can only be done by
SAP ECS and then only upon request (extra
cost).
• Finally Excluded Tasks can only be done by the
Customer themselves, and are not offered as a
service by SAP
Migration Strategy &
Approach
Transition Approach Overview
Fully activated appliance is available for trial purposes
Greenfield Implementation (New Implementation)
• New instance or re-implementation of current ERP either from non-SAP legacy/On Premise SAP system. SAP SAP
• Available Options ERP S/4HANA
• Empty System
• SAP Best Practices
• Enterprise Management Layer (SAP service)
• Partner Template (e.g., SAP-Qualified Partner Packaged solution). Move
After
Brownfield Implementation (System Conversion) • Transform your business processes by
• Retains existing processes, migrates current system to RISE

Brownfield •
moving to RISE.
Seamlessly transition your current SAP
Business Suite ERP system to SAP S/4HANA
with a comprehensive in-place technical
migration/conversion.
Landscape Structure for Both Approaches • Embrace new innovations at your preferred
pace.
• Brownfield: Typically utilises existing landscape with considerations for conversion prerequisites.
• Greenfield: 3-system or 2-system landscape with DEV, QAS, PRD in 2 or 3 systems, additional systems available on request by
extending subscription.
Development Quality Production Additional
System
(000)
System
(000)
System
(000)
Subscription
System SAP/ SAP
System
3rd Party
System System
Administration Administration Administration
(050) (100) (100) S/4HANA

Best Practices
(100)
System Integration
Testing
Production
ERP
Development &
Customising
(110)
Test Validation
DEV QAS PRD SBX Reimplement

After
Partner Solutions in SAP S/4HANA Cloud Private Edition • Revamp and simplify processes leveraging the
latest innovations.
• Partner Add-ons/Solutions can be installed, provided they are compatible and operate exclusively on the ABAP stack. Specifically
installation of third-party software requiring OS, HANA, and Applications is not allowed.
Greenfield • Execute innovative business processes using SAP
best-practice content on RISE.
• Perform initial data loading and retire the
• Installation of uncertified Add-ons may impact future upgrades and system performance and as such is subject to our Terms & outdated landscape.
Conditions.
Partner-Led ECS Migration Workflow, what to expect
Partner Scope SAP ECS Scope

Customer Landscape PCE Landscape
Dev
Dev
App QA
App QA
PRD
PRD DB App
DB App
App
App DB
DB
DB
Fast Network Connection Migration Limited Network Access DB
Server Access
SUM SWPM
to Dump
Files
On Premise
Migration Server S/4HANA Skeleton Systems

• Standard Linux image. • Constructed based on agreed BOM.
• Provided by SAP ECS. • Provided by SAP ECS.
Customer Site (On-Premise) • Hosted in PCE environment. • Hosted in PCE environment.
• Partners have full control (SAP not • Partners have full root access. • Only limited partner access to
Internal Firewall
accountable). • Allows Partners to run Target system systems allowed (i.e., SAP GUI).
• Request network connection setup. migration/conversion steps using
• Prepare systems for standard SAP tools (SUM,SWPM)
migration/conversion.
• Run source system *Migration server not required for Tenant Copy method
External Firewall
migration/conversion steps using

standard SAP tools (SUM,SWPM)
Available Partner Implementation Approaches
System conversion System copy New implementation Selective data transition
SAP Legacy SAP ERP

SAP ERP Legacy SAP ERP
S/4HANA
On Premise
SAP SAP SAP SAP

PCE Cloud S/4HANA S/4HANA S/4HANA S/4HANA
• Update of existing system, • Lift and shift method for • New best practice system • Suitable for:
configuration and data S/4HANA on-premise implementation • Consolidating multiple SAP
• Reuse existing customers • Data migration (harder for ERP instances
Configurations/Investment • Migration of existing system old data) • Partial system redesign
• Direct conversion to to PCE Cloud • Benefit from full S/4HANA
• Retention of historic data in
S/4HANA, private cloud possible innovations productive system
edition dependent on immediately.
source release • Carve outs
Main focus Main focus Possible alternative • Requires evaluation
Transition Strategy
The transition options and tools utilised for PCE projects differ based on the
source system release. Partners choose the most suitable approach,
considering the customer's specific circumstances and the characteristics of
their source system
Requirements
• Partners execute S/4HANA Conversions and System Copies with ECS
delivery support
• Only releases with at least 9 months maintenance left are supported for
migration to Rise.
• Lower releases require an upgrade before migrating to PCE.
• Customers must upgrade to the latest S/4HANA version as per contract
dates and before end of mainstream maintenance.
• If a target release is below 1909, compatibility of subcomponents (e.g.,
additional SKUs on S/4HANA) needs manual verification.
• Check that the source HANA version matches the ECS target system build
• *S/4HANA 2023 estimated Q4/23
Choosing the Transition Approach
SAP provides different migration approaches to cover the PCE Transition Approach Selection Process
various customer scenarios.
In the sales cycle, the most appropriate transition
approach is selected by considering various customer
factors like technical setup, environment, source system,
network details, and partner preferences.
Yes
DMOVE2S4
Is Downtime Are Bandwidth
Yes
Optimisation Limitations met?
The chosen approach impacts the items which are
Yes
required? (Latency <20 ms) &
bandwidth >400 MBit/s)
Does the
No
included in the contracted Bill of Materials (BOM) i.e., source system
Yes
require
Yes
upgrade ?
Tenant Copy
Is the
Yes
Source
inclusion of migration server, storage, bandwidth
Is DB large & is there
Yes
S/4HANA? at least 10 Gbit/s
network bandwidth?
System Choose Backup
No
Versions best fit
requirements etc. Restore
No
Source == option
Choose Target ?
PCE DMO with
Migration
No
System
Approach
Partners must thoroughly understand the contracted Move
Yes
Is the
Are Bandwidth
Source
transition approach in order to create an effective
Limitations met?
Yes
DB SAP (Latency <20 ms) &
HANA? bandwidth
>400 MBit/s)
Choose
No
Best fit
project plan. Is source
option
Export
No
system Import
ERP?
Partners need to align timelines and deliverables with Is source system Assisted
No
Yes
BO, Java or ABAP Migration
on ASE? Service
the selected transition approach by building the distinct Selective Data
SAP ECS milestones into their project plan. Transition
Applicable to hyperscalers i.e., GCP, AWS, Azure
Understanding Transition Methods
• Partners prepare for specific migration tools based on
the chosen approach.
• Understanding limitations and Roles and

Responsibilities related to the chosen approach is
crucial.
• Partners must inform ECS of the system build plan

before activities commence.
• Best Practice Advice:
Complete preparation activities technical project

preparation, pre-conversion project execution, and
fit-to-standard preparation for specific features
Finalise the conversion approach before PPF form

submission to avoid extra costs.
Consider target system's landscape, network, and

SIDs; changes may incur additional expenses.
System copy and tenant copy require target ECS-

hosted HANA database version to match or exceed
the source database version.
PCE System Conversion Procedure
Align with SAP ECS for

S/4HANA, Private Cloud Setup.
Source System On Premise Target System On PCE Cloud
Run Software
Gather System Maintenance Perform System Prepare Custom Complete Post
Update Manager
requirements planner Pre-Checks code Steps
(SUM)
Execute Independently in Switch to Target System for All Activities performed

Source System Technical Conversion Downtime in Target System via
SAP GUI.
PCE System Copy Procedure
• Existing S/4HANA customer system migrated into PCE, including customisations, settings and data.
• Partners must verify existing add-ons and features for compatibility with PCE ideally before starting migration
PCE Cloud TARGET SYSTEM

SOURCE SYSTEM
Migration Server
DB Import
On Premise
Take Full Offline HANA Backup Install Temporary Server, Use SAP GUI to complete post
Restore to Target Database, and System copy steps
Transfer/Present Backup to Complete Post-Processing with Only HANA Specific system
Migration Server SWPM copy method supported
Selective Data Transfer
• Selective Data Transfer (SDT), is a strategic method for Manual Adjustment
moving from existing SAP ERP systems to S/4HANA PCE S/4HANA S/4HANA
Process to Target Shell
• SDT allows organisations to move to SAP S/4HANA Create Shell Golden Backup Production Shell
selectively, reusing parts of their existing ERP solution while S/4HANA
redesigning others. This flexibility is especially useful when, System
System System
for example, only specific business areas need an overhaul or Conversion Copy
when merging or splitting existing ECC instances
• SDT involves transferring data, including ABAP repository,
configuration data, master data, and transaction data, from Shell Creation
(No Data)
existing ERP solutions to the new S/4HANA using specialised
tools and services.
• Within SDT, there are two common approaches: Shell
Conversion (for reusing most of the existing solution) and Mix
and Match (for redesigning a majority of the solution). Both
involve data migration with SAP Data Management and
Landscape Transformation (DMLT) software.
• SDT is beneficial when organisations want to go live in
phases, reduce re-implementation effort by reusing certain
application areas, mitigate the risk of a big-bang go-live, or
split/merge existing SAP ERP instances.
• SDT projects typically involve creating a parallel SAP
S/4HANA sandbox, using Shell Conversion or New Install,
and then migrating data selectively. This phased approach
can be extended to implement business transformation
innovations in subsequent stages.
Optimising Technical Setup for PCE Migrations
Migration Server Additional Storage Requirements Temporary Bandwidth Increase
Storage for the Object store, which is used for storing various SAP supports customers with temporary higher bandwidth
Two migration VMs per are supplied in the base costs.
objects, data, and configurations during the migration process, is requirements for RISE deals at no additional cost to the customer for
included in the base costs the duration of the entire migration project.
“Migration Server” method is mainly used for both Block storage on the Rise HANA DB server*, which is used for backup storage,
System Conversion and System Copy scenarios Customers can request the bandwidth increase at an agreed time
is not included in the base costs and requires an additional storage SKU for
pricing (varies depending on method used). frame, and the process takes roughly an hour. The request must be
raised via a service request.
Partners can use the "Migration Server" method to Block storage can be reused for each system/tier migration, eliminating the
efficiently handle end-to-end Rise migrations. need to purchase separately for each HANA server in the environment. SAP handles the Hyperscaler gateway port and bandwidth speed,
while customers need to work with their ISP connectivity providers
to increase the bandwidth of their own connection.
Storage on the migration server, which is used for storing export dumps in
“Migration Server” method cannot be used for certain
migration or S/4 Conversion projects, requires an additional storage SKU for
solutions (listed below) due to SAP tool launching and pricing ( space varies depending on method used).
dump transfer issues. In such cases, the "Migration After migration completion, the connectivity should be reverted to
Assisted Service" must be ordered to support the its original state.
Partner with the migration.
*In backup/restore scenarios, as Partners cannot access the HANA server
directly, they must copy the source system backup to the object store first.
Then, they must request the SAP ECS Delivery team to move the backup to the For DMOVE2S4 scenarios, minimum bandwidth requirements for
HANA server via SR. transition.
Solutions requiring “Migration Assisted Service”:
In case the cloud provider is Azure, then Blob storage can be mounted as
Java System Migrations NFS3.0 volume on customer On-Premise servers and ECS servers (DB + App + Technical prerequisites:
Migration Server). This mount will be used for data transfer purpose. Low latency (<20 ms)
BO System Migrations Note: SWPM can only be launched for a maximum of two systems via blob. To High bandwidth (>400 MBit/s)
ASE Migrations launch more than two systems, customers need to request additional storage. Note: that Microsoft has confirmed that Azure Blob does not support the SUM
PIPE method.
Migration Server
HANA
VM
PAS Add Block

Storage
(Backup)
RAM: 128GB ECS Only Access
Migration
vCPU: 32
VM
Disk: 100GB
Object
Store
Provides Partner Root
Access to install PAS for Add
Migration Purposes Storage
(Export)
Partner Access ECS Cloud
Key Project Handover
Points
Brownfield Transition Process
▪ PCE Brownfield migrations are performed by organisations looking to
modernise their SAP systems while retaining their existing
investments, including data, customisations, and processes.
▪ Partners migrate customer systems from an existing on-premise SAP
landscape, with or without conversion, into the SAP S/4HANA Private
Cloud.
▪ The Partner team is responsible [not SAP] for leading the transition 1.Partner performs System
and/or conversion of source system tasks. Copy/ System Conversion
(DMO with System Move,
ECS Tasks
▪ SAP ECS is responsible for technical administration of target systems DMOVE2S4)
hosted within the RISE environment (incl. system provisioning, 2.Partner completes the
start/stop of servers, finalising post steps etc.) import/conversion tasks 3. ECS starts up skeleton
4. Partner completes final application server on request
▪ During the project Partners must trigger SAP ECS responsible tasks by
migration post processing and 5. ECS completes hosting
opening incidents and service requests to the build team at various post steps and configuration
points by selecting the appropriate SR template from the Launchpad. configuration tasks after the
in target system limited to
system move R&R obligations.
▪ It is important to follow the Lead Time of 2 days for raising a Service
6. ECS Hand over System
Request. Lead Times may vary depending on which service is & Move to Run with RISE
▪
requested, which will be mentioned in the Template for creating SR.
As soon as the partner is finished their post processing tasks the
Partner
system must be handed back to ECS for post processing ( see deep
dive rise handover process slide). The handover to ECS should be Tasks
done along with the completed brownfield Excel.
Overview of Typical System Handover Points
Discover Prepare Explore Realise Deploy Run
• Partner notify SAP for • Partner receives all • Partner gives SAP with • Partner gives SAP 10 • Partner gives SAP with • Partner gives SAP 10 • SAP performs post go-
Migration Assisted Skeletal System from 10 days' notice when business days' notice 10 business days' business days' notice live checks.
Service, if required. SAP. the system will be when QAS will be ready notice when the Dry that the system will be
• SAP Implement CQC
ready for post- for post-processing. Run system will be ready for Go live post-
• Partner submit • SAP Implement High (Customer Quality
processing. ready for post- processing.
completed PPF form Availability (HA) if • Partner requests Center) parameter
processing.
within business 5 days applicable. • After completing the startup of skeleton • After completing the recommendations.
of Signature. import/conversion application server by • Partner requests import/conversion
• Partner gives SAP with • SAP Runs System
tasks that are raising an SR and startup of skeleton tasks that are
• Partner place orders 10 days' notice when
performed on the selecting the template application server. performed on the
for standard services. the system will be
Migration Server. “SWITCH APPLICATION After completing the Migration Server. The
• Partner request SAP ready for post- import/conversion Partner requests start
BACK TO MAIN
CQC services. processing. • Partner requests tasks that are up of skeleton
INSTANCE POST
startup of skeleton performed on the application server by
• Partner & Customer • Partner requests MIGRATION” in
application server by Migration Server raising a Service
participate in startup of skeleton customer launchpad.
raising an SR and Request by selecting
migration kick off call application server by • After completing the
selecting the template • After completing the the template “SWITCH
with SAP PL. raising an SR and import/conversion
“SWITCH APPLICATION import/conversion APPLICATION BACK TO
selecting the template tasks that are
• Partner share project BACK TO MAIN tasks that are MAIN INSTANCE POST
“SWITCH APPLICATION performed on the
plan with SAP PL INSTANCE POST performed on the MIGRATION” in
BACK TO MAIN Migration Server
(Project Lead). MIGRATION” in Migration Server customer launchpad.
INSTANCE POST
customer launchpad. • Partner hands over Dry
• If needed, Partner MIGRATION” in • Partner hands over QAS • After completing the
customer launchpad. • After completing the for Post Processing by Run system for post
requests temporary import/conversion
import/conversion SAP processing by SAP
increased bandwidth • After completing the tasks that are
via SR (Service tasks that are • Partner requests DR performed on the
import/conversion
Request). performed on the Test if in scope Migration Server
tasks that are
Migration Server
performed on the • Partner then hands
Migration Server • Partner hands over Dev over PRD system for
for Post Processing by post processing.
• Partner hands over SBX
SAP
for Post Processing by
SAP
Deep Dive: System Migration Handover Process
ECS Configuration
[FRUN Setup]
Standard Rise Migration Process
Factory Model Less Partner Control Clear Communication Service Request SLAs
Factory Model restrictions based With PCE, partners' control of the Clear, accurate and timely Consider factory lead and
on R&R; Partner need to end-to-end migration process is communication is crucial. SAP ECS processing times in planning to
understand and plan handover reduced. Limited access to ECS acts based on received avoid unexpected delays in system
points with SAP for smooth hosted systems leads to the instructions, including SRs and handover.
transition requirement to raise SRs for incidents.
routine tasks
Project Planning
& Resourcing
Typical Project Durations
SMALL MEDIUM LARGE

PROJECT PROJECT PROJECT
(Weeks) (Weeks) (Weeks)
PREPARE 1 2 4
EXPLORE 5 9 12
REALISE 3 7 10
DEPLOY 1 2 4
Total: 10 Total: 20 Total: <30
Timelines are approximate, project duration normally depends on scope, available resources, and desired speed of completion.
Overview of PCE Phases & Milestones
Discover Prepare Explore

~2-4 weeks ~ 4-6 weeks ~6-8 weeks
• Identify business needs, objectives, and challenges. • Define detailed project scope and objectives. • Conduct detailed business process analysis and
• Conduct feasibility studies and solution assessments. • Create comprehensive project plan with timelines requirements gathering.
• Define project scope and goals. and milestones. • Perform system configuration and customisation.
• Identify key stakeholders and assemble the project team. • Perform detailed solution design and configuration. • Develop functional specifications for customizations.
• Perform initial high-level planning. • Set up project governance and establish roles and • Create test scenarios and scripts.
• Plan system landscapes, infrastructure, responsibilities. • Conduct integration testing and resolve any issues.
and technical requirements. • Sandbox usually temporary system created using
Quality resources (reuse)
Key Phase Deliverables Key Phase Deliverables Key Phase Deliverables

• Identify if Migration Assisted Service Needed • Finalise Project Plan and share with SAP ECS Project • Migrate Development System
Lead
• Partner Cloud Architect (PCA) to Provide completed • **Raise required ECS Build Task SRs
PPF Form within 5 business days • **Request temporary increase in storage and
bandwidth for migration via SR ( if required)
• **Order Standard Services for source system as
required • Handover Systems
• **Order SAP Enterprise Support CQC Services as • Migrate Sandbox System

required
• **Raise required ECS Build Task SRs
*Duration and activities depend on the selected scope item(s) and on customer requirements.
SAP involvement Partner involvement **SRs are subject lead time and ECS SLA’s, e.g., stop/start application servers, move export dump to RISE servers etc.
Overview PCE Phases & Milestones (cont.)
Realise Deploy Run

~12-16 weeks ~ 2-4 weeks ~ Ongoing
• Execute the detailed solution design. • Finalise system configuration and data migration. • Monitor system performance and user feedback.
• Customize and configure SAP system components. • Conduct user acceptance testing. • Provide ongoing system maintenance and support.
• Develop and test interfaces and conversions. • Prepare cutover plan for system go-live. • Conduct regular system updates and
• Conduct end-to-end system testing. • Perform data migration and system cutovers. enhancements.
• Prepare and execute user training • Execute go-live and provide post-go-live support. • Perform system optimisation and performance
tuning.
• Continuously assess and improve system
operations.
Key Phase Deliverables Key Phase Deliverables Key Phase Deliverables

• Migrate Quality System • Deploy/Cutover Production System • Apply SAP EW Recommendations
• **Raise required ECS Build Task SRs • **Raise required ECS Build Task SRs • Rise team take over support
• Complete Dry Run and DR test
• **Raise required ECS Build Task SRs
**SRs are subject lead time and ECS SLA’s, e.g., stop/start application servers, move export dump to RISE servers etc.
SAP involvement Partner involvement
PCE Sample Plan On A Page
PCE Dry Run & Cutover Supports
PCE Support for Dry Runs ECS Post Processing Support

• Standard PCE basic contract scope offers additional test • ECS Post Processing Tasks are performed after the Partner
runs with the option to add more as a billable service if completes Migration and Post System Copy Tasks.
required
• These tasks involve the internal setup of ECS components which
• One for migration scenarios are not accessible by the Partner/Customer resources.
1. Additional test run of the production (PRD) system
• Timeframes and lead-times for requesting these actions via
• Two for S/4HANA conversion scenarios: Service Requests should be incorporated into your Migration
1. non-production (QAS, DEV, etc.) system and Cutover Plan.
2. productive (PRD) system
• If PRD hardware is used for dry runs, there is no need to Non-Production

rebuild the target system for the final run; Partner can
simply drop the database and continue migration. • Non-PRD Post-Processing Duration: 4 Business Days.
• Customer can perform multiple dry runs using the • Non-PRD Post-Processing Lead-Time: 5 Business Days.
Migration VM process, but ECS post migration/build Production
activities are limited as per R&R.
• PRD & Dry-Run Post-Processing Duration: 14.5 hours (2 hrs pre-
• For SBX run, QA or PRD tier resources can be reused if no checks, 10.5 hr Post processing + 2 hr Validation checks by ECS,
standalone SBX included in contract . (+ 2 more hours for Java systems), (+3 more hours in validated
GxP environments)).
• PRD & Dry-Run Post-Processing Lead-Time: 3 weeks.
Sample Project
Team Structure
Example PCE Project Team Structure
• Partners need to stand up their own

dedicated project team to run the
migration project effectively.
• Alignment between the SAP Project
Lead and Partner Project Manager
is crucial throughout the project to
maintain coordination and achieve
project objectives.
• Establish clear communication
channels and setup regular
meetings between SAP, Partner and
Customer to foster seamless
collaboration.
• Regularly review the project
progress and milestones to address
any potential risks or roadblocks
promptly. Alert SAP as and when
necessary.
• Ensure all stakeholders are
informed about the project status,
achievements, and upcoming
milestones to maintain
transparency and support *Actual organisational structures will depend on the project scope and on customer requirements.
throughout the project.
SAP Partner Manager
Responsible for managing and nurturing relationships with SAP's partner ecosystem. They work closely with partners to drive mutual
business growth, enable successful implementations of SAP solutions, and ensure partner satisfaction. SAP Project Support Structure
Responsibilities
▪ Manage and cultivate relationships with SAP's partner ecosystem to drive mutual growth and success.
▪ Collaborate with partners to drive business growth, leveraging synergies for mutual benefit.
▪ Enable successful implementation and delivery of SAP solutions by providing partners with support, guidance, and necessary resources.
SAP Industry Account Executive(IAE)

Owns the account relationships SAP line of businesses and ECS, Contact for all contract related topics
Responsibilities
▪ Building customer relationships and understanding their business challenges
▪ Developing industry-specific sales strategies and go-to-market plans
▪ Collaborating with customer executives for digital transformation opportunities
▪ Supporting the customer throughout the sales cycle for successful deals
SAP Project Lead (PL) SAP Digital Customer Engagement Manager (dCEM)
Primarily responsible for managing the ECS project activities during the Bridges the gap between customers, SAP, and implementation partners
customers’ lifecycle in ECS to ensure project success.
Responsibilities Responsibilities
▪ Coordinates with Customer Project Team (Customer & SI) and the ▪ Liaise between customer, SAP, and implementation partner
extended SAP teams to align project information, requirements ▪ Guide on SAP RISE methodologies, best practices, and migration
and rollout timelines. ▪ Understand and fulfil customer needs throughout the project
▪ Technical planning of major Customer upgrades ▪ Expertise in leveraging SAP technologies effectively
▪ Escalation Management during planned project activities
SAP Technical Services Manager (TSM) Customer Delivery Manager (CDM)

Primary technical contact for all technical and infrastructure related Primary point of contact for ongoing service and support requirements
topics of the customer.
▪ Leads and advise ECS technical teams regarding Service Delivery ▪ Ensures regular weekly operations and service sync meetings with
▪ Supports the customer technical queries the customer throughout the duration of the SAP ECS contract.
▪ Act as the technical single point of contact during the de- ▪ Contract administration and operational change management.
escalation process ▪ Escalation Management during operational run phase..
SAP ECS Resources ( COE, Backoffice, etc)

Dedicated groups responsible for ensuring the successful implementation,
support, and optimisation of SAP solutions within an organisation.
Responsibilities *Actual organisational structures will depend on the project scope and on customer
▪ Provide expertise and guidance on SAP technologies and best practices requirements.
▪ Optimise SAP solutions to improve efficiency and productivity
Partner Account Executive (AE)
Nurtures and manages relationships with customers. Working alongside SAP Industry Account Executives (IAEs), they play a vital role Partner Rise Project Team Structure
in building and strengthening partnerships to drive business growth and deliver value to SAP customers.
Responsibilities
▪ Work with SAP IAEs to align offerings with customer needs and challenges.
▪ Facilitate effective communication and collaboration among the partner organisation, SAP, and customers.
▪ Understand customer requirements and tailor partner solutions to meet their customers specific needs
Partner Project Lead (PL) Partner Cloud Architect (PCA)

Oversees and manages the project from the partner organisation's Provide expertise and guidance within the partner organisation
perspective. Responsibilities
Responsibilities ▪ Collaborate with customers and SAP CAA to design and
▪ Coordinate project activities and resources to ensure architect scalable solutions
successful implementation. ▪ Assess customer requirements and align them with suitable
▪ Serve as the primary point of contact for the partner SAP Rise cloud offerings.
organisation and facilitate effective communication. ▪ Implement and optimize SAP cloud solutions, ensuring
▪ Ensure project is delivered on time, within budget, and meets efficiency and maximising benefits for customers.
customer requirements.
SAP Technical SAP Functional

Serves as a Partner SAP Technical Basis Rise expert within the Fulfil the role of a Partner SAP Functional expert within the
partner organization partner organization.
▪ Provide technical expertise on SAP Basis for SAP Rise projects. ▪ Work with customers and partners to provide functional
▪ Assess customer requirements and align them with SAP expertise and guidance on SAP Rise solutions, aligning
technical solutions and best practices. customer requirements
▪ Support setup, configuration, optimisation, and smooth ▪ Implement and optimise SAP functional modules to meet
operation of systems and landscapes customer needs
▪ Offer guidance on best practices, business processes, and
industry-specific requirements
Data Migration
Testing, Change Management, Training…
Serve as a Partner Data Migration expert within the partner
organization. Responsibilities
Responsibilities ▪ Implementation of other essential project tasks including
▪ Collaborate with customers and partners to understand data OCM activities to ensure successful onboarding to Rise
migration requirements and align with SAP RISE methodologies.
▪ Develop and execute migration strategies, plans, and mappings *Actual organisational structures will depend on the project scope and on customer
for accurate data transfer. requirements.
▪ Ensure data integrity and collaborate with cross-functional teams
Chief Information Officer
Leads the development of a strategic roadmap for SAP implementation, aligning it with the organisation's business objectives and
long-term goals. Customer IT Organisation Structure
Responsibilities
▪ Oversees the evaluation and selection of implementation partners to ensure the best fit for the organisation's needs.
▪ Responsible for overseeing the project's execution, ensuring it stays on track, on budget, and meets predefined milestones.
▪ Ensures that the SAP system integrates smoothly with existing IT infrastructure and other business applications.
▪ Maintains clear communication with other C-suite executives, stakeholders, and employees to keep them informed about the
project's progress and benefits.
Infrastructure manager
Oversees all aspects of the IT infrastructure that support the SAP system Migration to Rise
Responsibilities
▪ Collaborates with project stakeholders, including the CIO, project managers, and SAP
functional teams, to define the infrastructure requirements for the SAP project
▪ Ensuring Network architecture in place to support project, express route etc
▪ Implementing and enforcing security measures to protect the SAP system and its data from
security threats.
▪ Collaborating with SAP functional teams to understand their requirements and align
infrastructure decisions with the project's overall objectives.
Technical Lead (Basis Manager) Network Lead

▪ Primary point of contact for ongoing service and technical ▪ Primary Point of contact for connectivity and networking
support requirements of SAP solutions items between customer and SAP Solutions, express route,
▪ Requesting Storage extensions Direct connect , interconnect
▪ Requesting Bandwidth extensions
▪ Technical documentation of on-premise solution
*Actual organisational structures will depend on the project scope and on

customer requirements.
Partner Escalation Path
• Partners can escalate issues to the

Project & Program(P&PO) ECS Support Channels
Management team via email if
unsatisfied with issue support and
resolution from the SAP Project Lead.
• The regional P&PO management may
then choose to involve the industry
account executive team if required.
• The P&PO management can also
reach out to the assigned Partner
contact to participate in the
escalation process.
• The Strategic Partner Management
team assists in resolving escalations
Managing the Change
Process
RISE Factory Model Request and Incident Management
Software Incident Technical Infrastructure Service Request

A request for a desired change in a business process or
A problem or failure with the standard SAP
service related to standard core services. For instance,
software, such as a function or capability not requests for technical updates involving downtimes or
working as documented or expected. HANA revision upgrades.
ECS
Factory
Technical Incident Model Security Patch Service Request
An unforeseen disruption to a technical system
A request for security patches to address
function, for example, when a system is
threats and vulnerabilities in the ECS
inaccessible.
infrastructure.
• In the RISE Factory Model, partners must follow the process when contacting ECS. This entails submitting a ticket for each SAP Enterprise Cloud Services
request and categorising it as either a Service Request (SR) or an Incident (INC) based on the nature of the request using the relevant Fiori tiles
• Service Requests involve tasks outlined in the Roles & Responsibilities (R&R) document, covering technical activities like System Restart, Parameter Changes,
Client Copy, etc.
• Some services are standard and covered by the private cloud contract, while others may incur additional costs; refer to the R&R for details.
• Incidents represent unexpected events causing operational disruptions, such as system downtime or incomplete production system upgrades.
Priority 1 Incident Request Workflow
Typical Service Request Workflow
How to Initiate a Client Copy Request
Customers start the Service Request process

in the Service Request App in the SAP One
Support Launchpad
➢ Choose a template
➢ Utilise searchable keywords in the upper right of the window
➢ Flag commonly used ones as "Favourites"
How to Initiate a Client Copy Request (Cont.)
How to Initiate a Client Copy Request (Cont.)
➢ Choose the service execution start time

➢ Schedule the request with a 1-hour lead time
How to Request Security Patch
• From the "Security Patches" tile select the

relevant system for patching
• Create a service request directly and set
maintenance windows for ECS to apply
patches.
• Not all security patches need downtime.
• If downtime is needed, it can be scheduled
during the regular maintenance window or at a
convenient time.
• Usually, the latest patch is applied to the first
tier, and then the same version goes to the
others.
Upgrade and Patching Responsibility
Technical Basis Tasks Logical Basis Tasks

• In RISE PCE, SAP is accountable for executing technical upgrades upon the • Customers or partners can perform tasks such as planning, coordination,
customer's request. proactive services, implementing SAP Notes, manual corrections, and
application-related technical tasks.
• Customers can utilise SAP Cloud Application Services for package-based
services, including release upgrades, application security upgrades, support
management, and testing execution.
SAP ECS ONLY SAP CAS, PARTNER or CUSTOMER Responsibility
R&R Ref. Service Category Service Description R&R Ref. Service Category Service Description
OS and DB Upgrade and Patching Application Software Upgrade and Patching
INFRA 1.6.12 Standard Software Lifecycle Management of operating system BASIC_1.1.01 CAS Version upgrade/update of SAP Software: planning and coordination
HANA_1.1.33 Standard SAP HANA version upgrade and update of DB Client Implement SAP Notes, transport-based corrections instructions (TCI), and other types of
manual corrections (corrections not provided as software correction package) in managed
HANA_1.1.12 Standard Update SAP HANA database software
BASIC_1.5.03 CAS system (notes and corrections required to fix application related issues)
HANA_1.1.12A Standard Install or Update SAP HANA client
BASIC_1.5.22 CAS Version update of SAP Software: Pre- and Post BASIS Tasks
HANA_1.1.33 Standard SAP HANA version upgrade and update of DB Client
Execute application related technical error handling tasks as part of the technical
DB_1.1.11 Standard Perform upgrades of database software
BASIC_1.5.08 CAS execution process for upgrades and updates and for Change Management
DB_1.1.12 Standard Apply database patches
Application Software Upgrade and Patching
Implement SAP Notes, transport-based corrections instructions (TCI), and other types of
BASIC_1.5.04 Standard manual corrections (corrections not provided as software correction package) in managed
system (notes required to fix issues related to technical SAP components)
BASIC_1.5.06 Standard Implementation of patches for system software running on OS level, e.g. SAP kernel
BASIC_1.5.07 Standard Version upgrade of SAP Software: Execute technical upgrade tasks
BASIC_1.5.09 Standard Implement updates to the managed SAP solution using standard tools and methods
BASIC_1.5.10 Standard Ongoing maintenance of system languages, e.g. performing language fill-up
BASIC_1.5.21 Standard Implement kernel patches using Rolling Kernel Update Service
Implement updates or upgrades to the managed SAP business software - ABAP solution
BASIC_1.5.11 Additional using Zero Downtime Option (ZDO) of SUM which is part of the Maintenance Downtime
Minimization Service
BASIC_1.5.20/
Additional Conversion of SAP ERP & BW Systems to SAP S/4HANA & SAP BW4/HANA
MOVE_1.3.02
Support Channels
SAP provides various support offerings and trainings to make sure you team is effective in collaborating with SAP Support
SAP ONE
Global Delivery Management Support Launch
CIC SAP for Me Pad
Organisation Services Supports
Level 1 SAP Launchpad
ECS Office of the CTO Service & Planning
Support
ECS Cross Delivery and Security Office Escalations Change Requests
Raise Service & Incident Requests
Catch &
ECS Customer Office Innovation & Adoption
Dispatch SAP CIC Expert
(24/7) Chat
Onboarding &
Alert Management and Automation
Adoption 24/7 Customer Interaction Center (CIC)
L1 & L2 Incident Management Option CAS Services
Non Standard Customer Hotline
Request Fulfillment
Requests
Major Incident Management Project Management
Technical
Database Management
Management Service & Delivery Management
Server Management
Service Management; Project Management; Technical
Backup, Disaster Recovery & Infrastructure
Management; Primary Contacts for Customer Lifecycle;
Cloud Application Services – optional service Escalation Points
Typical Project Issues &
Mitigations
Typical Migration issues
Typical challenges that Partners have encountered when
delivering Rise Migration Projects include: Reported Partner Challenges
Service Requests
• Most problems arise when the partner’s delivery team doesn't fully & Processing
understand the Rise migration process and tooling, especially in complex Times
areas like SYBASE migrations. 14%
Technical
• Another common issue is the absence of a clear initial plan or Knowledge Gaps
unexpected scope changes during the project. These changes can be 36%
technically challenging to accommodate within the Rise factory model
because once the environment has been setup it can significantly impact Awareness of
Rise Factory
the project timelines and costs to adjust often resulting in partial or full
Model
rebuild effort for ECS, i.e., transitioning from a brownfield to a greenfield
18%
approach at the start of project.
• Although Partners may possess expertise in on-premise migrations, they

often encounter challenges due to the nuances of the PCE environment
which contributes to confusion and inquiries and escalations to SAP.
Typically, this manifests as a lack of awareness regarding the PCE
Factory model operation and the Roles & Responsibility Matrix.
Knowledge &
Planning
Service Requests & Processing Times Project Planning

& Scope Changes
• Partners often do not provide clear communication and instructions in 32%
their correspondences with SAP, leading to misunderstandings and
issues which arise particularly at the ECS handover points.
Inexperienced partners also tend to overlook lead and processing times
for service requests and incidents resulting in unforeseen project delays.
Common Pitfalls and How to Avoid Them
Commonly Reported Issues Mitigations
TMS setup issues. • Place experienced staff in key roles.
Technical & Infrastructure
• Incorrect system sizing • Make sure to validate network configurations to avoid overlapping segments before
submitting PPF to SAP.
• Delays in access and user creation.
• Complete and return PPF with accurate information within 5 days of contract signing to
• Challenges with system sizing, disk mounting, storage, and network avoid delays
setup.
• Do not wait to log on to systems, check specifications of servers at handover
• Overlapping segments, DNS & VPN setup challenges, slow file
transfer. • Request temporary increase in bandwidth and storage via SR as required
• Coordination issues. • Clearly understand the roles and expectations as defined in the Roles and Responsibilities
Communication &
• Slow or inadequate partner communication. Matrix (R&R).

Coordination
• Challenges with ECS timelines. • Set up regular communication channels and meetings with ECS SAP Project Lead.
• Miscommunication, escalations, and unclear technical dependencies. • Align timelines with ECS requirements during planning, i.e., embed PCE milestones and SR
creation lead times into project plan.
• Customer not aligned
• Maintain clear, timely and concise communications with SAP and customer
• Lack of RISE migration process understanding, Ignorance of • Firm up the project scope at the start.
lead times, schedules etc • Use experienced resources in key project roles and keep them same resources engaged
• Lack of migration process knowledge, technical expertise. throughout the project lifetime
Knowledge &
Build plan accordingly, share with SAP early, conduct regular reviews to monitor scope
Planning
• Challenges with upgrading and migrating. •
• Improper project planning, documentation, creep – costs time and money ( employ good project management practices)
• Changing Scope from greenfield to brownfield after initial system delivery • Partner Project Manager must lead the migration project ( Not SAP ).
• Partner team should complete Rise certification (Rise Sell/Service trainings) before project
starts.
Common Pitfalls and How to Avoid Them (cont.)
Commonly Reported Issues Mitigations
• Settle system landscape build specifications (SID, System #, ports etc) before build starts.
• Issues related to system post-processing (e.g., HANA DB user Thoroughly review PPF before returning to SAP.
password).
• Conduct thorough end-to-end testing (SIT, UAT).
• Delay in handover of systems for post-processing.
System Specific
• Perform dry run-on Production kit.

• Unexpected issues with system backup and restore during migration.
• Verify system readiness before handing over to SAP for post-processing.
• Interface issues.
• Maintain proper documentation of system configurations and passwords.
• Requesting changing of SIDs without following ECS timelines.
• After restore the source system overwrites the base ECS build (skeletal system) including
users. Update ECS with the new user and passwords
• Original ECS Skeletal system backup is available for only 15 days, if longer retention is
required Partners are responsible for copying the backup image to supplied storage pool
• Project experiences unexpected delays and escalations • Make sure team thoroughly reviews the R&R to understand roles and responsibilities from
• Unclear timelines and steps. the outset of the project.
SAP Services &
Collaboration
• Partner expecting SAP to perform tasks that are actually their own • Give clear and timely instruction to ECS specifically at the handover points
responsibility. • Build a close relationship with the SAP PL and maintain regular communication throughout
• Ineffective collaboration between Partner/SAP/Customer during the project. Keep them up to date on progress and flag key dates well in advance
migration. • Partners own the migration project delivery and should therefore proactively schedule
regular calls with ECS PL to keep SAP updated on progress
Monitoring Overview
SLA Overview
RISE Production SLA Spans the Entire Solution Stack
• RISE offers customers a guaranteed up to 99.9% SLA for
uninterrupted service. Customer
• SAP ECS brings together hyperscaler infrastructure, • Standard SLA: 99.7%
• Premium SLA: 99.9%
software, enterprise support, and services for efficient
SAP workload operation in the cloud under one roof. This
includes simplified management with a single contract,
one SLA, and a unified point of contact for easy
administration
• SAP ECS utilises advanced technologies and a 24/7

SAP APPLICATION
operations team to meet availability goals, monitor
customer system health, and enhance overall service. Comprehensive
availability SLA
SAP HANA DATABASE provided by SAP
• Singular accountability as SAP oversees software extends across
support, technical services, and cloud infrastructure, each layer
allowing customers to focus on core business processes. OPERATING SYSTEM
• SAP team committed to optimising cloud performance
and ensuring efficiency of mission-critical systems.
Knowledge &
HYPERSCALER
Planning
Hyperscaler
• The Service Level Agreements (SLAs) for RISE PCE can specific
be found at this link. service SLAs
apply
Monitoring in RISE
• Monitoring in ECS is focused on Infrastructure, Database, and SAP Applications
allowing proactive intervention and quick response to incidents facilitated through
integrated tools across servers, infrastructure layers, monitoring cockpit, incident
management, and continuous improvement system. It is built on the following
components:
• Primary Monitoring: Based on SAP Monitoring solution ‘FRUN’ or Focused ECS Hosted Customer Systems
Run, which concentrates on application and database monitoring. All SAP
Private Cloud systems are linked to a central FRUN system.
• Secondary (Emergency) Monitoring: Implemented through Nagios/ICINGA2.
• IT Infrastructure Monitoring: Encompasses infrastructure-related aspects

such as network, server, and storage. Servers are provisioned and monitored
using our internal tools and Prometheus. The collected metrics, processed in SAP Basis + DB SAP Basis + DB Prometheus
the Service Provider Cockpit, are stored in Victoria Metrics for long-term CAS Services (Primary) (Secondary) Infrastructure
storage, and Grafana provides visual analytics using Prometheus and Victoria
Metrics as data sources.
• SPC Alert Inbox: Processes alerts from FRUN and Nagios around the clock.
Alert Inbox
• SAP ECS solely monitors and manages shared devices hosted within ECS environment
Service Provider Cockpit
• SAP does not monitor the network connection between ECS and Customer On-
prem environment.
• VPN connections are not monitored and there are no SLAs for VPN
connections.
• Note: IPSEC-based VPNs are unsuitable for permanent use in business-critical
scenarios.
• For critical business operations, it's best to choose a more robust solution such
Knowledge &
as Hyperscalers VNET Peering, Azure Expressroute, AWS Direct Connect, or

Planning
GCP Cloud Interconnect. These premium services, directly contracted from the
hyperscaler by the customer, provide advanced support and service level
agreements (SLAs) beyond RISE's coverage. It's the customer's responsibility
to arrange these services.
• Running an on-premise Solution Manager system enables the use of SAP's Monitoring
and Diagnostics tooling. If additional application or business monitoring is required,
customers are responsible for configuring it themselves. And their operations team will
need to manage the routine monitoring and alert-handling activities.
Security Overview
Customer Connectivity Options
Site-to-Site VPN
•Site-to-site VPN connects on-premise network with Dedicated Connection
Hyperscaler Network, encrypting traffic. • For Reliable access to productive workloads: opt for a
•Customers establish IPSec-based Site-to-Site VPNs over dedicated private connection with redundancy.
the Internet for cloud network connection. • Hyperscalers (AWS, Azure, GCP) provide solutions like
•Point-to-Site scenarios not supported. AWS Direct Connect, Azure ExpressRoute, GCP Cloud
•VPN configurations vary by Hyperscaler platform (AWS, Interconnect for network connection.
Azure, GCP) with detailed requirements in respective • Find details about edge locations and networking
documentation. partners in respective hyperscaler documentation.
•RISE with SAP S/4HANA Cloud, Private Edition's base
option comes with VPN connectivity by default, and
additional options are available through specific SKUs.
Fiori Access
• Fiori apps can be made accessible from customer mobile SaaS Integration
WAF
devices over the Internet. • S/4HANA Private Cloud Edition provides connectors and CON
• Publishing to the Internet requires TLS 1.2+ encryption agents for S/4HANA integration with SAP public cloud
with customer certificates. solutions.
TLS 1.2
TLS 1.2 • Internet inbound access secured by a Web Application • Agents provisioned upon customer request and
Firewall (WAF). acquisition of specific cloud solutions.
• Access not enabled by default; customers must specify • Outbound connections follow a restricted access control
during onboarding. list in the cloud's security components. CON
• Post-implementation, a pure internet approach via HTTPS • All outgoing accesses must use TLS 1.2 or above for in-
is feasible for Fiori apps. transit encryption.
• SAPGUI over the internet is not supported.
PCE is built on Zero Trust Principles
Zero Implicit Trust
• Treat all users, devices, networks, and apps as untrusted.
• More details can be found at SAP Trust Center
Verify Data Sessions

• Authenticate all data flows with least privilege.
Micro Segmentation
• Implement to limit lateral threat movements.
Role-Centric Access
• Consistent, secure access based on roles and context.
Minimum Access Principle

• Grant minimal access following least-privileged principles.
Adaptive Policies
• Centralised control for dynamic policy enforcement.
Data Protection Measures

• Encrypt, anonymise, tokenise, and obfuscate data.
Continuous Monitoring
• Log and monitor for suspicious activity at all levels.
PCE is Aligned with the NIST Framework
Identify Protect Detect Respond Recover

• Network Security – • Continuous Monitoring and
• Asset Management
Segmentation, WAF, NSG Logging • Remediation
• Risk Management
• Data Security • Event Correlations • Response Planning
• Security Governance • Disaster Recovery
• Secure Cloud Admin Access • Security Incident • Communications
• Configuration Management Planning/Testing
• RBAC – CAM Management • Root Cause Forensic Analysis
• Supply Chain Risk • Lesson Learned
• Security Patch Management • VAPT • Security Breach Notifications
Management (Sub • Security Automation for
• Communications
• Security Controls at various
processor/Subcontractor) layers Detection
Security Patch Management Malware Management

24x7 Security Monitoring 24x7 Incident Response
Vulnerability Scanning Identity & Access Management
Privileged Identity
Vulnerability Advisory Cloud Security & Compliance Root Cause Analysis Advanced Forensics
Management
Customer Penetration Testing Backup and Restore
Single Tenant Data Application Security Audit

Hacking Simulations PII Data Breach Notification Lesson Learned
Segregation Logs (SAL)
Cloud Security Compliance Security Hardened System

Scanning Cloud Security Configuration
DDoS Protection Checks
Security Awareness
Web Dispatcher (Proxy)
Baseline Configuration Checks
Asset & Change Mgmt.
Cloud Connector
Golden Image (Hyperscaler)
Application Security Updates
Securing the Environment
Vulnerability Customer Managed
Management and SAP
Logically Isolated Enhanced Penetration Testing Data and Process Security
Functional • Safeguard own data and configure business processes securely.
Virtual Private Compliance Layer
Network and Audits
Auto Restart High User Identity and Access Management
Availability and • Manage user identities, authentication, and authorisation effectively.
Regional Disaster Application
Recovery Secure Integration and Audits
Basis Layer • Ensure secure connectivity to cloud services, integrate with SAP securely, and conduct regular
security audits.
24x7 Security
Resilience
Monitoring and
Personal Data
and TCO of Technical SAP Managed
Hyperscaler Operations by SAP
Breach Technical Independent Attestation and Certification
Infrastructure
Notifications Basis Layer • Validated and certified RISE security measures implemented to meet the highest industry standards
Service Resiliency
• Guaranteed 99.7% SLA with a focus on high availability and robust disaster recovery (if in scope)
Database
Layer Vulnerability Assessment and Penetration Testing
Dedicated Account/Subscription/Projects • Proactive identification & remediation of system vulnerabilities, reinforced through simulated attacks
for enhanced defence.
Operating Cloud Operational Security

• Robust security protocols implemented and safeguards established for both data and processes.
System Layer
Reference Architecture
Upgrade Installation on Code Enhancement & • Adherence to secure, standardised infrastructure blueprints ensuring consistent and reliable system
Customer Request Modifications design
Storage Layer
Platform Logging and Monitoring
• Monitoring and logging of activities for early threat detection and troubleshooting, offering real-time
insights into system behaviour.
Network Hyperscaler/SAP DC Account Management

Access to S/4HANA Extensibility Framework Layer • Accounts managed securely within hyperscaler and SAP data centres, exercising precise control over
access and permissions to thwart unauthorised intruders.
Security Operation & Governance
Design & Build Account Security Data Protection Monitoring & Operational
& Privacy Logging Security
• Preventive Controls • Sub-Processor and Sub- • Incident Management • System Hardening
•Account Creation • Monitoring, Alerting, and
•Cloud Network and Detective Contractor Oversight • Regular Scheduled
Monitoring • Personal Data Breach Forensic Analysis Maintenance
Configuration (VPC, Subnet, • Real Event Correlation
NSG, WAF, LB, DNS, Proxy) • Cloud Account Life Notifications • Access and Change
Cycle Management • Secure Data Deletion at and Security Event Management
•IP Addressing Management
•System Build • Golden Image (VMs, Contract Termination • Security Patch
Containers) • SAP DPA and • Personal Data Breach Management
•SAP Global Security Policy Notification
Deployment • Compliance Security Technical/Organisational • Administrative
Scanning. Measures (TOM) • Security Use Case Access and User
Development Management
• External Cyber Threat • Backup and Restore
Intelligence
Support Audits Resilience & Security Contracted

Offerings Continuity Assessments Responsibility
• Global implementation and
management of key security
• SAP Cyber Security • Bi-Annual SOC 1 and • Cloud Disaster • Regular Vulnerability operations.
Team SOC2 Audits and Recovery Management • R&R INFRA_1.6.04 Inform customer
• SAP standard support Report Management • Regular Penetration regarding security incidents
• R&R INFRA_1.8.xx Backup &
offering • ISO 27001 Audits • IT Service Continuity Testing Restore
• SAP Enterprise support • ISO22301 and Management • Risk Assessment • R&R BASIC_1.2.xx SAP Security
offering BS10012 Audit • Process Continuity • Remediation of Identified Management

• R&R BASIC_1.9.xx Disaster
• SAP Product offerings • ISO9001 Audits • Asset Management Vulnerabilities Recovery
• SAP Delivery offering • Business Continuity • Approval and Review of • R&R BASIC_1.11.xx Certificate
Handling
• SAP Premium and Operational Customer-Initiated • R&R BASIC_1.8.17 Monitoring and
engagement Resiliency Penetration Test Results event detection of SAP system
availability and critical system states
• R&R BASIC_1.5.xx Release
Management
PCE Security Accreditations
SAP Audit Certification

ISO 27001 Certification for Information Security Management Systems
ISO22301 Certification for Business Continuity Management Systems
ISO 9000 Quality Management Systems
SOC 1
Statement of effectiveness of Type 1 examination
Type 2
BS10012 Personal Information Management
SOC 2
Type 2 Service Organization Controls Report (Attestation report)
Customer Subscription Setup
• Hyperscaler Ownership
• SAP owns and manages the Hyperscaler Root
Account.
• Customer Access Central SAP

Master Customer
• Customers do not have direct access to the Account
Landscape
Hyperscaler Account, Subscription, or Project.
Account
• Security Measures
• SAP enforces Global Security Policies and ECS Separate VNET/VPC
Policies.
for each customer
subscription
• Secure default deployment and compliance

scans are utilised.
SAP Master Account
(SAP SE)
• Flexibility for Customers Security
SAP Enterprise Cloud Policy
• Customers are free to choose their preferred Services Inheritance
Hyperscaler. Cascaded
Customer
• This choice aligns with SAP's managed security
Subscriptions
framework.
Safeguards for Customer Data
SAP Manages technical stack and customer has no access to CUSTOMER
SAP SCOPE
Infrastructure OS. SCOPE
Customer manages configuration, implementation, integration, Functional Client 000

monitoring, application support etc Layer (No PII Access) LOGICAL
BASIS
SAP has no direct access to customer data residing in database Application
Basis Layer
(PRD Client)
No default access is granted to the customer's business client

(customer-managed) unless explicitly authorised and granted by Technical
the customer. Basis Layer
Database Business &

For Client 000 Access, SAP and Sub-processors need - Layer PII Data
▪ A secure HTTPS and encrypted VPN connection Operating PHYSICAL

System Layer BASIS
▪ Strong authentication
▪ Terminal servers and Jump Hosts usage
Storage Layer
▪ Monitoring and recording of all sessions in SAP SIEM
▪ Implementation of Data Loss Prevention measures
Network Layer
Encryption Overview
Data in Transit Encryption Key Management Database Keys
• Defined Policy and Standard Operating Procedures

• Defined Key Rotation and Destruction processes HANA Native Key
Management Solution
TLS 1.2
• Strict User and Access and Authentication Management
• Least Privilege, Need to Know Disk Keys
Data at Rest
(Database) • No Read Access to HANA Encryption Keys
• Unique Keys Generated

Hyperscaler
• Keys are backed up along with database backup Native KMS Tools
AES-256 bit • Key Management Service (KMS), hardware security
module (HSM) or comparable functionality to secure
Data at Rest Key Management
the encryption keys (FIPS 140-2 certified)
(Backup)
• Security Logging and Security Monitoring for critical

activities / access Managed by SAP
AES-256 bit
Security Incident and Event Management
Network Operations and Security Incident and

Security Centre Team Event Management (SIEM)
Correlate and Assess, analyse Security Task

detect suspicious and trigger Force
•Collect, correlate, and analyse event logs from
behaviour security
system components and security solutions.
taskforce
•Automated use-cases trigger immediate alerts.
•Manual extended analysis for identifying
sophisticated attacks.
Infrastructure Logs and Administrative Activities

Initiate defensive actions
(e.g. block access for attacking users)
SAP Cloud SAP Cloud SAP Corporate
Security Monitoring Detection, Protection and Response
IN-SCOPE FOR SECURITY MONITORING
HOST Network Infrastructure Authentication
EVENTS
Security Incident and Event External

Management (SIEM) Threat
Data Intelligence
ALERTS
Enrichment and
Security Orchestration, Automation and Indicators of
Response Compromise
Playbook
CASES
Incident Response
Defense in Depth Security
✓ISO 27001
✓ 24x7 (SIEM) Continuous

Security Logging and Monitoring
✓ Multiple Subnets
✓ Secure Software
Development Lifecycle
✓ Identity Authentication
✓ Role Based Access Control
✓ Physical Security ✓ Dedicated Application and DB ✓ Breach Notification
✓ Supplier Security Servers ✓ Backup and Restore
✓ Secure Cloud Delivery ✓ Problem Management
✓ Disaster Recovery Plan ✓ Continuous Logging and Monitoring
✓ SAP Risk Management Plan ✓ Security Incident & Problem Management
✓ Data Protection and Privacy ✓ Disaster Recovery Plan and Regular Testing
✓ Service Continuity Management ✓ Vulnerability Scanning & Penetration Testing
✓ Vulnerability Management Policy ✓ Patching, Malware and Change Management
SAP CONTRACTUAL
SAP
SAP Data Processing • Information General Terms
Classification and Handling Customer Data SAP Support SAP Service Level SAP Product
Agreement and Conditions ASSURANCE Policy Agreements Supplements
Conclusions
© 2023 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL

Conclusion
• ECS works in a factory mode, this provides partners and customers with several advantages such as streamlined
processes, expert support, cost-effectiveness, reduced risk, and faster time-to-value.
• PCE sets specific boundaries on tasks for partners and SAP. Partners must adapt to these limits and work within this
new framework. It's essential to get used to this new way of working and embrace the new reality.
• Adapt to the new way of working defined by the Roles & Responsibility (R&R) Matrix which outlines the contracted
tasks for all stakeholders in the new PCE model.
• Partners should complete PCE Sell/Service certification ( technical and consultant paths) for your organisation, which
equips your team to understand the factory model intricacies, encompassing phase milestones, system handover
points, and SAP's service delivery model for service and incident requests .
• Implement good project management practices taking a proactive approach with communications and strategically
place experienced and certified resources in key positions.
• SAP is here to support you.

Key Takeaways for Successful PCE Migrations
Partner Enablement
• Assemble a team of experienced consultants (OS/DB) Communication
who are aware of the PCE migration process with • Focus on maintaining clear and concise communication and
sufficient cloud capability/skillset instruction to SAP.
• Obtain PCE Sell/Service certification before starting the • Cultivate a close relationship with the SAP PL
project. • Understand the PCE engagement model
• Build Team Awareness: Cloud vs. On-Premise.
Build
Roles and Scope • Start project preparations early
• Use the Roles & Responsibilities Matric (RACI) to clearly • Ensure information in PPF is correct before sharing with SAP
understand defined roles, responsibilities, and project scope (network segments, SIDs, etc.).
from the beginning. • Request extra bandwidth, storage, and additional services as
• Conduct regular reviews to prevent scope creep. required in advance noting ECS lead times.
• Implement data validation checks during exports.
Effective Project Management • Ensure system readiness before handing over to SAP for post-
processing
• Develop a well-defined project plan with clear timelines
and milestones. Share with SAP Project Lead.
• Provide regular updates to all stakeholders.
• Plan for SAP lead time and processing times of requests
• Integrate PCE phase milestones and handover points into
your project schedule
Appendices
Reference Material
• Partner Services for RISE with SAP: SAP Services to fill Partner Gaps
• Mandatory Partner Training: Consultant Training
• Partner Community: SAP Community
• SAP S/4HANA Cloud, Private Edition: SAP S/4HANA Cloud, private edition, Help
• SAP Activate Methodology for RISE with SAP S/4HANA Cloud, private edition: Road Map Viewer
• SAP S/4HANA Cloud, private edition: Roles and Responsibilities
• SAP S/4HANA Cloud, private edition: Adoption Framework
• SAP S/4HANA Cloud, private edition blogs: SAP S/4HANA Cloud, private edition Blog Posts | SAP Community
• SAP S/4HANA Cloud, private edition resources: SAP S/4HANA Cloud, private edition Knowledge Cente... - SAP Community Groups
Where Partners can find More Information / Resources
• S/4HANA Cloud on SAP Partner Portal
CLEAN CORE ON PARTNER PORTAL
• SAP Partner Portal | SAP S/4HANA Cloud
• SAP Partner Portal | SAP S/4HANA Cloud, public edition |About
• SAP Partner Portal | SAP S/4HANA Cloud, private edition |About Clean Core Landing Page
Clean Core Certification Program
• SAP Digital Discovery Assessment Tool
Certification of Partner Solution (Blog)
• Cloud Choice page of the SAP Partner Portal to learn more about Cloud Choice Flex (CCF) Point of View “Clean Core”
SAP Business Technology Platform (BTP) - Clean Core
• RISE with SAP, SAP S/4HHANA Move, and SAP Customer Evolution Pages on the SAP Partner Portal SAP S/4HANA – Clean core with/and SAP BTP (Blog)
• RISE with SAP on Partner Edge

• SAP Customer Evolution Program
• Maintenance Timelines for SAP ERP 6.0
• Sales Play: MOVE to SAP S/4HANA – End of Mainstream Maintenance for SAP ERP 6.0
• SAP S/4HANA Movement on Partner Portal
• SAP Partner Pricing App & Latest Pricing Update on Partner Portal (pdf along with a mp4 video).
• Demo Store: SAP Demo Store (Navigate Demo Store Scenarios)

• Shared Demo Scenarios: https://partneredge.sap.com/en/partnership/licenses/shared_demo.html
• Demo Store: https://sapdemostore.com/sap/bc/ui5_ui5/sap/yunifiedstore/index.html#/searchview/user/keywords:12122313160401
• How to get started with SAP Business Technology Platform (SAP BTP)
- Overview: SAP BTP TOP TEN Partner Enablement Resources
- Details: SAP BTP Partner Enablement & Coaching Overview
For more information for The Case for Cloud: One-Pagers
and FAQ Document
Thank you.
© 2023 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 this material.

RISEwithSAP PrivateCloudEdition BrownField Migrations Partner Overview

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

RISEwithSAP PrivateCloudEdition BrownField Migrations Partner Overview

Uploaded by

Copyright:

Available Formats

RISE with SAP

INTERNAL – SAP and Partners Only

INTERNAL – SAP and Partners Only

Advisory & Application

Business Benefits Strategic Benefits Technical Benefits Operational Benefits

• SERVICE partners provide various customer services, operating

Notes Build Timeline

• Partner CAA confirms via email SAP BP in

Notes Build Timeline

• Partners handle advisory and project implementation tasks.

• Partners handle the application specific upgrade activities, with CAS

• Partners access the application layer of the ECS hosted system

• In case of migration issues, SAP may provide partners with a 'Jailed'

• To facilitate the migration process, SAP offers a Migration Server

• Responsibilities of ECS are as stated in the R&R. Additional service

The 'Roles and Responsibilities Matrix' shows who

• Standard Services covered by the PCE contract

• Retains existing processes, migrates current system to RISE

(050) (100) (100) S/4HANA

DEV QAS PRD SBX Reimplement

Partner Scope SAP ECS Scope

Migration Server S/4HANA Skeleton Systems

migration/conversion steps using

System conversion System copy New implementation Selective data transition

SAP Legacy SAP ERP

SAP SAP SAP SAP

Main focus Main focus Possible alternative • Requires evaluation

The chosen approach impacts the items which are

the selected transition approach by building the distinct Selective Data

SAP ECS milestones into their project plan. Transition

Applicable to hyperscalers i.e., GCP, AWS, Azure

• Understanding limitations and Roles and

• Partners must inform ECS of the system build plan

• Best Practice Advice:

Complete preparation activities technical project

Finalise the conversion approach before PPF form

Consider target system's landscape, network, and

System copy and tenant copy require target ECS-

Align with SAP ECS for

Source System On Premise Target System On PCE Cloud

Execute Independently in Switch to Target System for All Activities performed

PCE Cloud TARGET SYSTEM

PAS Add Block

SMALL MEDIUM LARGE

Total: 10 Total: 20 Total: <30

Discover Prepare Explore

Key Phase Deliverables Key Phase Deliverables Key Phase Deliverables

• **Order SAP Enterprise Support CQC Services as • Migrate Sandbox System

Realise Deploy Run

Key Phase Deliverables Key Phase Deliverables Key Phase Deliverables

• Complete Dry Run and DR test

• **Raise required ECS Build Task SRs

PCE Support for Dry Runs ECS Post Processing Support

• If PRD hardware is used for dry runs, there is no need to Non-Production

• Partners need to stand up their own

SAP Industry Account Executive(IAE)

SAP Technical Services Manager (TSM) Customer Delivery Manager (CDM)

SAP ECS Resources ( COE, Backoffice, etc)

Partner Project Lead (PL) Partner Cloud Architect (PCA)

SAP Technical SAP Functional

Technical Lead (Basis Manager) Network Lead

*Actual organisational structures will depend on the project scope and on