Since its release, SAP Fiori has been constantly evolving, improving the UX and implementing the latest design standards. The current version is SAP Fiori 3.
In this blog post, we’ll walk through a sample SAP Fiori upgrade process.
The first prerequisite you need to take into account is component versions. The central component is SAP_UI, but it’s dependent on the following components:
There are some minimal requirements that can be found in the online documentation, but the optimal versions are shown in this figure.
In the documentation, you also can find information about key capabilities and prerequisites.
Note: The current documentation can be found at http://s-prs.co/v544908. From there, navigate to Set Up and Configure SAP Fiori > Setup of SAP Fiori System Landscape.
The recommended approach for any SAP software maintenance, including SAP Fiori upgrades, is to use Maintenance Planner and SUM.
Maintenance Planner will determine the required packages and their dependencies, and you will execute the upgrade process in SUM. For the upgrade itself, SUM uses the stack XML file generated by Maintenance Planner.
Note: More details about SUM can be found at https://support.sap.com/sltoolset.
Sometimes, an upgrade of SAP Fiori frontend components requires an upgrade of the backend as well. A combined upgrade of the frontend and backend is also supported and can be executed in one run using Maintenance Planner. But before executing the upgrade, it’s recommended that you familiarize yourself with the release SAP Notes for your specific SAP S/4HANA version.
For example, if you want to upgrade the frontend in version 1909, SAP Note 2769531 will offer information about dependencies with the backend version, as shown below (see highlighted text).
To access the Maintenance Planner, go to https://support.sap.com/mopz. This opens the Maintenance Planner home page (see figure below), which contains a lot of useful information, including links to navigate to more detailed documentation.
From here, navigate to the next page by clicking the Access Maintenance Planner link. The resulting page looks as shown in the next figure. This is the new, recently updated Maintenance Planner dashboard.
Next, you’ll select the system on which you want to perform the upgrade via the Explore Systems tile. In the example shown below, the system ID is S19.
The next screen presents lifecycle options for the selected system, as shown here.
From here, navigate to Plan to reach the screen shown in the next figure.
In the left part of this screen, you’ll see the current information about your system, and to the right, you’ll see the different maintenance options available for this system. Among other options, in the example above, you can see Plan an SAP S/4HANA Upgrade, as this system is on SAP S/4HANA 1909. But the option you’re looking for to proceed is Install or Maintain an Add-on. If you click this option, you’ll navigate to the screen shown in the next figure.
Flags to the right show which add-ons are already installed and can be patched. Now select the component you want to upgrade, and then select the Support Package Stack (SPS) from the dropdown to the right (see below).
Once you confirm the selection, Maintenance Planner will calculate the necessary files. Once the calculation is done, Maintenance Planner will bring you back to the planning screen. Now we have the option to select additional components to be installed or patched, or proceed to the next step by clicking Next.
After that, Maintenance Planner will navigate you through a series of screens where you can see selected and add additional files—first OS/DB files, and then ABAP/non-ABAP files.
Clicking Next takes you to a screen with a list of files to be downloaded, as shown in this figure.
On this screen, you have the option to download the stack XML file that will be used by SUM and to push files to a download basket. After you push files to a download basket, you can use Download Manager for mass file download.
Editor’s note: This post has been adapted from a section of the book SAP Fiori: Implementation and Development by Souvik Roy, Aleksandar Debelic, and Gairik Acharya.