5e6410ba-737c-0010-82c7-eda71af511fa

SAP Fiori - Troubleshooting Guide for Financial Apps
Version 2.1
SAP FIORI - TROUBLESHOOTING GUIDE FOR FINANCIAL APPS
TABLE OF CONTENTS
VERSION HISTORY .................................................................................................................................... 4
LIST OF ABBREVIATIONS USED .............................................................................................................. 4
RELATED PRODUCTS AND SOFTWARE COMPONENT VERSIONS ....................................................... 4
IMPORTANT NOTES .................................................................................................................................. 4
TOOLS FOR ERROR ANALYSIS ................................................................................................................ 5
Deleting Caches ......................................................................................................................................... 5
Fiori Launchpad Intent Resolution Analyzer ............................................................................................ 5
Fiori Content Check ................................................................................................................................... 5
Catalog Consistency Check in FLPD ........................................................................................................ 6
Performance aspects ................................................................................................................................. 6
FIORI APP CANNOT BE OPENED ............................................................................................................. 7
Issue Description ....................................................................................................................................... 7
Issue Analysis & Resolution ..................................................................................................................... 7
ERROR SERVICE FAILED IN APP .......................................................................................................... 9
Issue Analysis & Resolution ..................................................................................................................... 9
WEB-DYNPRO/HTMLGUI APP CANNOT BE STARTED ............................................................................ 9
Issue Analysis & Resolution ................................................................................................................... 10
NEW APP IN CATALOG DOES NOT APPEAR ON THE LAUNCHPAD.................................................... 11
Issue Description ..................................................................................................................................... 11
Possible root causes ............................................................................................................................... 11
STRANGE EFFECTS WHEN EDITING FIORI-CONTENT ......................................................................... 14
Issue Resolution ...................................................................................................................................... 14
CHIP INSTANCE NOT FOUND OR PARTIALLY SAVED OBJECTS ........................................................ 14
NO OR TOO LITTLE DATA IS SHOWN IN THE APP ................................................................................ 15
ODATA-SERVICE OF FACTSHEETS CANNOT BE ACTIVATED ............................................................. 16
HOW DO I FIND OUT SAPGUI TRANSACTIONS THAT CAN BE USED ON THE FIORI LAUNCHPAD? . 16
HOW TO IMPROVE TICKET PROCESSING TIME .................................................................................... 17
TRIAL BALANCE/TRIAL BALANCE COMPERISON ................................................................................ 19
PROCESS COLLECTION WORKLIST ...................................................................................................... 19
2

APPS FOR JOB SCHEDULING OR APPLICATION LOG DISPLAY ......................................................... 19
FIORI CONTENT CHANGES IN S/4HANA FINANCE 1605 (AKA SFIN 3.0) ............................................. 20
BROKEN REFERENCES APPEAR IN DELIVERED BUSINESS CATALOGS .......................................... 20
FINANCIAL APPS ARE NOT WORKING ANYMORE AFTER UPGRADE................................................. 20
3
This document shall provide you some guidance on how to resolve issues related to SAP Fiori
content and starting apps
VERSION HISTORY
2.0 New chapters introduced:
Related Products and Software Component Versions
Important Notes
App specific issues
Upgrade related issues
2.1 Chapter How to speed up ticket processing was enhanced

New chapter How do I find out SAPGUI transactions that can be used on the Fiori launchpad
LIST OF ABBREVIATIONS USED

FLP Fiori Launchpad
FLPD Fiori Launchpad Designer
CONF Configuration mode of the Fiori Launchpad Designer
CUST 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
RELATED PRODUCTS AND SOFTWARE COMPONENT VERSIONS

Product Product Version Frontend Software Component
Version
SAP S/4HANA Finance SAP Simple Finance, on premise UIAPFI70 200
edition 1503
SAP S/4HANA Finance 1605 UIAPFI70 300
SAP S/4HANA SAP S/4HANA, on premise UIAPFI70 300
edition 1511
SAP S/4HANA 1610 UIAPFI70 400
The chapters that are not app specific can also provide help for other Fiori related software components.
IMPORTANT NOTES
Note Description
2242596 Release Information: Changes in Fiori Content in S/4HANA Finance 1605 (sFIN 3.0)
2235246 SAP S/4HANA, on premise edition 1511: Access to WebDynpro ABAP and SAP GUI
functionality via Fiori Launchpad
2269272 "Reference Lost" Error for FLP Tiles after applying new UI component version
2316443 User Default Values - Activation
4
TOOLS FOR ERROR ANALYSIS
Most issues that occur are related to cached content that should be deleted. That is why it is
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 is not working as expected, there are a couple of
tools to check the content for consistency.
In the rest of this document, there are references to the following tools:
Deleting Caches
Basically, there are three 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 -> Delete
3. 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 of
semantic object and action) can be resolved. The FLIA also allows you to check the intent for a dedicated
device 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 as
unresolvable 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:
5
Catalog Consistency Check in FLPD

The FLPD also provides some consistency checks for catalogs and a where-used list that can help to
analyze the catalog during maintenance. In comparison to the FLC (mentioned above), the consistency
check in the designer has fewer capabilities.
Performance aspects
You can add the string sap-statistics=true& to the URL. Every request to the server will then return
statistical data on how much time was spent on the frontend server, on the backend server, and on for the
remote function call.
6
Generic Problems & Solutions

FIORI APP CANNOT BE OPENED
Issue Description
Users complain that when they click on a tile, the app does not start and they receive a popup with this
message:
Issue Analysis & Resolution

The above error can have different root causes.
A. Missing Software Component
If this issue occurs for job scheduling apps or apps, displaying application logs please check if the
software component UIBAS001 is installed. For details, check the chapter for app specific issues.
B. Inactive ICF nodes
1. Call the FLP and clear your browser cache 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 probably cannot start
7
because of a deactivated ICF-Node.

Hint: Each app has two ICF app nodes and both must be active to start the app.
Activate the ICF-nodes.
5. Call the SICF transaction on the frontend server 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-name
occurs twice. Both must be activated.
6. Clear the cache.

Run the /UI2/INVALIDATE_GLOBAL_CACHES report to clear the FLP caches.
C. New UI sources:
1. Check if your gateway system has the report /UI5/APP_INDEX_CALCULATE scheduled.
For details, see the corresponding documentation.
D. 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.
8
Check that the For Local App flag is not selected.
ERROR SERVICE FAILED IN APP

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

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 an
example of the error message for the Set Controlling Area app.
9
This error occurs when LPD_CUST is used to connect frontend and backend for Web Dynpro and
transactions. From release S/4HANA Finance 1605 (aka sFIN 3.0) on, LPD_CUST entries have been
removed and app descriptors have been introduced.

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 Dynpro
application or HTMLGUI transaction is located.
This connection for these app types (Web Dynpro, 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.
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 one
entered in the target mapping.
Here in the example its SetControllingArea.
10
3. Check the system-alias.

Check if there is an RFC-connection with the same name available in the SM59 transaction and
if this connection works properly.
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 it
does not show up on the end users Launchpad.
Possible root causes

For 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.

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 the
device type and thus the tile is automatically hidden.
11
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 apps
coming 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 apps
coming 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 for
the app that causes the problems, run it for Customizing.
Call the FLPD in CUST-mode (URL extension scope=CUST). Catalogs that differ between the
customizing and configuration layers are marked with a red icon.
To delete the customizing layer, while you are in the customizing mode (!), drag the catalog to
the trash bin area. Then refresh the browser.
12
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.
13
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 of
the browser, some of the deleted objects appear again.
Issue Resolution
When deleting objects from the FLPD, wait until you get the toast message that the object was successfully
deleted before trying to delete the next object.
CHIP INSTANCE NOT FOUND OR PARTIALLY SAVED OBJECTS
Issue Description
You are creating, for example, new tiles in a catalog. When you try to save the configuration details, you
receive an error message stating that a chip instance was not found and after refreshing the browser, none
of your data was saved or only parts of the data.
Issue Resolution
This effect can occur when more than one application server is used. When a tile or mapping is created, the
OData service is redirected to one server to retrieve the GUID of the tile/mapping, but when you enter the
details and save again, the request might be redirected to a different server. If the time between the save
actions is very short, the servers might not be in sync. Then, the FLPD raises an error because the second
request wants to save data for a tile/mapping that does not exist yet on the other server.
If you have a multi-server setup, follow the instructions in SAP Note 2057804.
14
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 the
possibility to pass ABAP authorization objects. If this is used, an SQL statement is generated that
excludes 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 is
always generated. This means SU53 cannot pick up any issues and the app will not raise an error
message indicating that there is a lack of authorizations.
For more information, please read SAP Note 2147808.
Similar cases are when apps directly make use of CDS views where authorizations are modeled in
DCLs. In that case all authorizations traces only show positive results even if due to missing
authorizations the returned dataset was reduced.
If no data is shown, there could be a second reason. In very rare cases, it can happen that the artefacts of
Data Control Language (DCL) on the ABAP server are not synchronized with the database. In this case, an
initial load can be triggered with the SACM transaction. Be aware that this initial load takes some time and
should not be done during production use.
The component for problems related to DCL issues is BC-SEC-AUT-DCL.
15
ODATA-SERVICE OF FACTSHEETS CANNOT BE ACTIVATED

Issue Description
You 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 DO I FIND OUT SAPGUI TRANSACTIONS THAT CAN BE USED ON THE FIORI LAUNCHPAD?
With SAP S/4HANA, on premise edition 1511 FPS1 and SAP S/4HANA Finance 1605 the pre-delivered Fiori
content was enriched with a lot of SAPGUI transactions and WebDynpro applications so that they can be
part of Fiori catalogs and appear on the Fiori launchpad.
To figure out if a certain transaction or WebDynpro application can be used on the Fiori launchpad you can
search for it in the table of backend app descriptors.
Call transaction SE16 on the backend server and enter table SUI_TM_MM_APP. You can enter the
transaction code on the selection screen. If an entry is found you also see the technical backend catalog that
contains the transaction. From there you can put it into your own catalogs as a reference.
16
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 Fiori
apps reference library. Here is an example:
Always provide the backend system information and gateway system (if a local gateway is not used)
Provide the app version and UI5 version in the ticket
o To retrieve the versions call the about dialog of the app:
17
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), 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.
18
App Specific Issues

TRIAL BALANCE/TRIAL BALANCE COMPERISON
Issue Description
500 SAP Internal Server Error ERROR: The component table is empty (termination: RABAX_STATE)
Issue Resolution
These apps require a BI-content activation before they can be used.
For details on how to configure these apps, check out the note 2180892 or configuration guide in chapter 3.
PROCESS COLLECTION WORKLIST

Issue Description
Service UDMO_COLLECTION_WORKLIST failed. Contact your system administrator.
Issue Resolution
This app requires 2 OData-services to be activated. The primary service is
UDMO_COLLECTION_WORKLIST and the second one is FAR_DUNNING_PROPOSAL_SRV. The second
one is sometimes forgotten to be activated even if it is documented in the Fiori Reference Library.
Activate the OData-service FAR_DUNNING_PROPOSAL_SRV.
APPS FOR JOB SCHEDULING OR APPLICATION LOG DISPLAY

Issue Description
Applications that are using the job scheduling or application log framework are not starting and showing error
message Error Could not open app.
Issue Resolution
If this issue occurs for applications that are of type Transactional (Generic UI5 Job Scheduling Framework)
according to the Fiori Reference Library, please check if the software component UIBAS001 is installed on
the frontend server.
Those applications are using generic services and UIs from Netweaver and are only providing app specific
configurations that are part of the application frontend software component like UIAPFI70. So both UI
software components are required to get the apps running.
Apps of that kind in the area of Financials are for example:

Fiscal Year Change
Manage Depreciation Run
Recalculating Values
19
Upgrade Related Issues

FIORI CONTENT CHANGES IN S/4HANA FINANCE 1605 (AKA SFIN 3.0)
An upgrade from SAP Simple Finance, on premise edition 1503 (sFIN 2.0) to S/4HANA Finance 1605 (sFIN
3.0) or to SAP S/4HANA, on premise edition 1511 will lead to severe changes in the pre-delivered Fiori
content. The changes are described in detail in note 2242596.
One major change is the introduction of App Descriptor objects. App Descriptors replaced former
LPD_CUST entries.
The purpose of App Descriptors is to assign an intent, the combination of semantic object and action, to a
SAPGUI transaction or a WebDynpro application. This enables you to use SAPGUI transactions or
WebDynpro applications in the Fiori launchpad.
A first set of App Descriptors was delivered with release S/4HANA Finance 1605 (sFIN 3.0) and SAP
S/4HANA, on premise edition 1511 and already used in business catalogs as reference.
In SAP S/4HANA, on premise edition 1511 App Descriptors are available from Feature Package Stack 1 on.
BROKEN REFERENCES APPEAR IN DELIVERED BUSINESS CATALOGS

Issue Description
After applying the first Feature Pack Stack for SAP S/4HANA, on premise edition 1511 or after
upgrade/installation of S/4HANA Finance 1605, Fiori Launchpad Designer shows "Reference Lost" Errors in
Business Catalogs. When opening such a tile in the Fiori Launchpad Designer, the tile title field begins with
"Reference lost: Page X-SAP-UI2-ADCAT:SAP...".
The corresponding tiles have disappeared from the Fiori Launchpad for End Users.

Follow the description in note 2269272.
FINANCIAL APPS ARE NOT WORKING ANYMORE AFTER UPGRADE
Issue Description
Financial apps that have been running before are not working anymore after upgrade of software component
UIAPFI70 to version 300 or higher.
In the console
Issue Resolution
With UIAPFI70 300 the financial apps have been enhanced to allow the usage of user default values. Since
then the OData-service FIN_USER_DEFAULTPARAMETER_SRV must be activated.
If this is not the case the apps are not properly working anymore.
For further information see the documentation:
SAP S/4HANA, on premise edition 1511: http://help.sap.com/s4hana_op_1511_002 > Additional
Information > Product Assistance > Enterprise Business Applications > Finance > Apps for Finance
> Additional Implementation Activities for All Finance
20
SAP S/4HANA Finance 1605: http://help.sap.com/sfin300 > SAP Fiori for SAP S/4HANA Finance >
English (SAP Fiori for S/4HANA Finance Implementation Information) > Settings Needed for All
Apps
21
www.sap.com
2016 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form
or for any purpose without the express permission of SAP SE or an SAP
affiliate company.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an
SAP affiliate company) in Germany and other countries. Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices. Some software products
marketed by SAP SE and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for
informational purposes only, without representation or warranty of any kind,
and SAP SE or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP SE or
SAP affiliate company products and services are those that are set forth in
the express warranty statements accompanying such products and services,
if any. Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue
any 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 SEs or its affiliated companies
strategy and possible future developments, products, and/or platform
directions and functionality are all subject to change and may be changed by
SAP SE or its affiliated companies at any time for any reason without notice.
The information in this document is not a commitment, promise, or legal
obligation to deliver any material, code, or functionality. All forward-looking
statements are subject to various risks and uncertainties that could cause
actual results to differ materially from expectations. Readers are cautioned
not to place undue reliance on these forward-looking statements, which
speak only as of their dates, and they should not be relied upon in making
purchasing decisions.

5e6410ba-737c-0010-82c7-eda71af511fa

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

5e6410ba-737c-0010-82c7-eda71af511fa

Transféré par

Droits d'auteur :

Formats disponibles

SAP Fiori - Troubleshooting Guide for Financial Apps

Issue Description ..................................................................................................................................... 19

2.1 Chapter How to speed up ticket processing was enhanced

LIST OF ABBREVIATIONS USED

RELATED PRODUCTS AND SOFTWARE COMPONENT VERSIONS

TOOLS FOR ERROR ANALYSIS

Fiori Launchpad Intent Resolution Analyzer

Fiori Content Check

Catalog Consistency Check in FLPD

Generic Problems & Solutions

Issue Analysis & Resolution

A. Missing Software Component

B. Inactive ICF nodes

3. Clear the console.

4. Click on the tile again and check the console.

because of a deactivated ICF-Node.

Activate the ICF-nodes.

6. Clear the cache.

D. Misconfiguration of the system alias:

1. Get the system alias for your app.

2. Check the system alias configuration in the IMG.

Check that the For Local App flag is not selected.

ERROR SERVICE FAILED IN APP

Issue Analysis & Resolution

WEB-DYNPRO/HTMLGUI APP CANNOT BE STARTED

Issue Analysis & Resolution

1. Find the LPD_CUST data.

2. Find the app in LPD_CUST.

3. Check the system-alias.

NEW APP IN CATALOG DOES NOT APPEAR ON THE LAUNCHPAD

Possible root causes

Issue Analysis & Resolution

2. Check the target mapping.

4. Check if there is a customizing layer for the catalog.

STRANGE EFFECTS WHEN EDITING FIORI-CONTENT

CHIP INSTANCE NOT FOUND OR PARTIALLY SAVED OBJECTS

NO OR TOO LITTLE DATA IS SHOWN IN THE APP

Issue Analysis & Resolution

The most probable reason is an authorization issue:

1. Check if any authorization violations are shown in the SU53 transaction.

ODATA-SERVICE OF FACTSHEETS CANNOT BE ACTIVATED

1. Log on to the backend and start the ESH_TEST_SEARCH transaction.

HOW TO IMPROVE TICKET PROCESSING TIME

Try to find out if the problem is a backend or frontend Issue:

o Check if the request works without any issues or timeouts.

App Specific Issues

PROCESS COLLECTION WORKLIST

APPS FOR JOB SCHEDULING OR APPLICATION LOG DISPLAY

Apps of that kind in the area of Financials are for example:

Upgrade Related Issues

BROKEN REFERENCES APPEAR IN DELIVERED BUSINESS CATALOGS

Issue Analysis & Resolution

FINANCIAL APPS ARE NOT WORKING ANYMORE AFTER UPGRADE

2016 SAP SE or an SAP affiliate company. All rights reserved.

Vous aimerez peut-être aussi