sap fiori - troubleshooting guide for sap s_4hana finance%2c on-premise edition

8/18/2019 SAP Fiori - Troubleshooting Guide for SAP S_4HANA Finance%2c on-Premise Edition

1/16

SAP Fiori - Troubleshooting Guide for SAP S/4HANAFinance, On-Premise Edition


2/16

TABLE OF CONTENTS

List of Abbreviations Used ............................................................................................................................. 3

TOOLS FOR ERROR ANALYSIS .................................................................................................................... 4 Deleting Caches ............................................................................................................................................... 4 Fior i Launchpad Intent Resolut ion Analyzer ................................................................................................ 4

Fiori Content Check......................................................................................................................................... 4 Catalog Consistency Check in FLPD ............................................................................................................. 5

FIORI APP CANNOT BE OPENED .................................................................................................................. 6 Issue Description ............................................................................................................................................. 6 Issue Analysis & Resolution .......................................................................................................................... 6

ERROR “ SERVICE FAILED” IN APP .............................................................................................................. 8 Issue Description ............................................................................................................................................. 8

Issue Analysis & Resolution .......................................................................................................................... 8

WEB-DYNPRO/HTMLGUI APP CANNOT BE STARTED ............................................................................... 8

Issue Description ............................................................................................................................................. 8

Issue Analysis & Resolution .......................................................................................................................... 8

NEW APP IN CATALOG DOES NOT APPEAR ON THE LAUNCHPAD ...................................................... 10 Issue Description ........................................................................................................................................... 10 Possible root causes ..................................................................................................................................... 10 Issue Analysis & Resolution ........................................................................................................................ 10

STRANGE EFFECTS WHEN EDITING FIORI-CONTENT ............................................................................. 12 Issue Description ........................................................................................................................................... 12

Issue Resolution ............................................................................................................................................ 12

CHIP INSTANCE NOT FOUND OR PARTIALLY SAVED OBJECTS ........................................................... 12

Issue Description ........................................................................................................................................... 12 Issue Resolution ............................................................................................................................................ 12

NO OR TOO LITTLE DATA IS SHOWN IN THE APP ................................................................................... 13 Issue Description ........................................................................................................................................... 13 Issue Analysis & Resolution ........................................................................................................................ 13

ODATA-SERVICE OF FACTSHEETS CANNOT BE ACTIVATED................................................................ 14 Issue Description ........................................................................................................................................... 14

Issue Resolution ............................................................................................................................................ 14

HOW TO IMPROVE TICKET PROCESSING TIME ....................................................................................... 14

www.sap.com

http://www.sap.com/corporate-en/legal/copyright/index.epx%23trademark


3/16

SAP FIORI – TROUBLESHOOTING GUIDE

This document shall provide you some guidance on how to resolve issues related to SAP Fiori

content and starting apps.

List of Abbreviations Used

FLP Fiori Launchpad

FLPD Fiori Launchpad Designer

CONF Configuration mode of the Fiori Launchpad DesignerCUST Customizing mode of the Fiori Launchpad Designer

FLIA Fiori Launchpad Intent Resolution Analyzer

FLC Fiori Launchpad Content Check

SADL Service Adaption Definition Language

SFIN SAP S/4HANA Finance, On-Premise Edition

3


4/16


TOOLS FOR ERROR ANALYSIS

Most issues that occur are related to cached content that should be deleted. That is why it’s

important for you to regularly delete the cache, especially after the application of support

packages.

If the problem is related to customer-defined content that isn’t working as expected, there are a couple oftools to check the content for consistency.

In the rest of this document, there are references to the following tools:

Deleting CachesBasically, there are 3 caches involved where a deletion could solve the problem:

1. Delete the Fiori content caches using the /UI2/INVALIDATE_GLOBAL_CACHES report.2. Delete the browser cache using the respective function in the browser, for example, for Internet

Explorer: Internet Options -> General -> Browser History -> Delete3. Delete the Metadata Cache on the Gateway-Server (only relevant after import of support packages).

To do so, make settings in the Clear Cache Customizing activity in the IMG (SPRO transaction)

under SAP Netweaver -> Gateway -> OData Channel -> Administration -> Cache Settings ->Metadata -> Clear Cache.

Fiori Launchpad Intent Resolution Analyzer

The Fiori Launchpad Intent Resolution Analyzer (FLIA) can help you to find out if an intent (combination ofsemantic object and action) can be resolved. The FLIA also allows you to check the intent for a dedicateddevice type for configuration, customizing, and personalization.The Fiori Intent Analyzer can be started with the /UI2/FLIA transaction code.

Fiori Content Check

The Fiori Launchpad Content Check (FLC) helps you to analyze your catalogs for potential issues such asunresolvable intents or tiles without mappings. The FLC can also be restricted to either configuration,customizing, or personalization. The following example shows the check results for a catalog that contains a

tile but no mapping:

4


5/16


Catalog Consistency Check in FLPD

The FLPD also provides some consistency checks for catalogs and a where-used list that can help toanalyze the catalog during maintenance. In comparison to the FLC (mentioned above), the consistencycheck in the designer has fewer capabilities.

5


6/16


FIORI APP CANNOT BE OPENED

Issue DescriptionUsers complain that when they click on a tile, the app doesn’t start and they receives a popup with thismessage: “Error – Could not start app”. This issue usually is caused by either inactive ICF-nodes or anincorrectly configured system alias.

Issue Analysis & Resolution

1. Call the FLP on your computer and try to reproduce the problem.

2. If you receive the same popup, call the browsers console (for example, by using F12 in Google

Chrome).

3. Clear the console.

4. Click on the tile again and check the console.If you get an error stating “Error: found in negative cache”, the app cannot start because of adeactivated ICF-Node. Hint: Each app has 2 ICF app nodes and both must be active to start the app.

6


7/16


Activate the ICF-nodes.

5. Call the SICF transaction and search for the BSP-name of the app.

You can find the BSP-name of the app by using the Fiori Reference Library. The BSP-nameoccurs twice. Both must be activated.

6. Clear the cache.Run the /UI2/INVALIDATE_GLOBAL_CACHES report to clear the FLP caches.

If this does not resolve the problem, a second root cause might be a misconfiguration of the system alias.

1. Get the system alias for your app.

Call the /IWFND/MAINT_SERVICE transaction and search for the OData-service of your app.The system alias is in the lower right corner.

2. Check the system alias configuration in the IMG.To do so, make settings in the Manage SAP System Aliases Customizing activity in the IMG(SPRO transaction) under SAP NetWeaver -> Gateway -> Configuration -> Connection Settings-> SAP Gateway to SAP System -> Manage SAP System Aliases.

Check that the “For Local App” flag is not selected.

7

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/


8/16


ERROR “SERVICE FAILED” IN APP

Issue DescriptionWhen users start the app, a popup is displayed saying that the service failed.

Issue Analysis & Resolut ion

This error is raised when the OData-service is not active. Call the /IWFND/MAINT_SERVICE transaction and

activate the service. The corresponding ICF-node must be active.

WEB-DYNPRO/HTMLGUI APP CANNOT BE STARTED

Issue Description

Users want to start a Web Dynpro or an HTMLGUI app but they get an error message instead. Below is anexample of the error message for the “Set Controlling Area” app.


This error message is an indicator that a connection is not properly established between the frontend server,where tile/mapping and LPD_CUST entries are stored, and the backend server, where the Web Dynproapplication or HTMLGUI transaction is located.This connection for these app types (Web Dypro, HTMLGUI transactions) is stored in LPD_CUST.

1. Find the LPD_CUST data.You can find the right role/instance by looking at the configuration details of the target mapping.

8


9/16


2. Find the app in LPD_CUST.

First, find the right role/instance and then open the Launchpad.

Within the Launchpad, search for the application where the application-alias matches the oneentered in the target mapping.Here in the example it’s “SetControllingArea”.

3. Check the system-alias.Check if there is an RFC-connection with the same name available in the SM59 transaction andif this connection works properly.

9


10/16


NEW APP IN CATALOG DOES NOT APPEAR ON THE LAUNCHPAD

Issue Description

You have added a new application to an existing catalog and transported the catalog to a target system but itdoes not show up on the end users’ Launchpad.

Possible root causesFor this problem there are several possible root causes:

1. Caches have not been cleared.2. App is not released for the device type.3. Target mapping is not part of a catalog included in the users’ role.4. Customizing layer is overwriting the configuration layer.

Issue Analysis & Resolution

1. Delete the caches.The users should delete the browser cache.The admin should delete the FLP caches by starting the /UI2/INVALIDATE_GLOBAL_CACHES report.

2. Check the target mapping.If the issue occurs only on certain device types, the target mapping was not released for thedevice type and thus the tile is automatically hidden.

3. Check if the user has a role assigned that points to the catalog that includes the target mapping.Important to understand is that if a role points to groups with, for example, 10 apps coming from

different catalogs, it is decisive to have both catalogs in that role. If one catalog is missing, all appscoming from the missing catalog are automatically hidden.

4. Check if there is a customizing layer for the catalog.If the catalog was changed in the designer in CUST-mode, a layer is created that hides new appscoming into the catalog in CONF-mode.To check if such a layer exists, use the Fiori Launchpad content check (/UI2/FLC transaction).Use the report first with the setting for “Configuration”. If the report does not report any error forthe app that causes the problems, run it for “Customizing”.Call the FLPD in CUST-mode (URL extension scope=CUST). Catalogs that differ between thecustomizing and configuration layers are marked with a red icon.

10


11/16


To delete the customizing layer, while you are in the customizing mode (!), drag the catalog tothe trash bin area. Then refresh the browser.

Hint: You can easily identify in which mode you are by checking the upper right corner: “Client: ALL” means configuration mode, a dedicated client “Client: ???” means customizing mode.

11


12/16


STRANGE EFFECTS WHEN EDITING FIORI-CONTENT

Issue Description

You quickly delete a series of tile/mappings. The objects disappear from the designer but, after a refresh ofthe browser, some of the deleted objects appear again.

Issue ResolutionWhen deleting objects from the FLPD, wait until you get the toast message that the object was successfullydeleted before trying to delete the next object.

CHIP INSTANCE NOT FOUND OR PARTIALLY SAVED OBJECTS

Issue DescriptionYou are creating, for example, new tiles in a catalog. When you try to save the configuration details, youreceive an error message stating that a chip instance was not found and after refreshing the browser, noneof your data was saved or only parts of the data.

Issue ResolutionThis effect can occur when more than one application server is used. When a tile or mapping is created, theOData service is redirected to one server to retrieve the GUID of the tile/mapping, but when you enter thedetails and save again, the request might be redirected to a different server. If the time between the saveactions is very short, the servers might not be in sync. Then, the FLPD raises an error because the secondrequest wants to save data for a tile/mapping that doesn’t exist yet on the other server.If you have a multi-server setup, follow the instructions in SAP Note 2057804.

12


13/16


NO OR TOO LITTLE DATA IS SHOWN IN THE APP

Issue Description

Users call an app and see either no data or too little data, even when the app is configured properly.


The most probable reason is an authorization issue:

1. Check if any authorization violations are shown in the SU53 transaction.2. If SU53 shows no violations, the issue could be the following:

Some apps make use of the Service Adaption Definition Language (SADL). This API offers thepossibility to pass ABAP authorization objects. If this is used, an SQL statement is generated thatexcludes all data the user is not allowed to see by evaluating the handed-over authorization objects.This technique leads to the issue that a valid SQL statement without any authorization violations isalways generated. This means SU53 cannot pick up any issues and the app will not raise an errormessage indicating that there is a lack of authorizations.For more information, please read SAP Note 2147808.

If no data is shown, there could be a second reason. In very rare cases, it can happen that the artefacts ofData Control Language (DCL) on the ABAP server are not synchronized with the database. In this case, aninitial load can be triggered with the SACM transaction. Be aware that this initial load takes some time andshould not be done during production use.The component for problems related to DCL issues is BC-SEC-AUT-DCL.

13


14/16


ODATA-SERVICE OF FACTSHEETS CANNOT BE ACTIVATED

Issue DescriptionYou are not able to activate a Factsheet-specific OData-service. The following message is displayed:

Issue Resolution

1. Log on to the backend and start the ESH_TEST_SEARCH transaction.2. Enter the corresponding connector (for example, DBOM1_H, as shown in the screenshot of the

error message above) as object type and run the report (F8) or check the connector.3. In case of an error stating that there are “no search connectors for selected scope”, activate the

corresponding search connector in the backend.

HOW TO IMPROVE TICKET PROCESSING TIME

To speed up the processing time of tickets, try these quick fixes:

• Use the correct component.To find the correct component for creating tickets, please check the app information in the SAP Fioriapps reference library. Here’s an example:

• Always provide the backend system information and gateway system (if a local gateway is not used)

14


15/16


• Try to find out if the problem is a backend or frontend Issue:o Perform all actions until you are one step ahead of the action causing the issue.o Open the developer tools of your browser (F12) and clear the shown network and console

entries.o Perform the action that causes the issue and retrieve the proper network request:

o Check if the request works without any issues or timeouts.o Provide this information and the retrieved request in the ticket to accelerate processing time.

15


16/16

© 2015 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any formor for any purpose without the express permission of SAP SE or an SAPaffiliate company.SAP and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP SE (or anSAP affiliate company) in Germany and other countries. Please seehttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademark f oradditional trademark information and notices. Some software productsmarketed by SAP SE and its distributors contain proprietary softwarecomponents of other software vendors.National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company forinformational purposes only, without representation or warranty of any kind,and SAP SE or its affiliated companies shall not be liable for errors oromissions with respect to the materials. The only warranties for SAP SE orSAP affiliate company products and services are those that are set forth inthe express warranty statements accompanying such products and services,if any. Nothing herein should be construed as constituting an additionalwarranty.In particular, SAP SE or its affiliated companies have no obligation to pursueany course of business outlined in this document or any related presentation,or to develop or release any functionality mentioned therein. This document,or any related presentation, and SAP SE’s or its affiliated companies’

strategy and possible future developments, products, and/or platformdirections and functionality are all subject to change and may be changed bySAP SE or its affiliated companies at any time for any reason without notice.The information in this document is not a commitment, promise, or legalobligation to deliver any material, code, or functionality. All forward-lookingstatements are subject to various risks and uncertainties that could causeactual results to differ materially from expectations. Readers are cautionednot to place undue reliance on these forward-looking statements, whichspeak only as of their dates, and they should not be relied upon in makingpurchasing decisions.

www sap com
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademarkhttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademarkhttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademarkhttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

sap fiori - troubleshooting guide for sap s_4hana finance%2c on-premise edition

Documents