Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert

In converting to SAP S/4HANA or upgrading SAP S/4HANA product versions, changes in the user interface can significantly impact the customers’ business processes.

Customers want to know in advance – meaning before the conversion or upgrade - which UI elements (Fiori, SAP GUI transactions, and Web Dynpro) will be deprecated, unavailable, or available with a successor in the target SAP S/4HANA release they are converting or upgrading their current system to.


App Availability Overview

Leveraging the SAP Fiori Upgrade Impact Analysis in the SAP Fiori Apps Reference Library, and based on system usage statistics, this check identifies apps using technology types SAP GUI, SAP Fiori, and Web Dynpro in the source system, which may need your attention. The check then assigns the identified apps (note that transactions in SAP GUI are considered apps in this context) to one of the following status categories:

    • Deprecated: Apps assigned to this category are still supported but outdated. The apps are considered to be in maintenance mode, and there are no new features available. If possible, the apps should not be used. You can, however, still use them, but they may no longer be supported in the future and may even be removed. The apps are usually replaced with successor apps.


    • Unavailable: Apps assigned to this category are not supported any longer. The apps may not work as expected and can no longer be used.


    • Available with Successor: Apps assigned to this category are still available in the target release; however, successor apps are available. We recommend that you use the successor app where it’s available.

Please note that the check shows not all deprecated or unavailable apps but only those the customer uses based on data from the previous 12 months. Also, note that this check does not include apps that will still be available in the target release.


Details View

The details provide information to assist customers and partners in scoping and planning the required activities.

As a next step, we recommend reviewing the apps presented in the table. You can download the results using the Export to Spreadsheet function at the top of the table to follow up on the findings. Alternatively, you can manually maintain the scoping evaluation status of each app and its recommended successor (if available) in the Scoping Evaluation Status column in the table.

Learn more about recommended successor apps by following the links provided in the Successor ID and SAP Note columns in the table. The links will take you to the successor SAP Fiori apps in the SAP Fiori Apps Reference Library and to relevant SAP Notes, helping you assess the applicability of recommended successors for your organization. If an identified app and its recommended successor are not relevant for you, you can change the scoping evaluation status to Out of Scope.

The By Scoping Evaluation Status bar chart at the top right of the screen provides an overview of the progress of this assessment and enables you to filter the table content by choosing the status In Scope, Out of Scope, or New.

In addition, the table content can be filtered by technology type (SAP GUI, SAP Fiori App, or Web Dynpro) and by status (Deprecated, Unavailable, or Available with Successor).



Data Collection

For this check, the SAP Readiness Check data collection framework captures the SAP GUI and Web Dynpro usage information from ST03N within the source system. Note that this check only displays results if usage data collected contains 12 or more months of usage statistics. For the SAP Fiori applications, the required app IDs are collected in two parts:

    1. The ST03N is used to collect the information about the used OData services.


    1. The /SDF/FIORI_ANALYSIS report reads the activated SAP Fiori app IDs and connects them with the corresponding used OData services.

Note that this check is client dependent. If your production system has multiple productive clients, the analysis must be run in each client.

To create a new SAP Readiness Check analysis for planning an SAP S/4HANA conversion, follow the description in SAP Note 2913617 – SAP Readiness Check for SAP S/4HANA.

To create a new SAP Readiness Check analysis for planning an SAP S/4HANA upgrade, follow SAP Note  3059197 – SAP Readiness Check for SAP S/4HANA upgrades.

To update an existing SAP Readiness Check analysis with the new App Availability check, you need to run the analysis for App Availability in program RC_COLLECT_ANALYSIS_DATA and upload the data collection archive to the existing SAP Readiness Check analysis.

Note that an update of an existing analysis is only possible for the same target SAP S/4HANA version.