Download Sample project plan -> https://go.support.sap.com/roadmapviewer/#group/AAE80671-5087-430B-9AA7-8FBE881CF548/roadmapOverviewPage/MATS4HANA
Prep work needs to be done
CVI (Customer Vendor Integration)
SAP Add-on Suport
https://launchpad.support.sap.com/#/notes/2214409
Since partners receive SAP S/4HANA releases at the same time as customers, there isusually a lag between the release of a new release and the provision of a certified partneradd-on for that release. By the time FPS01 is released, most partner add-ons are available. o Customers are advised to check expected release dates of partner add-ons directly with therelevant partner organization.
Custom Code Remediation
Things that will impact your project timeline
You need to upgarde from HANA 1.0 to 2.0
Decide to change Fiori architecture from Hub to embedded
You start on an initial shipment pack but plan to go-live with FPS01 or higher
You have many integrated parralel solutions, which increase testing.
You have parrallel integrated cloud solutions that plan to be updated during the course of your project.
Due to simplifcation of tables to CDS views in critical reports/analytics you need to allocate more time to remediate them.
Your business has strict SOD rules and require additional authorization testing
You have more systems in your S/4 Landscape e.g. Training server
You have remote or mixed onsite/remote team
Key Lessons Learned
s/4 is not a once off project
Upgrades and continous improvement projects will become a normal part of keeping up with innovation
Initial versions of S/4 are already going out of maintenance
Customers running 1610 need to consider upgrading
Create an internal knowledge center
Consider creating a CoE
Use latest release and not an “n-1” strategy as cloud has had the release running for a year already
Upgrade Execution
Start with a sandbox, before upgrading your development (DEV) environment.
Downtime Optimization
There are a comprehensive list of measures that can be taken to reduce the technical downtime of the system during the S/4HANA upgrade in SAP Note 2351294
By performing your upgrade in a sandbox - which should be based on a copy of production – you can evaluate if the downtime window will fit into the business downtime window agreed with the business
At the end of each upgrade run, the SUM logs should be used to investigate opportunities for downtime optimization.
Use theSAP Technical Downtime Optimization app provided by SAP - Note 2881515
The more you want to optimize the downtime, the more effort you have in the project.
Standard: several downtime-optimizations (e.g. shadow system operations)
near-Zero Downtime Maintenance (nZDM): downtime reduction by moving main import and table conversion partly into uptime. SAP Note 1678565
Zero Downtime Option (ZDO): handling all update related changes in uptime. SAP Note 2707731
Patch Strategy
Contain bug fixes and performance improvements.
Fiori FES, Server, UI5, NWBC
Apply the latest patches immediately after upgrade, and prior to follow-on EXPLORE and REALIZE activities such as fit-to-standard of successor apps.
Post Upgrade Activities
Update Enterprise Search Content
UX Upgrade programs
Fiori Launchpad configuration, content, layout
Adjust authorizations with new roles and objects
Known Issues
Add-on not available for target release
Upgrade “stuck” due to non-released code and customizing requests (release all transport requests)
DB Space runs out during upgrade +70% of your current DB size
Long runtimes due to incorrect transport sequences
Poor performance of Client Copy esp. with large volume of data
Provision additional hardware
Apply SAP notes to improve performance or apply parameters - SAP Note2550545
Reduce dataset by archiving
Technical errors in ACT_UPG phase, because of clashes in CDS view names - SAP Note 2050604
Evaluate impact of simplifications against your existing processes
Replace deleted functionality and Apps with successors (Fiori Apps, Classic UIs, Business Roles, Obsolete launchpad items)
Review custom custom built UI5 Apps and ABAP Monoliths
Review Authorizations
Identify critical processes for regression testing
Review your UX Strategy
Review Fiori Coverage
See SAP Lighthouse scenarios - https://www.sap.com/corporate/en/documents/2018/01/12b3dec4-ec7c-0010-82c7-eda71af511fa.html
Recommended for Technical Upgrade
If using Standalone Fiori server, migrate to embedded
Review Launchpad and activate high value apps - e.g. New App support feature
Move to latest best practice tools for managing Launchpad content, layout, authorisations.
Review end to end performance and test automation options
Consider extensions to solutions with “side by side” services and capabilities
Recommendations for Functional Upgrade
Replace standalone solutions with embedded solutions.
Extend Fiori coverage - replace classic UIs with Fiori Apps, add embedded analytics and intelligent automation apps
Consider SAP cloud extensions and SAP BTP offerings
Identify Change Management scope with Readiness check
Identify Add-ons and and business functions for target release
Evaluate custom code for opportunities to “go back to standard” - align to SAP’s cloud strategy
Use Standard Fiori App (F3191) Custom code migration available from 1809
Technical Planning
Every project should include performance testing and assume that authorizations will need to change
Maintenance Planner is the key tool for updating an existing system that is performed by the Software Update Manager (SUM) tool
Always recheck your sizing as part of an upgrade. If you intend to add new functionalities during or after upgrade, perform additive sizing using the SAP Quick Sizer Tool
Consider Database versions. If you are upgrading from 1511 or 1610 this will also involve a upgrade to HANA 2.0
Get Fiori FES set up, embedded is recommended incl. Web Dispatcher and associated Launchpad, Search, Notifications etc.
Set up SAP Screen Personas to provide non-coding options to improve classic interfaces.
Check supported browsers for business users, to ensure Internet Explorer support etc.
Security
If moving from intranet only to Internet access for the first time, allow additional time to ensure security has been appropriately considered -> https://blogs.sap.com/2017/12/15/considerations-and-recommendations-for-internet-facing-fiori-apps/
New and changed authorizations are introduced due to: Fiori Apps, Catalogue assignments, business process changes and data extracts (e.g CDS Views)
Prerequisites before the upgrade to repair inconsistent data, initialize timestamps, create backups.
After upgrade there are a number of post processing settings for profile generator, business roles and customer tables.
New Fiori Administration Roles to build and extend Fiori Apps
Upskill your Team
A number of open SAP course exist to cover key S/4 Topics Fiori, Conversions, Hyperscalar depoyment etc.
openSAP microlearning video Finding delta simplifications between SAP S/4HANA releases - https://microlearning.opensap.com/playlist/dedicated/173270151/1_2mnya897/1_i7lj1d8z
Upgrade Types
Technical Upgrade
Main Focus
Get Infrastructure ready
Upgrade of hardware and software
Mandatory changes to custom code and configurations
Custom ABAP code may need to be remediated due to simplifications in the ABAP Platform and changes in the database.
From SAP S/4HANA 1809 or higher you can use the SAP Fiori app F3191 Custom Code Migration to assist code migration.
See SAP recommendations https://launchpad.sap.com/#/notes/2190420
Ability to perform semi-automatic code remediations - https://blogs.sap.com/2018/10/02/semi-automatic-custom-code-adaptation-after-sap-s4hana-system-conversion/
Regression testing and remediation esp. for integration
Check any integration to analytics platforms, such as SAP BW or SAP BW/4HANA.For BW Extractors refer to SAP Note 2500202
If you are integrating to Cloud solutions, such as SAP cloud or 3rd party solutions, it is important to check for any shift in integration techniques due to the change in release
Approach
Start upgrade on an non-integrated Sandbox system
Less disruption to business as usual landscape DEV/QA/PRD
Delta simplifications, mandatory custom code corrections and perfomance optimizations can be done on “real” data
Copy of production enables regression testing on realistic business data
Identify fine detail in existing apps
Quicker upgrades in your DEV/QA/PRD system, as early discoveries or corrections made in the sandbox can be factored into upgrade process
Runbooks of all activities can be captured
Test cases and test scripts can be identified and refined on sandbox
Any test automation can be trialed on this system and used to speed up regression testing on later systems.
Mandatory custom code corrections can be performed on a sandbox and optionally transported to DEV.
DEV & QA is where you undertake integration testing
Use latest Feature Pack Stack 1 or higher of current SAP release
Ensure HANA DB is on 2.0
Only Mandatory functional and technical changes applied i.e defer new innovations
Project Resources
Project Manager
Solution Architect
UX Expert
Technical Basis Expert
Functional SME
Developers
Business User Testers
Drivers
Stay in maintenance and current support incl. security
tay current with corrections and security patches that are delivered with new releases, new Feature Package Stacks (FPS), and Support Package Stacks (SPS)
Replace compatability packs which expire end of 2025