SAP Fiori for SAP S/4HANA – Upgrade Impact Analysis

[Leslie_Castle]

As a UX specialist in the SAP S/4HANA Regional Implementation Group, my team and I often get to work with customers upgrading to a higher SAP S/4HANA release. A frequently asked question from these customers is how to work out which SAP Fiori apps are deprecated, have successors or are new in their target release.

Good news! There is now a new tool to help you quickly identify these changes so you can better plan your upgrade.

The new tool is called the SAP Fiori Upgrade Impact Analysis and it can be accessed from the SAP Fiori Apps library as shown below.

 

With the SAP Fiori Upgrade Impact Analysis, you can more easily plan your upgrade and minimise regression testing effort.

This blog post is valid from SAP S/4HANA Cloud, private edition and SAP S/4HANA 2020 onwards.

Why you need the SAP Fiori Upgrade Impact Analysis

To benefit from the latest innovations in SAP S/4HANA and SAP Fiori, you need to have a clear understanding of the impact of an SAP S/4HANA upgrade on your SAP Fiori landscape.  For example, of the apps you are using now compared to your target release: which of these apps fall into the following categories?

• No longer available (obsolete)


• Available but deprecated (soon to become obsolete)


• Available but has a new and improved successor


• Available and are still fine to use

These categories help you decide what you must change, should change as soon as possible and what remains the same.

Having this critical information will allow you to carefully plan and successfully upgrade your SAP Fiori landscape so that you can implement the latest SAP innovations and maximise the associated business benefits.

Read on, to find out how to use this tool and understand the critical information it provides you.

How to use the SAP Fiori Upgrade Impact Analysis

With the Upgrade Impact Analysis in the SAP Fiori apps reference library, you can identify the impact an upgrade will have on your SAP Fiori apps.

You should run an analysis at the upgrade planning stage. For example, before you run an upgrade from SAP S/4HANA 2020 to SAP S/4HANA 2021, you want to understand the impact on your SAP Fiori configuration. Using the SAP Fiori Upgrade Impact Analysis, you can determine the status of the apps in the target release. You can see if they're available, deprecated, obsolete, or if there are successor apps available.

To start the analysis, you upload a list of app ID’s in a .csv (comma separated value) file. Your list can include the following:

• SAP Fiori apps IDs


• SAP GUI transaction codes


• WebClient UIs


• WebDynpro ABAP applications

After you have uploaded the list, simply press the upload button to start the tool and generate the Upgrade Impact Analysis.

The impact analysis shows which apps fall into the following categories for upgrade:

• Unavailable Apps. These apps are not available or are obsolete in your target release. You cannot use obsolete apps, use the nominated successor app.


• Deprecated Apps. Deprecated apps are outdated. You should not use these apps as they will soon become obsolete. You are recommended to use a successor app where it’s available or move to the successor app as soon as possible.


• Available Apps with Successor. These apps are still available in your target release; however, these apps have been superseded and will not be improved any more. Successor apps are available with improved features. You are recommended to use the successor app.


• Available Apps. These apps are still available in your target release. No change is required.


• Unknown Apps. These apps are either incorrect or not recognized by the SAP Fiori apps reference library. For example a custom app or a Z transaction.

Once you've completed the analysis and want to find out more about the each of the apps, you can navigate from the results of the analysis to the app details in the SAP Fiori apps reference library.

For future reference, the analysis is saved under Categories > Apps Upgrade Analysis and you can also download the analysis as a .csv file.

Creating a .CSV File That Contains a List of App IDs

You can create a .csv file that contains a list of app IDs you want to analyse. When you run an Upgrade Impact Analysis, you need to upload a .csv file with this list of app IDs.

The format of the app IDs depends on the type of user interface (UI) technology. Here are some examples App IDs per UI technology.

UI Technology	Example App ID	Description
SAP Fiori	F0251	The app ID is the SAP Fiori ID.
SAP GUI	VA01	The app ID is the transaction code.
Web Dynpro ABAP	/MOC/WDA_ACTIVITY (/MOC/WDA_ACTIVITY)	The app ID consists of the Web Dynpro application name followed by the Web Dynpro application configuration name in brackets, so Web Dynpro application name (Web Dynpro application configuration name).
Web Dynpro ABAP	/SCMTMS/PAGE_LAYOUT ()	The app ID consists of the Web Dynpro application name followed by empty brackets, because there is no Web Dynpro application configuration name, so Web Dynpro application name ().
Web Dynpro ABAP	W0134	The app ID is the Web Dynpro application that has an SAP Fiori ID. The ID starts with W rather that an F to indicate it is a Web Dynpro application.
Web Client UI	TICM-OPDIS	The app ID is the Web Client application ID.

Here is an example of what a .csv file might look like:

Sample .csv file

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

• 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. For more information, refer to SAP Fiori for SAP S/4HANA – Finding the technical name of an app


• 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. For more information, refer to How to Create a Usage Profile CSV File.


• 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. For more information, refer to Creating a CSV File Using the SAP Fiori Launchpad Content Aggregator.

Refer to Creating a CSV File That Contains a List of App IDs

Running an Upgrade Impact Analysis

Before running your Upgrade Impact Analysis, ensure you Log on to the SAP Fiori apps reference library using your S-user (#1). The system will automatically log you on or prompt you for your details when you choose Run SAP Fiori Upgrade Impact Analysis (#2) as shown below:

Running an Upgrade Impact Analysis

Select a .csv file that contains a list of app IDs (#3). This file should include the app ID's that you are currently using or plan on using where you want to see the impact an upgrade will have on these SAP Fiori apps. Only the data in the first column of the file is used. If the data in a cell in this column is not a valid or recognized app ID, the system ignores this cell and moves onto the next cell.

Enter a description for your Upgrade Impact Analysis (#4) and click on Upload (#5)

Starting an Upgrade Impact Analysis

Refer to Running an Upgrade Impact Analysis

Understanding your Upgrade Impact Analysis

Using the example .csv file from above and setting the target release as SAP S/4HANA 2022, the Upgrade Impact Analysis shows the following tabs:

• Unavailable Apps – These apps are not available or obsolete in your target release. You cannot use obsolete apps. Please use a successor app where it’s available.

This tab shows you the apps that are no longer available or obsolete. Support is not provided for obsolete apps. You should remove these apps from your list of apps and replace them with the  successor apps. Where an app has a successor app, you can navigate to the successor app.

• Deprecated Apps – Deprecated apps are outdated. You should not use these apps as they will soon become obsolete. You should use the nominated successor app.

This tab shows you the apps that are deprecated. You can continue to use these deprecated apps, but you should replace them with the successor apps as soon as possible. You can use the link provided to navigate to the successor app.

• Available Apps with Successor – These apps are still available in your target release; however, these apps have been superseded and will not be improved any more. Successor apps are available with new and improved features. You are recommended to use the successor app.

This tab shows you the apps that are available in the target release and also have successor apps available. Where an app has a successor app, you can navigate to the successor app using the link provided.

• Available Apps – ‘These apps are available in your target release’

This tab shows you the apps that are available in the target release. You can continue using these apps but you might need to make changes to your configuration, such as adding a service or applying an SAP Note. To see if changes are recommended, please visit the app details.

• Unknown Apps – ‘These apps are either incorrect or not recognized by the SAP Fiori apps reference library’

This tab shows you the app IDs that are either incorrect or not recognized by the SAP Fiori apps reference library. The app IDs entered in the .csv file don't match app IDs in the library. An app ID might not match app IDs in the library because it's entered incorrectly in the file, or it's not known to the SAP Fiori apps reference library. You need to remove these app IDs from your list of apps and, if necessary, enter the correct IDs.

These apps could be for example a custom or partner app or indeed a Z transaction using SAP GUI for HTML.

Refer to Upgrade Impact Analysis - Analyzing Results

Becoming an SAP Fiori for SAP S/4HANA guru

You’ll find much more on the community topic page for SAP Fiori for SAP S/4HANA

Other helpful links in the SAP Community:

• Follow our tag SAP S/4HANA RIG for more from the SAP S/4HANA Customer Care and RIG


• See all questions and answers about SAP Fiori for SAP S/4HANA


• Follow SAP Fiori for SAP S/4HANA for more blogs and updates


• Ask a Question about SAP Fiori for SAP S/4HANA

Brought to you by the SAP S/4HANA Customer Care and RIG.

[srekapalli]

Hi Leslie,

Great news in deed. Thanks for the informative blog. This is certainly a simplified process comparing to the  previous approach to identify deprecated, delta, replacements and new apps through multiple steps in an upgrade context.

[raires]

I found this functionality very cool and practical; it will help a lot in mapping the apps. Leslie, thank you for sharing!

[former_member44171]

This is what we needed. A very great tool offered by SAP.

[awalkenhorst]

I wonder how you get the apps ids, the three options you mentioned are not really useful.

• 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. For more information, refer to SAP Fiori for SAP S/4HANA – Finding the technical name of an app
  
  
  
  • We have to open every App and not write down the appid. Sounds more like 1800s datascience. I know no one who want to do this for all apps that are assigned to users, and how do you check if you got all apps?
  
  
  
  


• 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. For more information, refer to How to Create a Usage Profile CSV File.
  
  
  
  • For this solution we need to  have run all  applications within the usual three months period. But some are not run that often. Also you don't know if you got all transactions that are assigned to users.
  
  
  
  


• 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. For more information, refer to Creating a CSV File Using the SAP Fiori Launchpad Content Aggregator.
  
  
  
  • Not available in 1909
  
  
  
  

Any table where I can find the Fiori Apps and the link to catalogues and roles?

[former_member192018]

You can use the download selected ids feature in the Fiori apps library to download CSV files with selected Fiori IDs. See the attachment

[awalkenhorst]

Thank you for your quick reply,

what we need is a list of apps that are used in our roles. I don't have the time to look at each and every app and check if it is part of our processes.

 

Could be easy if there is any table where I can find the Fiori Apps and the link to catalogues and roles?

[Leslie_Castle]

Hi Willem

Thanks for your feedback and questions. Please see my answers below.

1. For the usage profile, I will try and find out if you can use ST03 with a wider date range and update this post. For now, thorough testing and speaking with your key users to review the ST03 data should help significantly.


2. The SAP Fiori Launchpad Content Aggregator is available via SAP Note https://launchpad.support.sap.com/#/notes/3263015 for SAP S/4HANA 1909 systems. See also the excellent blog post https://blogs.sap.com/2021/05/12/sap-fiori-for-sap-s-4hana-3-simple-use-cases-for-launchpad-content-...

On a related point, you may find this blog post helpful to help you upgrade much more frequently, it's based on real life customer feedback and contains the latest tools / best practice recommendations.

https://blogs.sap.com/2022/10/31/sap-fiori-for-sap-s-4hana-customer-experiences-in-optimizing-upgrad...

BR, Leslie

[Leslie_Castle]

Hi Willem

As well as the SAP Fiori Launchpad Content Aggregator is available via SAP Note https://launchpad.support.sap.com/#/notes/3263015 for SAP S/4HANA 1909 systems , there is also the SAP Fiori Launchpad Content Manager should be of some help in your analysis:

https://help.sap.com/docs/ABAP_PLATFORM_NEW/a7b390faab1140c087b8926571e942b7/936ab6034c5f4a56aa090e2...

BR, Leslie

[awalkenhorst]

Hello Leslie,

 

I am aware of this, but I need a replacement for the very simple scenario to get all the necessery apps in one go.

In the good ol' world of R/3 I could just geht all relevant transaction codes from the table AGR_1251.

Now I am working with Fiori for a couple of years and it has improved a lot. But I can't find a solution to that very simple requirement. Event if more tables are involved, that I have to join first.

 

 

[Leslie_Castle]

Hello Willem

 

Further to your ST03 query, please see SAP Note https://launchpad.support.sap.com/#/notes/0001843151 in order to change the data retention settings, note this will only work going forward.

The SAP Fiori Launchpad Content Manager and Launchpad Aggregator should both give you links between catalogues and apps. From the Fiori Apps Library you can also make a selection and export to excel. In every implementation / upgrade project you will have to review the apps and do a fit-gap analysis.

BR, Leslie

[former_member192018]

You can also do that. I have put in a snapshot, How to select by Roles:

[awalkenhorst]

Dear Soumyadeep,

the Fiori Apps Library only has the SAP template roles. These are not the roles you find in any proper SAP System (on Premise). Catalogues and roles are created to the requirements of business. I know no one that uses SAP BR roles in production.

regards

 

[srekapalli]

Hi Leslie,

This is with reference output 'Available Apps' section discussed above from Upgrade Impact analysis tooling perspective. Looks like this is still a manual activity still to figure out if there are any changes to underlying configuration for each app in the available app list and there is no systematic way or tooling available in this regard. For eg: change of odata service version behind Display Customer list Fiori app from release 2020 FPS01 to release 2021 FPS00. Please advise.

Best Regard

Sriram Rekapalli

[Leslie_Castle]

Hi Sriram

You can look at the App Documentation and also the What's New Viewer - SAP S/4HANA.

In practice, the following also happens:

• Some floorplan changes are usual and documented centrally eg export to PDF was added with SAP S/4HANA  2022


• Occasionally apps are refactored into different business catalogs. This is documented in the Fiori apps library.


• App changes are very rare. It is the responsibility of the Product Owner to ensure the app documentation includes any changes


• Tile/TM changes are very rare… and usually have an accompanying SAP Note. 

I hope this helps but let me know if you need further info.

BR. Leslie

[ranjit_daniel]

Hi leslie thanks for this awesome blog. How do I complete a similar impact assessment on SAP business suite (hub deployment)?

We are patching software components such as GBX01HR5 605, UIHR002 and UIBAS001 to a higher SP level.

Please advise.

Thanks

Ranjit

[former_member192018]

Dear Ranjit, This feature is only available for SAP S/4HANA and not for the SAP Business suite.

 

Thanks

Soumyadeep

[zoltanfekete]

Great blog!