The MOVE Journey

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 1

Agenda

v Executive Summary

v SAP Upgrade and Migration Scope

v High Level SAP Deliverables

v Upgrade and Migration Timeline

v Deliverables

v Roles and Responsibilities

v General Assumptions

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 2

Executive Summary

Wonder Brands is currently defining their Future Architecture based on SAP S/4HANA & has following
objectives for their upgrade to SAP S/4HANA 2021 and Migration to cloud:
▌ Seamless upgrade and migration of their current S/4HANA 1709 to SAP S/4HANA 2021
▌ Smooth transition to SAP S/4HANA 2021 for End Users

Wonder Brands has requested SAP Services to provide an overall approach & cost estimate for Technical
upgrade and migration of existing SAP S/4HANA 1709 Landscape to SAP S/4HANA 2021 in RISE

The current estimates are based on SAP S/4HANA Readiness Checks and ABAP Test Cockpit (*)

(*) ATC results are in process by SAP team

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ INTERNAL 3

 SAP Upgrade and Migration Scope

HEC RISE / PCE

Source Target
DB UC / Source Source Source Target Target Target # of Approach
SAP Solution System IDs Stack Appln Stack Appln
Size NUC Release DB OS DB Release DB OS DB Cycles
OS OS
HANA
SLES 15 SLES 15 1) Upgrade DB from HANA 2.0 SP05 rev 55 to HANA 2.0 SP05 rev
SE1, S/4HANA 2.0 SAP
SAP S/4HANA < 1 TB UC ABAP SP1 SP1 SLES 56 or higher by customer/HEC
DE1,QE1,PE1 1709 SP05 S/4HANA HANA
(x86_64) (x86_64) 15 SLES 15 2) SAP S/4HANA upgrade to SAP S/4HANA 2021 with Embedded
rev 55 2021 with ABAP 2.0 5
(x86_64 (x86_64) Fiori using SUM and migration to PCE environment for SBX (Copy
SLES 15 SLES 15 ASE Embedded SP05
SF1, DF1, < 500 ) of PE1), DE1, QE1, Mock(Copy of PE1) & PE1 by SAP Services
SAP FIORI (*) UC 7.52 SP18 ABAP SP1 SP1 16.0.03. Fiori
QF1, PF1 GB Team
(x86_64) (x86_64) 08
SLES
SAP SLES 15 SAP 1. Installation of Webdispatcher by PCE team
SAP SW1,DW1,Q 15
- - WebDispa - SP1 - - WebDispat - - - 4 2. Re-Configuration of dispatcher for S/4HANA by SAP Services
WebDispatcher W1,PW1 (x86_64
tcher 7.53 (x86_64) cher 7.85 Team
)

(*) Fiori will be moved from HUB to Embedded in S/4HANA

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

Upgrade and Migration of S/4HANA 1709 to S/4HANA 2021: High Level SAP Deliverables

Platform Functional Custom Code UX/Fiori Security

§ Upgrade DB from HANA § Mandatory functional § Technically remediable § “As Is” migration of 150 § Identify the roles affected
2.0 SP05 rev 55 to HANA activities (pre and post scope – bucketed as no standard and 20 custom by Upgrade and Security
2.0 SP05 rev 56 or higher migration) related to the relevant extracts were Fiori apps from Hub Fiori post Upgrade processing
by HEC relevant simplification available from the to Embedded Fiori in Sandbox
§ SAP S/4HANA upgrade to items customer’s system § Set up Custom Fiori § Up to 100 master roles
SAP S/4HANA 2021 with § Mandatory Preparation Launchpad and adjustments during
Embedded Fiori using Activities § S/4HANA 1610 to Launchpad Designer in system Upgrade to
SUM and migration to § 1709 – 2021 Upgrade S/4HANA 2020 Upgrade Embedded system S/4HANA.
PCE environment for SBX § Activate Fiori content in § Security pre-go-live check
§ Business Priorities: § SPDD : 350 objects
(Copy of PE1), DE1, QE1, Embedded Fiori system as to ensure consistency
Finance (GL, AP, AR, § SPAU : 350 objects
Mock(Copy of PE1) & PE1 identified in HUB Fiori
Asset, Bank, Basic CO) | § User creation for project
by SAP Services § HCA : 500 impacts Server
Procure to Pay | Order to support, test scenarios
TeamSupport to ABAP & (mandatory only)
Cash | Plan to Product § Activation of Enterprise and end users during final
Functional team § S/4HANA : 800 impacts
§ Upgrade cycles: 5 Search preparation phase
§ Technical support during (technically remediable
§ My Inbox App § Unit Testing, Integration
UAT cycle and Cutover only)
configuration Testing and User
Planning activities
§ Creation of one custom Acceptance Testing
§ Project Planning & Post support
Fiori Theme (logo change
Go Live Support activities
for landing page) § Support the Functional
covering 2 CWs
Team at Simplification List
evaluation (Transactions),
after SU25 execution, at
specific Workshops.

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

Upgrade and Migration of S/4HANA 1709 to S/4HANA 2021: Platform

Scope Assumptions Exclusions

▌ Upgrade DB from HANA 2.0 SP05 rev 55 to
HANA 2.0 SP05 rev 56 or higher by HEC
▌ SAP S/4HANA upgrade to SAP S/4HANA 2021
with Embedded Fiori using SUM and migration to
PCE environment for SBX (Copy of PE1), DE1,
QE1, Mock(Copy of PE1) & PE1 by SAP Services
TeamSupport to ABAP & Functional team
▌ Technical support during UAT cycle and Cutover
Planning activities
▌ Project Planning & Post Go Live Support activities
covering 2 CWs
▌ Customer is responsible for maintenance
landscape setup as part of S/4HANA& Fiori
Upgrade project . Customer is responsible for
retrofitting of changes in S/4HANA & Fiori
environment as part of maintenance activities
▌ It is assumed that the Connected Hub
solutions (GRC, PI & BW systems etc.) are on
minimum SAP Release SAP NW 7.5 or higher
which supports interoperability with S/4HANA
2021 version.
▌ Customer/HEC is responsible for OS/DB
upgrade, SAP Patching as part of pre-
requisite completion if required
▌ Any 3rd party add-ons related changes or analysis
and Coordination with Third-party Add-on
▌ SSL setup and configuration
▌ OS and DB upgrade Activities / File system
activities (Covered by HEC)
▌ Backup - Restore activities / System Copy
activities (Covered by HEC)
▌ Any other SAP solutions not part of basis scope
▌ HA / DR activities / Cluster related activities
(Covered by HEC/RISE)

▌ Customer to check with 3rd party vendor for ▌ Interfaces / 3rd party integrations
the compatibility of 3rd party Addons (if any)
with S/4HANA and ensure the strategy and ▌ Frontend GUI installation / upgrade
prerequisites are met prior to start of the
project
▌ Performance Testing/Tuning and Hardware Sizing
▌ Any impact and cascading update/upgrade
requirements on interfaced SAP systems
including and BW related mapping changes
© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ Public will be scoped only in detailed assessment 6
Upgrade and Migration of S/4 HANA 1709 to S/4 HANA 2021: Functional
Scope
▌ Mandatory functional activities (pre and post
migration) related to the relevant simplification
items
▌ Mandatory Preparation Activities
▌ 1709 – 2021 Upgrade
▌ Business Priorities: Finance (GL, AP, AR, Asset,
Bank, Basic CO) | Procure to Pay | Order to Cash
| Plan to Product
▌ Upgrade cycles: 5
Explore Phase Pre-requisite: Technical Upgrade
Assessment - Scope Revalidation
© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ Public
Assumptions Exclusions
▌ Resolution of root cause of Inconsistencies except
▌ No new innovations / functionalities / business bug fixes at S/4HANA Upgrade in scope work.
processes will be introduced apart from the
mandatory functional changes to be done for the ▌ Integration (Middleware), BW extractors and HCM
relevant simplification items during the upgrade Support since its an upgrade
project.
▌ The Simplification Items that fall under the
categories given below will be discussed during
detailed assessment [Scope Validation] and
estimated for project execution as part of change
request.
▌ Functionality unavailable (no alternative planned)
▌ Functionality unavailable (alternative exists)
▌ Non-strategic-function (alternative exists)
▌ Functionality unavailable (alternative planned)
▌ Functionality deprecated (alternative exists with
roadmap)
▌ Non-strategic-function (alternative planned)
▌ Functionality deprecated (alternative exists)
▌ Change of functionality
▌ Any Screen variants / Transaction variants that
are not carried forward by upgrade tool will be
recreated manually by the customer. 7
Upgrade and Migration of S/4 HANA 1709 to S/4 HANA 2021: Custom Code
Scope
▌ SPDD: 350 Objects [Bucketed]
▌ SAPU: 350 Objects [Bucketed]
▌ Application Specific follow on activities
▌ HCA (HANA Code Adaptation) : 500 impacts (mandatory
only – bucketed)
▌ S/4HANA : 800 impacts (technically remediable only –
bucketed)
To Note: The defined scope is bucketed due to
unavailability of the relevant extracts from the
customer’s system. The resources estimates are
based on above bucketed scope
(*)Team is adjusting the scope based on received
ATC report.
© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ Public
Assumptions
▌ Custom code objects scoped for upgrade must
have No Syntax Errors
▌ Any new development effort required to substitute
the functionality not available in S/4HANA will not
be considered and can be covered as a Change
Request on T&M basis.
▌ SPDD, SPAU, SPAU_ENH and Custom Code
Remediation activities are considered for one
system only and transported to subsequent
systems.
▌ Custom Code system in which code remediations
are to be performed should be a copy of
production system
▌ Code remediation will be performed on the active
version of the object available in provided system.
▌ Customer is responsible for ensuring version
correctness in the system provided for code
remediation.
▌ Customer system does not have any
inconsistency in their database tables.
Exclusions
▌ Custom code adjustment due to dual maintenance
and retrofit is out of scope.
▌ New innovations / business processes will be
introduced apart from the mandatory changes.
▌ New mapping changes. Screen variants /
Transaction variants that are not carried forward
by upgrade tool
▌ Changes in AS IS Interface file structure and
content. Configuration and installation on
S/4HANA required for third party interfaces
▌ Interfaces impacted under functionality not
available/no supported and no equivalent
available
▌ Fixes to SAP Queries or Info set Queries
▌ S/4HANA specific Data modelling for Custom
DDIC objects are not in scope. E.g. Compatibility,
CDS View and AMDP methods on custom DDIC
objects will not be part of adaptation.
8
Upgrade and Migration of S/4 HANA 1709 to S/4 HANA 2021: Fiori
Scope
▌ The Scope is for “As Is” migration of 150
standard and 20 custom Fiori apps from Hub
Fiori to Embedded Fiori
▌ Set up Custom Fiori Launchpad and
Launchpad Designer in Embedded system
▌ Activate Fiori content in Embedded Fiori
system as identified in HUB Fiori Server
▌ Activation of Enterprise Search
▌ My Inbox App configuration
▌ Creation of one custom Fiori Theme (logo
change for landing page)
© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ Public
Assumptions Exclusions
▌ Customer has to provide the 150 Standard Fiori Apps list ▌ Functionality , Performance and Unit testing
active in their current Productive Environment.
▌ Application redevelopment & new Apps
▌ All the custom content (Custom apps, catalogs, groups
and business roles) will be moved through TRs import by development
Basis Team.
▌ Any bugs/defects in standard Fiori applications will be ▌ Creation of custom catalogs, groups, pages and
addressed via the SAP support tickets. spaces
▌ Any deviation from the scope defined in this document will
be subject to the Change Request Procedure to assess ▌ End-user training
its impact and feasibility for inclusion and may incur
additional effort, time and cost.
▌ Fine-tuning the performance and redesign the
▌ List of custom Fiori applications along with code repository existing app using latest Fiori guidelines
& BSP names will be Provided
▌ Business Application Studio access will be provided by ▌ Any fixes related to compatibility issues like UI5
Customer version, Custom CSS, OData, Data Model or API
issues
▌ For Custom Fiori Apps Only Sanity check of the apps will
be performed.
▌ Preparation of Test script
▌ If any custom Fiori app does not work, only the analysis to
find the root cause will be performed and fixed or
redevelopment through a CR.
9
Upgrade and Migration of S/4 HANA 1709 to S/4 HANA 2021: Security
Scope
▌ Identify the roles affected by Upgrade and
Security post Upgrade processing in Sandbox
▌ Up to 100 master roles adjustments during
system Upgrade to S/4HANA.
▌ Security pre-go-live check to ensure consistency
▌ User creation for project support, test scenarios
and end users during final preparation phase
▌ Unit Testing, Integration Testing and User
Acceptance Testing support
© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ Public
Assumptions
▌ Customer’s existing role design was based on
SAP best practices and proper naming convention
was used
▌ Any role adjustments over and above the scoped
roles would be guided by SAP consultant and
would be owned, built and adjusted by the
customer Security Team
▌ Configuration and browser specific settings
required for end user desktops and Laptops is
customer Responsibility
▌ Customer has or will onboard competent SAP
Security resource(s) to work along with the SAP
Security Team
Exclusions
▌ Data maintenance related to SU22 / SU24 is out
of Scope
▌ ADFS related configuration for SSO
▌ User specific requirements on Active Directory for
the solution to work will be customer responsibility
▌ User Creation, Infra Security related to SSO, DMZ
▌ Redesigning Home page for NWBC roles will be
consider out of scope
▌ Third-party tools for testing or any other purpose
▌ Infrastructure Security related changes
▌ NW SAP Single Sign On configuration is not
scope in the efforts.
▌ Developing new Enterprise roles and privileges
except for Fiori role scoped in the efforts
10
Upgrade and migration of S/4HANA 1709 to S/4HANA 2021: Timeline

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ Public 11

Milestones / Deliverables
PHASE DELIVERABLE COMPLETION CRITERIA

Prepare Project Plan • Approval of the project plan outlining schedule, resource, dependent activities as per the statement of work.

• Sandbox environment containing upgraded and migrated SAP Software, upgrade and migration cookbook and
Upgraded and Migrated Sandbox
validation report.
Explore Systems and Migration Cookbook
• Signoff Criteria: Existing features, and configured functionality of the source system should function in the
Documentation
target Sandbox environment.
• Development environment containing upgraded and migrated SAP Software, migration cookbook and
Upgraded and Migrated
validation report.
Development Systems and
• Signoff Criteria: Existing features, and configured functionality of the source system should function in the
Migration Cookbook Documentation
target Development environment.
Realize
• Quality Assurance environment containing upgraded and migrated SAP Software, upgrade and migration
Upgraded and Migrated QA Systems
cookbook, validation report.
and Migration Cookbook
• Signoff Criteria: Existing features, and configured functionality of the source system should function in the
Documentation
target Quality Assurance environment.
Cutover plan • Finalized cutover plan for Production upgrade and migration.
Dry Run of Production upgrade and
migration • Dress rehearsal run of the Production upgrade and migration completed.
Migration Cookbook Documentation
Deploy
• Production environment containing upgraded and migrated SAP Software and report documenting issue
Upgraded and Migrated Production
resolution as part of post go-live support.
Systems
• Signoff Criteria: Existing features, and configured functionality of the source system should function in the
Migration Cookbook Documentation
target Production environment.

Run Project Closure • Post go-live support of 2 weeks; sign-off criteria; handover of project closure report.
© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ Public 12
Roles & Responsibilities (1/2)

ACTIVITY SAP PSO SAP RISE Wonder Brands

Refresh Sandbox with Production Data in Source System C I R

Definition of End State Architecture I R C

Setup Direct Connectivity between on-premise Datacenter and SAP PCE I R R

System Copies, DB Backups and File Transfer activities in Source System C I R

Target Infrastructure Readiness (Hardware/Network/Security/Backup/Media Download) and System Provisioning I, C R C

Code Freeze and Transport Strategy during the upgrade and migration Project C I R

Temporary Production Support Strategy, Maintenance landscape for current projects C I R

Coordinate with 3rd party vendors to check for compatibility of 3rd party add-ons, interfaces or extensions in
C C R
target environments and perform suitable adjustments/upgrades

Any HA/DR activities on Target System I R C

Single Sign On Reconfiguration in Target System C C R

Provide list of prerequisites for upgrade and migration project R C C

Finalize Go-Live Date C C R

Review/assessment of existing source system technical landscapes R C C, I

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ Public 13
Roles & Responsibilities (2/2)

ACTIVITY SAP PSO SAP RISE Wonder Brands

Project Plan R C C

Technical upgrade and migration of systems in scope from source to target R I I

Upgrade and migration cookbook documentation R I C, I

SAP PCE specific pre and post upgrade and migration activities C, I R C, I

Technical quality review of the target systems R C I

ABAP Code adjustments, HANA remediation and unit testing R I C

Cutover Plan R C C

Integration/Functional/Performance/User-Acceptance testing C I R

Resolution of current upgrade and migration related technical issues during testing R I C, I

Resolution of issues not related to the upgrade and migration project during testing I I R

System Turnover Documentations R I C, I

Maintain Authorizations on Target System C, I I R

Acceptance and Sign-off C, I I R

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ Public 14

Governing Assumptions
• This is a technical upgrade and migration and no functional enhancements or developments is in scope.
• As part of the project planning and kick-off, SAP will perform a detailed technical validation of the systems in scope
• Joint Planning is required during the Prepare phase to finalize Migration and Testing Windows for each tier/solution
• Customer / Hosting Partner to fulfill Technical Prerequisites especially in Source System
• Downtime can be estimated only after the sandbox run. Final timeline and approach to be defined and verified based
on dry runs cycles and production simulation.
• Testing (Unit/Regression/Interface) will be performed by Customer. SAP Migration team will provide technical support
during testing

© 2022 SAP SE or an SAP affiliate company. All rights reserved. ǀ Public 15

Thank you
Sandeep Sehgal – VP SAP Services
Ryan Blaney – SAP Services Account Executive
Thiago Lopes – Strategic Solution Director