- SAP Managed Tags:
As a SAP Fiori User Experience consultant, I often get questions from business users about SAP Fiori app troubleshooting and maintenance. Usually, the root cause of the issue when an SAP Fiori app is not working is not immediately apparent at first glance. Identifying root cause and fixing the issue would require significant effort from the Basis, Security, and Development teams and would involve navigating between multiple SAP GUI transactions to narrow down the root cause.
The F4914 App Support tool in the SAP Fiori launchpad can simplify troubleshooting by providing a starting point for troubleshooting configuration and authorization issues for SAP Fiori apps. It also allows users to download the error logs to be shared with the relevant Basis, Security, or Development admins. Additionally, administrator users can see logs generated by the activity of other users in the SAP Fiori launchpad.
For what’s available in App Support for SAP S/4HANA 2020 FPS01 to SAP S/4HANA 2022, check out the blog App Support for the SAP Fiori Launchpad by Tobias Moessle.
To launch the App Support tool for SAP S/4HANA 2023, please refer to the steps mentioned here: SAP Help - SAP Fiori Launchpad - Administration Guide - Launchpad Support Tools - Displaying Launchpad Configur...
To setup the App Support tool in SAP S/4HANA 2023, please refer to the prerequisites and steps mentioned here: SAP Help - SAP Fiori Launchpad - Administration Guide - Launchpad Support Tools - Displaying Launchp...
IMPORTANT: If you are running on SAP S/4HANA 2023, you need to apply some SAP Notes for the App Support tool to get the full features. If you are on a lower release of SAP S/4HANA, check the SAP Notes to confirm which ones you can apply to your release.
This blog post explains the new features and the SAP Notes you will need to apply to get them.
New Features
- SAP Fiori launchpad Intent Errors to help resolve app-to-app navigation issues.
- SAP Fiori Menu showing available SAP Fiori components and their versions being used for the currently launched app
- Extract SAPUI5 messages from the console log
SAP Notes
IMPORTANT: Apply the lowest SAP Note number to the highest in order and then you will not face any issues with the App Support tool.
REMINDER: Apply the latest version of the SAP Notes to get the latest features and updates.
Number | Name | Comments |
App Support: add TCD SICF to authorizations default for SUI_FLP_APP_SUP_SRV service | Apply manual steps. | |
App Support: Improved Checks |
| |
App Support: Technical correction of unit test |
| |
App Support: Intent Analysis and Fiori Logs |
| |
App Support: OData V4 support |
| |
Fiori Launchpad App Support: No information displayed for app type WDA |
| |
App Support: Information messages labeled as errors |
|
How to use the App Support Tool
Once you have setup App Support in the SAP S/4HANA system, users who have permissions for the App Support tool can go to their SAP Fiori launchpad, launch an app and view the App Support tool to get more details of the more common authorization or configuration errors.
Let’s take an example of launching F3163 Manage Business Partner Master Data SAP Fiori app as an Admin user.
1. Inside the app, I click on my user avatar and a drop-down menu appears. In the drop-down menu, I see an entry for App Support. Click on App Support.
2. The App Support tool opens in a dialog box and there is a message that it has identified problems with this app.
For an embedded SAP Fiori deployment, there are sections for App Information, SAP Fiori, and Embedded Server issues.
For a hub deployment of SAP Fiori, there are sections for App Information, SAP Fiori, Front End Server, Back End Server.
App Information shows useful information like OData Service Name, SAP Fiori ID and Application Component ID.
3. Click on SAP Fiori menu entry. It shows the available SAP Fiori components and their versions and the language, time zone, time and date formats used in the launched app.
4. Click on SAPUI5 Log Messages menu entry. This extracts the error log messages from the web browser console log. It displays the error messages in an easy to read format.
5. I see that App Support has identified issues with Embedded Server. Click on Embedded Server menu entry. App Support displays a summary of checks performed for the Fiori app, warnings, and errors received. I see warning about the ICF node for this app is inactive.
Click on Manual Check. A new tab with the SICF transaction as a SAP GUI for HTML app opens in the web browser. Activate the relevant ICF node (/sap/bc/ui5_ui5/sap/md_bsp1) to resolve the warning.
REMINDER: Make sure your user has authorization for SICF transaction, otherwise nothing will happen when you click the Manual Check button.
6. I navigate back to the App Support tool and click on Embedded Server - Authorization Errors menu entry. I see a list of errors received.
- Clicking on Read More link will navigate you to the SAP for Me SAP Note relevant to the selected error.
- I can click on Download Logs button to share the errors with other administrators.
- As an Admin user, I can filter for errors generated by other users in the system for this SAP Fiori app as well. Here, I am checking for authorization errors received by user T179_BUMASP.
For SAP GUI for HTML apps, the App Support tool looks different. Let's take an example of FB60 Creating Incoming Invoices app.
1. Inside the app, I click on my user avatar and a drop-down menu appears. In the drop-down menu, I see an entry for App Support. Click on App Support.
2. Inside the tool, I see App Information telling me that this is a SAP GUI for HTML type of application. Also shown are system SID, client number and application component ID.
3. Only front-end server errors are available. The system checks for RFC connections, active ICF services are displayed.
The SAPUI5 log messages in App Support tool can also show you more details for a Tile not shown error as in the below screenshot.
Clicking on the Download Logs button will download the logs as a Microsoft Excel file which I can share with other Basis administrators to troubleshoot further.
Another example is the F0862 My Inbox app. My Inbox app is not in codeployed mode. My Inbox shows Front-End Server and Back-End Server menus. App Support display is different for My Inbox app because the app is deployed in standalone mode.
My Inbox app's OData service has a system alias LOCAL_TGW which means it is deployed in standalone mode.
Let us know your experience and if you find any surprises or anything interesting with App Support tool.
Additional Readings
Once you have setup App Support, check out the following blogs by Tobias Moessle to learn more about user authorization troubleshooting and displaying custom error messages via the App Support tool
How to Identify Authorization Errors in the SAP Fiori Launchpad
Example implementation of a custom error message provider in App Support for the SAP Fiori Launchpad
Getting Support
The SAP support component for App Support tool is App Support Tool Integration (CA-FLP-EXT-ASI)
It is recommended to check for the latest improvement and SAP Notes related to App Support tool in SAP for Me (https://me.sap.com) using the component CA-FLP-EXT-ASI.
Becoming a 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
Brought to you by the SAP S/4HANA Customer Care and RIG
3 Comments
