PUBLIC

Upgrading SAP S/4HANA: Why, How, and Best Practices

Version: January 2023

TABLE OF CONTENTS
1. Introduction and motivation for the upgrade................................................................... 6
1.1. Why this best practices guide is needed ............................................................................ 8
1.2. Our most important recommendation – capture your own Lessons Learned .............. 9
1.3. Defining your business strategy for the upgrade.............................................................. 9
1.3.1. Drivers for a Technical Upgrade strategy ....................................................................... 10
1.3.2. Drivers for a Functional Upgrade strategy ..................................................................... 11
1.3.3. How to find out what’s new .............................................................................................. 11
1.3.4. SAP S/4HANA release and maintenance strategy.......................................................... 13
1.3.5. Expiration of Compatibility Packs .................................................................................. 13
1.4. Business functionality impacts ......................................................................................... 14
1.4.1. Delta simplifications .......................................................................................................... 14
1.4.2. Business function activation impacts ............................................................................... 16
1.4.3. Add-on impacts .................................................................................................................. 17
1.4.4. Introducing new business innovation .............................................................................. 18
1.5 Responsibilities during the upgrades of SAP S/4HANA Cloud, private edition .................. 19
2. Preparing for the upgrade ................................................................................................ 20
2.1. Key Considerations for choosing your target release / Feature Pack Stack ................ 21
2.2. Key considerations for Functional Upgrade vs Technical Upgrade decision .............. 23
2.2.1. Example upgrade plan for a Functional Upgrade .......................................................... 25
2.2.2. Example upgrade plan for a Technical Upgrade ........................................................... 26
2.2.3. Key considerations when estimating effort to upgrade ................................................. 28
2.3. Setting your update strategies incl. UX and mobile devices .......................................... 29
2.4. General planning for the upgrade ................................................................................... 30
2.4.1. Identifying delta scope ...................................................................................................... 30
2.4.2. Identifying change management scope via Readiness check ......................................... 31
2.5. Technical planning for the upgrade................................................................................. 33
2.5.1. Planning the upgrade in the Maintenance Planner ........................................................ 34
2.5.2. Reviewing your sizing ....................................................................................................... 34
2.5.3. Operating system requirements ....................................................................................... 34
2.5.4. Database requirements ..................................................................................................... 35
2.5.5. Application server considerations .................................................................................... 35
2.5.6. Globalization, country versions and languages .............................................................. 36
2.5.7. Server architecture impacts ............................................................................................. 36
2.5.8. Security - authentication ................................................................................................... 40
2.5.9. Security - authorizations ................................................................................................... 40
2.5.10. Operating environment impacts ...................................................................................... 41
2.5.10.1. Operating environment for business users ..................................................................... 41
2.5.10.2. Operating environment for administrators and support teams ................................... 41

Public 2/122
2.5.10.3. Operating environment for developers ........................................................................... 42
2.5.11. Custom code impacts......................................................................................................... 44
2.5.12. Upgrading custom ABAP code......................................................................................... 45
2.5.13. Upgrading custom SAP Fiori apps .................................................................................. 46
2.5.13.1. Deprecated SAPUI5 themes, libraries, and controls ...................................................... 47
2.5.13.2. Using the Support Assistant to identify required changes ............................................ 47
2.5.13.3. Using the Migration Tool to adapt custom code to higher SAPUI5 releases ............... 48
2.5.14. Integration .......................................................................................................................... 48
2.5.15. Move to Hyperscaler ......................................................................................................... 49
2.5.16. Leveraging CQC Support Services (SAP Enterprise Support customers) .................. 50
2.5.17. Leveraging support services (standard support)............................................................ 51
2.5.18. Leveraging support services (SAP Product Support for Large Enterprises) .............. 51
2.5.19. SAP Enterprise Support value map................................................................................. 52
2.6. Improving your User Experience ..................................................................................... 52
2.6.1. Review your UX strategy .................................................................................................. 53
2.7. User Experience impacts................................................................................................... 54
2.7.1. Obsolete, deprecated, and superseded apps.................................................................... 55
2.7.2. Changed apps..................................................................................................................... 57
2.7.3. Changes in classic user interface capabilities ................................................................. 58
2.7.4. Deleted and deprecated classic user interfaces ............................................................... 59
2.7.5. Changes in catalog assignments ....................................................................................... 59
2.7.6. Changes in accessibility features ...................................................................................... 60
2.7.7. New apps ............................................................................................................................ 60
2.7.8. New SAP Fiori launchpad and shared features .............................................................. 61
2.7.9. Essential business roles required to administrate and extend SAP Fiori .................... 61
2.7.10. Required adaptations to custom SAP Fiori Apps........................................................... 62
2.8. Functional planning for the upgrade ............................................................................... 66
3. Upgrade execution ............................................................................................................. 67
3.1. Technical tooling and process .......................................................................................... 67
3.1.1. General procedure ............................................................................................................. 67
3.2. Technical Upgrade Steps for your SAP S/4HANA target release................................. 67
3.2.1. Downtime optimization options ....................................................................................... 68
3.2.2. Downtime optimization approaches of Software Update Manager (SUM) ................. 69
3.2.3. Silent Data Migration ........................................................................................................ 70
3.2.4. Patch strategy in general .................................................................................................. 70
3.2.5. Patch strategy for SAP Fiori FES .................................................................................... 70
3.2.6. Patch strategy for SAP S/4HANA Server ....................................................................... 71
3.3. Post-upgrade follow-up activities ..................................................................................... 71
3.3.1. Additional activities to be applied after upgrade ........................................................... 71
3.3.2. Updating the Enterprise Search content ......................................................................... 71
3.4. User Experience post-upgrade activities ........................................................................ 72
3.4.1. Move to new tools and accelerators ................................................................................. 72

Public 3/122
3.4.2. Update SAP Fiori Launchpad configuration parameters and features ....................... 73
3.4.3. Review SAP Fiori performance improvement options .................................................. 74
3.4.4. Update SAP Fiori launchpad content and layout ........................................................... 75
3.4.5. Update authorizations ....................................................................................................... 77
3.4.6. Transition from deprecated to successor SAP Fiori apps ............................................. 77
3.5. Functional post-upgrade activities ................................................................................... 78
3.5.1. Transitioning users to new or changed functionality ..................................................... 78
3.6. Regression testing .............................................................................................................. 80
3.6.1. Automated testing for custom SAP Fiori apps ............................................................... 81
3.6.2. Validate your business processes ..................................................................................... 82
3.6.3. Verify SAP Fiori floorplan changes ................................................................................. 82
3.6.4. Validate changes in classic UI capabilities ...................................................................... 82
3.7. Cutover and go-live ........................................................................................................... 83
4. Driving additional value from your upgrade .................................................................. 83
4.1. Introducing new business functions and processes ........................................................ 83
4.2. Example project plan for a continuous improvement project ...................................... 84
4.3. Prerequisites....................................................................................................................... 85
4.4. Introducing new User Experiences .................................................................................. 86
4.5. Introducing new Intelligent Technologies ....................................................................... 91
4.6. Introducing new SAP Fiori launchpad features ............................................................. 92
4.7. Introducing native clients ................................................................................................. 95
5. Known issues ...................................................................................................................... 97
6. Frequently asked questions (FAQ) ................................................................................ 109
6.1. General ............................................................................................................................. 109
6.2. Functional......................................................................................................................... 110
6.3. User Experience ............................................................................................................... 110
6.5. Services ............................................................................................................................. 114
7. Additional information resources .................................................................................. 115
7.1. openSAP Microlearning.................................................................................................. 115
7.2. openSAP courses.............................................................................................................. 115
7.3. openSAP podcasts............................................................................................................ 117
7.4. SAP Community topics ................................................................................................... 117
7.5. SAP Learning Journeys .................................................................................................. 118
7.6. Useful SAP Notes and recommended blog posts .......................................................... 119
8. Appendix .......................................................................................................................... 121
8.1. Additional SAP Solution Manager details .................................................................... 121
8.1.1. Using Solution Manager to manage your regression testing ....................................... 121
8.1.2. Using SAP Solution Manager to manage the impact on business processes .............. 121

Public 4/122
VERSIONING

Date Changes

Initial version June 2020 • Initial version of the document

Revision 1 – August 2020 • Incorporating initial feedback

• Additional information added re SAP Activate Functional Upgrade roadmap and project plan
• Options for downtime optimization expanded
• Expanded advice for SAP Fiori, especially for custom apps
• Added additional known issues
• Expanded advice re available services
• Added Learning Journeys and available microlearnings

Revision 2 – June 2021 • Revised content structure

• Removal of duplicate content
• Additional information about added business value with upgrades
• Updated information with respect to latest release SAP S/4HANA 2020 and project
experiences
• Added several additional chapters based on lessons learned from projects
• Additional references for further information and learning

Revision 3 – January 2023 • Revised content to latest findings

• Additional comments with regards to whether recommendations are specific to SAP
S/4HANA Cloud, private edition
• Release strategy / compatibility scope updated
• Readiness Check for Upgrades and SAP Fiori Upgrade Impact Analysis added
• More details on general availability of ZDO
• Revision of section 4.4 Introducing New User Experiences re how to approach UX Adoption
planning during and post upgrade

The authors welcome your feedback to improve this guide further. Please email your feedback to
Feedback for Upgrading SAP S/4HANA Why, How and Best Practices

Public 5/122
1. INTRODUCTION AND MOTIVATION FOR THE UPGRADE

This guide provides lessons learned and best practices for upgrading from your current SAP S/4HANA
release to a higher version to take advantage of the latest capabilities.

This guide is relevant for SAP S/4HANA Cloud, private edition and SAP S/4HANA On-Premise.

You will also find advice on how to manage the pace of organizational change by running multiple,
repeatable continuous improvement projects after the upgrade to drive more business value from your
SAP S/4HANA solution over time.

Customer experiences of SAP S/4HANA upgrades confirm that upgrading is a relatively smooth process.
Statistics as of January 2023, show that technical upgrades to higher releases of SAP S/4HANA
take an average of 1.5 to 4 months (reported by the SAP S/4HANA Customer Care Program) with more
and more customers being able to perform their upgrades in a shorter timeframe.

This guide complements the official SAP S/4HANA Upgrade guide of your chosen target release of
SAP S/4HANA, which can be found on the SAP S/4HANA product page, for example: Upgrade Guide
for SAP S/4HANA 2022.

Important: You must refer to the official SAP S/4HANA Upgrade guide of your target SAP S/4HANA
release for detailed technical upgrade steps and post upgrade activities for your target release.

We also recommend reviewing the lessons learned in blog posts SAP Fiori for SAP S/4HANA –
Customer Experiences in Optimizing Upgrades – Yes You Can Upgrade Regularly and Prepare your SAP
S/4HANA System for an Upgrade.

Fast Track path for this guide - While you will find a lot of knowledge, shared experiences and
recommendations about upgrades in this guide, you can start with the most important chapters to start
your initial planning and activities. As you progress through your upgrade, you will find the remaining
chapters full of valuable information that will save you missteps and rework. Should you want to start
with this fast-track approach, the following diagram outlines the most important chapters and adds up to
around half of this document.

Public 6/122
Figure 1- Fast-track most important chapters

You can get a high-level overview of the entire upgrade project in the SAP Activate roadmap SAP
S/4HANA Upgrade and Product Integration. Here you find a description of all phases from Discover to
Run for the upgrade project and detailed information for all required activities and tasks within the
phases, followed by How SAP can support sections containing the SAP service offerings and links to all
tools and guides which help to perform the activities.

Figure 2 - SAP Activate Roadmap Overview of the Functional Upgrade of SAP S/4HANA

Important: This SAP S/4HANA How, Why and Best Practices Guide is applicable in scenarios where
customers are upgrading from an SAP S/4HANA release to a higher SAP S/4HANA release, e.g. from
SAP S/4HANA 1809 to 2022.

Migrating from the earlier solution SAP S/4HANA Finance (previously known as SAP Simple Finance)
releases 1503 or 1605 is not considered as an SAP S/4HANA upgrade. That solution was an add-on to
SAP Business Suite on HANA and moving to SAP S/4HANA is therefore treated as a system conversion.

Public 7/122
For more details, refer to the SAP Note 2450377 - Conversion of SAP S/4HANA Finance to SAP
S/4HANA – Migration Steps for Finance.

1.1. Why this best practices guide is needed

SAP S/4HANA was introduced in 2015 as SAP’s strategic digital core solution for the Intelligent
Enterprise. It was a major shift from the very successful SAP Business Suite to a new future focused
solution that took a cloud-first, mobile-first, and intelligent technologies approach to SAP’s
comprehensive ERP solutions. In each SAP S/4HANA release the capabilities have grown, along with the
number of SAP S/4HANA customers.
The first release SAP S/4HANA 1511 has gone out of mainstream maintenance on December 31 st, 2020.
Successive releases will reach end of standard 5-year maintenance period in successive years. Many
customers who went live on early SAP S/4HANA releases have already upgraded, some multiple times.
This guide brings lessons learned from real customer experiences across many upgrade projects gathered
by the SAP S/4HANA Regional Implementation Group, SAP S/4HANA Customer Care Program, SAP
Centre of Excellence, SAP Mission Control Center, SAP Enterprise Support and SAP Intelligent Delivery
Group.

Figure 3 - The evolution of SAP S/4HANA from release 1511 to 2022

The year 2020 marked the first year where one of the SAP S/4HANA releases went out of support. SAP
S/4HANA 1511 mainstream maintenance expired on December 31 st, 2020. At the end of 2023 SAP
S/4HANA 1809 will reach its end of mainstream maintenance.

Refer to the SAP Product Availability Matrix and specific SAP S/4HANA release version information in
there.

Public 8/122
Customers who are still running SAP S/4HANA 1809 or older releases are strongly advised to start
planning their upgrade now.

SAP S/4HANA Cloud, private edition customers are required to upgrade once their release is no longer
supported. Customer-specific maintenance is not an option for private edition.

On-premise customers should consider moving their systems to SAP S/4HANA Cloud, private edition
since the upgrade procedure and operations will be easier and typically can be achieved in a shorter
amount of time compared to dealing with the upgrade entirely on your own.

Usually there is a direct upgrade path available from one SAP release to any other subsequent release,
provided the releases are all in mainstream maintenance. However, in some cases, an upgrade to a release
that is several releases beyond customer’s current release may have to be performed in more than one step
which can result in delays and/or incur additional cost.

1.2. Our most important recommendation – capture your own Lessons Learned

We expect that upgrades and continuous improvement projects will become a normal part of
keeping up with the pace of innovation for all SAP customers.
There is a new release of SAP S/4HANA each year. Business changes quickly and functional
requirements may be different in the next upgrade, but with guidance from SAP and your own lessons
learned, adopting changes and new SAP S/4HANA innovations will become easier and more routine with
experience.
Whether you are executing an upgrade as part of your initial SAP S/4HANA implementation; executing
an upgrade after you have been live for some time; or simply executing one of many smaller continuous
improvement projects, it is always a good idea to review and capture lessons learned immediately after
go-live. This is the time to recognize what has been done right and what could be improved next time.
Depending on your organizational culture, you may even consider a Centre of Excellence team to ensure
these lessons are captured, communicated, and updated with each project.
Important:
You will notice that the largest chapter in this guide is 2 PREPARING FOR THE UPGRADE.
Provided appropriate preparation and planning has been completed in advance, upgrading is a relatively
smooth process. Preparation and planning ensure you have:
• Involved appropriate business and technical stakeholders
• Included appropriate resources and effort estimations in your project plan
• Made informed decisions regarding the scope of the upgrade
• Minimized surprises and associated risks

For examples of lessons learned captured by other customers, review blog post SAP Fiori for SAP
S/4HANA – Customer Experiences in Optimizing Upgrades – Yes You Can Upgrade Regularly.

1.3. Defining your business strategy for the upgrade

Public 9/122
The need to upgrade an SAP S/4HANA platform can come from your business or IT departments or both.
The identified needs will determine the scope and approach to the upgrade namely – Functional Upgrade
or Technical Upgrade.

• A Technical Upgrade focuses on minimum mandatory changes, and defers taking advantage of
new business value until later continuous improvement projects
• A Functional Upgrade includes a Technical Upgrade, with added scope to take advantage of at
least some new business functionality immediately

Regardless of your chosen upgrade approach, it is usual to introduce further business functionality after
upgrade via multiple continuous improvement projects over time.

In this chapter you will find the main reasons for upgrade and the driving factors for both types of
upgrade. Continuous improvement projects are covered in chapter 4 DRIVING ADDITIONAL VALUE
FROM YOUR UPGRADE.

You can also apply for a SAP Innovation and Optimization Pathfinder report, which provides tailor-made
recommendations on areas of relevant SAP innovations, business process improvements and IT
optimization potentials for your SAP S/4HANA system. This interactive report is available free-of-charge
for all customers on SAP Maintenance and provides recommendations that are based on the way you are
using your system today, for example:
• Where are areas of business process improvement for my system, and how am I positioned
compared to my peers?
• Out of SAP’s vast offering of SAP Fiori apps, SAP S/4HANA scenarios or Cloud extensions,
which are the most relevant ones, based on my system usage today?
• If you are operating an older SAP S/4HANA release: what are most relevant innovations in the
latest SAP S/4HANA release?
• Where are potential areas for IT optimization?
• And, for all the above: how can I best use SAP Services to implement innovations, or optimize
business or IT processes? What is suitable from SAP Enterprise Support, SAP Services, SAP
S/4HANA Value Assurance Packages etc.?

Refer to:

• SAP Innovation and Optimization Pathfinder on Spotlight

• Pathfinder for SAP S/4HANA Overview
• Pathfinder for SAP S/4HANA Sample Report
• How to apply for a Pathfinder report – video and guide

1.3.1. Drivers for a Technical Upgrade strategy

One driving factor for an SAP S/4HANA Upgrade is to simply stay on a supported SAP S/4HANA
release as dictated by the SAP S/4HANA maintenance schedule.
Another driving factor is to replace any classic ERP Compatibility Packs that expire on 31 st December
2025 with the alternative new capabilities in SAP S/4HANA.

Public 10/122
In addition to the maintenance reasons mentioned above, the key driving factors for the IT department to
upgrade the SAP S/4HANA system are to stay current with corrections and security patches that are
delivered with new releases, new Feature Package Stacks (FPS), and Support Package Stacks (SPS).
Keeping current with updates not only helps stabilize the system, but also improves performance as well
as ensures the security of the system.
The pure Technical Upgrade approach is more suitable if you are not ready to adopt the functional
changes and sets the path for future initiatives to adopt functional changes for added business value via
continuous improvement projects. You can find a summary of the technical upgrade approach in the SAP
Activate roadmap SAP S/4HANA Upgrade and Product Integration Roadmap.
Even with a pure technical upgrade, you should still take the opportunity to ensure your systems are ready
for future continuous improvement projects, e.g. by ensuring your SAP Fiori for SAP S/4HANA
architecture is in place.

1.3.2. Drivers for a Functional Upgrade strategy

The primary reason for choosing a Functional Upgrade is to drive more value out of your SAP
S/4HANA system by taking advantage of new business functionality immediately.
The business need for an upgrade is usually driven by new requirements, for example:
• Providing mobile access for internal and external users
• Digitalizing a feedback process
• Reducing manual effort for payment matching or improving the quality of payment matching
Innovations, new features, and improvements in new SAP S/4HANA releases help realize these
requirements and increase business value by demonstrating return on investment (ROI). Depending on
your scope there may be significant functional work that happens in this type of upgrade with redesign of
business processes. Such efforts are offset by the expected business benefits of change.

The main drivers for functional upgrades are:

• Introduce new business processes or improve existing business processes

• Move from side-by-side to embedded solutions within SAP S/4HANA
• Improve and grow your SAP Fiori User Experience
• Introduce new use cases for intelligent automation and intelligent technologies

Important: These drivers are not exclusive – it is reasonable and expected for a functional upgrade to
introduce multiple benefits at once, for example to grow the SAP Fiori user experience so that you can
take advantage of new business processes, new apps, new features, and new intelligent use cases only
available in SAP Fiori.

1.3.3. How to find out what’s new

You can use the SAP S/4HANA What’s New Viewer to quickly identify any new, changed, deprecated,
or deleted functionality between SAP S/4HANA source and target releases.

The link to the SAP S/4HANA What’s New Viewer is found on the SAP Help Portal product page for
SAP S/4HANA. The quick link to get to the product page is https://help.sap.com/s4hana_op.

The What’s New Viewer link can be found on the What’s New tab.

Public 11/122
Figure 4 - What's New Viewer for SAP S/4HANA in the SAP Help Portal

In the What’s New Viewer you can select the releases and feature pack stacks (FPS) above your source
release up to and including your target release/FPS.

Figure 5 - What's New Viewer - showing selection of SAP S/4HANA releases and feature pack stacks for evaluation

Public 12/122
You can further filter on: Line of Business, Solution area, and Type (Must Know, New, Changed,
Deprecated, or Deleted). You can use the free text Search to search for terms such as “Fiori”, “report”,
etc.

You will also find a What’s New Viewer for ABAP Platform on the What’s New tab. This includes
changes in:
• SAP Fiori launchpad
• ABAP programming models (such as RAP)
• CDS Views
• And other platform-dependent areas.

Refer to:
• openSAP microlearning video Working with the What's New Viewer in the SAP S/4HANA
playlist, Lines of Business Cross-Topics

1.3.4. SAP S/4HANA release and maintenance strategy

SAP S/4HANA releases prior to release 2023 follow a yearly cycle, i.e. every year there is a major release
for SAP S/4HANA. These releases are applicable for SAP S/4HANA Cloud, private edition and SAP
S/4HANA On-Premise.
Every release has a five-year mainstream maintenance phase after which it enters the customer-specific
maintenance phase. See SAP Note 52505 - Support after end of mainstream maintenance or extended
maintenance and/or SAP Maintenance Strategy for a description of all maintenance phases.
Starting from SAP S/4HANA 1709, SAP is offering extended maintenance until end of 2025, which is
included for SAP S/4HANA Cloud, private edition customers, but comes with additional cost for on-
premise customers once the earlier releases have gone out of mainstream maintenance.
Starting from SAP S/4HANA 2023, SAP plans to deliver a new major release every two years and
mainstream maintenance will be extended from five to seven years.

Refer to:
• SAP Release Strategy (PDF)
• SAP S/4HANA Maintenance Strategy (PDF)

1.3.5. Expiration of Compatibility Packs

Some of the classic features in SAP ERP are supported in SAP S/4HANA as Compatibility Packs, listed
in the Compatibility Scope Matrix. The usage rights to run these selected classic SAP ERP solutions on
SAP S/4HANA expire on December 31st, 2025. This is under the condition that you have licensed the
applicable solutions as set forth in your license agreements

Important: The announcement about the extension of maintenance for SAP Business Suite solutions has
no influence on the end of compatibility pack use rights - they will be terminated after 2025.
Out of 183 compatibility pack items, only 15 are still in clarification for an alternative.

SAP will, however, provide a selective and specific extension of Compatibility Scope usage rights to
December 31, 2030 for Transportation (LE-TRA), Customer Service (CS), and selected Production
Planning in Process Industry (PP–PI) items on an exceptional basis.

Public 13/122
If you are currently using any Compatibility Pack and an alternative solution has already been
provided in SAP S/4HANA, you should adopt it as part of your upgrade.

You can find the alternative solutions listed in the Compatibility Scope - Way Forward attachments to
SAP Note 2269324 - Compatibility Scope Matrix for SAP S/4HANA on-premise. Refer to the blog posts
The Future of Compatibility Packs in SAP S/4HANA and Compatibility Scope: What Happens after
2025/2030.

Figure 6 - The Future of Compatibility Packs for SAP S/4HANA

The SAP Readiness Check for SAP S/4HANA upgrades also comes with a Compatibility Scope analysis,
see chapter 2.4.2 for more details.

1.4. Business functionality impacts

These are the main areas to review to understand the business impacts:

• Delta simplifications due to the ongoing transformation from SAP Business Suite to SAP
S/4HANA
• New and changed functionality in SAP S/4HANA
• Business function activation impacts
• Add-on impacts for SAP S/4HANA releases
• Impacts due to the future of Compatibility Packs

1.4.1. Delta simplifications

Simplifications relate to the ongoing transformation from SAP Business Suite to SAP S/4HANA.
Simplifications are significantly reduced for upgrades between SAP S/4HANA releases compared to
initial system conversions to SAP S/4HANA, however, some simplifications still apply in an upgrade
context and need to be reviewed. Simplifications need to be assessed for:

• SAP S/4HANA
• ABAP

Public 14/122
Important: These Simplifications are checked as part of the upgrade process prior to upgrade. Ensure the
latest version of SAP Note 2502552 - S4TC - SAP S/4HANA Conversion & Upgrade new Simplification
Item Checks has been applied to your source (as-is) SAP S/4HANA release.

Delta simplifications between SAP S/4HANA source and target releases can be found in the SAP
Simplification Catalog at https://launchpad.support.sap.com/#/sic/overview. The simplification catalog
contains all simplifications including SAP S/4HANA and ABAP. The related SAP Notes explaining the
simplifications have the title prefix:

• S4TWL for SAP S/4HANA simplifications

• ABAPTWL for ABAP platform simplifications

Within the Simplification Catalog, to identify delta simplifications, set the following filter criteria:

• Source Validity (Prod) = your source SAP S/4HANA release e.g. 1809
• Source Validity (Stack) = your source SAP S/4HANA release FPS or SPS stack, e.g. Initial
Shipment Stack
• Target Validity (Prod) = your target SAP S/4HANA release e.g. 2022
• Target Validity (Stack) = your target SAP S/4HANA release FPS or SPS, e.g. 01 for FPS01
An example of filtering in the SAP Simplification Catalog is shown below.

Figure 7 - Comparing delta simplifications between releases in the SAP Simplification Catalog

You can filter on additional criteria such as: LoB/Technology or Business Area. The category filter can be
used to identify whether this is a change of existing functionality or impacted by the roadmap.

Public 15/122
Figure 8 - Simplification categories

You can also use the free text Search to search for terms such as ACR, ABAP, etc.

Once you have found the relevant items, select the SAP Note listed in the SAP Note column for a detailed
description of the change and its business impacts.

Alternatively, you can use the target release Simplification List PDF on the SAP S/4HANA product page
in the SAP Help Portal – and visually compare with your source release Simplification List PDF.

Refer to:
• SAP Note 2502552 - S4TC - SAP S/4HANA Conversion & Upgrade new Simplification Item
Checks
• openSAP microlearning video Finding Delta Simplifications between SAP S/4HANA releases in
the SAP S/4HANA playlist, Lines of Business Cross-Topics

1.4.2. Business function activation impacts

Business functions can have the following status: always_on, customer_switchable, and always_off. This
results in the following behaviour during the upgrade:

• If a business function was switched on in the SAP S/4HANA source release system but defined as
always_off in the SAP S/4HANA target release, then an upgrade of the business function is not
possible with this release.
• If a business function was switched off in the SAP S/4HANA source release system but defined as
always_on in the SAP S/4HANA target release, then the business function will be activated during
the upgrade.

Public 16/122
 • If a business function is defined as customer_switchable in the SAP S/4HANA target release, it
will keep the state defined in the target release during the upgrade.
Additional business functions can be activated or deactivated after upgrade.

1.4.3. Add-on impacts

Upgrades to standard SAP add-ons are delivered as part of the SAP S/4HANA release.
You will need to check:

• What add-ons are currently installed in the source system and what are their target releases?
• Are any add-ons installed in the source system that are not yet supported on the target release?
• Is any 3rd party software present in the landscape that was imported via transports?
• Does this software require any update as part of the upgrade?
For 3rd party software you may need to contact your 3rd party vendor to check on the status and expected
delivery date of any updates.

Important: Contact your 3rd party vendor early, e.g. when planning your project, as this may influence
your choice of target release and go-live date.

You should also be aware that add-ons running on SAP S/4HANA Cloud, private edition cannot have any
operating system access requirements.

Figure 9 - 3rd Party and SAP add-on support for SAP S/4HANA compared to SAP ERP

You can find the What’s New information in the product page for each standard SAP add-on in the SAP
Help Portal, e.g. for the add-on SAP Access Control, you would go to the related SAP Access Control
product page in the SAP Help Portal.

You should also check for related integration information for SAP S/4HANA, such as:
Integration: Access Control with Fiori Apps for S/4HANA On-Premise

You will need to check if your add-on is available for your target SAP S/4HANA release if:

• You want to introduce new SAP add-ons during the upgrade

Public 17/122
 • You want to uninstall ABAP add-ons during the upgrade
• Your add-on was developed by SAP Custom Development (formerly IBSO)
• Your add-on is provided by a partner
In each of these scenarios, consult SAP Note 2214409 - SAP S/4HANA: Compatible Add-Ons.

1.4.4. Introducing new business innovation

Upgrading SAP S/4HANA automatically delivers new business innovations including new business
processes, new SAP Fiori apps, and new use cases for intelligent technologies.
Typical new business innovation includes:

• New business processes

• New use cases for intelligent technologies
• New apps and improvements in existing apps
• New SAP Fiori features
• New classic User Interface (UI) capabilities when launched from SAP Fiori
• Performance improvements

Figure 10 - What's delivered with SAP S/4HANA as standard "out of the box" functionality

You can find all SAP Fiori for SAP S/4HANA apps and supported classic UIs in the SAP Fiori apps
reference library. You can also get some useful starting points for discussion with business stakeholders
on the best new business value for specific lines of business in the SAP Fiori lighthouse scenarios
(regularly updated).

You can find intelligent use cases provided with SAP S/4HANA in the Best Practice scope items and in
the SAP Help Portal. For example, Use Cases for Situation Handling. Further advice on where to find
relevant UX can be found in SAP Activate accelerator UX Value Goal App Selection Guides (Public)

Public 18/122
Figure 11 - Use cases for Intelligent Technologies introduced as new innovations with SAP S/4HANA

While these new business innovations will technically exist in your upgraded system, most new innovations
must be activated, configured, and assigned to users before you can use them. Some changes may be
automatically applied to your existing usage, such as: improvements in existing apps, some changes in SAP
Fiori features, some classic UI capabilities, and some performance improvements.

You can choose to take advantage of these new business innovations immediately as part of your upgrade,
i.e. the Functional Upgrade approach. Alternatively, you can choose to introduce new business innovations
after a Technical upgrade, e.g. as part of one or more innovation phases or continuous improvement
projects. In either strategy, you dictate the pace of organizational change to balance effort with reward.

You can pace the introduction of new business functionality to your desired Now/Next/Later roadmap, for
example, using the UX Adoption planning approach discussed in 4 DRIVING ADDITIONAL BUSINESS
VALUE AFTER UPGRADE.

VERY IMPORTANT: If you wish to take advantage of new business innovations after a Technical
Upgrade, you will need to ensure you put the requisite technical architecture in place during your technical
upgrade. For example: your SAP Fiori front-end server (FES) established, your system sized appropriately,
and prerequisites for intelligent technologies established, such as considering security needs for mobile
devices and on-premise/cloud integration.

1.5 Responsibilities during the upgrades of SAP S/4HANA Cloud, private edition

When upgrading SAP S/4HANA Cloud, private edition there are responsibilities to be considered on
project side while the actual technical upgrade will be executed by SAP Enterprise Cloud Services (ECS).

SAP S/4HANA Cloud, private edition customers are entitled to regular upgrades, for both Feature
Package Stacks (FPS) and major releases but will still have to request the technical upgrade by opening a
service request or reaching out to their responsible SAP ECS Client Delivery Manager (CDM).

Public 19/122
Preparation steps on application side must be taken care of on project side by the customer or
implementation partner, such as:

• Replacing deprecated apps with successor apps

• Adapting custom code as it might be required for the newer release (for example, because of new
simplifications)
• Performing regression testing
• Adapting / adding authorizations as required for new or replaced apps and features
• Executing performance testing for new or replaced apps and features

More details can be found in the Roles & Responsibilities Matrix (status 2022).

2. PREPARING FOR THE UPGRADE

This phase covers the DISCOVER and PREPARE phases of the SAP Activate Methodology. It will
typically start weeks to months before your intended upgrade.
Some customers treat creation of the business case and effort estimation as a small project itself. Before
you upgrade you will need to prepare your business case. Your upgrade drivers are based on
understanding the benefits of upgrading and mapping those benefits to the expected business and
technical value of the upgrade.
Important: There may be a gap between completing these phases and starting the upgrade itself, e.g. to
allow for approval of the business case, for resourcing the skills needed for the technical upgrade itself,
and for deploying relevant tools needed for the upgrade. If the operating environment for business users
needs to change, this may also be done before or parallel to the upgrade project.
At this point, you usually have a rough idea of a potential timeline for your upgrade. This will help you
determine your likely target SAP S/4HANA release and Feature Pack Stack. You will need to have
decided on your target release to work out the delta changes from your source release. While this decision
will vary depending on your circumstances, in this chapter you will find Key considerations for
choosing your target release and Feature Pack Stack.

You will need to decide whether:

• You will use a Functional Upgrade approach, i.e. introduce new functionality as part of your
Upgrade scope, or
• You will use a Technical Upgrade approach, do the minimum changes now and introduce new
functional changes in the RUN phase Post Upgrade, e.g. via one or more continuous
improvement projects
In this chapter you will find Key considerations for choosing functional upgrade versus technical
upgrade.

Having decided on your upgrade scope, you will need to estimate the effort to upgrade, and the resources
needed. Estimation depends on many factors, such as:

• Planned functional scope

• Whether SAP Fiori is already in use
• Whether new intelligent technologies are in scope
• Resources and skills available

Public 20/122
In this chapter you will find 2.2.1 Example upgrade plan for a Functional Upgrade, 2.2.2 Example
plan for a Technical Upgrade and 2.2.3 Key considerations when estimating effort to upgrade.
You will need to propose a timeline for your upgrade. Make sure you have allowed sufficient time for:

• Approval of your business case,

• Gathering resources for your upgrade
• Making commercial arrangements with system implementation partners
• Booking SAP Services to support your plan, e.g. MaxAttention Business Process Performance
Optimization (BPPO) service
To ensure your Business Case and effort estimates cover your upgrade scope, you will need to understand
the impacts for these major areas discussed in this chapter:

• Architecture and technical impacts

• Business process and other functional impacts
• User experience impacts
• Custom code impacts
Having assessed the impacts and discussed them with your project sponsor and stakeholders, you can then
determine:

• The business value of upgrade to your organization

• Any risks or issues to be factored into your business case and upgrade plan
For those customers taking advantage of SAP Solution Manager you will find a brief overview of SAP
Solution Manager features that will help you scope business impacts and critical areas for regression
testing later in this guide in the appendix.

2.1. Key Considerations for choosing your target release / Feature Pack Stack

The key considerations for choosing your target release / feature pack stack are:

• Expected start date of your upgrade project

• Expected go-live date of your upgrade project
• Availability of desired to-be functionality
• Availability of desired partner add-ons
As a rule of thumb, it is recommended to start your upgrade project with the most recent release of SAP
S/4HANA. The initial shipment stack of each SAP S/4HANA release is followed by Feature Package
Stacks (FPS01, FPS02 and additionally FPS03 starting from SAP S/4HANA 2023) bringing some
additional new features, and then moves to maintenance mode with any further corrections or
improvements via successive Support Package Stacks (SPS03, SPS04, etc.).

Public 21/122
Figure 12 - Example of SAP S/4HANA release strategy up to SAP S/4HANA 2023

Figure 13 - SAP S/4HANA release strategy from SAP S/4HANA 2023 onwards

You should consider implementing the most recent shipment stack - Feature Package Stack (FPS) or
Support Package Stack (SPS) - of your SAP S/4HANA release. Most importantly you should consider
implementing Feature Package Stack 1 (FPS01) or a higher stack, rather than starting with the Initial
Shipment Stack. This has the following benefits:

• Simplified support
o While most apps/processes are pre-tested in SAP S/4HANA Cloud, public edition , there
are always additional apps/processes that are specific to SAP S/4HANA Cloud, private
edition and on-premise. Moving to FPS01 or higher FPS/SPS applies available fixes
related to known issues with the initial release.
• Long-term maintenance
o The long-term maintenance version of SAPUI5, the primary user interface technology
used for SAP Fiori apps, is aimed at the FPS01 of each release of SAP S/4HANA. Going

Public 22/122
 live on FPS01 or a higher FPS/SPS reduces the need for further upgrades or patches in the
short to medium term. Similarly, before go-live you should ensure your SAPUI5 version is
on the highest available minor version – refer to section 3.2.5 Patch strategy for SAP
Fiori FES
• Partner add-ons
o Since partners may receive SAP S/4HANA releases at the same time as customers, there is
usually a lag between the release of a new release and the provision of a certified partner
add-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 the
relevant partner organization.
Depending on the timing of your project, it may make sense to start your project on a sandbox on the
latest currently available shipment stack, even if you intend to go-live on a different shipment stack.
However, once you move to your development environment you should keep the shipment stack stable to
avoid further technical impacts, for example:

• The initial shipment stack of SAP S/4HANA 2022 is available at the project start, however SAP
S/4HANA 2022 Feature Pack Stack 1 (FPS01) is planned to be released prior to the expected date
to upgrade your development (DEV) environment.
• By starting on the initial shipment stack on a sandbox you can do most of your discovery and
exploration while waiting for Feature Pack Stack 1 (FPS01) to be released.
• Once the Feature Pack Stack is released, you then start the upgrade of your development
environment on FPS01.
• You then continue the rest of the project on FPS01.
• This approach is sensible because generally the majority of new innovations for each SAP
S/4HANA release are part of the Initial Shipment Stack, so the difference between shipment
stacks of the same SAP S/4HANA release is much smaller than the differences between e.g. SAP
S/4HANA 2021 FPS02 and SAP S/4HANA 2022.

The following are NOT considerations for choosing your target release and feature pack stack:

• Your source SAP S/4HANA release or feature pack stack

• Your SAP add-ons
o These are released aligned to the current SAP S/4HANA source release or feature pack
stack
• “N-1” release approach to support
o This approach is not recommended for SAP S/4HANA Cloud, private edition or on-
premise, as the majority of functionality has already been released on SAP S/4HANA
Cloud, public edition up to 1 year before the release of the equivalent SAP S/4HANA
release.
You should also check for any restriction notes for the target SAP S/4HANA release. This gives a
summary of any major restrictions, for example SAP Note 3230844 - SAP S/4HANA 2022: Restriction
Note.

2.2. Key considerations for Functional Upgrade vs Technical Upgrade decision

The main difference between a Functional Upgrade and a Technical Upgrade is the timing for introducing
new business value and/or process changes.

Public 23/122
A Technical Upgrade includes only the minimum mandatory changes in its scope. Adding new business
value is deferred to running continuous improvement projects after upgrade. Continuous improvement
projects are discussed in more detail in chapter 4 DRIVING ADDITIONAL VALUE FROM YOUR
UPGRADE.

A Functional Upgrade necessarily includes both Technical Upgrade and some expanded scope for
introducing new business value to one or more business processes and impacts one or more business user
groups (i.e. business roles).

The main tipping points between Functional Upgrade vs. Technical Upgrade are:

• Is there a hard deadline for go-live that would prevent a functional upgrade approach?
• Is the business ready for functional improvements?
• Are there particular user groups who need to take advantages of innovation sooner than later?
• Are there particular budget concerns that restrict the scope of any functional changes?
Remember that all upgrades will introduce some mandatory changes, e.g. automatic changes to SAP Fiori
app floorplans and simplification changes.

Very important: If you have not yet implemented SAP Fiori in your current SAP S/4HANA release,
you must include implementation of your SAP Fiori front-end server – embedded (recommended)
or standalone - and SAP Fiori Launchpad even when choosing a Technical Upgrade approach.
You must do this even if you intend to use SAP Build Work Zone as your primary launchpad.
This is because SAP Fiori is where business users consume SAP S/4HANA innovations. This includes
innovations such as embedded analytics, intelligent use cases, new business processes (such as Group
Reporting, Central Procurement, and Predictive MRP), and the new user experience itself. Without SAP
Fiori driving new business value from your SAP S/4HANA solution will be greatly impaired.
There are also configuration and extension options for SAP S/4HANA that can only be performed using
SAP Fiori apps, even where these changes impact on classic SAP GUI transactions. For example adding
custom fields to the virtual data models based on CDS Views, which is done using the SAP Fiori app
F1481 Custom Fields and Logic.
The SAP Fiori setup must be done either during the initial implementation of SAP S/4HANA or during an
upgrade, because establishing SAP Fiori involves:
• Setup of the SAP Fiori FES & related architecture (such as SAP Web Dispatcher)
• Impacts on system sizing and performance
• Central configuration of the SAP Fiori launchpad and related features (search, notifications, user
defaults, context-sensitive help, etc.)
• Activation of essential business roles to support configuration and extensions.
Refer to: 2.7.9 Essential business roles required to administrate and extend SAP Fiori.
Even where you are planning to use SAP Build Work Zone, standard edition or advanced edition as your
primary launchpad, the local SAP Fiori front-end server of your SAP S/4HANA system is where your
SAP S/4HANA apps are stored and launched.

Public 24/122
Figure 14 - SAP Build Work Zone, standard edition and advanced editions can federate content from SAP S/4HANA alongside other content.

Similarly, if you have not yet installed SAP Screen Personas in your SAP S/4HANA solution, you should
consider doing so as part of your Technical Upgrade.
SAP Screen Personas provides no-code/low-code options to improve classic user interfaces, such as SAP
GUI and Web Dynpro ABAP applications, for example to hide unwanted fields / buttons and merge tabs.
This improves user experience in areas where there is no equivalent SAP Fiori app yet and it is not viable
to create a custom Fiori app.
Refer to:
• Blog post SAP Fiori for SAP S/4HANA – Yes you need SAP Fiori to Configure, Adapt and
Extend SAP S/4HANA
• SAP Screen Personas topic in the SAP Community

2.2.1. Example upgrade plan for a Functional Upgrade

You can download the example project plan provided in the SAP S/4HANA Upgrade and Product
Innovation Roadmap in the SAP Roadmap Viewer. Further details of all tasks listed in the plan are
explained in the Roadmap Viewer content section. The project plan template is intended to give you a
complete list of all tasks and should be adapted to your project setup and requirements.

Refer to: SAP Roadmap Viewer Download ZIP

Public 25/122
Figure 15 - Example Functional Upgrade Plan for SAP S/4HANA

2.2.2. Example upgrade plan for a Technical Upgrade

The primary focal points of a technical upgrade are:

• Technical upgrade of the hardware and software

• Mandatory changes to configuration and custom code
• Regression testing and remediation
With a technical upgrade, adding new functionality (such as deploying more SAP Fiori apps) is deferred
until the RUN phase after upgrade, and is added via continuous improvement projects.

Public 26/122
Figure 16 - Technical Upgrade plan example from SAP Activate roadmap SAP S/4HANA Upgrade and Product Integration Roadmap

Customer experiences show that a technical upgrade averages from 1.5 to 4 months (reported by SAP
S/4HANA Customer Care Program).

A sample 5-month plan for a Technical Upgrade is shown below. This is based on a real-life example of a
customer who upgraded from SAP S/4HANA 1610 to 1909, with a 1 TB system.

Figure 17 - Example Technical Upgrade Plan for SAP S/4HANA

Key assumptions in the plan are:

• You have a standard 3-tier DEV-QAS-PRD landscape and a separate sandbox server
• Your sandbox system is a non-integrated environment so that other parallel solutions are not
impacted.
• You start the upgrade with a sandbox system, which is a snapshot copy of your production system
and sized accordingly
• DEV & QAS regression testing includes integration testing since this cannot be tested on the
sandbox
• The upgrade project starts on Feature Pack Stack 1 or higher of the current SAP S/4HANA release
• SAP Fiori FES is already in place, in either embedded or standalone mode
• The current choice of embedded or standalone deployment is not to be changed
• SAP HANA database is already on SAP HANA 2.0 version
• Only mandatory functional and technical changes are to be applied
• No new apps will be introduced, other than successor apps for deleted or deprecated apps
• Go-live occurs over a weekend

Public 27/122
 • Hypercare needs to cover the initial fiscal period end after go-live
• Resourcing estimates are for an onsite team

Project Resources needed typically include:

• Project Manager – Required

o Part-time, moving to full time for the production upgrade and Hypercare period
• Solution Architect – Required – Part-time throughout the project
• UX Architect – Required – Part-time throughout the project
• Technical/Basis Expert(s) – Required
o Full-time – moving to overtime for the upgrade go-live
• Functional SME (Subject Matter Expert) for each functional area in scope
o Part-time depending on business functions in scope
o E.g. Finance consultant may be full-time during uptime and regression testing, while
Logistics expert may be part-time
• Developer(s) – Required
o Full-time during custom-code remediation on the sandbox
o Part-time after that to diagnosis & resolve any residual issues in other systems
• Business User Tester(s) – Required
o Business User Testers dedicated for each functional area in scope
o Full-time during regression testing

2.2.3. Key considerations when estimating effort to upgrade

Key considerations for estimating efforts for the upgrade include:

• What experience and skills do you have available to assist with the upgrade?
• Does your scope include any new functionality, e.g. new SAP Fiori apps, new build of custom
SAP Fiori apps or new business functions that will be activated?
• Does your existing scope (in your current SAP S/4HANA system) include any obsolete,
deprecated, or superseded SAP Fiori apps, SAP GUI transactions or other classic UIs that will
require business process changes? You can use the SAP Fiori Upgrade Impact Analysis to identify
these.
• Is your existing scope impacted by any delta simplifications that will require business process
changes?
• What degree of test automation do you have available for regression testing?
• How many test scripts will need to be revised or written from scratch?
You may wish to consider starting your project explore phase with a sandbox system that is a copy of
production, rather than in your development environment.

The benefits of starting with a sandbox that is a copy of production are:

• Less disruption to your business-as-usual DEV-QAS-PRD systems

• Delta simplifications, mandatory custom code corrections and areas requiring performance
optimization can be assessed against realistic data
• Using a copy of production enables regression testing on realistic databases
• It rapidly identifies any fine detail changes in existing apps

Public 28/122
 • During regression testing, you can quickly identify & assess any first targets for performance
optimization
• Quicker upgrades in your DEV-QAS-PRD systems, as any early discoveries or corrections made
in the sandbox can be factored in to optimize the upgrade process
o Runsheets of all upgrade activities should be made for the upgrade on the sandbox, then
used to speed up the upgrade of subsequent systems
o Test cases and test scripts should be identified and refined on the sandbox, then used to
speed up regression testing in later systems
o Any test automation can be trialed and refined on a sandbox, then used to speed up
regression testing in later systems
• Mandatory custom code corrections can be performed on a sandbox and optionally transported to
DEV, minimizing the uptime requirement for DEV before moving to QAS
Add extra time to your Upgrade Project if any of the following circumstances apply:

• You need to upgrade from SAP HANA 1.0 to 2.0

• You have decided to migrate your SAP Fiori FES from standalone(hub) to embedded mode
• You start on the initial shipment stack and need to upgrade to FPS01 or higher before go-live
• You have many integrated parallel solutions and need to allow additional time for integration
testing
• You have parallel integrated Cloud solutions that are updated during the timeline of the project and
need to allow additional time for integration testing after each Cloud upgrade
• You need to upgrade the operating environment for business users as part of the project, e.g. deploy
new devices, new versions of device operating systems, or new browser versions
• Due to simplifications of tables to CDS Views in critical reports/analytics, you may need to allow
additional time to remediate custom reports/analytics
• You have strict segregation of duties requirements that require a more than usual degree of
authorization testing
• You have more systems in your SAP S/4HANA landscape to upgrade, e.g. training servers
• You have a remote or mixed onsite/remote team

2.3. Setting your update strategies incl. UX and mobile devices

Your mobile device strategy is a living document. While use of mobile devices is optional, their use is
now so widespread that it is rare for mobile devices to be out of scope. Even if the current strategy is
desktop and laptop only, some statement of the business reasons for this choice should be kept on record,
along with any conditions that would need to change before mobile devices can be considered.

There are many holistic considerations when using mobile devices, for example:

• Company-issued vs BYOD (bring your own device)

• Mobile device management, e.g. remediation strategy in case of lost or stolen devices
• Internet and/or VPN access
• Cyber security, authentication, and Single-Sign On (SSO) arrangements
• Supported device operating systems (device OS)
• Native vs. online app requirements

Public 29/122
Moving to mobile devices can be done at any time, however the strategy around mobility does need to be
carefully considered before moving any business apps and data onto these devices.

Your User Experience strategy is a living document that should be defined at the latest as part of your
initial SAP S/4HANA project. Once defined, your UX strategy should be updated whenever you upgrade
or other circumstances change. You can find a UX Strategy Template in SAP Activate.

Circumstances that could require your UX strategy to be adjusted include:

• Upgrade to a new SAP S/4HANA release, e.g. to take new UX options in the SAP Fiori launchpad
or in SAP Fiori floorplans (such as Fiori elements) into consideration
• Introduction of mobile devices and a mobile device strategy, e.g. to capture new entry point
options for business users
• Introduction of new software, e.g. SAP Cloud solutions, which need to be aligned to the overall
strategy
• Mergers and acquisitions, as these may change the mix of business users to be supported
• Introduction of new web browsers or desktop client software, which may impact entry points and
launching options
• Move to a central hub such as SAP Launchpad Service running in the SAP Business Technology
Platform (BTP), which has impact on entry points and app launching options
• Introduction of new intelligent technologies and how they impact the delivery, appearance, or
behavior of the user experience

2.4. General planning for the upgrade

Once you have taken the decision whether to plan for a technical or functional upgrade and set your UX
strategy, you are ready to take the next steps and plan for the exact identification of delta scope and
change management. There are different important considerations and tools you can leverage for it.

2.4.1. Identifying delta scope

The minimum required delta scope for a Technical Upgrade is:

• Review and update your architecture including:

o Patching your SAP Fiori FES and SAP S/4HANA solution to the most recent patches for
your target SAP S/4HANA release to minimize issues
o Key areas to patch include kernel, Unified Rendering, ABAP, and SAPUI5
• Evaluate the impact of delta simplifications on your current processes
• Replace obsolete, deprecated, and superseded functionality with successors, including:
o SAP Fiori apps superseded by new versions or new apps
o Classic UIs, e.g. obsolete GUI transactions due to simplifications
o SAP Business Roles, e.g. in rare cases a role may be split or renamed
o Obsolete SAP Fiori launchpad configuration features
• Review launchpad content and layout for outdated references, e.g. where tiles/target mappings
have been reassigned to a different catalog
• Review any custom-built SAP Fiori apps and ABAP code, where needed to migrate them to the
target SAPUI5 version, and similarly adjust the ABAP code layer, e.g. for delta simplifications
• Review authorizations, e.g. new authorizations added to processes or apps

Public 30/122
 • Review launchpad layouts, e.g. check that tiles to obsolete, deprecated or superseded apps/UIs
have been replaced with tiles to successors
• Regression test all critical processes

Strongly recommended scope for a technical upgrade includes:

• If using standalone Fiori front-end server, migrate to embedded Fiori front-end server
• Review launchpad features and activate any obvious high benefit features, e.g. new App Support
option in SAP S/4HANA 2020 FPS01 greatly simplifies support, review new launchpad
configuration parameters
• Replace existing predecessor apps with their successors
• Move to the latest best practice tools for managing launchpad content, layout, authorizations, and
support to improve efficiency and capability
• Review end-to-end performance to take advantage of any performance improvement options
• Review test automation options, to minimize future regression testing
• Consider extending your solution with side-by-side services and capabilities using SAP
Business Technology Platform, such as SAP intelligent Robotic Process Automation. Spotlight
reports highlight innovation opportunities for your transformation journey.

For a Functional Upgrade, you include the technical upgrade scope as a minimum. You add whatever
additional scope is aligned to the business outcomes of your functional upgrade. Typical scope additions
include:

• Replace standalone solutions with solutions embedded in SAP S/4HANA

• Grow your coverage of processes, including new business processes in SAP S/4HANA
• Grow your coverage of users and business roles
• Grow your SAP Fiori coverage, e.g. replace classic UIs with SAP Fiori apps, add embedded
analytics, add intelligent automation apps
• Activate new SAP Fiori launchpad features
• Grow your usage of intelligent automation, by deploying use cases embedded within SAP
S/4HANA
• Extend your solution with additional side-by-side capabilities, using SAP Business Technology
Platform, such as SAP intelligent Robotic Process Automation
• Extend your solution by integrating with additional SAP cloud solutions, such as SAP Analytics
Cloud

2.4.2. Identifying change management scope via Readiness check

Since 2021 SAP has introduced the new SAP Readiness Check for SAP S/4HANA upgrades, which will
analyze your current SAP S/4HANA implementation for the estimated impact when moving to a higher
SAP S/4HANA version.

Like the conversion from your earlier ERP system to SAP S/4HANA, where you had to deal with a large
set of simplification items to prepare the ERP system for the conversion, there are additional
simplification items with every release and feature package as part of the SAP S/4HANA maintenance
strategy.

With every feature package, different modules and processes are being renewed, resulting in a (small)
number of new simplification items you may need to address. SAP Readiness Check for SAP S/4HANA

Public 31/122
upgrades shows the relevant simplification items based on your source and target release and feature
package.

Amongst others, the following checks are available for SAP S/4HANA upgrades and additional checks
are typically added every year:
• Simplification Items
• Recommended SAP Fiori Apps
• Obsolete, Deprecated, Superseded SAP Fiori apps and classic UIs
• Integration
• Custom Code Analysis
• SAP Innovative Business Solutions
• Add-On Compatibility
• Compatibility Scope Analysis

In context of an upgrade, you should consider adding more innovation and rolling it out as per SAP Fiori
app recommendations.
• Change management is very important when moving from classic SAP transactions to SAP Fiori
and you can find a lot of useful information about how to pace organizational change in the blog
posts SAP Activate – Introducing UX Value Goals for your UX adoption roadmap and SAP Fiori
for SAP S/4HANA – Recommendations for transitioning users from SAP GUI to SAP Fiori.

It is crucial to run the SAP Readiness Check for SAP S/4HANA upgrades as early as possible in your
project. Learn more about it in blog post SAP Readiness Check for SAP S/4HANA upgrades.

The Compatibility Scope Analysis will check for compatibility packages used in your current SAP
S/4HANA system, highlighting where alternatives exist, exist with roadmap, or are planned.

You should consider simplifying future upgrades and aligning to cloud strategy by reverting to standard
with a clean core. Review the latest guidance in Custom Extensions in SAP S/4HANA Implementations -
A Practical Guide for Senior IT Leadership and the detailed guidance on Extensibility for SAP
S/4HANA in the SAP Help Portal.

Public 32/122
Figure 18 - Extensibility for SAP S/4HANA clarifies the options for reverting to a clean core approach.

You should evaluate your custom code for opportunities:

• to replace custom extensions with equivalent capabilities provided as standard in SAP S/4HANA,
and/or
• move custom developments to the Cloud, e.g. via SAP Business Technology Platform services.

A typical evaluation order to maximize clean core is:

1. Key User Extensibility – no-code/low-code, upgrade-safe, and usually least effort
2. Depending on the use case, Developer Extensibility (tightly-coupled complex extensions) or Side-
by-Side extensibility (loosely-coupled complex extensions)
Classic Extensibility should be considered a fallback option due to its higher ongoing TCO impacts.
Classic Extensibility should be avoided where clean core alternatives exist.

You can evaluate your code using the SAP Fiori app F3191 Custom Code Migration that is part of your
SAP S/4HANA solution (releases 1809 and higher).

2.5. Technical planning for the upgrade

There are several architecture and technical impacts to be considered during the upgrade. These need to
be reviewed and key decisions made to ensure your target release meets expectations and can cope with
any expected increase in usage.

• System architecture
• System requirements for the target release
• SAP HANA database changes
• Globalization, country versions and languages
• Sizing

Public 33/122
In addition, the following technical areas need to be reviewed and updated. These may affect the scope,
timing and resources needed.

Important: As a minimum, every upgrade project should include performance testing and assume
authorizations will need to be adjusted.

• Patch strategy
• Performance
• Authorizations
• Operating environment for users
• Development environment
• Security
• Integration
• Intelligent capabilities

2.5.1. Planning the upgrade in the Maintenance Planner

Like new installations and system conversions, the Maintenance Planner is the SAP tool to be used for
planning upgrades of the existing system. It will perform several checks on the system, point out the
impact and help calculate and download the software files required for the actual upgrade. The actual
upgrade will then be executed with the Software Update Manager (SUM).

The Maintenance Planner is accessible at https://apps.support.sap.com/sap/support/mp and will check the

source system for Add-Ons and Business Functions.

2.5.2. Reviewing your sizing

Always re-check your system sizing as part of your upgrade.

In addition to database growth due to business changes, new features, new capabilities, new performance
options, increasing your SAP Fiori and analytics coverage, and/or adding new users can all have an
impact on sizing.

An upgrade is the ideal time to re-check and adjust your system size if needed.

Important: If you intend to add new functionalities during or after the upgrade - such as SAP Fiori
and embedded analytics – you will need to perform additive sizing using the SAP Quick Sizer, too.

Reference notes:
• SAP HANA Quick Sizer introductory resources
• SAP Help Portal - SAP Fiori implementation chapter on Sizing
• SAP Note 1872170 - ABAP on HANA sizing report (S/4HANA, Suite on HANA...)
• SAP Note 2813738 - Brownfield sizing for SAP S/4HANA embedded analytics
• SAP Note 2815376 - Greenfield sizing for SAP S/4HANA embedded analytics
• SAP Note 2467172 - How to size Fiori applications based on number of users

2.5.3. Operating system requirements

Public 34/122
Before you upgrade your SAP S/4HANA system, you may need to upgrade or change the operating
system for your application servers. The following SAP Notes are a must read:

• SAP Note 2620910 - SAP S/4HANA 1511, 1610, 1709, 1809 and SAP BW/4HANA 1.0, 2.0:
Recommended and released Application Server Platforms.
• SAP Note 2696472 - Upgrade/Conversion planning hints for de-supported platforms lists different
options to handle this situation.

2.5.4. Database requirements

Before you upgrade your SAP S/4HANA system, you may need to upgrade your SAP HANA database to
the relevant release, support package stack (SPS), and revision for your target SAP S/4HANA release.

For example, for upgrading to SAP S/4HANA 2020, SAP HANA 2.0 SPS05 revision 51 is the minimum
revision. The latest available revision is typically recommended.
The SUM tool will check if the correct SAP HANA revision has been applied.
Important: If you are upgrading from 1511 or 1610 to 1709 or higher, this also involves an upgrade from
SAP HANA 1.0 to SAP HANA 2.0

Refer to:
• SAP Note 2655761 - SAP S/4HANA - restrictions and recommendations regarding specific
revisions of SAP HANA database for use in SAP S/4HANA

Other useful references:

• SAP HANA Server Installation and Update Guide

• SAP Note 2426339 - Support for SAP HANA 2 in SAP S/4HANA - Technical Information
Regarding SAP HANA Requirements
• SAP Note 2372809 - Mandatory Preparation Steps for Upgrading a SAP HANA 1 System to SAP
HANA 2
• SAP Note 2378962 - SAP HANA 2.0 Revision and Maintenance Strategy
• SAP Note 2600030 - Parameter Recommendations in SAP HANA Environments

2.5.5. Application server considerations

Ensure you check the target release’s Release Information Note for the available upgrade paths, required
feature pack stacks and tooling requirements.

For example, for SAP S/4HANA 2020:

• You can upgrade from SAP S/4HANA 1511, 1610, 1709, 1809, 1909, 2020, or 2021 to SAP
S/4HANA 2022
• Check the SAP Note 3145277 SAP S/4HANA 2022: Release Information Note for the required
feature package stack equivalencies for the upgrade from SAP S/4HANA 1511, 1610, 1709, 1809,
1909, 2020, or 2021 to SAP S/4HANA 2022

Public 35/122
 • You must additionally check the release information note for the minimum required Software
Update Manager 2.0 (SUM) Support release and support pack for the upgrade
A summary of the stack components for each release can be found in blog post: Upgrade to SAP
S/4HANA 2020 – time to change.

2.5.6. Globalization, country versions and languages

If you want to add additional language packs as part of upgrade, check the globalization note for your
SAP S/4HANA target release for any considerations and the relevant SAP Note number for language
availability of your SAP S/4HANA target release.
For example, for target release SAP S/4HANA 2022, all feature pack stacks:

• SAP Note 3107606 - SAP S/4HANA 2021 and 2022, Globalization & Local Versions: Release
Information & Restriction Note
• SAP Note 3196048 - SAP S/4HANA ON-PREMISE 2022: Language Availability

Important: If Best Practices content was applied to the source system, it is not possible to apply language
packs to Best Practices content. Adding system language packs is still possible.

2.5.7. Server architecture impacts

Out of the typical server architecture of an SAP S/4HANA system, the SAP Fiori front-end server and
SAP S/4HANA server are the most important components.

Important: In embedded mode the SAP Fiori FES and SAP S/4HANA server are different components
of the same server. This reduces the technical upgrade of the servers somewhat, however all other
considerations are largely similar regardless of whether embedded or standalone mode is used. While
additional components are needed - such as SAP Web Dispatcher for load balancing and to avoid cross-
site scripting - upgrading these is typically unlikely to add significant effort in a technical upgrade project.

Refer to: SAP Web Dispatcher guide on SAP Help Portal

In a functional upgrade project, there may be additional effort if there is a significant shift in security
requirements. For example:

• If mobile devices are introduced for the first time as part of the functional upgrade
• If internet access to apps is introduced for the first time as part of the functional upgrade
If your original SAP S/4HANA system was deployed using the standalone approach for the SAP Fiori
FES, migrating from standalone to embedded should be considered, i.e. with your SAP Fiori FES on a
separate server to your backend SAP S/4HANA server.
Embedded mode provides numerous benefits such as reduced server costs and simpler configuration.

Public 36/122
Figure 19 - Embedded Fiori front-end server comparisons across SAP S/4HANA releases

For SAP Fiori FES 2022 for SAP S/4HANA, both deployment options - embedded and standalone server
- are supported. In case of a standalone server deployment, the minimum SAP NetWeaver release is SAP
NetWeaver 7.52.

The general architecture recommendation has changed since December 2017 from standalone to
embedded Fiori FES deployment. This is how most SAP customers are planning their architecture.
For an architecture overview and possible deployment options, see SAP Fiori Deployment Options and
System Landscape Recommendations. Important: This document is regularly updated.
How to move from standalone to embedded deployment is described in Migrate SAP Fiori Front-End
Server from Standalone to Embedded System Deployment.
For example, the installed software components of a SAP S/4HANA system with embedded FES will
include components for:
• SAP FIORI FOR S4HANA – the software component containing the SAP Fiori apps
• SAP FIORI FES FOR S/4HANA – the software component for the SAP Fiori front-end server
itself

Figure 20 - Example of Installed Product Versions for SAP S/4HANA 2022 Initial Shipment Stack system with embedded SAP Fiori front-
end server

Refer to SAP Fiori Deployment Options and System Landscape Recommendations for more information
and details of the considerations.

Public 37/122
Important: This document is usually updated several times per year, so it is important to re-check the
document during your project.
The following are NOT considerations for standalone (hub) versus embedded mode:
• SAP Build Work Zone, standard edition (formerly known as SAP Launchpad Service on SAP
BTP)
• SAP Build Work Zone, advanced edition (formerly known as SAP Work Zone on SAP BTP)
In both these cases the SAP Launchpad launches the app which is stored on your SAP S/4HANA On-
Premise or SAP S/4HANA Cloud, private edition solution.

Upgrade prerequisites:
Important: There are strict dependencies on which SAP FES releases can be used with SAP S/4HANA.
Each SAP S/4HANA release has minimum and maximum FES releases that can be used. Depending on
your release and architecture, there can also be restrictions on using standalone FES as a central hub; and
on certain UX integration capabilities (e.g. in-place navigation). Please check the latest version of the
SAP Fiori Deployment Options and System Landscape Recommendations carefully!

Figure 21 - SAP Fiori front-end server release upgrade options within SAP S/4HANA releases

Finally, in the Software Downloads of the SAP Support Portal, check for the identified known side-
effects of the related SAP_UI component on your target release. These side-effects are usually related to:

• Unified Rendering Library Patches

• Business Client (formerly NWBC) Runtime Patches

Public 38/122
Figure 22 - Example: Identified side-effects of SAP_UI 7.54 SP02

Considerations for after your upgrade:

Once you have decided on the deployment of your SAP Fiori FES, future upgrades of the FES release are
possible as demonstrated in the example below via any of the 3 following scenarios:

1. Upgrade SAP FES with your upgrade of SAP S/4HANA

2. Upgrade your SAP FES and ABAP Platform, without upgrading SAP S/4HANA
3. Patch your SAP FES to the latest SAPUI5 release.

Figure 23 - Options to upgrade SAP Fiori for your SAP S/4HANA system

Refer to:
• SAP Fiori Deployment Options and System Landscape Recommendations
• SAP Fiori deployment options and SAP Fiori front-end server strategy – UPDATE 2022
• How and Why to Upgrade SAP Fiori for your SAP S/4HANA solution

Public 39/122
 • SAP Fiori for SAP S/4HANA – Transition from Standalone to Embedded Deployment in SAP
S/4HANA
• SAP Note 2217489 - Maintenance and Update Strategy for SAP Fiori Front-End Server – this
contains a central table mapping of SAP Fiori FES to SAPUI5 versions

2.5.8. Security - authentication

If moving from intranet only to Internet access for the first time, allow additional time to ensure security
has been appropriately considered.

Refer to the latest recommendations in:

• Blog post Considerations and Recommendations for Internet-facing Fiori apps

2.5.9. Security - authorizations

New and/or changed authorizations may be introduced due to:

• New SAP Fiori apps

• Changes in SAP Fiori apps
• Changes in the catalog assignment of SAP Fiori apps or classic UIs
• Changes in business processes
• Additional authorizations on existing data extracts (e.g. OData Services, CDS Views)
A key watchpoint for regression testing is to gather and assess data authorization changes, especially
those related to OData Services and their underlying CDS Views. You can use transaction SU24 to
compare your authorization defaults compared to SAP authorization proposals.

Refer to:
• SAP Fiori for SAP S/4HANA – SAP Fiori Security Design Fundamentals
• Getting back to Standard Proposals with SU24 Authorisation Variants
• SAP Note 2919392 – Determining missing authorizations for Access Controlled CDS Entities

From a security perspective, plan on executing these activities prior to running the upgrade:
• Program: SU24_AUTO_REPAIR – Repair Inconsistent data
• Program: SU25_INITIALIZE_TSTMP – Initialize Timestamps
• Transaction: SU25 – Step 3 - export and create backup
• Transaction: PFCG – read old status and merge with new data
• Transaction: PFCG – create backup transport and export

After upgrading plan for executing these activities:

• Review SAP Note 440231 - SU25 | FAQ: Upgrade postprocessing for Profile Generator
• Transaction: SU25 – 2a, 2b - Postprocessing settings
• Transaction: SU25 – 2d, 2c - Postprocessing settings, comparison of transactions, roles
• Transaction SUPC – regenerate authorization profiles of SAP Business Roles
• Transport customer tables

Public 40/122
These steps ensure consistency for your authorization objects and will help correctly activating new apps
when executing the SAP Fiori rapid activation or content activation for (custom) business roles task lists.

2.5.10. Operating environment impacts

There are differences to be considered for operating environments for business users, administrators,
support teams and developers.

2.5.10.1. Operating environment for business users

Always check the following operating environment pre-requisites for all business user operating
environments:
• Supported web browsers and related versions
• Supported device operating system and related versions
• Supported versions of connected physical hardware (such as printers and barcode scanners)

Refer to SAP Note 1672817 Browser: Microsoft Legacy Edge and Internet Explorer Support Policy Note

Important: SAP FES 2020 is the last SAP Fiori FES version to support Internet Explorer. Refer to
Internet Explorer 11 will no longer be supported by various SAP UI technologies in newer releases.

To find supported browsers, OS versions, etc., refer to the SAP Product Availability Matrix (PAM) for
your SAP S/4HANA target release. Check your target release for the following software components:
• SAP S/4HANA release
• SAP FIORI FOR SAP S/4HANA target release
• SAP FIORI FRONT-END SERVER target release
E.g. for SAP S/4HANA 2022, within the Product Availability Matrix tool:

1. Navigate to SAP FIORI FOR SAP S/4HANA 2022 (Note: This is the main software component for
SAP Fiori apps delivered with SAP S/4HANA)
2. Then go to Essential Information and open the Essential Information document
3. On the Table of Content Links, follow the Browser Support link to go to the related information for
this release
You can also find the related SAP Fiori FES release for your SAP S/4HANA release in the Product
Availability Matrix, e.g.:

1. Navigate to the related Frontend server release for SAP S/4HANA 2022 which is SAP FIORI FES
2022 FOR SAP S/4HANA
2. Then go to section Related Links and use the link Web Browser information

2.5.10.2. Operating environment for administrators and support teams

Like other business users, administrators require access to the SAP Fiori launchpad to launch relevant
SAP Fiori apps of the SAP Business Role Administrator, e.g. Extensibility Inventory app, Application
jobs scheduling app, etc.

This is particularly true for Launchpad content and layout administration tools, such as SAP Fiori apps
F4384 Manage Launchpad Spaces and F4512 Manage Launchpad Pages. The SAP Fiori administration

Public 41/122
role is generated via the task list SAP_FIORI_FOUNDATION_S4 for this purpose. By default, the
generated role name is Z_FIORI_FOUNDATION_ADMIN.

Figure 24 - Launchpad content and layout tools delivered as part of the Fiori Foundation Administrator role with the main launchpad
content and layout tools highlighted

However, it is expected that administrators and support teams will continue to perform many activities via
SAP GUI. These can be launched from the SAP Fiori launchpad, from SAP Business Client, or accessed
directly via SAP GUI.

For administrators and other users accessing SAP S/4HANA directly via SAP GUI, refer to:
SAP Note 66971 Supported SAP GUI platforms

2.5.10.3. Operating environment for developers

Most development tools and services are made available on the SAP Business Technology Platform. They
are the recommended and most efficient development tooling for:

• Developer-led extensions of SAP Fiori apps

• Custom-built apps – including those based on SAP Fiori elements and freestyle apps based on the
SAPUI5 and SAP Fiori design guidelines
• Integration of intelligent technologies services into apps, e.g. SAP intelligent Robotic Process
Automation

Developers are strongly recommended to keep up to date with the latest best practice advice regarding
tools, coding and environments, e.g.:
• via https://developers.sap.com
• via SAPUI5 Software Development Kit (SDK) at https://ui5.sap.com
• via SAP Community topic pages, e.g. https://community.sap.com/topics/fiori and
https://community.sap.com/topics/business-application-studio

For example, SAP Business Application Studio and the SAP Fiori Tools extension for SAP Business
Application Studio were released in 2020. These are considered the next generation tools compared to
SAP Web IDE. These tools come with improved options for building custom apps and extending
delivered apps. If you are currently using the SAP Web IDE, you are advised to evaluate these new tools
and decide the appropriate timing for moving to the new tools.

The Fiori Tools extension is the recommended tool for creating apps using the SAP Fiori elements
floorplans.

Public 42/122
For offline development, Visual Studio Code is the equivalent of SAP Business Application Studio. SAP
Fiori Tools extension can also be used with a local installation of Visual Studio Code (aka VSCode).

Refer to:
• SAP Community topic SAP Business Application Studio
• SAP Community topic SAP Fiori
• SAP Community topic SAP Fiori elements
• SAP Community topic ABAP Development
• Blog post SAP Fiori Tools is generally available. Increase the efficiency of developing SAP Fiori
elements apps
• SAP Developers Tutorials for SAP Fiori Tools
• SAP Developers Tutorial Set up SAP Fiori Tools in your Development Environment (VSCode)
• Blog post Adaptation Project – your one stop tool for extending SAPUI5 applications

Figure 25 - Simplified overview of SAP Fiori development tools and technologies (source: openSAP)

Current minimum tools & services requirements are:

• Developer-led extensions of SAP Fiori apps and custom Fiori apps will require:
o SAP Business Application Studio on SAP Business Technology Platform (Cloud Foundry)
or
o SAP Web IDE (Full Stack edition) on SAP Business Technology Platform (Neo)
Additional tools & services requirements may be desirable depending on your scope and development
preferences, e.g.:
• DevOps tooling for custom SAP Fiori apps
o For example, if you are deploying apps side by side in the SAP Business Technology
Platform, you may want to consider Continuous Integration and Delivery solutions for
SAP Business Technology Platform

Public 43/122
 • SAP mobile services on SAP Business Technology Platform
o For example, for creating offline apps or adding additional native app features such as
GPS, Voice Recording, etc.
Refer to:
• Continuous Integration and Delivery Best Practices guide in the SAP Help Portal
• SAP Solutions for Continuous Integration and Delivery in the SAP Help Portal
• Blog post Meet our new continuous integration and delivery solution
Important: While there are some alternatives development environments possible for custom-built apps,
these do not provide the wide range of accelerators for efficient development. Similarly, developer-led
extensions of SAP Fiori apps are not able to be generated outside of SAP Business Technology Platform
tools such as SAP Business Application Studio or SAP Web IDE.

Some on-premise tools are also required to complete your development environment. These tools and
more can be downloaded from the SAP Development Tools site https://tools.hana.ondemand.com where
you will find further details and instructions. The primary tools are:

• To connect your SAP S/4HANA On-Premise or SAP S/4HANA Cloud, private edition
development environment with the SAP Business Technology Platform, the SAP Cloud
Connector must be installed or upgraded.
o The SAP Cloud Connector acts as a VPN tunnel to your SAP S/4HANA On-Premise
system or SAP S/4HANA Cloud, private edition.
• For ABAP development, the Integrated Development Environment (IDE) is ABAP Development
Tools for Eclipse. This must also be installed/upgraded on developer PCs.

2.5.11. Custom code impacts

Custom code impacts may require rework due to:

• Changes in the ABAP Foundation capabilities of your SAP S/4HANA system

• Delta simplifications, e.g. changes in the underlying database model and CDS Views
• Successor SAP Fiori apps providing new or changed extension options
• Evolution of the recommended ABAP Programming Model

Important: For those coming from SAP S/4HANA 1511, 1610, or 1709, the ABAP Foundation of SAP
S/4HANA was changed from SAP NetWeaver to ABAP Platform. From SAP S/4HANA 1809, the ABAP
Platform is shipped with your SAP S/4HANA system and is not provided standalone.

Refer to:
• ABAP Platform in the SAP Help Portal
• What’s New Viewer for the ABAP Platform
• Blog post ABAP Platform for SAP S/4HANA 1909

Evolution of the ABAP Programming Model has progressed across SAP S/4HANA releases. With SAP
S/4HANA 1909, the unmanaged scenario of the ABAP RESTful Programming Model was introduced.
With SAP S/4HANA 2020, further scenarios of the ABAP RESTful Programming Model were
introduced.

Public 44/122
In SAP S/4HANA 2020 and higher releases, ABAP RESTful Programming Model is the current best
practice for creating custom apps on-stack. Where custom code is currently based on earlier programming
models and requires significant revision, consider moving to the ABAP RESTful Programming Model.
Earlier programming models are still supported but will not be further improved.

Figure 26 - Evolution of ABAP Programming Model

Refer to:
• ABAP RESTful Programming Model
• SAP Community topic ABAP Development
• Blog post Evolution of the ABAP Programming Model
• Blog post Getting Started with the ABAP RESTful Application Programming Model
• TechEd 2019 Replay CAA103 Get the Big Picture of the ABAP RESTful Programming Model
• TechEd 2020 Replay Major Updates on ABAP RESTful Application Programming Model
[DEV102]

2.5.12. Upgrading custom ABAP code

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 to your target release. The app is part of SAP Business Role Project Manager – IT.

Alternatively, you can use the ABAP Test Cockpit as described in the Custom Code Migration guide to
check your custom code against the SAP S/4HANA simplifications of your SAP S/4HANA target release.
Running the tool will give a results list of instances where your custom code does not comply with the
scope and data structure of your SAP S/4HANA target release.

You must resolve any mandatory non-compliance items. You may optionally resolve other non-compliant
items, e.g. to improve performance by removing the use of Compatibility Views.

Public 45/122
Refer to:
• Blog post Custom code analysis for SAP S/4HANA with SAP Fiori App Custom Code Migration
• SAP Note 2190420 - SAP S/4HANA: Recommendations for adaption of customer specific code
• SAP Note 2241080 - SAP S/4HANA: Content for checking customer specific code

2.5.13. Upgrading custom SAP Fiori apps

When upgrading from SAP S/4HANA 1511 to any higher SAP S/4HANA release, this is also an upgrade
from the original SAP Fiori design to SAP Fiori 2.0 or SAP Fiori 3 design. This means that there are
some additional checks to be performed. Find more information in the guide Welcome to SAP Fiori 2.0
pack.

When upgrading from SAP S/4HANA 1610, 1709, or 1809 to SAP S/4HANA release 1909 or higher, it is
an upgrade from SAP Fiori 2.0 design to SAP Fiori 3 design. This is an evolution of the SAP Fiori design
and typically does not require any rework of custom-built apps, provided current SAP Fiori 2 best
practice recommendations were followed during the development.

For all SAP S/4HANA releases you will need to reference the SAPUI5 SDK to review the advice on
upgrading from your current to your target SAPUI5 version. Refer to SAP Note 2217489 - Maintenance
and Update Strategy for SAP Fiori Front-End Server for a central table mapping of SAP Fiori FES to
SAPUI5 versions. You will need to:

• Check for deprecated SAPUI5 themes, libraries, and controls

• Check for deprecated APIs
Where you need to replace deprecated controls, you should also review current best practices and
recommendations for your target SAPUI5 version in the SAP Fiori design guidelines.
To identify required and recommended changes directly in your code you can use the tools:
• Support Assistant
• UI5 Migration Tool

To minimize custom code remediation in future upgrades, review these best practices when building
SAPUI5 apps:

• Consider migrating freestyle apps to SAP Fiori elements where possible

o SAP Fiori elements are automatically updated on upgrade to your target SAPUI5 version
o Review the SAP Fiori element feature map for your target SAPUI5 version
• Review the Best Practices for App Developers in the SAPUI5 SDK
• Blog post Performance Checklist for UI5 Apps
• Blog post Best practices for async loading in UI5
• Blog post UI5 Tooling: a modern development experience for UI5!
• OPENUI5 Development Conventions and Guidelines
• Ruleset for ESLint Code Checks for SAPUI5

Refer to:
• openSAP course Evolved Web Apps with SAPUI5
• SAP Community topic Fiori elements
• Blog post 3 ways to speed up development with SAP Fiori elements
• Blog post When to use SAP Fiori elements to reduce development time and costs

Public 46/122
 2.5.13.1. Deprecated SAPUI5 themes, libraries, and controls

Deprecated SAPUI5 controls can be found in the SAPUI5 Software Development Kit. Each deprecated
element typically provides recommendations for alternatives. Within the Documentation section, search
for the term “deprecated” to find the section Deprecated Themes and Libraries.

Figure 27 - SAPUI5 Software Development Kit section Deprecated Themes and Libraries

Within the API Reference, select the checkbox “include deprecated controls”, and selected deprecated
APIs to find the index of deprecated APIs. The list of all deprecated APIs as of each SAPUI5 version is
displayed.

Figure 28 - SAPUI5 Software Development Kit - section Index of Deprecated APIs

Important: Tools such as the SAP Business Application Studio typically display warning messages for
deprecated elements.

Some customers have also developed ways of assessing deprecated elements in their apps, for example,
the chrome extension detailed in Detecting and Updating Deprecated UI5 controls.

2.5.13.2. Using the Support Assistant to identify required changes

The Support Assistant check apps are built according to the current SAPUI5 best practices and guidelines.
You can use Support Assistant to identify the required changes in your custom SAP Fiori (SAPUI5) apps.

Public 47/122
Start the Support Assistant from the Technical Information Dialog by using the following keyboard
combination [CTRL + SHIFT + ALT + P], then Select Activate Support Assistant.

Figure 29 - Example of Support Assistant identified issues for remediating custom SAP Fiori (SAPUI5) apps

Refer to:
• Using the Support Assistant in the SAPUI5 SDK

2.5.13.3. Using the Migration Tool to adapt custom code to higher SAPUI5 releases

The UI5 migration tool is a node.js-based offering that supports you in the migration of UI5 projects by
adapting the code to fit newer UI5 framework versions. The UI5 migration tool performs source code
replacements and optimizations to reduce or get rid of deprecated APIs.

Migration consists of an analysis part and a code modification part. The tool comes with a comprehensive
set of command-line options to configure the steps to analyze or to migrate specifically for your UI5
project.

Refer to:
• UI5 Migration tool on Github

2.5.14. Integration

In a technical upgrade, most integration is covered by regression testing.

You must also check any integration to analytics platforms, such as SAP BW or SAP BW/4HANA.
For BW Extractors refer to SAP Note 2500202 S4TWL - BW Extractors in SAP S/4HANA

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. For example, from SAP S/4HANA
1809, integration to SAP Ariba requires a change to the Content Integration Gateway (CIG) integration
approach.

For changes in integration of SAP cloud solutions refer to the appropriate references, which can be found
on the Integrate tab of the SAP S/4HANA product page in the SAP Help Portal.

Public 48/122
Figure 30 - Integrate tab of the SAP S/4HANA product page in the SAP Help Portal

For integration to other solutions check:

• Simplification Item Catalog for any deprecated BAPIs or APIs
• SAP API hub https://api.sap.com for advice regarding APIs for SAP S/4HANA

2.5.15. Move to Hyperscaler

As part of your upgrade, you might have taken the decision to move your SAP S/4HANA into a
Hyperscaler and run it as a hosted cloud system. You can find more information about this option in SAP
S/4HANA Deployment on Hyperscalers and in our openSAP course SAP on Hyperscalers – Strategy,
Architecture and Deployment.

Figure 31 - Running SAP S/4HANA on a hyperscaler

You should plan for the following activities:

Public 49/122
 1. Review your current operating system and check if you need to change to another supported OS
available on your hyperscaler. Refer to SAP Note 2620910 for Recommended Application Server
Platforms.
2. For landscape planning use standard reference architectures as offered by the hyperscaler vendors
including high availability (HA) and disaster recovery. These are available with standard
automation scripts for creation of instances to reduce cost. High availability can be configured
within an availability zone, across availability zones, or in a combination of both. HA
configuration and the choice entirely depends on availability requirements and how much your
organization can afford in terms of cost.
3. Evaluate hardware requirements. For sizing you can scale up or scale out all your servers.
Therefore, it becomes easier to initially use lower sized application and database server instances
to save cost.
4. Please ensure a backup solution is selected and in place before the upgrade. You may find it
convenient to change to a cloud-native backup service instead of third-party tools.
5. Plan the landscape rollout strategy using either horizontal or vertical strategy of the hyperscaler
rollout. In a horizontal strategy you would move sandboxes first to the hyperscaler, then the non-
production systems and finally the production system. In a vertical strategy all instances of non-
critical systems would directly be moved to the hyperscaler.
6. Evaluate deployment options for key components like application central services, Fiori front-end
server, SAP Web dispatcher, SAP Cloud Connector and agents.

Migration approach
Select the Migration approach based on your cutover window, migration link bandwidth, platform change
needed, database-to-database replication capability and file synchronization offered by the hyperscaler.
Feasibility will depend on your contract with the hyperscaler vendor and/or feasible target OS.

The options below may be considered:

1) Use the Software Provisioning Manager (SWPM) tool to first “lift and shift” without upgrading
SAP S/4HANA. Evaluate both the options of moving the database backup or database export to
files. Database-to-database replication capability should also be considered to reduce downtime.
You can then use the Software Update Manager (SUM) tool to upgrade to the target release
version.
2) Use the Software Update Manager (SUM) tool to upgrade the SAP S/4HANA system to the target
release and then move to the hyperscaler using the Software Provisioning Manager (SWPM) tool
to “lift and shift”.

2.5.16. Leveraging CQC Support Services (SAP Enterprise Support customers)

If you have an SAP Enterprise Support maintenance contract for your SAP S/4HANA system, it is
recommended that you schedule the following SAP Support services to perform some quality checks
specific to Upgrades:
• From the beginning of the project to the deploy phase:
o CQC for Transformation Assessment: Make sure the team is aware of the latest tools,
services, enablement materials and best practices through two questionnaire-based checks
• During the deploy phase, to analyze system configuration and tuning:
• CQC for Upgrade if the SAP S/4HANA system is on-premise or on hyperscaler. It consists of:
• An Analysis Session, which includes parameter setting checks and sizing (delivered 5-6
weeks before upgrade Go-Live)
• A Verification session, which includes parameter setting checks and performance
analysis (delivered 6 weeks after Go Live)

Public 50/122
 • CQC for Private Cloud go-live, if the SAP S/4HANA system is a SAP S/4HANA Cloud,
private edition. It consists of:
• An Analysis Session, which includes parameter setting checks and sizing (delivered 5-6
weeks before upgrade Go-Live)
• A Verification session, which includes parameter setting checks and performance
analysis (delivered 6 weeks after Go Live)
• CQC Going Live Support
• Monitors your system on the first 3-5 productive days after Go-Live to detect issues
before, or as soon as they arise

In case of an SAP Fiori FES standalone deployment both services can and should be booked for the SAP
S/4HANA and the SAP Fiori FESs.

In case of moving from hub/standalone to embedded deployment both services should be booked for the
SAP S/4HANA system only. You should mention that there will be increased workload due to the
embedded SAP Fiori FES.

Optionally, you could book the following additional services to improve system performance and
minimize potential risks prior to the upgrade:

• CQC Business Process Performance Optimization

• In case of specific performance issues on a process, SAP Fiori App, or Transaction,
regardless of the upgrade
• CQC Business Process Improvement
• Understand business issues in your critical processes before upgrade, and try to implement
solutions during your upgrade project
• CQC Security Optimization Service
• Improve security settings of your system before or after the upgrade

You can book these services by creating an incident under component SV-BO-REQ (SAP Note 1296527)
or contacting the SAP Enterprise Support Advisory team via our Customer Interaction Center (CIC).

2.5.17. Leveraging support services (standard support)

If you do not have an SAP Enterprise Support maintenance contract for your SAP S/4HANA system, it is
recommended that you schedule the following SAP Support services to perform some quality checks
specific to Upgrades. It is recommended to request the following services:
• A GoingLive Upgrade Check
• In case of vital alerts reported by SAP EarlyWatch® Alert, up to two (2) SAP EarlyWatch®
Checks may be performed per calendar year for a production system if required

Prior to ordering the services, it is recommended to read the standard support scope description.

2.5.18. Leveraging support services (SAP Product Support for Large Enterprises)

If you have a Product Support for Large Enterprise (PSLE) contract, it is recommended to reach out to
your SAP contact to discuss which services could be planned for your project.

Prior to ordering the services, it is recommended to read the SAP Product Support for Large Enterprises
scope description and the SAP Product Support for Large Enterprises web page.

Public 51/122
 2.5.19. SAP Enterprise Support value map

SAP Enterprise Support value map for SAP S/4HANA offers a one-stop shop for prescriptive guidance,
interactive learning, and social collaboration, covering each phase of an SAP S/4HANA project.

Prescriptive content within the “Run Learning Journey” available in the value map includes a range of
meet-the-expert webcasts, blog posts, and best practices documentation relevant for SAP S/4HANA
upgrade. We have also set out remote services (availability depending on your SAP maintenance
agreement) that will help to safeguard your upgrade project from potential showstoppers. If you have
questions about any aspect of your SAP S/4HANA upgrade project, you can ask them in the value map.

Joining SAP Enterprise Support Value Maps:

• If you are an SAP Enterprise Support, SAP Enterprise Support Cloud Edition or SAP Product
Support for Large Enterprises (PSLE) customer, then value map access is already included in
your maintenance contract.
• Read more about SAP Enterprise Support value maps and sign up at SAP Enterprise Support
Value Maps.
• Please note that before you can access the value map, a one-time registration in SAP Learning
Hub, edition for SAP Enterprise Support, is required. A detailed step-by step guide to
registration can be found at SAP Learning Hub, edition for SAP Enterprise Support.
• If you have any questions, please contact [email protected].

2.6. Improving your User Experience

User Experience is the corner stone of user productivity, satisfaction and adoption. User Experience is
arguably the most important factor in realizing customer value from the Intelligent Enterprise, including
from SAP S/4HANA. Business outcomes can only be achieved when business users adopt to the new
solution. The faster the user adoption, the more swiftly benefits can be achieved.

SAP Fiori is the way business users consume SAP S/4HANA innovations including:

• UX on multiple web browsers and mobile devices

• Embedded analytics
• New business processes only on SAP Fiori – such as Group Reporting, Central Procurement,
Predictive MRP, etc.
• Intelligent Technologies – such as Situation Handling, Machine Learning, and Robotic Process
Automation, and chatbots.

Your user experience drives solution adoption and changes in user behavior towards achieving strategic
and tactical business outcomes.

Public 52/122
Figure 32 - SAP Fiori is the way business users consume SAP S/4HANA innovations – summary of the content provided with SAP S/4HANA
including more than 2.8K SAP Fiori apps

Your SAP S/4HANA upgrade an important time to review your UX Strategy. Reviewing your UX
strategy helps you avoid surprises, take advantage of new SAP-delivered business value, and bring more
value to your users. Such benefits can be major or incremental, for example:

• Major: as part of a functional upgrade, you may introduce new SAP Fiori apps.
o With each SAP S/4HANA release, SAP typically delivers 300-400 new SAP Fiori apps
plus new SAP Fiori features.

• Incremental: as part of a technical upgrade, you introduce new SAP Fiori features in the
launchpad, and in commonly used SAP Fiori floorplans
o For example, in SAP S/4HANA 1909, many floorplans automatically added an Export to
spreadsheet feature; in SAP S/4HANA 2020, the ability to save multiple value sets of
User Defaults was added to the Launchpad > User Actions > Settings dialog; in SAP
S/4HANA 2022, many floorplans added an Export to PDF feature.

2.6.1. Review your UX strategy

Upgrading provides significant improvements in SAP S/4HANA User Experience in:
• Increased SAP Fiori coverage
o Each new release of SAP S/4HANA has typically introduced approximately 350-400 new
SAP Fiori apps
o Improvements in existing apps that cover new use cases
• New SAP Fiori features
o New launchpad options and new in-built features in floorplans
o For example “export to spreadsheet” was added to many SAP Fiori elements apps in SAP
S/4HANA 1909
• New classic User Interface (UI) capabilities when launched from SAP Fiori
o For example, touch-enabled user interfaces for Web Dynpro ABAP applications and SAP
GUI for HTML transactions

Public 53/122
 • Performance improvements in both SAP Fiori and classic user interface technologies.
There are always significant UI design and performance improvements, new features, and apps (and often
lifting of previous restrictions) that the upgraded version of SAP Fiori brings along with the upgrade of
SAP S/4HANA. Refer to this blog post that explains SAP Fiori upgrade scenarios in detail – How and
Why to Upgrade SAP Fiori for your SAP S/4HANA solution.
You can get some useful starting points for discussions with business stakeholders in the SAP Fiori
lighthouse scenarios (regularly updated), which highlights apps with the best new business value for
specific lines of business.
You can find the list of all SAP Fiori for SAP S/4HANA apps in the SAP Fiori apps reference library.

For your UX strategy, whether you are doing a Technical Upgrade or a Functional Upgrade, review as a
minimum:
• Changes in supported operating systems and web browsers for desktop and mobile devices
• Improvements and new launchpad features
• New performance improvement options, e.g. for your Fiori launchpad and for the Gateway
component on which it runs
• Improvements in major SAP Fiori floorplans (covered in section 2.7.2 Changed Apps)
o Especially the most common: SAP Fiori elements and SAP Smart Business Framework –
refer to section 2.7.2 Changed Apps
• Improvements in support for classic UI technologies and their deployment options
• New/improved options for context-sensitive help, e.g. updates to the User Assistant
• New/improved tools for managing launchpad content and layout
• New/improved support tools

For functional upgrades you should also review:

• New/improved intelligent use cases and capabilities
• New/improved in-app extension capabilities within your target SAP S/4HANA release
• New/improved side-by-side extension capabilities in the SAP Business Technology Platform, e.g.
SAP Launchpad service.

Refer to:
• PAM for your target release, e.g. SAP FIORI FOR SAP S/4HANA 2020 > Essential Information –
for supported browsers and operating systems
• Fiori Launchpad guide for your target SAP S/4HANA release
• What’s New Viewer for the ABAP Platform - this includes What’s New for the Fiori launchpad
• SAP Note 2217489 - Maintenance and Update Strategy for SAP Fiori Front-End Server – this
contains a central table mapping of SAP Fiori FES to SAPUI5 versions

2.7. User Experience impacts

If you are using SAP Fiori apps in your SAP S/4HANA source system, as a minimum you will need to
assess:
• Deleted and deprecated SAP Fiori apps
• Successor apps for existing SAP Fiori apps you have deployed
• Changes to existing SAP Fiori apps that you have deployed
• Changes to classic User Interface capabilities
• Deleted and deprecated classic UIs
• Change to catalog assignment of SAP delivered SAP Fiori apps and classic UIs

Public 54/122
 • Changes in Accessibility
If you are using a Functional Upgrade approach, you will also need to assess:

• New apps available in your target SAP S/4HANA release and FPS
• New SAP Fiori launchpad features
• Essential business roles required to configure/adapt/extend SAP Fiori
A detailed summary of app changes and recommendations per app can be found in SAP Note
2881803 - FAQ: S/4HANA Fiori Best Practices - Collective Note

2.7.1. Obsolete, deprecated, and superseded apps

Obsolete (i.e. deleted) and deprecated SAP Fiori apps can be identified in the SAP Fiori apps reference
library. You must replace obsolete and deprecated apps with an alternative. The SAP Fiori apps reference
library will also present you with their successors. You are recommended to use the tool SAP Fiori
Upgrade Impact Analysis to identify obsolete, deprecated, and superseded apps.

Essentially:
• Obsolete apps are deleted and must be replaced
• Deprecated apps still exist but are no longer supported and should be replaced
• Superseded apps are still available, however new capabilities, improvements and new features will
only be provided in the successor app.

You should aim to replace predecessor apps with their recommended successors, where possible.

In 2022 SAP has introduced the new SAP Fiori Upgrade Impact Analysis tool, which is integrated into
the SAP Fiori apps reference library and will help you identify easily SAP Fiori apps that are deprecated,
have successors or are new in their target release.

You can learn more about the tool in the blog SAP Fiori for SAP S/4HANA – Upgrade Impact Analysis.
The tool is accessed from the home page of the SAP Fiori apps reference library.

Public 55/122
Figure 33 - SAP Fiori Upgrade Impact Analysis

The tool provides a breakdown of obsolete, deprecated, and superseded SAP Fiori apps and classic UIs
that must be addressed as part of your upgrade. You must make decisions for these apps/UIs on whether
to replace now or replace later. Suitable successor apps/UIs are indicated in the results.

The analysis results also confirms which apps/UIs that are still available. Available apps typically require
limited regression testing. Unknown apps are typically custom apps/UIs that must be reviewed for
impacts and regression tested.

Public 56/122
Figure 34 - Example of Upgrade Impact Analysis results highlighting obsolete apps tab

It is also possible to perform a manual check following the subsequent steps in the SAP Fiori apps
reference library. Refer to:
• openSAP microlearning video Finding available SAP Fiori apps in the SAP S/4HANA playlist,
Lines of Business Cross-Topics

Successor apps are typically introduced as a new app with a new app id. The relationship between
predecessor and successor apps is held in the SAP Fiori apps reference library. For a specific app, you can
find Predecessor or Successor apps section in the Related Apps tab, for example:

SAP Fiori app F0842 Manage Purchase Orders shows the following subsection on the Related Apps tab

Figure 35 - Successor apps subsection of Product Features listing and linking to the successor apps

Similarly, SAP Fiori app F0842A Manage Purchase Orders (Version 2) shows the following subsection
on the Related Apps tab:

Figure 36 - Predecessor apps subsection of the Product Features tab listing and linking to predecessor apps

2.7.2. Changed apps

Public 57/122
Major functional changes to apps are typically listed in the SAP S/4HANA What’s New Viewer.

There can also be automatic changes to SAP Fiori apps due to improvements in the underlying SAPUI5
controls and SAP Fiori floorplans and frameworks, such as:
• SAP Fiori elements floorplans
• SAP Fiori Smart Business
These depend on your SAPUI5 version and changes can be found by examining SAPUI5 version
differences for your target SAPUI5 version in:
• SAP Fiori Design Guidelines – What’s New
• SAPUI5 Software Development Kit – What’s New in SAPUI5 and Change Log
• SAP Note 2217489 - Maintenance and Update Strategy for SAP Fiori Front-End Server – this
contains a central table mapping of SAP Fiori FES to SAPUI5 versions

2.7.3. Changes in classic user interface capabilities

Classic User Interfaces are existing SAP technologies that can be launched from the SAP Fiori launchpad.

Figure 37 - Classic UI technologies can be launched from the launchpad or from SAP Fiori apps.

From SAP S/4HANA 1511, SAP GUI transactions and ABAP Web Dynpro applications have been
supported as classic user interfaces. From SAP S/4HANA 1909, Web Client UIs are also supported as
classic user interfaces.

The full list of whitelisted SAP Fiori launchpad content can be found in the SAP Fiori apps reference
library using the main filter All Apps for SAP S/4HANA.

In preparation for upgrade, review changes to classic user interface capabilities, limitations, and
restrictions. These are contained in release notes for the related Kernel and Unified Rendering.

For example, there was a major change as of SAP S/4HANA 1909 to provide mobile and touch capability
of classic UIs. Refer to SAP Note 2700517 - Mobile device support for Unified Rendering based
frameworks: Web Dynpro ABAP and SAP GUI for HTML.

Public 58/122
Related capabilities for SAP Screen Personas should also be checked, as SAP Screen Personas is the
recommended tooling for adjusting the look and feel classic user interfaces.

Theming restrictions should also be reviewed, regardless of whether you use standard or custom themes.
Theming improvements are usually applied to SAP Fiori in advance of classic user interfaces.

Refer to:
• SAP Note 2658822 - Release notes for SAP GUI for HTML (short WEBGUI)
• SAP Note 314568 - SAP GUI for HTML functionality / Limitations / Sp. Behaviour
• SAP Note 1927011 - Restrictions to Unified Rendering
• SAP Note 2050838 - SAP Screen Personas - Limitations / Restrictions / Behavior
• SAP Note 2814266 - Restrictions of SAP Fiori 3 visual theme for classic applications

2.7.4. Deleted and deprecated classic user interfaces

Deleted and deprecated classic UIs are typically listed in the SAP S/4HANA What’s New Viewer.
They can also be listed in the ABAP blocklist monitor, e.g. table SBLM_BLACKLIST.

Refer to the SAP Fiori Upgrade Impact Analysis tool described in chapter 2.7.1 as well.

For more information refer to blog post SAP Fiori for SAP S/4HANA - Identifying classic user interfaces
available for use with SAP S/4HANA.

2.7.5. Changes in catalog assignments

Changes in catalog assignment of SAP delivered apps can impact your existing custom business catalogs.
These changes can result from:

• New or deprecated SAP Business Roles

• New or deprecated business catalogs or technical catalogs
• New or deprecated content in business catalogs or technical catalogs
• New navigation capabilities in SAP Fiori, e.g. inclusion of SmartLink dialogs that impact the
display and selection of related apps
Recommended actions for upgrade:

1. Review best practices and tools for launchpad content creation and assignment for the target
release. Consider the impact of changes on your current catalog design
a. The SAP Fiori apps reference library can be used to compare the catalog assignment of the
source vs. target release.
2. Before upgrading, check for references to SAP technical catalogs or business catalogs in custom
business roles to avoid changes after upgrade.
a. Upgrade in a sandbox system aids comparison of before/after catalog changes
b. Consider migrating to best practice approach of copying SAP Business Roles to custom
business roles to better manage the pace of change

3. Extract all needed and active ICF nodes for your custom roles (e.g. in the SAP Fiori launchpad
content manager) to be able to check, and if necessary, re-activate them afterwards.

Public 59/122
 a. You can use the program RS_ICF_SERV_ADMIN_TASKS to export the list of active
services from your source release
b. If necessary, a mass activation can be performed with the report
RS_ICF_SERV_MASS_PROCESSING.
c. Refer to SAP Note 1555208 - ICF services become inactive after upgrade or SP update for
more information.

Refer to:
• openSAP Microlearning video Refining Business Roles with SAP Fiori Launchpad Content
Manager
• SAP Note 2455198 - Business Catalog or Group Outdated in Fiori Launchpad Designer

2.7.6. Changes in accessibility features

Accessibility refers to the possibility for everyone, including and especially people with disabilities, to
access and use information and communication technology

Accessibility features available at the framework level relate to the target UI technology versions of your
SAP S/4HANA release.

For SAP Fiori, refer to Accessibility in SAP Fiori and select your target SAPUI5 version. For developers
creating custom apps refer to the SAPUI5 SDK documentation for your target SAPUI5 version,
particularly the sections:
• Essentials > Accessibility
• Developing Apps > Accessibility

For SAP GUI for HTML and ABAP Web Dynpro applications, accessibility is driven by the Unified
Rendering framework. Refer to SAP Note 2376128 - Accessibility with Unified Rendering based UI
technologies

For general advice on accessibility across SAP solutions, refer to SAP Note 1139953 - Requirements and
infrastructure for accessibility which includes guides for an administrators and users in the Attachments
section of the Note.

Refer to:
• Accessibility in SAP Fiori in the SAP Fiori Design Guidelines.
• SAP Note 2376128 - Accessibility with Unified Rendering based UI technologies
• openSAP microlearning Accessibility playlist

2.7.7. New apps

Even when planning a technical upgrade, it is useful to capture the delta of new SAP Fiori apps during
upgrade planning to motivate subsequent continuous improvement projects. For example, the list of new
apps available can be distributed to relevant business stakeholders to encourage forward planning to take
advantage of new opportunities provided by your SAP S/4HANA upgrade.

The delta of new apps between SAP S/4HANA releases can be found in the SAP Fiori apps reference
library. For more information refer to the blog post SAP Fiori for SAP S/4HANA – Finding the Delta of
New Apps between SAP S/4HANA Releases

Public 60/122
Important: You will usually also find many of the new apps mentioned in the SAP S/4HANA What’s
New Viewer.

Refer to:
• openSAP microlearning video Finding available SAP Fiori apps

2.7.8. New SAP Fiori launchpad and shared features

New features to extend your SAP Fiori apps and SAP Fiori launchpad are added with each release. New
features typically add functionality for business users, improve performance, and make supporting SAP
Fiori easier.

Key areas to review on upgrade are:

• New Fiori launchpad configuration parameters
• Changes in Best Practices for managing launchpad content and layout
• Changes tools for managing launchpad content and layout
• New support tooling
Special attention should be given to adjusting new launchpad configuration parameters that improve
performance and usability such as:

• HOMEPAGE_GROUPSELECTIONBAR_MODE (if still using Groups layout mode)

• NAVIGATION_WDA_INPLACE
• NAVIGATION_GUI_INPLACE
• NAVIGATION_GUI_STATEFUL_CONTAINER
• HOMEPAGE_BACKGROUNDSHAPES

Refer to:
• SAP Fiori launchpad guide section Launchpad Configuration Parameters for your SAP S/4HANA
release on the SAP Help Portal
• Blog post Recommendation for Structuring Roles, Spaces and Pages in the SAP Fiori Launchpad
Based on Common User Behaviors
• Blog post SAP Fiori for SAP S/4HANA – Overview of tools for maintaining custom launchpad
content and layout
• Blog post Check out the improvements in SAP Fiori launchpad content administration and
operations with SP01 of SAP Fiori front-end server 2020
• Blog post App Support for the SAP Fiori launchpad

2.7.9. Essential business roles required to administrate and extend SAP Fiori
There are a small set of business roles delivered with SAP Fiori for SAP S/4HANA that are considered
essential roles for all customers. They are considered essential because they contain SAP Fiori apps that
enable you to monitor, configure, adapt, and extend other SAP Fiori apps.
If not previously activated, you should ensure these business roles are activated when you upgrade.
If previously activated, you should reactivate these business roles.
You can use the Select Recommended Roles feature in the SAP_FIORI_CONTENT_ACTIVATION
(Rapid content activation) and SAP_FIORI_FCM_CONTENT_ACTIVATION (Content activation) to
pre-select these roles for activation.
The essential business roles are:

Public 61/122
 • Administrator SAP_BR_ADMINISTRATOR
o The Administrator role contains apps that enable you to add custom fields and logic, adjust
email & form templates, schedule jobs, monitor extensions made by key users, etc.
• Analytics Specialist SAP_BR_ANALYTICS_SPECIALIST
o The Analytics Specialist role contains apps to review CDS Views, adjust KPI thresholds,
and manage date functions for analytical apps such as Smart Business, Overview Pages,
and Analysis Path Framework.
o It also contains apps to create new custom analytical queries and Intelligent Scenario
Lifecycle Management for machine learning use cases.
• Business Process Specialist SAP_BR_BUSINESS_PROCESS_SPEC
o The Business Process Specialist role contains apps to manage teams and responsibilities
for flexible workflows.
• Configuration Expert – Business Process Configuration SAP_BR_BPC_EXPERT
o The Configuration Expert – Business Process Configuration role contains app to centrally
manage new processes and intelligent features such as Group Reporting, Central
Procurement, Advanced Compliance Reporting, flexible Workflows and Situation
Handling
o It also contains a number of mass processing apps for a variety of business objects such as
File Upload/Download, Data Replication, Hierarchy Maintenance, Catalog Item
Recommendations and Scheduling.
Refer to:
• Blog post SAP Fiori for SAP S/4HANA – Yes you need SAP Fiori to Configure, Adapt and
Extend SAP S/4HANA

2.7.10. Required adaptations to custom SAP Fiori Apps

In preparation for your SAP Fiori for SAP S/4HANA upgrade, you will need to review the status of your
current developments. This is required because you will be obtaining new features in the UI layer by either
the updated UI5 libraries, the updated UI components in the ABAP stack, or through the new features in
the ABAP layer, for example, programming model improvements or new features available for CDS View
development.

We recommend reviewing the following tasks to identify the possible adaptations to your custom
developments.

Identify the target SAPUI5 library version

Having selected your target SAP S/4HANA release, you must confirm the long-term maintenance version
of the SAPUI5 libraries (and the associated version of SAP_UI components) you will be using in your
target SAP S/4HANA release. The SAPUI5 version will have an impact on the features provided by these
libraries, and may impact the code remediations you might need to perform. Refer to:
• SAP_UI Support Packages
• SAPUI5 Versions Maintenance Status

Identify supported browsers, platforms, and reference devices

Public 62/122
With the use of updated SAPUI5 libraries, support for specific browsers, platforms and reference devices
may be dropped. Keep this in mind when you decide to use a certain product version and adjust or rebuild
your custom applications accordingly. Refer to:

• Browser and platform support Matrix

• Visual Degradations
• Product Availability Matrix
• Blog post Update: Future SAPUI5 versions will no longer support Microsoft’s legacy browsers

Removal of SAP Fiori Client from Public App stores

If you have developed custom applications leveraging the SAP Fiori Client to enhance the features provided
by your apps, for example, by adding barcode scanning capabilities, your custom applications must be
reviewed and redesigned considering new development approaches focused on the use of native browser
features or native developments for iOS or Android.

The SAP Fiori Client app was initially developed to help users run SAP Fiori web applications using their
mobile devices. With the considerable improvement of device browser capabilities, the need for the SAP
Fiori Client app has been significantly reduced. In addition, due to the increasing limitations of the
WebView component, applications such as the SAP Fiori Client that are built on top of it can no longer
provide an optimal user experience.

For these reasons, SAP will be removing the SAP Fiori Client app from the public app stores, with the
recommendation that end-users use their native browsers instead. Refer to:

• Removal of SAP Fiori Client from Public app stores

• SAP Fiori for IOS design
• SAP BTP SDK for iOS
• SAP Fiori for Android design
• SAP BTP SDK for Android

Consider moving to SAP Mobile Start instead.

Identify SAPUI5 library upgrade impacts in Custom Apps

As SAPUI5 evolves, multiple improvements are introduced, and specific APIs are deprecated. You can use
the UI5 Migration tool to perform source code replacements and optimizations to remove deprecated APIs.
Refer to:

• Blog Post UI5ers Buzz #45: UI5 Migration Tool

• Github Project UI5-migration

Identify Core Data Service updates and run remediations

In SAP S/4HANA, the source object for data extraction in most reports, transactions and SAP Fiori apps
are the Core Data Service (CDS) Views. CDS Views are also leveraged by the new programming models
in SAP S/4HANA. When new versions are released, improvements to these sources may require performing
minor adjustments in the custom objects you have built that consume these objects.

You can leverage the ABAP Test Cockpit (ATC) and the check variants in SAP S/4HANA to run checks
on your custom developments and custom CDS views. Refer to:
• Blog post Remote Code Analysis in ATC – One central check system for multiple systems on various
releases

Public 63/122
 • Blog post Semi-automatic custom code adaptation after SAP S/4HANA system conversion

To run ATC checks for custom CDS views, run the following steps:

1. Set up ATC
2. Create a copy of variant S4HANA_READINESS_<your_target_S/4HANA_version> via report
SYCM_SETUP_VARIANT_FOR_RELEASE
3. In transaction SCI and your custom check variant, activate all checks for CDS views and deactivate
all other checks
4. In ATC define Object Set (Z*, Y* packages) and run inspection
5. Analyse incidences and run manual remediations

Evolve your custom apps with the new programming models

Starting with SAP S/4HANA new programming models have been released for you to take advantage of
the new platform features. You should pay particular attention to the ABAP RESTful programming model
for releases SAP S/4HANA 2020 and higher, and ABAP Programming Model for Fiori for SAP S/4HANA
releases 1909 or lower. It is highly recommended you migrate your custom app developments to these new
models. See chapter 2.5.11 and refer to:

• openSAP course Evolved Web Apps with SAPUI5

• openSAP course Building Applications with SAP Cloud Application Programming Model
• openSAP course Building Apps with the ABAP RESTful Application Programming Model
• openSAP course SAP Fiori Overview: Design Develop and Deploy (Week 3)

Validate status of custom fields and custom logic added via key user extensibility tools
If you are performing an upgrade from recent SAP S/4HANA versions and have used SAP Fiori low
code/no code extensibility apps like Custom Fields and Logic, there are some recommendations you need
to be aware of to ensure a successful upgrade:

1. Ensure all custom fields are in active state – inactive objects will be flagged during SUM
execution.
2. Remove all custom fields or custom logic that are not active – most times these are test fields or
test scenarios ran by your team that you can get rid of prior to running the upgrade.
3. Keep control of the custom objects generated via extensibility tools by using the Extensibility
Inventory App.
4. Run transaction SCFD_FIELDVIEWER after and before the upgrade to ensure consistency of
custom fields. Note that via this transaction you may repair your custom fields after or before the
upgrade.
5. Any issue with objects generated via SAP Fiori extensibility tools should be reported via an SAP
incident to component BC-SRV-APS-EXT-FLD

Public 64/122
Figure 38 - Field Viewer showing the Check Fields feature

Upskill your team

Along with SAP S/4HANA, multiple development technologies and procedures have been delivered by
SAP either via On-Premise or Cloud solutions. Explore the deployment of these additional technologies
that help you cover extended business requirements, and intelligent automation features which bring you
new business opportunities and increased process efficiency. Refer to:

• openSAP course Delivering Value with Intelligent Innovations in SAP S/4HANA

• openSAP course Developing and Extending SAP Fiori Elements Apps

Figure 39 - Learning topics for extending or building SAP Fiori apps

Public 65/122
 2.8. Functional planning for the upgrade

With more and more solutions and functionalities being embedded and enhanced with each release of
SAP S/4HANA, an upgrade provides the option to activate and adopt such business functions for
customers who can benefit from them.
For example: The embedded SAP Transportation Management (TM) solution was made available in SAP
S/4HANA 1709 and enhanced in subsequent releases as explained in blog post SAP Transportation
Management with SAP S/4HANA 1709.
The integration of a new embedded product is described in the SAP Activate roadmap SAP S/4HANA
Upgrade and Product Integration (currently covering embedded SAP Transportation Management,
embedded Extended Warehouse Management, SAP S/4HANA Service, and embedded Production
Planning and Detailed Scheduling).

Refer to:
• openSAP microlearning video Finding delta simplifications between SAP S/4HANA releases in the
SAP S/4HANA playlist, Lines of Business Cross-Topics

Public 66/122
3. UPGRADE EXECUTION

After scoping your project, reviewing your strategy and deciding about change management scope, it is
time to execute the upgrade technically. There are several tools provided and required.

3.1. Technical tooling and process

3.1.1. General procedure

These are the EXPLORE, REALIZE and DEPLOY phases of your SAP S/4HANA Upgrade project. You
apply the upgrade steps to the following environments in your landscape:
• Development
• Quality Assurance
• Dress Rehearsal
• Pre-production (if it is planned/existing in the landscape)
• Production

Figure 40 - Roadmap for Functional Upgrade

3.2. Technical Upgrade Steps for your SAP S/4HANA target release
The recommendation is to start at least with a sandbox, before upgrading your development (DEV)
environment.
Upgrade steps will be repeated on each system, except for configuration and custom code which are
realized in Development and transported to the next tiers of the landscape. When you reach the
Development environment upgrade, you may consider switching to the latest release/Support Package of
the SUM software. The cutover plan and cookbook should be improved throughout each upgrade
exercise until it is finalized and ready for the dress rehearsal.

Public 67/122
Important: You can find the specific upgrade steps for your target SAP S/4HANA release in the section
Realizing the Upgrade in the Upgrade Guide for SAP S/4HANA for your SAP S/4HANA release.

Figure 41 - Upgrade to SAP S/4HANA sequence of activities (source: Upgrade Guide for SAP S/4HANA 1909)

3.2.1. Downtime optimization options

During the SAP S/4HANA system conversion, SAP ERP data models have been converted into the SAP
S/4HANA simplified data models. This also occurs for system upgrades within S/4HANA releases, even
though it is to a reduced extent.

These data conversions are performed by data conversion methods such as XPRAs, XCLAs or AIMs.
Some of these data conversion methods are processing potentially large amounts of master and/or
transactional data, requiring efficient resource usage to achieve minimal runtime.
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 - S/4HANA System Conversion / Upgrade:
Measures to reduce technical downtime.
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, where you are using a copy of production, the SUM logs should be stored
in a safe place, as these can be used to further investigate opportunities for downtime optimization. The
upgrade evaluation file (UPGANA.XML) is particularly important. At the end of each SUM run, the
upgrade statistics can be uploaded to SAP. The data is used to further optimize the runtimes of updates
and upgrades.
Also, the data will be visible in the newly launched Technical Downtime Optimization app as part of
the SAP ONE Support Launchpad. The app helps upgrade or conversion project members to meet tight
downtime requirements by providing the following:
• Easy to consume analytics
• Tailored downtime minimization advice
• A simulation from a continuously updated knowledge base that is managed by upgrade and
conversion experts

The app is available for customers free of charge in the SAP One Support Launchpad via the tile
Technical Downtime Optimization.

Refer to: SAP Note 2881515 - Introduction to the Technical Downtime Optimization App.

Public 68/122
 3.2.2. Downtime optimization approaches of Software Update Manager (SUM)

Performing an update or upgrade of SAP S/4HANA can be achieved using one of the following
approaches of Software Update Manager (SUM):
• 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.
o Refer to: SAP Note 1678565 - Prerequisites and restrictions of nZDM (near-Zero
Downtime Maintenance).
• Zero Downtime Option (ZDO): handling all update related changes in uptime.
o Refer to: SAP Note 2707731 - Prerequisites and restrictions of Zero Downtime Option of
SUM for SAP S/4HANA.

Both the standard approach as well as the near-Zero Downtime Maintenance (nZDM) contain major
improvements for minimizing the technical downtime. These approaches are generally available for all
customers.
However, neither standard nor near-Zero Downtime Maintenance offer the option to reduce the technical
outage down to zero. This can be achieved by the next level of downtime-optimization: Zero Downtime
Option of SUM.

The Zero Downtime Option of SUM is generally released for source release SAP S/4HANA 2020 and
higher.

Jump upgrades where you can skip interim releases are only possible with Zero Downtime Option of
SUM from source release SAP S/4HANA 2020 onwards.

Important: You should consider that the more you want to optimize the downtime, the more effort you
have in the project. The effort includes project planning effort, as well as testing effort which is higher in
case of zero downtime updates.

Figure 42 - High-level comparison of downtime optimization approaches of the Software Update Manager (SUM)

With nZDM, the technical downtime is already significantly reduced by moving the main import and
table conversion partly into uptime. Going beyond this to use ZDO, the technical downtime is replaced by
the so-called Uptime on Bridge.

Refer to:
• SAP Community blog post Leveraging Zero Downtime Option of SUM for SAP S/4HANA Support
Package Stack updates.

Public 69/122
 3.2.3. Silent Data Migration

When planning a release upgrade and executing Software Update Manager (SUM), often data migrations
are required due to changes in the data structures. These changes may occur while developing new
features or enabling more performant applications. Usually, such data migrations when carried out during
the upgrades, prolongs the downtime period since they are executed as part of the XPRAs execution
(technical phase name: XPRAS_AIMMRG).

To reduce the duration of the downtime in such a scenario, a new data conversion technology known as
Silent Data Migration (SDMI) has been introduced for target releases SAP S/4HANA 1909 or higher.

SDMI allows migrating application data during uptime, which means in that time you can use the system
productively. The migration to the new model happens after upgrade to the new release. Until the Silent
data migration has finished in the background, the application continues to work without impacting the
business processes. This approach requires the upgrade to follow release sequence step by step.
Important: No jump upgrade is allowed – i.e. an upgrade that skips a release - with ZDO. Jump
upgrades are possible with standard and nZDM.

For more details on the implementation and execution of SDMI approach, refer to the SAP Note 2907976
Silent Data Migration (SDMI) - FAQ and 2916801 - Silent Data Migration (SDMI) Configuration
Options.

Refer to:
• Blog post Silent Data Migration for S/4HANA 1909 Upgrade/Conversion
• Blog post Monitoring Silent Data Migration (SDM_MON) – S/4HANA 1909 upgrade/conversion

3.2.4. Patch strategy in general

You will need to apply the latest patches to the user interface technologies used throughout SAP
S/4HANA. These patches contain bug fixes and performance improvements. Applying these patches
avoids wasted effort encountering known issues that have already been resolved.
You should apply the latest patches immediately after upgrade, and prior to follow-on EXPLORE
and REALIZE activities such as fit-to-standard of successor apps.

Important: You should be prepared to apply patches later in your upgrade project, especially prior to
regression testing.

3.2.5. Patch strategy for SAP Fiori FES

Applying the latest SAP_UI component patch levels is essential for optimal performance and operation of
all SAP Fiori and Web Client UI screens, which are both based on SAPUI5 technology. These patches
update your SAPUI5 minor version to apply the latest bug fixes and optimizations, helping you avoid
rediscovering known issues that have already been resolved.

Refer to:
• SAP Note 2217489 Maintenance and Update Strategy for SAP Fiori Front-End Server
• openSAP microlearning video How to Patch your SAP Fiori (SAPUI5) Version and Why in the
SAP S/4HANA playlist, Lines of Business Cross-Topics

Public 70/122
 3.2.6. Patch strategy for SAP S/4HANA Server

Applying the latest Kernel and Unified Rendering patch levels is essential for optimal performance and
operation of all SAP GUI for HTML and Web Dynpro ABAP applications. Make sure these are patched
to the latest available patch for your target release.

Refer to:
• SAP Note 2658822 - Release notes for SAP GUI for HTML (short WEBGUI)
• SAP Note 2895568 Maintenance Strategy for Web Dynpro ABAP / Floorplan Manager
• SAP Note 2500800 - UR: General information about cumulative patches for Unified Rendering

If you are using SAP Business Client Launchpad Connection to access the SAP Fiori launchpad, refer to:
SAP Note 2302074 Maintenance strategy and deadlines for SAP Business Client / NWBC

3.3. Post-upgrade follow-up activities

Every upgrade requires certain application-specific activities to be executed after the upgrade.

Important: You can find the specific activities for your target SAP S/4HANA release in the section
Realizing the Upgrade in the Upgrade Guide for SAP S/4HANA for your SAP S/4HANA release.

3.3.1. Additional activities to be applied after upgrade

There may also be some additional release-specific activities and notes to be applied after upgrade. These
may be listed in SAP Notes for your SAP S/4HANA release.

For example, for SAP S/4HANA 2022 refer to:

• SAP Note 3226548 - SAP S/4HANA 2022 - application specific notes in system conversion /
release upgrade follow-on phase

3.3.2. Updating the Enterprise Search content

As one of the last steps during the upgrade the following Task Lists (STC01) needs to be executed to
ensure that the Enterprise Search content is updated with the correct information.

Note that these steps are essential when you are using classic searches, which are client-specific. Where
you are using CDS View searches, which are cross-client, they are not needed. You can use the SAP Fiori
app F3036 Manage Search Models to review and adjust the available CDS View search models. Classic
search models can be seen in transaction ESH_COCKPIT.

1. SAP_ESH_RESET - The task list is used to reset the Enterprise Search to the initial state in your
working client
2. SAP_ESH_INITIAL_SETUP_WRK_CLIENT – The task list is used to create your Search
Connectors for the newly deployed applications

Refer to:
• SAP Note 2626143 - How to execute SAP_ESH_RESET
• SAP Note 2626107 - How to execute task list SAP_ESH_INITIAL_SETUP_WRK_CLIENT
• Blog post SAP Fiori for SAP S/4HANA –Limit Search Object Access in Fiori Launchpad made
easier

Public 71/122
 • Video Creating custom CDS Search models in S/4HANA

3.4. User Experience post-upgrade activities

As you are introducing a new version of SAP S/4HANA along with new SAP Fiori new components,
features and capabilities on the UX level and the technical level (in the ABAP stack), you need to plan for
specific tasks to ensure all SAP Fiori components behave correctly in your new SAP S/4HANA version.

There are certain upgrade tasks that are important and ensure object consistency within SAP Fiori. During
an upgrade, you must pay particular attention to the following activities:

1. Run report: RUTDDLSACT

2. Run report: RS_ICF_SERV_MASS_PROCESSING
3. Run reports: /UI2/GET_APP_DESCR_REMOTE_ALL and
/UI2/GET_APP_DESCR_REMOTE_DEV
a. Note that these reports are essential for a standalone Fiori Frontend Server (FES). The
need for these reports is greatly reduced in embedded environment.
4. Run report: /UI2/DELETE_CACHE_AFTER_IMP
5. Run report: /UI5/APP_INDEX_CALCULATE
6. Run report: /UI2/INVALIDATE_CLIENT_CACHES
7. Run report: /UI2/INVALIDATE_GLOBAL_CACHES
8. Regenerate custom themes in SAP Fiori Theme Designer
9. Ensure end-users clear browser cache

Depending on your target SAP S/4HANA release, there can be more steps required to ensure the correct
execution of SAP Fiori tools and apps after an upgrade.

In the following sections you will find the recommended project activities to run after any upgrade in SAP
Fiori for SAP S/4HANA.

3.4.1. Move to new tools and accelerators

You will find that each new SAP S/4HANA release usually introduces new tools that help you streamline
your SAP Fiori implementation, adjustment, and support.

Public 72/122
Figure 43 – How to deploy SAP Fiori for SAP S/4HANA efficiently

These tools are usually introduced in a non-disruptive way, giving you time to adjust your processes.
However, you should strongly consider moving to the new tools as quickly as possible during or
immediately after an upgrade because:

• New tools are more efficient for managing UX at scale

• New tools typically supersede older tools which are intended to be deprecated in a future release
• Any further improvements will be added to new tools only

Refer to:
• SAP Fiori Launchpad Administration guide for your target SAP S/4HANA release, see sections
“Tools for Setting Up Launchpad Content” and “Launchpad Support Tools”
• Blog post SAP Fiori for SAP S/4HANA – Activate SAP Fiori in 1 day or less – the video playlist
and FAQ
• Blog post SAP Fiori for SAP S/4HANA – Creating your custom business roles – the end-to-end
process and video playlist
• Blog post SAP Fiori for SAP S/4HANA – Overview of tools for maintaining custom launchpad
content and layout
• openSAP Microlearning video Creating launchpad content with the SAP Fiori Launchpad App
Manager
• Blog post SAP Fiori for SAP S/4HANA – 3 simple use cases for Launchpad Content Aggregator

3.4.2. Update SAP Fiori Launchpad configuration parameters and features

In the latest releases of SAP S/4HANA, configuration of launchpad parameters, features and plug-ins has
been simplified by moving these settings into simple configuration tables. Many of these settings in
earlier releases were made in the SAP Web Dispatcher configuration and/or made in target mappings as
part of launchpad content.

You should look at migrating such settings to the new configuration tables to:

Public 73/122
 • Simplify ongoing management of launchpad features
• Improve performance and usability via newly available launchpad configuration parameters and
features
• Apply delivered launchpad plug-ins for extended features
• Review and remove any obsolete configuration parameters to avoid confusion

You can also take advantage of the latest best practice options during the upgrade by reviewing the task
list SAP_FIORI_FOUNDATION_S4 and selectively executing tasks that update your launchpad.

Refer to:
• SAP Fiori launchpad, see the respective administration guide for your target SAP S/4HANA
release, e.g. Sections “Managing Launchpad Settings”, “Launchpad Configuration Parameters”,
“Customizing the Shell Bar”, “Configuring SAP Web Analytics Plugin for the Launchpad”,
“Obsolete Configuration Settings”
• Blog post SAP Fiori for SAP S/4HANA – Calling GUI & Web Dynpro ABAP without opening a
new tab
• Blog post SAP Fiori for SAP S/4HANA – Improve Performance via SAP Fiori launchpad
configuration in SAP Fiori for SAP S/4HANA
• Blog post Simplified configuration of Help links in SAP S/4HANA
• Blog post App Support for the SAP Fiori launchpad

3.4.3. Review SAP Fiori performance improvement options

Performance is a key factor in user adoption. Users should ideally be able to traverse from one screen to
another at their speed of thought. Performance is a very broad consideration impacting many dimensions:

• Device operating system behavior

• Web browser version behavior
• Network/bandwidth considerations
• Server placement
• Single sign-on behavior
• SAPUI5 bootstrap placement
• SAP Fiori launchpad versions
• Behavior of individual app versions and classic user interfaces
Every new release of SAP S/4HANA so far has introduced new options to further improve performance
on many dimensions.

Changes in technical architecture, changes in functional scope, changes in the user experience and
changes in the numbers of users of your SAP S/4HANA solution also affect performance. To enable these
performance improvements, you may need to adjust your current configurations.

It is essential to measure performance and identify bottlenecks before applying mitigation techniques.
This avoids unnecessary effort applying changes that may make little difference to overall performance.
The recommended approach for measuring performance is explained in SAP Note 2456424 - Fiori
Launchpad: How to report performance issues by recording HTTP traces.

Be aware of the latest guidance on SAP Fiori Performance Troubleshooting. A summary of current
recommendations can be found in: SAP Note 2916959 - Fiori Performance Troubleshooting

Public 74/122
Refer to:
• SAP Fiori Peak Performance – Introduction & Top 10 Ways to Prevent Performance Issues
• SAP Note 2456424 - Fiori Launchpad: How to report performance issues by recording HTTP traces
• SAP Note 2916959 - Fiori Performance Troubleshooting
• SAP Note 2447857 - Fiori Launchpad: How to check browser settings for better performance
• Performance Improvements in SAP Gateway Foundation
• Performance Improvements for SAP Smart Business Drill-Down Applications
• Blog post Recommendation for Structuring Roles, Spaces and Pages in the SAP Fiori Launchpad
Based on Common User Behaviors

3.4.4. Update SAP Fiori launchpad content and layout

As part of your upgrade, SAP Business Roles will be automatically updated with new apps and new layouts.

You can better manage the pace of change and minimize future upgrade impacts by shifting from SAP
Business Roles to custom business roles. Refer to blog post SAP Fiori for SAP S/4HANA – Creating your
custom business roles – the end-to-end process and video playlist.

Following upgrades, even custom business roles can themselves require changes where they:
• Use SAP technical catalog content that has changed (e.g. been moved to a different technical catalog)
• Reference apps that are obsolete (i.e. deleted) or deprecated

For custom business roles, you can identify changes needed through the Launchpad Content Manager tool
as explained in Adjusting Launchpad Content after an Upgrade and blog post SAP Fiori for SAP S/4HANA
– How to fix Changed and Outdated Catalogs. You can use the quick fix options to swap obsolete apps for
successors. You can also use the Check Services feature in the tool to check that all required services are
active for the role.

Where services are not active you can use SAP_FIORI_FCM_CONTENT_ACTIVATION task list to
activate all services required for apps in custom business roles.

You may need to adjust related authorizations in the underlying security role. The program
PRGN_COMPARE_ROLE_MENU can be an effective aid for identifying and resolving changes in
authorisations.

You can also review your existing content for any issues with obsolete/deprecated apps or inactive
services using the Launchpad Content Aggregator (transaction /UI2/FLPCA) tool. This provides an
aggregated overview of the launchpad content in your system. You can review the content of SAP
Business Roles and custom business roles in your system. Refer to blog post SAP Fiori for SAP
S/4HANA – 3 simple use cases for Launchpad Content Aggregator

Public 75/122
Figure 44 - Launchpad Content Aggregator showing an aggregated view of a custom business role for the Accounts Receivable Accountant

Important: From SAP S/4HANA 2022 the technical catalog tool Launchpad App Manager has a new
adaptation mode – refer to blog post SAP Fiori Launchpad: New Fast and Easy Option to Adapt SAP-
delivered Launchpad Content (for On-Premise and Cloud, Private Edition). This adaptation mode allows
greater reuse of SAP technical catalogs. Post upgrade, you should consider whether custom technical
catalog entries created purely to change tile texts, icons, or keywords, can instead be reverted to the
adaptation mode. This has the potential to reduce effort for future upgrades.

Refer to:
• Setting up Technical Catalogs with the Launchpad App Manager
• Setting up Business Catalogs with the Launchpad Content Manager
• Mass Maintenance of Business Roles

Updating Launchpad Layouts

From SAP Fiori FES 2020, new layout options for Spaces and Pages are now available to help you
implement SAP Fiori at scale. Spaces and Pages provides a more robust and more scalable layout of content
on the launchpad for business users. Spaces and Pages provide a better default user experience and starting
point for business users to encourage high user adoption and optimal productivity. Future direction is based
on Spaces and Pages, such as the New My Home Page already available in SAP S/4HANA Cloud, public
edition.

Groups have been deprecated from SAP S/4HANA 2021 and should no longer be used. You should migrate
to Spaces and Pages as soon as possible. To migrate to Spaces and Pages, you can use the migration tool
Create Launchpad Pages from Groups to copy SAP-delivered spaces and pages; and/or create your own
spaces and pages from scratch.

Spaces and Pages can be enabled for individual users via personalization or made the default globally via
launchpad configuration parameters. Users can import apps from the Groups-based classic home page to
the spaces and pages My Home pages.

Refer to:

• SAP Fiori for SAP S/4HANA – Migrating from groups to spaces and pages – Why, When, and Key
Differences for Users
• SAP Fiori for SAP S/4HANA – How to migrate from groups to spaces and pages

Public 76/122
 • Managing Launchpad Spaces and Pages
• Importing Apps and Personalizations from the Classic Home Page to My Home
• Blog post Best Practices for Structuring Spaces and Pages
• Blog post Recommendation for Structuring Roles, Spaces & Pages in the SAP Fiori Launchpad
based on Common User Behaviors

3.4.5. Update authorizations

Where new apps are introduced, related authorizations are added to SAP Business Roles and will need to
be added to your affected custom business roles.

Authorizations for SAP Fiori apps are determined by the OData Services used. You can find authorization
proposals in SU22 and create your own authorization variants to adjust which authorizations are proposed
for your own custom business roles using transaction SU24. Creating authorization proposals simplifies
adjusting authorizations on upgrade, as you can compare your proposals against the SAP delivered
proposals. Refer to blog post Getting back to Standard Proposals with SU24 Authorisation Variants.

You may find existing apps and UIs have additional data authorizations applied by the upgrade, for
example: to provide improved segregation of duties. Where this has occurred, typically a SAP Note will
explain these changes, e.g. SAP Note 2505099 - Worklist for transition to SAP S/4HANA - authorization
objects in quality management.

Errors relating to missing explicit authorizations are typically shown in the error log transactions SU53,
/IWFND/ERROR_LOG, /IWBEP/ERROR_LOG and STAUTHTRACE. Where available, you can also
view these errors in the SAP Fiori launchpad using the App Support feature in the User Actions menu.
Transaction SUPC and program PRGN_COMPARE_ROLE_MENU can be used to resolve missing
authorizations in SAP Business Roles and custom business roles.

Where authorizations have been added to CDS Views, these are implicit authorizations that act as a filter
on the view and are more likely to be identified as missing data than as an authorization error. You can
use transaction SACMDCLS to review and test the authorizations related to CDS Views. Refer to:

• SAP Note 2919392 - Determining missing authorizations for Access Controlled CDS Entities
• Blog post App Support for the SAP Fiori launchpad

3.4.6. Transition from deprecated to successor SAP Fiori apps

Successor apps are the next generation of their predecessor. Relationships between predecessor and
successor apps are maintained in the SAP Fiori apps reference library and can be viewed there.

Successor apps typically offer improved features, such as new personalization and extension options, and
may also apply an entirely new UX design to the task. In some cases a predecessor app may be split into
multiple successor apps, provided to support different use cases.

Important: Successor apps can be significantly different to their predecessors. You need to explore the
successor app and confirm it fits to your use cases and processes.

You can include both the successor and the predecessor in your custom business roles to aid migration to
the successor app if desired.

Public 77/122
 3.5. Functional post-upgrade activities

A collection of information of post-upgrade application-specific activities, which have not been described
within the Business Impact Notes of relevant Simplification Items nor in any application specific
documentation of the conversion/upgrade process can be found in:

SAP Note 3226548 - SAP S/4HANA 2022 - application specific notes in system conversion / release
upgrade follow-on phase

On the Finance side it is important to understand the following post-upgrade activity. If an operating
concern with type Margin Analysis (account-based) was generated by transaction KEA0 and/or new
characteristics (which had not been assigned before to an operating concern of type Margin Analysis)
were assigned to this operating concern, it is important to run the report
FCO_ADD_COPA_FIELD_TO_ACDOCA after the upgrade. For more details, refer to SAP Note
2176823 - FAQ on CO-PA issues in S/4 HANA Finance (SFIN).

3.5.1. Transitioning users to new or changed functionality

You will need to prepare business users for any changes introduced as part of the upgrade. This change
communication activity is a normal part of organizational change management. You will find the
following resources are helpful for enabling users on the changes.

Users moving from SAP Fiori 1.0 (SAP S/4HANA 1511) and SAP Fiori 2.0 design (SAP S/4HANA
1610, 1709, or 1809) to SAP Fiori 3 design (SAP S/4HANA 1909 or higher) will experience a major shift
in launchpad features and behaviors. You can find a summary of the major changes in:

• Blog post SAP Fiori for SAP S/4HANA – Upgrading from Fiori 2.0 to Fiori 3 for SAP S/4HANA
Cloud 1908 and SAP S/4HANA 1909 and higher Users

You can use the tutorials available as part of the User Assistant provided as part of your SAP S/4HANA
system to enable business users on the target SAP S/4HANA release, in particular the Users Assistance
tutorial sets “Working with Launchpad” and “Working with Apps” give a general introduction.

Public 78/122
Figure 45 - Working with Launchpad tutorial landing page

Figure 46 - Working with the Launchpad interactive tutorial

openSAP Microlearning SAP S/4HANA User Experience “Business End User Experience” playlist
contains a number of videos to familiarize users with most common launchpad and personalization
features.

Public 79/122
Figure 47 - openSAP microlearning video playlist SAP S/4HANA > User Experience > Business End User Experience

When moving users from GUI to SAP Fiori, consider the advice in Blog post SAP Fiori for SAP
S/4HANA – Recommendations for transitioning users from SAP GUI to SAP Fiori.

Refer to:
• Podcast Inside SAP S/4HANA Podcast 46: SAP GUI to SAP Fiori
• Blog post SAP Fiori for SAP S/4HANA – Recommendations for transitioning users from SAP GUI
to SAP Fiori
• Blog post SAP Fiori for SAP S/4HANA – Upgrading from Fiori 2.0 to Fiori 3 for SAP S/4HANA
Cloud 1908 and SAP S/4HANA 1909 and higher Users
• Blog post Major next steps of SAP Fiori 3 available for SAP S/4HANA on-premise – spaces,
central entry point, and more
• Blog post SAP Fiori 3 update: evolution continues, with flat tiles and more – have a look, and learn
how to find what’s new
• Blog post SAP Fiori 3: How to put intelligence into your user experience
• Blog post SAP Fiori for SAP S/4HANA – How to setup the User Assistant in your S/4HANA Fiori
launchpad
• Blog post Simplified Configuration of Help Links in SAP S/4HANA

3.6. Regression testing

As for any application of Support Package, Enhancement Package, or release upgrade, regression testing
is necessary and will be a significant part of the project. The following need to be verified:

• Changes to business processes, e.g. those impacted by simplifications or new functional features

Public 80/122
 • Changes to the SAP Fiori launchpad
• Changes to currently used SAP Fiori apps and classic user interfaces in scope
• All Custom extensions and custom-built apps

A particular watchpoint is performance of the overall solution and of specific apps, especially high-
volume apps. While upgrades typically bring improved performance and new performance configuration
options, these need to be reviewed and verified against your current system usage.

SAP Solution Manager can facilitate your regression testing. Since the relevant SAP Solution Manager
capabilities could be used for any type of upgrade or conversion and are not SAP S/4HANA specific, they
are described in the appendix.

3.6.1. Automated testing for custom SAP Fiori apps

For custom-built SAP Fiori apps, deeper technical regression testing may be needed. For testing of
custom-built Fiori apps, refer to the SAPUI5 Software Development Kit for the latest advice on testing
tools and best practices.

Figure 48 - SAPUI5 Testing Pyramid

For example, you can opt to use automated testing capabilities provided as part of SAPUI5, such as:
• OPA5 tests (One Page Acceptance Tests)
• UIVeri5 tests (end to end testing framework for SAPUI5 applications)
From SAPUI5 1.74, you can use the Unit Test Recorder to assist with creating these tests. You can use
open source Test Automation Frameworks such as Vyper for UI5 to run repetitive tests.
Refer to:
• Testing section of the SAPUI5 Software Development Kit
• Blog post UIVeri5: More stable system tests for UI5 Applications
• Blog post Automated Testing for SAP Fiori apps: Piece of cake with SAP Web IDE and the
SAPUI5 Testing Tools
• Blog post Test Recording with UI5 Recorder

Public 81/122
 • Blog post Get started with UIveri5 – SAPUI5 Test Automation
• Blog post Automate SAP UI5 Application Testing using Vyper Test Automation Framework
You can also do automated testing of OData Services using eCATT. Refer to: Testing OData Services in
the SAP Help Portal

3.6.2. Validate your business processes

When replacing deprecated SAP Fiori apps with new apps and where there are major changes to existing
apps, you must validate whether business processes are still running as desired. For new apps, you may
also need to consider whether custom extensions might be required. You should also consider if the
business process can be further optimized by using the new app features provided.

Deprecated and changed SAP Fiori apps can usually be identified with help of the What’s New Viewer
for SAP S/4HANA, or the SAP Fiori Apps library. Refer to:
• openSAP microlearning video Working with the What's New Viewer
• openSAP microlearning video Finding available SAP Fiori apps

3.6.3. Verify SAP Fiori floorplan changes

For any expected SAP Fiori floorplan changes, regression test a few apps with the relevant floorplan to
check there are no issues with the changes. You should make sure you test any import/export features,
e.g. export to spreadsheet, to ensure there are no issues being raised by your web browser settings, proxies
or firewalls. Refer to:
• SAPUI5 Software Development Kit – What’s New in SAPUI5 and Change Log

3.6.4. Validate changes in classic UI capabilities

For any change in classic UI capabilities, validate any important changes that impact business users are
working as expected. For example:
• Cut/copy/paste capabilities
• File upload/download
• Themes
• Behavior on touch-enabled devices
• Significant changes in icons

If you are using SAP Business Client, validate changes in behaviors such as:
• Side panels
• Themes
• Tab and busy indicator behaviors

If you are using SAP Screen Personas, validate important changes in behavior for your target release:
• Slipstream on mobile

Refer to:
• SAP Note 2658822 - Release notes for SAP GUI for HTML (short WEBGUI)
• SAP Note 2963562 - Icons are displayed differently in WinGUI and WebGUI
• SAP Note 2540597 - Supported Themes for SAPGUI for HTML
• SAP Note 2340424 - Availability of Side Panels in S/4HANA (on-premise)

Public 82/122
 • SAP Community topic SAP Screen Personas

3.7. Cutover and go-live

Cutover and Go-Live for a SAP S/4HANA upgrade is similar to the upgrade process for any software.
These are the main activities to be considered:

Main activities of the Cutover and Go-Live are:

• Get go/no go agreement to start the cutover from all stakeholders
• Freeze production, if needed
• Execute transports and cutover activities
• Execute production verification testing
• Get final go/no go agreement to go-live
• Advise the business-as-usual support team that the new changes are in production
• Re-open the system for business users
• Make the go-live announcements informing users/stakeholders that the system is ready for use
• Formally start the hypercare period for the upgrade

4. DRIVING ADDITIONAL VALUE FROM YOUR UPGRADE

4.1. Introducing new business functions and processes

After your SAP S/4HANA sandbox and/or development environment has been upgraded, you carry on
the design, configuration, and extension of your solution based on the scope of your project. These are
activities that depend on having system access to your target release of SAP S/4HANA.
Most of these activities are minimal for a Technical Upgrade, where the scope is constrained to
mandatory changes. More effort is required for a Functional Upgrade where new functionality is being
introduced.
Typical activities include:
• Fit-to-standard (aka fit-gap) blueprinting
o for mandatory simplification items
o for new or changed business processes
o for new or changed business roles
o for new apps, including successor apps of deprecated apps and classic UIs
• Configuration of functional processes
• Configuration of new features and options in SAP Fiori launchpad
• Extension of SAP Fiori apps
• Adjustment of security roles and authorizations to include new or changed authorization objects

This is the RUN phase of your SAP S/4HANA upgrade project.

Whether you applied a Functional Upgrade or Technical Upgrade approach, you are likely to want to
drive more business value from your upgraded SAP S/4HANA solution over time. You do not need to

Public 83/122
wait until the next upgrade to do this. Introducing new business value is readily achievable provided the
main activities and key considerations are understood.

For example: You may want to provide greater benefits to the business and business users by increasing
your coverage of new or changed processes, more apps, and/or new intelligent technologies.

Once your upgrade has exited Hypercare and moved to business as usual support, you can look to
introduce new business value by running much smaller continuous improvement projects.

Important: A continuous improvement project is much smaller and of shorter duration – typically
weeks rather than months - than an Upgrade or Implementation project.

Depending on your organizational culture, you may want to establish a Centre of Excellence to guide
running of continuous improvement projects and ensure lessons learned are captured and used to improve
future continuous improvement projects.

Using a project framework enables you to:

• Manage the potentially diverse impacts of process change on the system and on the
organization in a coherent manner
• Maintain good communications with sponsors, stakeholders, business users, and business-as-
usual support teams
• Continuously improve the execution and outcomes of any future continuous improvement
projects
o For example, by capturing lessons learned, before/after metrics, runsheets of activities, and
updating living documents to reflect lessons learned and key decisions taken (e.g. UX
Strategy, Mobility Strategy, Intelligent Technologies Strategy)
Continuous improvement projects can be used to introduce:
• Changes to existing business processes
o E.g. Adding more SAP Fiori apps to provide greater coverage of existing business
processes
• New intelligent technologies
o E.g. Adding Machine Learning or Situation Handling to existing business processes
• New business processes or business models
o E.g. Group Reporting, Central Procurement, and/or Demand-driven MRP
• New SAP Fiori launchpad features
o E.g. New notification types, new user defaults.

This section provides:

• Example Project plan for a continuous improvement project
• Prerequisites for a continuous improvement project
• Main phases and related considerations of a Continuous Improvement project
o SAP Activate phases have been used as a guide and can be mapped to your chosen
methodology

4.2. Example project plan for a continuous improvement project

A continuous improvement project is typically aimed at introducing new business functionality. The
project may include multiple phases such as Discover, Explore, Deploy. You can use SAP Activate
phases if you wish.

Public 84/122
Most phases will be much shorter than an implementation or upgrade project – typically of a few
weeks’ duration. This is particularly expected where your SAP Fiori architecture and UX/mobile
strategies are already in place, enabling the team to focus on the business process and related business
roles to be changed.

Important: If the focus of your Continuous Improvement project includes introducing any intelligent
technologies for the first time, you will need to allow additional time to:
• Adjust your architecture
• Update your UX Strategy (and if impacted your Mobile Device strategy)
• Enable the team on intelligent technology design, behavior & tooling
• Enable your business-as-usual support team on support tooling
In this example project plan, some new business roles and related apps are being introduced by the
Continuous improvement project. The project plan is 6 weeks from start in sandbox to go-live in
Production, plus a subsequent 3-week hypercare period. Discovery starts in a sandbox or trial system,
where the following activities can be completed without impacting the Development to Production
landscape:
• Standard apps are explored
• New or changed business process(es) are prototyped
• Fit of apps can be workshopped
• App extension options verified
• SAP Fiori launchpad home page (or spaces and pages) design for business roles are prototyped
App extension options have been limited to configuration and in-app extensibility options. Developer-led
extension options have been excluded from scope.
Once the new processes and apps to be introduced have been agreed, there is a quick progression to
activate, configure, and test the agreed changes.

Figure 49 - Example project plan for a continuous improvement project

4.3. Prerequisites

Before starting your continuous improvement project, check the following are already established:

• Your SAP Fiori for SAP S/4HANA system architecture

• Your Mobile Device strategy
• Your User Experience strategy
If your scope includes introducing new intelligent technologies, you will need to have considered the
strategy for the relevant capabilities. Intelligent technologies are varied and may include a range of
technologies. A few examples of Intelligent technologies with related use cases that are integrated with
SAP S/4HANA are:

Public 85/122
 • SAP Fiori Situation Handling scenarios (these can be just UX or involve additional technologies
such as Machine Learning)
• Machine Learning and Artificial Intelligence (ML/AI)
• Chatbots such as SAP Digital Assistant
• SAP Intelligent Robotic Process Automation (SAP iRPA)
• SAP Fiori Situation Handling scenarios (these can be just UX or involve additional technologies
such as Machine Learning)

4.4. Introducing new User Experiences

Ultimately the most important reason for upgrading SAP S/4HANA is to deliver new business value, by
enabling new ways of working. Once you have completed your upgrade, you can pace these changes to
incrementally introduce new value to more business users and across more of the business processes that
utilize your SAP S/4HANA environment. In this section, there are some general principles; a
recommended UX Adoption methodology, and some accelerators to guide you.

Introducing new user experiences requires you to engage your business stakeholders on your change
journey. You will need to discuss business priorities and capacity considerations. To aid these
discussions, you can use the UX Value Goals as broad categories of the types of improvement possible
with SAP S/4HANA and RISE with SAP S/4HANA.

Figure 50 - UX Value Goals provide 9 broad categories of the types of improvement possible with SAP S/4HANA

Each UX Value Goal maps to specific business and solution capabilities supported by standard delivered
content in SAP S/4HANA and which can be extended to custom use cases as shown in the following
table.

Public 86/122
Figure 51 - UX Value Goals explained alongside their innovation/solution adoption focus

General principles for planning incremental UX Adoption:

• Avoid effortful searching of the SAP Fiori apps reference library by keyword in the hopes of
stumbling across something relevant. Search “by roles” is a more effective starting point. Take
advantage of recommended process diagrams and test scripts in tools such as SAP Best Practices
Explorer to get ideas and examples of apps that work for your business processes.
• Avoid randomly trying various SAP Fiori apps in your sandbox in the hope of stumbling across
something useful. This is effortful and can be exhausting.
• Focus on target groups of users who perform the same business role. People in the same
business role often participate in similar business processes, share similar working environments,
work with similar mobile device types, and are likely to have similar user experience needs.
These similarities make it easier to understand their current pain points and future opportunities,
and mindsets.
• Engage the business early in effective business conversations around business value priorities,
needs, and challenges for the business roles in scope of your continuous improvement.
• Remember that business value is only achieved when business users adopt your user
experience, so involve business users early, involve your change management team early, and put
aside time to smooth adoption for your users by adjusting layouts and presetting personalizations.
• Make introducing new UX an iterative habit – a “little and often” approach allows you and your
business to absorb changes more easily and achieve smooth adoption as you build skills together.

The recommended UX Adoption process can be summarized as a discipline to quickly assess available
delivered content and custom options along a narrowing funnel of opportunities so that you can quickly
focus on the most likely candidates. The recommended approach refines the available opportunities in the
following order:
• Refine by business role
o Focus on what is relevant to the target users.
o This decimates the amount of available UX content you need to review.

Public 87/122
 • Refine by UX Value Goals
o Focus on what is relevant to the types of improvement you want to bring to these users.
o At this stage you scope the most likely types of UX content for exploration, within the
identified business roles.
• Refine by process use cases
o Focus on the specific process use cases in scope for change.
o At this stage you commence detailed exploration of apps, features, and use cases.
• Refine by project capacity / Refine by business capacity
o At this stage, where needed you can defer additional changes from now to next or next to
later
• Review what users actually use
o Review actual user behavior after you have introduced your changes and use those
learnings to improve future iterations.

Figure 52 - UX Adoption is a disciplined process in assessing which new UX to deploy

An effective way to engage your business stakeholders and sponsors on what new UX to introduce, is to
build a Now/Next/Later Roadmap to discuss business value and use case priorities using the UX Value
Goals and your business process use cases. Using your UX Adoption roadmap you:
• Map business use cases to apps, features, intelligent use cases, and potential custom use cases
• Identify where UX solves business needs and pain points, that will encourage adoption by your
business users
• Discuss challenges such as parallel business initiatives
• Adjust your roadmap for now/next/later considerations. For example:
o Now = Immediate value that fits alongside existing processes
o Next = Requires a significant process change or a governance discussion
o Later = available at the next upgrade or requires new technical skills or services
• Plan next steps. For example:
o Your Now scope guides the current improvements
o Your Next scope can be used to plan further conversations around potential change

Public 88/122
 o Your Later scope can be used as a part of a business case for future upgrades
• Each UX adoption iteration can shift the roadmap forwards, i.e. Now becomes as-is, move Next to
Now, Later to Next, and so forth

Figure 53 - Visualize your UX Adoption Plan as a Now/Next/Later roadmap where you map business value and use cases to available apps,
features, intelligent use cases and custom use cases.

Figure 54 - The 3 major decisions in adopting User Experience: Who will change? What will change and when? How to change?

Public 89/122
Consider the following as a high level flow for adopting new UX:
1. Decide WHO you will change, i.e. which business roles in your organisation
2. Gather information about your users e.g. needs, pain points, opportunities, current working
environment, mobile device usage, current UI technologies used etc.
3. Decide WHAT you will change and WHEN
a. Identify the most important use cases to bring business value. For example, is the aim to
move more of their tasks onto mobile devices? Bring automation? Bring better insights?
You can use the UX Value Goals as broad categories of the types of improvement
possible in SAP S/4HANA.
b. Map your own business roles to similar SAP business roles. This immediately decimates
the amount of delivered UX content you need to assess.
c. Map your use cases to apps, features, intelligent use cases that help achieve those goals.
You can use the UX Value Goal App Selection Guides in SAP Activate to assist you.
Where there is no delivered content to meet your needs, the guides include
recommendations on services to support custom use cases.
4. Decide HOW you will change
a. Craft a custom business role with the new apps, UIs, launchpad features, and intelligent
use cases you want to introduce.
b. Ensure changes to security authorizations and device considerations have been adjusted
c. Configure, adapt and extend your new UX as needed. Minimize effort by focusing first on
the most efficient extension options, such as key user extensions and personalizations.
5. Encourage adoption by making it easy for users to change
a. Encourage adoption by adjusting the launchpad layout. Work with impacted users to make
sure the layout makes sense and minimizes time for users to adopt the changes.
b. Take advantage of key user options to preset defaults for apps and features. For example,
by creating role-specific views. Refer to blog post SAP Fiori for SAP S/4HANA – New
options for managing Views for filters tables and charts
c. Expect that many business users will not bother to personalize, and others may not wish to
personalize until days/weeks after new apps are introduced

Keep front of mind that business value is only achieved when business users adopt your user experience.
So an important part of UX Adoption is making time to ease the adoption for your business users. This
includes: adjusting layouts and preset defaults within your system; and preparing change management
communications so that users understand what’s changing, why, and what is expected of them.

Public 90/122
Figure 55 - UX Adoption is an iterative process where learnings from initial rollouts are used to drive success in future rollouts

To support your UX Adoption journey, there are numerous accelerators in SAP Activate with the tag User
Experience, most importantly:
• UX Value Goal App Selection Guides
• Quick Guide to Evaluating SAP Fiori apps
• Enhancement using in-app extensions feature map

When moving users from SAP GUI to SAP Fiori, you should also consider the advice in blog post SAP
Fiori for SAP S/4HANA – Recommendations for transitioning users from SAP GUI to SAP Fiori.

Refer to:
• Blog post SAP Activate – Introducing the User Experience tag
• Blog post SAP Activate – Introducing UX Value Goals for your UX adoption roadmap

4.5. Introducing new Intelligent Technologies

Each new release of SAP S/4HANA offers the opportunity to implement new business processes and
introduce high business value through intelligent technologies such as Intelligent RPA (Robotic Processing
Automation), Situation Handling & Data Intelligence (incl. Machine Learning).

For each intelligent technology, SAP S/4HANA delivers use cases for business processes that are ready to
configure, activate, and deploy. Use cases can be embedded or side-by-side.

Embedded use cases run within SAP S/4HANA, they are embedded within specific SAP Fiori apps and
features. For example, most Situation Handling use cases and several Machine Learning use cases.

Side-by-side use cases require parallel services from the SAP Business Technology Platform (BTP), which
may require subscription or cloud credits. For example, all intelligent Robotic Process Automation use
cases, and some Machine Learning use cases.

Public 91/122
Intelligent processes can be introduced gradually and combined over time to improve experiences.

Figure 56 - Intelligent processes combine for better experiences - example of automating the order-to-cash process

Further details on these can be found below:

• Use Cases for Situation Handling
• Blog post Custom Situation Use Cases for SAP S/4HANA
• Blog post Intelligent Situation Automation – The next big step in Digital Transformation
• Intelligent Scenario LifeCycle Management
• Blog post Intelligent LifeCycle Management – Frequently Asked Questions
• SAP Best Practices for iRPA on SAP S/4HANA
• SAP intelligent RPA store
• Training and Activating the out of the box predictive content shipped by S/4HANA

4.6. Introducing new SAP Fiori launchpad features

SAP Fiori is not only a collection of apps. The SAP Fiori Launchpad as entry point provides many features
already including Enterprise Search, Notifications, Settings (including Default Values), Personalization
(including Edit Home/Current Page), User Assistance, About, and App Support. In the following image
you can see several of features available in the latest releases of SAP S/4HANA.

Public 92/122
Figure 57 - SAP Fiori Launchpad features

Along with App Support, it is recommended to always enable the following features for the SAP Fiori
Launchpad:

Figure 58 - Recommended SAP Fiori Launchpad features

From experiences across SAP S/4HANA customers, there are five main SAP Fiori launchpad features to
include in your project. Most of these features are either provided working out-of-the-box or require
minimal once-off configuration to get them going. They are as follows:

Enterprise Search
The SAP Fiori launchpad offers an SAP HANA Enterprise Search function that provides unified,
comprehensive, and secure real-time access across all apps and business objects, such as materials,
customers, and maintenance plans. The search icon is displayed in the shell bar of the launchpad and is

Public 93/122
always readily available at the top of the screen. More than 300 search models are provided. To avoid users
confusion and performance issues due to excessive use of search, it is recommended that users be restricted
to the top 5-10 search objects relevant to their role. Refer to blog post SAP Fiori for SAP S/4HANA –Limit
Search Object Access in Fiori Launchpad made easier

Notifications
Notifications are the best way to make users aware of a situation that requires timely action or attention.
This could be a situation that has just arisen, or a task triggered by a workflow. Notifications have the
following benefits:
• Use notifications to make users aware of situations that require attention.
• Reduce the amount of information and the number of actions to a minimum but provide enough
information to help users decide if the information is important.
• Use notification list items and notification list groups only in the SAP Fiori notifications popover.

For more information see SAP S/4HANA Notification Centre Part 1 Activation and SAP S/4HANA
Notification Centre Part 1 Providing Notifications.

Default Values
You can personalize your default values in SAP S/4HANA to save time when using apps launched from
your SAP Fiori Launchpad. You can set user-specific default values for any parameter values used when
launching any of your apps from the SAP Fiori Launchpad, including:
• SAP Fiori apps
• SAP Web Dynpro ABAP applications
• SAP GUI for HTML
• SAP GUI for Windows

Guidance on configuring user default values is detailed in Setting User Defaults in the SAP Fiori
Launchpad. Key users can also preset default values for other users. Refer to blog post SAP Fiori for
SAP S/4HANA – Yes Key Users can set Default Values for other Users

Personalization
One of the most important features in SAP Fiori is the possibility for each end-user to personalize the
SAP Fiori Launchpad. Personalization features available include the following:

• Setting default values

• Filter variants
• Smart table/chart personalization
• Setting favorite links in Smart link dialogs
• Managing Cards on an overview page
• Creating bookmarks
• Using Enterprise Search for reporting

See more in SAP Fiori for SAP S/4HANA - How can end users personalize SAP Fiori.

User Assistance
The main characteristics of User Assistance are:
• Seamless – can be used, exactly when the user needs it from within the application
• Context-sensitive - shows exactly what is needed for the user, depending on the current screen
• Guiding - provides an interactive step-by-step process guidance

Public 94/122
Guidance on configuring User Assistance is detailed in How to set up the User Assistant in your SAP
Fiori Launchpad.

The top 5 SAP Fiori features are further detailed in blog post The top 5 SAP Fiori features that bring
value to every business user.

App Support
App Support provides an effective self-diagnosis tool for users for common configuration and
authorization issues, with the ability to download logs that can be sent to your support team. For SAP
S/4HANA 2021 FPS01 and higher, this feature is considered an essential part of supporting your solution.
Refer to:
• Setting up App Support in the SAP Fiori launchpad Administration Guide
• Blog post App Support for the SAP Fiori Launchpad

4.7. Introducing native clients

Within the efforts for introducing new business value through new or enhanced applications, it might be
worth considering introducing new or extending existing apps to new devices and operating systems.

While SAP Fiori can be run in any HTML5 compatible browser, it’s possible to leverage additional
features and provide additional functionality and business value through native device / OS features.

Refer to the Mobile apps for SAP S/4HANA – Customer Guide.

For SAP Fiori using Apple iOS, refer to:

▪ Design Guidelines SAP Fiori for iOS
▪ SAP Business Technology Platform SDK for iOS

For SAP Fiori using Android, refer to:

▪ Design Guidelines SAP Fiori for Android
▪ SAP Business Technology Platform SDK for Android

SAP also delivers several native mobile apps for SAP S/4HANA, and so do some partners. For example,
• SAP Service and Asset Manager - Field Service Technician Persona in SAP Service and Asset
Manager
• SAP Maintenance Assistant
• SAP Direct Distribution – A New Mobile App for Direct Store Delivery
• SAP Warehouse Operator - How You Can Get Started with SAP Warehouse Operator App
• Partner apps are listed in the SAP Store

Public 95/122
Figure 59 - SAP Service and Asset Manager example screeenshots

Public 96/122
5. KNOWN ISSUES

# Issue Description Solution References

1 General - Some SAP Fiori apps, 1. Check all functional - Speed Up your
Missing e.g. SAP Fiori app configurations are complete SAP Fiori support
Translatio F3228 Sales incidents
ns Accounting Overview 2. If there are still issues, raise
might have missing an SAP incident providing the - Finding the
translations after the exact App Id and using the technical name of
upgrade. designated application an app
component for support of the
Prerequisites: app. These details can be - SAP Note
1. Configuration was found in the SAP Fiori apps 2838687 - [F3228]
not complete, e.g. reference library, and via the Sales Accounting
Semantic Tags were User Actions > About feature. Overview: Sales
missing for some Volume Per
financial statement Material Card
versions.
- SAP Note
2 There are 2855656 - Sales
untranslated texts that Accounting
need to be resolved via Overview - two
the usual SAP support cards show results
processes. slowly

2 General – Customer had Wait for next FPS/SPS or - SAP Note 832594
Equivalent upgraded one or more major S/4HANA release to - Importing
support components on their include the equivalent support Support Packages
package current release to a too package. Alternatively revert before an upgrade
missing high SPS level, which to a source release status
has/have no equivalent before upgrading the affected
support package components. Point the
released yet for the customer to SAP Note 832594
target S/4HANA
release
3 General - Customer is wondering In some cases the old version SAP Note 2911053
Add-on how to proceed in case can be uninstalled. Check with 2911053 -
version not of having an add-on the tooling in transaction SAINT. Uninstallation
available deployed, for which no SUM would also perform this Information
for target new version is available check and advise.
release yet for the target
S/4HANA release
4 Technical Customer upgrade is Ideally, you would release all transport requests to
- Release stuck due to non- avoid potential issues as much as possible. If you
of released non-standard have not released them, it will lead to locked objects
customizin code customizing and stopping the upgrade and SUM would inform you
g and development requests about it. You could then go into transaction SE03 or
developme SE09, unlock them and proceed with the upgrade.
nt requests Of course, you should know 100% that you can
unlock them without any side effects. If you want to
include and release objects during an upgrade, there

Public 97/122
 are some good recommendations how to save time
during the upgrade in:
https://blogs.sap.com/2020/08/07/reduce-time-for-
customer-transports-in-zdo-and-conversion-projects-
for-sap-s-4hana/
https://blogs.sap.com/2017/11/24/integrating-
customer-transport-requests-in-updates-and-
upgrades/
5 Technical Customer would like to OS updates can be done anytime, irrespective of
- know whether you can whether DB and PAS are running on the same
OS have app server and instance or on different instances. Of course the
upgrade - DB server running on target OS version needs to be in the supported range
app server different versions of OS versions for all SAP product(s) running on
and DB during an OS upgrade this instance. So running PAS and DB on the same
server instance might reduce the flexibility in terms of OS
running on upgrades. Usually the upgrade can be done in-place.
different For the PAS anyway. But there are also scenarios
versions where new install is recommended (e.g. see here).
during Depends also on the OS being used. E.g. for
upgrade Windows in-place upgrade support has only been
introduced quite recently (see SAP Note 1494740 ).
Whether it should be done in-place is of course
another question. In a productive or otherwise
critical environment, it might be a better choice not
to do an in-place upgrade, even in cases where it’s
supported and possible. Depends of course how big
the upgrade is, whether you just install some
security patches, or whether you upgrade to a major
new OS version. Also depends on which quick
restore options you have for the PAS in case the
upgrade fails. Also some high availability setups on
instance/OS level might technically prevent an in-
place upgrade.
6 Technical Customer is wondering Due to temporarily required objects/copies, the DB
- Ensure why a lot more DB capacity required during the upgrade might be +70%
more DB capacity is required of your current DB size. Ensure sufficient space is
space during upgrade available.
temporaril
y during
upgrade
7 Technical Customer is on Resolution is to use version management and
– S/4HANA 1809 and reactivate the following objects:
Customer upgrading to /SDF/CL_RC_CHK_UTILITY=>GET_TEXT_STR
cannot S/4HANA 2020 and /SDF/CL_RC_CHK_UTILITY=>SITEM_SKIP_ST
implement implemented prequisite AT_UPDATE_SINGLE
latest note 1668882 and /SDF/CL_RC_MANAGER=>PERFORM_CONSIS
Simplifica while trying to TENCY_CHECK
tion Item implement the latest /SDF/CL_RC_SIMPLE_CHK_DB=>PERFORM_C
Check note for 2399707 by HECK
Note resetting the note /SDF/CL_RC_SIMPLE_CHK_EN_POINT=>PERF
2399707 2399707 is not

Public 98/122
 allowed. Customer ORM_CHECK back to the 1809 version and then
then tries to impement reimplement SAP Note 2399707.
the latest note and runs
into syntax error with
class
/SDF/CL_RC_MANA
GER with method
PERFORM_CONSIST
ENCY_CHECK
8 Technical Optimizing the Any further optimization considered for the import
– Long transports requires of transports must be tested before using it in your
runtime firstly attention to the production environment. There are 3 main options:
for correct sequencing of
transports transports. Enable the feature “Customer Transport Integration
impacting with SUM”. This enables the import of multi-client
business customer transport requests and - in connection with
downtime the near-Zero Downtime Maintenance (nZDM) or
Zero Downtime Option (ZDO) technology - the
conversion of custom tables during the uptime.
Refer to SAP Note 1759080 - Prerequisites and
restrictions of Customer Transport Integration with
SUM. Please note that “Customer Transport
Integration” in combination with ZDO is not in
general availability and would therefore require SAP
consulting or support to be involved in your project.

Use parallel imports to accelerate the runtime for

importing transports after the upgrade/update. In the
Transport tool configuration, a new parameter
"parallel = n" can be set.”. Review each individual
setting and decide whether the recommendation is
valid for your environment. Refer to SAP Note
1223360 - Composite SAP Note: Performance
optimization during import.

For transport of authorization there a further

optimization possible. By using the parameter
AUTH/NEW_BUFFERING special “After Import
Methods” run later. Refer to SAP Note 1544295 -
Performance of the after-import method
PRGN_AFTER_IMP_PROFILE
9 Technical Client Copy Consider alternative solutions - SAP Note
– Poor performance can be a to achieve the same end. For 2163425 -
performan hidden cost for SAP example, if you are Recommendations
ce of S/4HANA upgrade experiencing client copy of for client copy
client copy projects, especially large amounts of data exceeds performance
where you have large the permitted durations, improvement ->
volumes of data, there consider using a system copy Central Note
has been insufficient with pre and post steps to
archiving of old data, achieve the same objectives. - SAP Note
and server resources 2555451 -

Public 99/122
 are scarce. It is always Where there is no better Performance
a good idea to ensure alternative to client copy, you improvement in
client copy will not be must manage the duration Client Copy for
an issue for the project. through project planning. For HANA ->
example, including activities Optimize Client
to test the duration and Copy parameter
calculate the expected
timeline, or by adding - SAP Note
temporary hardware resources. 2550545 - Client
copy performance
From a technical perspective, improvements ->
you can improve the Update Client copy
performance with some program
preparation. For example, by:
- SAP Note
- Calculating the client size 2761821 -
prior to client copy to ensure Performance
sufficient hardware resources improvement for
HANA systems :
- Using parallel processes Client copy -> Use
HANA Native
- Reducing the data set via SQL to accelerate
archiving
- SAP Note
- Deleting the target client or 2759161 - Internal
specific large tables in the error:
target client in advance of <TABLE_NAME>
client copy DWITH_CURS is
raised during client
- Excluding large tables from copy/client deletion
client copy
- SAP Note 489690
You should also review the - CC-INFO:
latest SAP Notes relating to Copying large
client copy. Apply these prior production clients
to starting a new client copy.
- SAP Note
2868569 -
Performance
Improvement in
Client Copy WAIT
statements

- SAP Note
2907850 - Enable
single copy after
performance
improvements in
Client Copy Tool

- SAP Note

Public 100/122
 2759161 - Internal
error:
<TABLE_NAME>
DWITH_CURS is
raised during client
copy/client
deletion-> To
accelerate Table
Deletion tasks

Examples of
relevant monitoring
tools:

- SAP GUI
Transaction SCC3
– Client copy
monitor

- SAP GUI
Transaction SM50
– Check client
copy work
processes. You can
see which job has
been running for
long, and what
kind of task is
being executed.

- SAP GUI
Transactions DB02
and
DBACOCKPIT –
Check from DB
level, for any
expensive SQL
being executed.
10 Technical This can occur due to In each release, where BEx - SAP Note
– Simplifications. queries that call Operational 2556089 - S4TWL
Deactivate Simplifications started Data Providers (ODP) are - Simplification in
d BEx with SAP S/4HANA used in the SAP Business Position Reporting
Queries 1511 and are still Suite, these BEx queries must for Financial
ongoing throughout be converted to CDS View Transactions
subsequent SAP queries in SAP S/4HANA.
S/4HANA releases. That is, BEx queries that call - SAP Note
the new CDS interface views. 2555990 - S4TWL
Refer to the related - CM: Unification
Simplifications in the of Technologies for
Simplification Catalog. Analytical Data
Provision

Public 101/122
 - SAP Note
2547347 - S4TWL
- CM: Commodity
Position Reporting
on Versioned
Pricing Data
11 Technical Occasionally issues Your support team should - SAP Note
– can be browser- always have access to an 2922263 - Webgui
Unexpecte specific, e.g. import alternate web browser to FSM: Clipboard
d issues in data from clipboard not confirm if an issue is specific access in Google
web working in SAP GUI to a certain web browser. Chrome 81
browsers for HTML transactions Check you are using a
due to with Chrome browser. supported browser as - SAP Note
changes in explained in section 2.5.10.1 2658822 - Release
SAP GUI Operating environment for notes for SAP GUI
for HTML business users for HTML (short
WEBGUI)
Keep in mind that SAP GUI
for HTML issues are fixed - SAP Note
with SAP Kernel patches and 2412840 - Kernel
Unified Rendering patches. Patch
SAPWEBGUI.SA
R

12 Technical This can be caused by Use the logs to analyze the SAP Note 2050604
– Errors in unexpected conflicts, errors and check for related - Problem analysis
the such as clashes in CDS SAP Notes for affected CDS in upgrade: Phase
ACT_UP View names. Views. ACT_UPG
G phase
SAP Note 3052823
- Agricultural
Contract
Management 2020
FPS1: CDS View
'I_ACMContractCo
unterparty' SQL
view name
correction

13 Functional In certain scenarios, SAP S/4HANA features MRP Live (MD01N); a

– New new functionality can new MRP run optimized for SAP HANA.
functionali impact classic
ty impact functionality. MRP Live reads material receipts and requirements,
on classic calculates shortages, and creates planned orders and
functionali For example: Material purchase requisitions all in one database procedure.
ty Requirements Planning This minimizes the volume of data that has to be
Live (MRP Live) copied from the database server to the application
versus classic Material server and back, which considerably improves
Requirements Planning performance.
(MRP)

Public 102/122
 MRP Live also has some restrictions listed in SAP
MRP Lists were Note 1914010 - MD01N: Restrictions for Planning
available in the earlier in MRP Live on HANA. One such major restriction
SAP S/4HANA is that MRP Live does not write MRP lists.
releases but were
removed in later MRP lists were intended for checking the MRP
releases due to the result. MRP lists were used to find materials with
introduction of MRP issues quickly. MRP lists are snapshots of the
Live. material supply and demand situation at the time of
the last MRP run. This snapshot is often outdated.
Refer to: S/4HANA With the HANA Database, stock/requirements lists
MRP – to Live or not can be read with high speed. Therefore, with SAP
to Live: MRP lists S/4HANA there was supposed to be no need for
outdated MRP lists. However, stock/requirements
lists do not resemble the same situation as MRP list
results in all scenarios. MRP Live currently doesn’t
provide a tool to check and verify MRP run results
N/A
13 Functional With SAP S/4HANA To get the pre-delivered SAP Note 2901247
- Pre- 1909, a new content, you need to manually - Sample
delivered functionality has been transport it to your working Configurations of
content introduced to speed up clients. Intercompany
unavailabl intercompany Matching and
e for reconciliation process Reconciliation(On
Intercomp from company close to Premise) explains
any corporate close. further steps to
Matching Intercompany implement the pre-
and Matching and delivered content.
Reconcilia Reconciliation (ICMR)
tion is a delivered solution
(ICMR) in SAP S/4HANA,
which matches
transactions without
any ETL process and
reconciles data in real
time.

To further facilitate
and accelerate the
usage of the
functionality, SAP has
offered certain sample
configurations that
come as pre-delivered
content.

If there is a new
S/4HANA 1909
installation, the content
should be available in
the target client after

Public 103/122
 making the client copy
from 000.

However, if you
upgraded from a lower
release to SAP
S/4HANA 1909, it is
not available by
default.
14 Functional Some unexpected data This error can occur when you are using the SAP
- inconsistencies were GUI transaction FINSC_LEDGER. For example,
Unexpecte identified during the where there are existing entries in table
d data upgrade. The FINSC_LD_CMP for a ledger that no longer exists.
inconsiste consistency checks In SAP S/4HANA 1511, the validation to identify
ncies stopped in Currency this inconsistency was not available. The
during conversion settings for consistency checks in higher SAP S/4HANA
upgrade in Company code releases are stricter than in SAP S/4HANA
certain (Message class 1511.This is the reason why these error messages
Financial FINS_ACDOC_CUST are displayed during the upgrade.
Ledger number 137).
If you want to get rid of these error messages, the
only way to do so is to delete these entries directly
from the table via SE16N, which will require a SAP
Incident to be created for SAP Development support
to handle this database correction.

15 Functional “Solution “Solution Configuration ERP 630 (SLCE 630)” with

- Configuration ERP S/4HANA 1809 based on license “7018774 SAP
Additional 630 (SLCE 630)” with Solution Sales Config., up to 20”. Upgrading
add-on S/4HANA 1809 based S/4HANA to 2020 requires the add-on to be
license for on license “7018774 upgraded to “Solution Configuration ERP 800
SAP SAP Solution Sales (SLCE 800)”. This however requires a new license
Solution Config., up to 20”. for the add-on.
Sales Upgrading S/4HANA
required to 2020 requires the
when add-on to be upgraded
upgrading to “Solution
from SAP Configuration ERP
S/4HANA 800 (SLCE 800)”. This
1809 to however requires a
2020 new license for the
add-on.
16 Functional Error instead of Apply correction from SAP Note 3024875 - Error
– Cost warning message message CK-040 is wrongly raised
routing not raised
correct
17 UX – Some customers have The recommended resolution is to capture the
Deactivate found certain activated activated ICF nodes prior to activation for
d ICF ICF nodes were comparison with after upgrade. You can use
nodes deactivate during program RS_ICF_SERV_ADMIN_TASKS to
upgrade. export the list of activated ICF nodes.

Public 104/122
 18 UX – Deactivation of OData There is a custom report to identify these services
Deactivate services can occur prior to the upgrade in blog post Mass OData
d OData when the OData Unassign. You then have the option to add the
Services service is activated as a services to a transport request.
temporary object in the
task lists (without
defining a transport).
19 UX – Lost In-app extensions can This can happen if the configuration in the
in-app be lost if they were Adaptation Transport Organizer, transaction
extensions saved against S_ATO_SETUP, is set to use temporary packages.
temporary packages Check the Adaptation Transport Organizer has been
rather than transport configured appropriately.
requests.
20 UX – During the upgrade You need to map new system SAP Note 2495630
Reference process, new system aliases to RFC Destinations. - Reference lost
lost due to aliases are introduced displayed in Fiori
missing in table You can make these changes: Launchpad
system /UI2/SYSTEMALIAS Designer
alias as new content is - Manually in SAP GUI
deployed. Transaction SM30 using
maintenance view
/UI2/V_ALIASMAP, or

- Automated by running task

list
SAP_FIORI_FOUNDATIO
N_S4, step Assign System
alias to S/4 System Alias to
update this table in your
sandbox/development
environments, and to generate
a transport request to apply
these changes to other systems
in your landscape.
21 UX – When moving from Go to transaction SICF and - SAP Note
Reference SAP S/4HANA 1511, activate ICF nodes: 2621243 Enable
lost errors 1610 or 1709 to SAP SAP Smart
for SAP S/4HANA 1809 or /sap/bc/ui5_ui5/sap/ssbtileslib Business for
Smart higher releases, the s1 – library for smartbusiness S/4HANA
Business ICF nodes for Smart tiles
KPI tiles Business apps have - SAP Note
been changed and new /sap/bc/ui5_ui5/sap/ssbtiless1 2500794 Fiori
nodes need to be – Smart Business Runtime Launchpad
activated. Tiles Designer: Tiles of
analytical
Starting with SAP S/4HANA applications cannot
1909, SAP Fiori app F2814 be displayed
Manage KPIs and Reports app properly
replaces SAP Fiori apps
- SAP Note

Public 105/122
 F0814 KPI workspace and 2701036
F2319 Report Workspace. S/4HANA 1809
Error Loading Tile
for Smart Business
Tiles in Fiori
Launchpad
Designer
22 UX – From time to time, as The current recommendation openSAP
Reference the content of SAP is to: microlearning
lost errors Business Roles is 1. In the SAP Fiori apps Refining Business
due to adjusted, tile reference library, compare Roles with SAP
changes in definitions and target the Implementation Fiori Launchpad
technical mappings can be Information for the app for Content Manager
catalogs reassigned to different your source and target
technical catalogs. If SAP S/4HANA Release to
you have created a identify the new technical
custom business catalog.
catalog that references
these entities in the 2. Correct the references in
technical catalogs, you your custom business
may experience catalog as part of your
Reference Lost errors follow-on activities during
in the SAP Fiori upgrade, preferably using
launchpad and the SAP Fiori launchpad
Launchpad Designer. content manager tool.

23 UX – Each new SAP Your user experience will openSAP

Unexpecte S/4HANA release change after upgrade where microlearning
d changes includes new SAP SAP Business Roles are Refining Business
in custom Fiori apps and grows assigned directly to users, or Roles with SAP
roles due the amount of SAP where SAP Business Catalogs Fiori Launchpad
to changes Fiori coverage in are assigned directly to custom Content Manager
in SAP related SAP Business roles. This is expected.
Business Roles. This requires
Catalogs changes in the content Important: Individual SAP openSAP
of SAP Business Business Catalogs can be used Microlearning
Catalogs, which are a in multiple SAP Business Creating
subset of SAP Roles or in assigned to your Launchpad Content
Business Roles. own custom roles. with the SAP Fiori
Launchpad App
If you need to minimize Manager
changes to existing users, you
can use the SAP Fiori openSAP
launchpad content manager to Microlearning
copy the SAP Business Activating SAP
Catalogs to the customer Fiori Content in
namespace. You can then Custom Business
refine and control the content Roles
of your custom business
catalog, and assign it to your

Public 106/122
 custom roles instead of
directly using SAP Business
Roles.

Make sure you check the

original SAP Business Catalog
for changes, such as
deprecated apps and their
successors. Adjust your
custom business catalog as
needed. Preferably this should
be done in your sandbox or
development environment.

Communicate any changes in

the SAP Fiori content to your
users before go-live.
24 UX – Occasionally, new Recommended resolution is to - Speed Up your
Unexpecte standard themes and use the personalization options SAP Fiori support
d issues in custom themes can in the SAP Fiori launchpad incidents
standard have unintended side User Actions menu to change
or custom effects on classic user to a standard SAP theme and - Finding the
themes interfaces and SAP confirm that the behaviour is technical name of
Fiori apps. These an app
specific to a theme.
problems do not occur
when using other - SAP Note
themes. You can then report this as an 2761326 - SAP
For example: SAP incident for resolution. GUI for HTML:
- [ENTER] key not When reporting issues, raise a Unexpected results
working in SAP GUI SAP Incident giving the exact or sizes
for HTML transactions App Id, and using the
designated application
- Selected dates cannot component for support of the
be seen in My Leave app. These details can be
Requests found in the SAP Fiori apps
reference library, and via the
User Actions > About Feature.
Remember to specify the
themes affected.

25 UX – Changes to search Running the following steps is - SAP Note

Search connector models have recommended: 2790616 -
connector been occurring since Enterprise Search
model the release of SAP - Re-index connectors after Models :
updates S/4HANA 1610 where and before the upgrade via Availability of
connector development task-list CDS based Search
was based on SAP_ESH_INDEX_USER_A models in 1909 On
BW/INA. In SAP UTHORITY Premise
S/4HANA 1909 and

Public 107/122
 higher releases a large - Run task list - SAP Note
number of search SAP_ESH_CONSISTENCY_ 2889953 -
connectors are now CHECK to identify issues in Deactivation of old
based on OData and search connectors retail ESH search
CDS Views. Multiple models in SAP
SAP Notes have been - Run task-list S/4HANA
delivered depending on SAP_ESH_UPDATE_SC to
specific errors. activate new search - SAP Note
connectors 2690843 - CDS
- Run report based search
ESH_REFRESH_RUNTIME_ connector
BUFFER "Products"

As a last resort if issues are - SAP Note

still unresolved, you can run 2888521 - Fiori
task list SAP_ESH_RESET Business Catalogs
and reactivate search assigned to
connectors with task list S4HANA
SAP_ESH_INITIAL_SETUP Enterprise Search
_WRK_CLIENT Models
- SAP Note
2462053 -
'Metadata call for
model XXX was
not successful' in
/n/iwfnd/maint_ser
vice

26 UX – Lost Setting configuration If you are upgrading from a - Setting

SAP Fiori parameters using a lower SAP S/4HANA release, Parameters in SAP
Launchpa launchpad you are recommended to move Fiori customizing
d config configuration file was all configuration parameters to
file deprecated in SAP setting parameters in SAP - Setting
S/4HANA release Fiori customizing using the Parameters in a
1809. transactions Launchpad
/UI2/FLP_SYS_CONF (cross Configuration File
client) or (Deprecated)
/UI2/FLP_CUS_CONF
(client-specific).

Public 108/122
6. FREQUENTLY ASKED QUESTIONS (FAQ)

6.1. General

What is the difference between an SAP S/4HANA system conversion and an SAP S/4HANA
upgrade?
SAP S/4HANA is a new product line, which is completely separated from the classical SAP Business
Suite. This is why we use the term “system conversion” (and not “upgrade”) for the migration from the
classic ERP system running on AnyDB to the SAP S/4HANA system which runs on SAP HANA.
You move from one SAP product (Business Suite) to the completely new one (S/4HANA), built on the
new architecture and data models, containing renewed applications and new UI technology (SAP Fiori).
A system conversion is a move from SAP ERP and SAP Simple Finance (1503 or 1605) to SAP
S/4HANA (1511 or higher). It involves moving to the SAP HANA database, removing unsupported add-
ons and deprecated functionality, moving to the new architecture and data models and executing a data
conversion from old table-based data structures to the new SAP S/4HANA data models based on CDS
Views.
Once your system is on SAP S/4HANA, you can in the future upgrade from your current SAP S/4HANA
release to a higher SAP S/4HANA release.

What are the risks if we do not upgrade from our current SAP S/4HANA release?
Once your SAP S/4HANA release reaches the end of maintenance date, SAP can provide extended
maintenance for an additional maintenance fee. After the supplementary maintenance agreement has
expired, the release automatically enters customer-specific maintenance, where additional maintenance
fees must be paid and there is a restricted scope of services.
The expiry dates of mainstream maintenance and extended maintenance are published in SAP’s Product
Availability Matrix and SAP Release Strategy.
SAP Release and Maintenance Strategy provides a description of all maintenance phases.
Important: New features and capabilities will not be downported to earlier releases. That is, unless and
until you upgrade you will not be able to access:
• new SAP Fiori apps
• new SAP Fiori launchpad features, e.g. new search objects, new notification providers
• new intelligent technologies scenarios
• new business processes
• new business models
• new maintenance and implementation tooling
Refer to:
• SAP Note 52505 Support after end of mainstream maintenance or extended maintenance
• SAP S/4HANA Release and Maintenance Strategy, and Related Commercial Terms for the On-
Premise Edition

Is the SAP Pathfinder report suitable for our SAP S/4HANA upgrade?

Public 109/122
Yes, the SAP Innovation and Optimization Pathfinder report is now also available for SAP S/4HANA
upgrades.

6.2. Functional

Why are simplification checks needed for upgrades?

Simplifications started with the first release of SAP S/4HANA 1511 and are ongoing as part of the SAP
S/4HANA roadmap as different modules and processes are being renewed. You can review all of the
Simplifications across all SAP S/4HANA releases in the Simplification Catalog.
The Simplification Item Check serves two purposes:
1. Relevance check: Determines which Simplification Items are relevant for the specific SAP
S/4HANA release in which you are running the Simplification Item Check. This will help you to
assess the functional and technical impact of the upgrade on your system.
2. Consistency check: During the upgrade process some parts of your solution may need to be
migrated to new data structures and new processes. The data conversion routines rely on
consistent data in order for this to happen automatically. If the Simplification Item Check
identifies data inconsistencies or missing mandatory preparation activities which could cause the
upgrade to fail, it will make you aware of these issues so you can correct or exempt them before
the actual upgrade starts.

How can we know the differences between our current SAP S/4HANA release and the latest
release?
You can get to know the delta between SAP S/4HANA releases using the SAP S/4HANA What’s New
Viewer, the Simplification Catalog, and the SAP Fiori apps reference library.
Refer to section 1.4 Business functionality impacts.

How do we approach financial closing in the month of go-live?

Monthly financial closing must be avoided during the DMO runs. Whether you run the month-end
closing before or after your SAP S/4HANA upgrade go-live is a choice and needs to be discussed with
your business subject matter experts.

6.3. User Experience

If we are currently using an SAP Fiori app that has a successor app, are we required to use the
successor app on upgrade?

There are two possible scenarios that determine whether you need to change from your currently used
SAP Fiori app to a successor app:

1. If your current SAP Fiori app is a deprecated app, it will no longer be available after upgrade. You
must move to the successor app.

Public 110/122
 2. If your current SAP Fiori app is marked as an alternate app, this means both your current app and
the successor app are available after upgrade. You can choose whether to continue with your
current app or move to the successor app.

Important: any new features will only be made available on the recommended successor app. This
includes new extension and personalization options.

Will our extensions to SAP Fiori apps still work after upgrade?
Provided the SAP Fiori app still exists and has not been deprecated, existing extensions will be retained.
However, because the app behavior and SAPUI5 control behaviors may have changed as part of upgrade,
all extensions must be:
• Reviewed to check that the extension is still needed, e.g. the upgrade may have provided equivalent
features in standard
• Regression tested to ensure the intended behavior is retained alongside the upgraded standard
behavior

Important: The SAP S/4HANA What’s New Viewer documents major changes to an app. More minor
behavioral changes can impact any app, such as changes to the behavior of SAP Fiori elements
floorplans.
For example:
• From SAP S/4HANA 1909, many of the SAP Fiori elements floorplans now include Export to
Spreadsheet as a standard feature. Customers who had extended apps to include an Export to
Spreadsheet feature should remove those extensions and revert to the standard behavior.
• From SAP S/4HANA 2022, many of the SAP Fiori element floorplans now include Export to PDF
as a standard feature.
• From SAP S/4HANA 2022, integration with Google Workspace and MS Teams is a standard
offering via the SAP Document Management service (please note additional licence may be
required). Refer to blog post SAP Fiori: What’s new for SAP S/4HANA 2022 (on-premise and
private cloud)
There may be additional rework required if your extension uses a deprecated SAPUI5 control or API
method.

Refer to section 2.5.13 Upgrading custom SAP Fiori apps for more details.

If the existing SAP Fiori app has been superseded, typically the successor app is an entirely new app.
This means frontend extensions to the SAP Fiori (SAPUI5) components are likely to be different.
Backend extensions (e.g. BADIs in the SAP S/4HANA system) will remain unchanged. Usually
successor apps offer improved behaviors and extension capabilities. So fit-to-standard analysis and
assessment of extension options must be reassessed as you would for any new app.

Will our custom-built Fiori apps need to be remediated after upgrade?

Custom Fiori apps need to be tested and verified during your upgrade project. In most cases there is
minimal rework required, provided best practice recommendations for SAP Fiori apps and SAPUI5 have
been followed. However, there may be additional rework required if:

Public 111/122
 • You are upgrading from SAP S/4HANA 1511 and need to adapt apps to SAP Fiori 2.0 design
requirements
• Your app uses a deprecated SAPUI5 control or API method

Refer to section 2.5.13 Upgrading custom SAP Fiori apps for more details.

We have modified an SAP Fiori app. Will it show up in SPAU or will it simply be overridden?

SAP Fiori apps typically consist of multiple components that may be affected in different ways via
modifications.
• ABAP components – including the backend OData Service and underlying CDS Views; and may
also include additional code in BOPF (Business Object Processing Framework) objects or ABAP
RESTful Programming Model objects.
• SAPUI5 components – HTML, XML, and JSON files which are stored in your ABAP foundation as
BSP applications

All these components are tracked for modification.

If an SAP object has been modified (usually due to an advanced correction) then a notification for the
relevant object will be raised during SPAU. Developers have two possible responses to the notification:
• Adopt the new (upgraded) standard code, or
• Keep existing (pre-upgraded code).
If you select adopt, then the modification will be overwritten with the new upgraded code from SAP, i.e.
the SAP standard code. If a developer has previously modified this SAP standard code, then adopting
SAP standard will overwrite the modification.
If you select keep, then the existing pre-upgraded code will be kept. However, this can cause conflicts
with upgraded code, and inconsistent or unexpected behaviors, which you will need to resolve. SAP does
not support custom modifications.
Important: If you have modified a SAP Fiori app in a previous release, to avoid ongoing conflicts in the
current and future releases, you should revert to an accepted extension approach instead, such as:
• Extensions supported by the SAP Fiori app and detailed in the Extensibility Documentation of the
app in the SAP Fiori apps reference library
• Side-by-side extension using SAP Business Technology Platform

For further information on approved extensions refer to:

Custom Extensions in SAP S/4HANA Implementations – A Practical Guide for Senior Leadership

6.4. Technical

How can we reduce the downtime of our SAP S/4HANA upgrade?

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 described in chapter 3.2.1 Downtime optimization options. With
Software Update Manager, the technical downtime can be reduced by either using near-Zero Downtime
Maintenance (nZDM) or Zero Downtime Option (ZDO).
Important: Read the SAP Note carefully. Some of the measures are specific to specific SAP S/4HANA
releases.
Refer to:

Public 112/122
 • SAP Note 2351294 - S/4HANA System Conversion / Upgrade: Measures to reduce technical
downtime

Why is custom code remediation needed for upgrade of SAP S/4HANA?

While many of your custom code adjustments will have been made when you first moved to SAP
S/4HANA, some further simplifications of ABAP have occurred across subsequent SAP S/4HANA
releases.

Refer to:
• Blog post SAP S/4HANA System Conversion – Challenge for your custom code
• SAP Note 2190420 - SAP S/4HANA: Recommendations for adaption of customer specific code

Are there any major Data Dictionary changes for SAP S/4HANA upgrades?

You should check the Simplification Items Catalog for these types of changes.
For example:
• SAP Note 2628654 - S4TWL: Amount Field Length Extension
From SAP S/4HANA 1809, currency amount fields with a field length between 9-22 including 2 decimals
have been extended to 23 digits including 2 decimals. In addition to currency amount fields, selected data
elements of DDIC type DEC, CHAR, and NUMC with varying lengths and decimal places that may hold
amounts have been affected.
The amount field length extension must be explicitly activated in customizing.
Read the SAP Note 2628654 carefully to understand the impact and requirements.
Decide if you want to keep the current length or to extend it.

What is the maintenance lifecycle for the add-ons for SAP S/4HANA?
There is no common on maintenance lifecycle for the add-on for S/4HANA, you need to refer to the SAP
standard documents for the compatibility information.
You need to run the maintenance planner tool as a first step in the upgrade process. It checks your
components, add-ons, and business functions to ensure compatibility with the SAP S/4HANA release to
which you are upgrading and creates the stack file used during the upgrade process (done by the Software
Update Manager tool).
For example: For the GRC add-on for S/4HANA, you find the maintenance lifecycle information in SAP
Note 2229853 - GRC and S/4HANA oP: compatibility information
Refer to:
• SAP Note 2214409 - SAP S/4HANA: Compatible Add-Ons

How can we find authorization changes?

Public 113/122
After the upgrade, you must do some follow-up activities to adjust authorizations. The default
authorization values are the data basis for the provision of authorizations required for applications in the
Profile Generator (SAP GUI Transaction PFCG). Default authorization values for standard SAP
applications are delivered via upgrade, support package deployment, or SAP Notes. This SAP-provided
data is displayed and maintained in transaction SU22. Customer default authorization values are
maintained in transaction SU24. Only these customer default authorization values are applied when
PFCG is used.

After the upgrade the SAP default values may have been changed. You therefore must use transaction
SU25 to carry out a comparison of the default values (steps 2a and 2b) and transfer the default values
maintained by SAP.

For more information about this process, refer to:

• SAP Note 1539556 - FAQ | Administration of authorization default values
• SAP Note 440231 - SU25 | FAQ: Upgrade postprocessing for Profile Generator.
• Blog post Getting back to Standard Proposals with SU24 Authorisation Variants

6.5. Services

What services are included in our SAP maintenance agreement to support our upgrade?

SAP provides different offerings for different maintenance agreements. See more details in chapters
2.5.16 - 2.5.19 of this document.

What other services are provided to support your upgrade?

You can apply for your upgrade project to be supported by the SAP S/4HANA Customer Care program.
This program helps your project to be a success by offering:
• A named Project Coach serving as a remote
contact to share best practices and collect feedback.
• A named Development Angel facilitating the
access to the SAP S/4HANA development organization

The offer is free of charge. To apply please send an e-mail to [email protected].

Public 114/122
7. ADDITIONAL INFORMATION RESOURCES

The following are a list of resources helpful for further learning, documentation, blog posts and videos.
While many of these are also relevant to any customer moving to SAP S/4HANA, they are also resources
for the latest SAP S/4HANA release.

7.1. openSAP Microlearning

Short how-to video playlists for business users and experts alike. New videos are added over time.

openSAP Microlearning videos can be accessed at https://microlearning.opensap.com/

Look for the SAP S/4HANA how-to playlists.

The following videos in the SAP S/4HANA playlist are specifically relevant to upgrades:
• Cross-Topics – Working with the What’s New Viewer
• Cross-Topics – Finding delta simplifications between SAP S/4HANA releases
• Cross-Topics – Finding available SAP Fiori apps
• Cross-Topics – Activating SAP Fiori apps with Rapid Activation
• Cross-Topics – How to Patch your SAP Fiori (SAPUI5) version and Why

The following videos in the SAP S/4HANA playlist are useful for adjusting your content:
• User Experience – Refining Business Roles with SAP Fiori Launchpad Content Manager
• User Experience - Activating SAP Fiori Content in Custom Business Roles
• User Experience – Adapting the UI of List Report Apps
• User Experience – Creating Launchpad Content with SAP Fiori Launchpad App Manager

Watch for more videos in the SAP S/4HANA User Experience.

Figure 60 - openSAP microlearning SAP S/4HANA playlist

7.2. openSAP courses

Public 115/122
Free comprehensive online open course trainings for everyone.
openSAP courses can be accessed at https://open.sap.com/courses
They include many courses relevant to SAP S/4HANA, SAP Fiori, and intelligent technologies used with
SAP S/4HANA.

Recommended SAP S/4HANA courses include:

• Gain Technical Knowledge on SAP S/4HANA Cloud, Private Edition
• New Employee Business Partner Model in SAP S/4HANA
• SAP S/4HANA Embedded Analytics
• Gain Experience with SAP S/4HANA – Logistics
• Gain Experience with a System Conversion to SAP S/4HANA
• Gain Experience with Business Partner for SAP S/4HANA Conversion
• Delivering Value with Intelligent Innovations in SAP S/4HANA
• Guide your SAP S/4HANA Project to Success
• Building Tomorrow’s ERP with SAP S/4HANA
• How to Deliver a Great User Experience with SAP S/4HANA
• Key Functional Topics in a System Conversion to SAP S/4HANA
• Key Technical Topics in a System Conversion to SAP S/4HANA

Related courses include:

• Developing and Extending SAP Fiori Elements Apps
• Building Apps with the ABAP RESTful Application Programming Model
• SAP Fiori Overview: Design, Develop, and Deploy
• Evolved Web Apps with SAPUI5
• Enter Next-Level Bot Building with SAP Intelligent RPA 2.0
• How to Build Chatbots with SAP Conversational AI
• Building Apps with the ABAP RESTful Application Programming Model
• Efficient DevOps with SAP

Figure 61 - openSAP courses on SAP S/4HANA annd SAP Fiori

Public 116/122
 7.3. openSAP podcasts

Inside SAP S/4HANA – the official SAP S/4HANA podcast series.

Figure 62 - Inside SAP S/4HANA podcast series

7.4. SAP Community topics

Blog posts, question & answer, and learning material from the SAP Community – SAP customers,
partners and employees.

SAP Community topics can be accessed at https://community.sap.com

• SAP S/4HANA
• SAP Fiori for SAP S/4HANA
• SAP Fiori
• SAP Fiori elements
• SAP Business Application Studio
• ABAP Development

Public 117/122
Figure 63 - SAP Community topic SAP S/4HANA

7.5. SAP Learning Journeys

Career paths defined by SAP via SAP learning Journeys tool that provides proper list of activates to be
followed in order to get an expert.

There are 2 ways to access the SAP Learning Journeys:

1. Access Learning Journeys directly in the SAP Help Portal

2. Access Learning Journeys via the Learning Hub

Figure 64 - Learning Journeys for SAP S/4HANA shown on the SAP S/4HANA product page in the SAP Help Portal

Public 118/122
 7.6. Useful SAP Notes and recommended blog posts
In addition to the many references included in this document, you should also consider these.

Useful SAP Notes:

• SAP Note 2916959 - Fiori Performance Troubleshooting

Recommended Blogs:
• Let’s talk SAP S/4HANA AnyPremise Upgrade
• How and Why to Upgrade your SAP Fiori for SAP S/4HANA solution
• SAP S/4HANA conversion or upgrade – Do not wait to run Simplification Item Check
• Large or Small: ERP Solutions from SAP

Customer/Partner blogs:
• Upgrade to SAP S/4HANA 1909 – Lessons Learned
• SAP S/4HANA On-Premise (AnyPremise) Release Version Updates 1511 – Current State

Public 119/122
www.sap.com/contactsap

© 2020 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product
specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This
document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by
SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and
they should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product
and service names mentioned are the trademarks of their respective companies. See www.sap.com/copyright for additional trademark information and notices.
8. APPENDIX

8.1. Additional SAP Solution Manager details

The following SAP Solution Manager information is not specific to an SAP S/4HANA upgrade but
applies to any SAP solution upgrade.

8.1.1. Using Solution Manager to manage your regression testing

Solution Manager 7.2 provides multiple capabilities to managing your upgrade from identifying
changes in business processes, to scooping and executing critical test cases.

The SAP Solution Manager Test Suite can help you plan and manage your regression testing, and
the testing of any new functionality introduced as part of the upgrade or post the upgrade process.

Figure 32 - SAP Solution Manager Test Suite components and major capabilities

The Test Suite is a full-featured application for manual/automated testing and change impact
analysis. Its functional scope includes:
• Manual and automated functional tests
• Automated change impact analysis of maintenance activities for test scope optimization of
regression tests
• New requirements triggering semi-automated test planning for user acceptance tests and
functional integration tests
• High degree of test automation possible
• Supports agile development approach within requirements to-deploy process through
Focused Build for SAP Solution Manager
• Seamlessly integrated with other components of SAP Solution Manager such as Process
Management, Solution Documentation, ChaRM, and ITSM.

8.1.2. Using SAP Solution Manager to manage the impact on business processes

Changes to Support Packages, custom developments, add-on installations, or other changes to the
system may also impact business processes.

Public 121/122
Within the SAP Solution Manager 7.2 Test Suite, the Business Process Change Analyzer (BPCA)
can assist you in managing your SAP S/4HANA upgrade in the following ways:
• Understanding changes in business processes between source and target releases
• Scoping critical test cases for regression testing
With the BPCA, you can do the following:
• Analyze which parts of a solution documentation are affected by the change.
• Analyze which parts of a solution documentation are affected by the planned activation of a
business function
• Optimize the test scope of an analysis result.
• Create test plans from the analysis results.

More information:
• SAP Solution Manager product page in the SAP Help Portal

Further links in the SAP Help Portal

• Test Suite
• Business Process Change Analyzer

Public 122/122