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.
cancel
Showing results for 
Search instead for 
Did you mean: 
astridtschense
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.

9 Comments
srekapalli
Participant
0 Kudos
Hi Astrid,

Thanks for sharing this addition to SAP Readiness check from tooling perspective. Considering that this check is based off of usage history in last 12 months, we will still need to rely upon the 'Fiori Upgrade Impact analysis' from an upgrade context if we wanted to assess the impact overall considering all Fiori apps enabled in the eco system regardless of their use ?
stefan_mett
Explorer
0 Kudos

Hi,

i have problems loading the Readiness Launchpad. Andy Idea to solve this?

In the past it woked all fine for me

astridtschense
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Sriram,

"this check only displays results if usage data collected contains 12 or more months of usage statistics" does not mean that any app has to be used consistently throughout that period. Every app or transaction that has been used (no matter how often) in the last 12 month will be considered in the App Availability check.

If you use the SAP Fiori Upgrade Impact Analysis within the SAP Fiori Reference Library, you would use the same logic, creating a usage profile csv.file based on ST03 data.

Hope this helps!

Best Regards,
Astrid

 
astridtschense
Product and Topic Expert
Product and Topic Expert
0 Kudos
Hi Stefan,

You are probably using a web browser which blocks Third-Party Cookies. Please follow the steps in the SAP Note 3330283.

Best Regards,

Astrid
srekapalli
Participant
0 Kudos
Hi Astrid,

 

Thanks for your response. During the last upgrade from S4 HANA OP 2020 --> 2022, we have in fact prepared the list containing all Fiori Apps enabled in our non production system and store the list in .csv format. Reason was to ensure completeness from an upgrade impact standpoint whether the app has been actively used or even enabled in PRD environment but going through SDLC during the upgrade. Using this list in .csv format as Input, we have executed Upgrade Impact analysis and the results were certainly helpful. But given this offering through Readiness check, I wanted to clarify if we still need to supplement with Upgrade Impact analysis for completeness or otherwise.
stefan_mett
Explorer
0 Kudos
Thank you - The link in the note solved my issue 👍
srekapalli
Participant
0 Kudos
Hi Astrid,

Just wanted to follow up and get a response on my query above. I also would like to elaborate that we have used the fist method below (highlighted in Bold) to create our own list and then run the Impact analysis in recent upgrade project (S4 HANA 2020 ---> 2022).

Snippet from SAP Help documentation. 

You can create a .csv with a list of app IDs in the following ways:





  1. Create your own list by entering a list of app IDs in a spreadsheet.


    For example, create a list of the apps that you are using in the system that will be upgraded.




  2. Create a usage profile to collect a list of transaction codes for your SAP GUI and Web Dynpro ABAP apps based on the runtime usage in your back-end system.




  3. Use the SAP Fiori launchpad content aggregator to collect the apps ID's of apps in your SAP Fiori launchpad. If you have custom apps in your launchpad, these may appear as unknown.




Thanks in advance. 

Best Regards

Sriram Rekapalli

 
Hi Astrid,

Although I have latest version of Note 2758146 i.e. version 110 implemented in my SAP system, while running the RC_COLLECT_ANALYSIS_DATA I am not able to see App Availability check option in the report. I have uploaded the ST03N data of 12 months as well into the system. Any suggestion on how to activate App Availability option in the report



App Availability option missing


version 110 implemented



TobiasMeinzer
Advisor
Advisor
0 Kudos
Hi Anil,

please open an SAP Incident on component SV-SCS-S4R. Remote access to your system is needed for further analysis.

Thanks for your understanding.

Best regards

Tobias