SAP Fiori for SAP S/4HANA Troubleshooting Tips and Tricks

PUBLIC

Jorge BaltazarNovember 2021

SAP Fiori for SAP S/4HANATroubleshooting Tips and Tricks

2PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Fiori Troubleshooting

• Learn the basics

• Most Common Errors – Examples

• Authorizations – CDS views

• Identify what’s being consumed by the services

• Enterprise Search

• Webdispatcher

• Webdynpro

• WebGUI

• Always remember these facts and transactions

Fiori Performance

• Tips and Tricks

SAP Fiori for SAP S/4HANA Troubleshooting Tips and Tricks


Learn the basics


Learn the basicsFiori Integration Flow – Hub Deployment

SAP Backend

SAP

FrontendWeb

dispatcher

Intranet DMZ Internet

▪ SAP Backend contains RFC functions, Odata Models, CDS Views and Webdynpro objects.

▪ These development objects contain the business logic to perform any business function in SAP.

▪ Frontend server consumes these objects and exposes them through web services.

▪ Frontend server consumes web services by implementing a UI layer based on Html5, javascript, xml.

UI5 Add-ons

▪ Exposes UI layer web services for remote access through

public internet▪ Handles cross-domain requests

▪ URL redirect, filtering, rewriting

▪ Can connect to the backend or frontend

▪ Masks internal server names

▪ Consume apps

NW 7.5x

NW 7.5x

HDB

RFC

HTTP(S)

HTTP(S)

HTTP(S)

Webdynpro & ESH


Learn the basicsFiori Integration Flow – Embedded Deployment

SAP Backend

Web dispatcher

Intranet DMZ Internet

▪ SAP Backend contains RFC functions, Odata Models, CDS Views and Webdynpro objects.

▪ These development objects contain the business logic to perform any business function in SAP.

▪ Frontend server add-on components consume these objects and exposes them through web services.

▪ Frontend server add-on component consumes web services by implementing a UI layer based on Html5, javascript, xml.

FES Add-ons

▪ Exposes UI layer web services for remote access through

public internet▪ Handles cross-domain requests

▪ URL redirect, filtering, rewriting

▪ Connects to the backend

▪ Masks internal server names

▪ Consume apps

NW 7.5x

HDB

HTTP(S) HTTP(S)

UI5 Add-ons


Learn the basicsUnderstand the S/4HANA ABAP Programming Model for Fiori and RESTful ABAP Programming Model

Application

(ABAP | CDS)

Database Table

OData Service

User Interface

(Fiori)

Fiori Launchpad

OData (Open Data Protocol)

is an OASIS standard that defines the best practice for building and consuming RESTful APIs.

SAP Fiori

is a collection of apps with a simple and easy-to-use experience for broadly used SAP software functions that work seamlessly across devices –

desktop, tablet, and smartphone.

CDS (Core Data Services)

CDS is an enhancement of SQL which provides a data definition language (DDL) for defining semantically rich database tables/views (CDS

entities) in the database. The enhancements include annotations, associations, and expressions

https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata



Application

(ABAP | CDS)

Database Table

OData Service

User Interface

(Fiori)

Fiori LaunchpadRendering errors

Wrong app routing

Wrong app navigation

Missing tiles

Missing Frontend Authorizations

High UI load times



Application

(ABAP | CDS)

Database Table

OData Service

User Interface

(Fiori)

Fiori Launchpad

Inactive OData services

Inactive CDS views (DCL, DDL)

ABAP coding error

Inactive ABAP objects

Inactive Business Functions

Missing / Wrong Functional configurations

Missing Backend Authorizations

High OData response times



Application

(ABAP | CDS)

Database Table

OData Service

User Interface

(Fiori)

Fiori Launchpad

Data inconsistencies

Errors in data replication

No data


1. Always start by reviewing

available information in Fiori

Apps Library

You need to obtain:

✓ Frontend/Backend Role

✓ Business Catalog/Group

✓ Application Type (UI5, Webdynpro,

WebGUI)

✓ ICF Nodes

✓ Search Connectors

✓ Mandatory SAP Notes

Learn the basicsHow to start a troubleshooting session?


2. As a minimum prerequisite you must assign the required roles to the analysis user.

3. Log on to Fiori Launchpad and identify the object that is causing the error.

4. Open the browser’s “Developer Tools”



5. Once the “Developer Tools” are open, clear the “Developer Tools” logs and do a webpage

refresh as you will notice errors that may not correspond to the context of your app.



6. With the logs cleared, try to replicate the error conditions.


Tip:

Always check the Network and Console

section of the “Developer Tools”, they will

offer valuable details of the error.


7. In the console area, analyze the error texts…


Might not look like, but the error tells us a lot:

OData call error in service: ISU_BI_OUTSRTD_RESOLVE

OData collection/entity: C_OutsrtUtilsBillgDoc

OData operation: Count

Preliminary analysis: OData service is not active or configuration is missing, additionally a CDS view may be involved


8. In the network area select the entry in red, navigate to the preview tab and expand the error

details to find the “Error Message”.


By reading the error message we can understand that there is a missing system alias assignment for service

ISU_BI_OUTSRTD_RESOLVE, this confirms our preliminary analysis.


9. Perform corrective measures…



10. Test and validate behaviour.



11. Troubleshooting never stops…



12. Repeat steps 4-10


Preliminary analysis: SICF node is not active


12. Keep troubleshooting…


In this scenario we know there is no data

in the system so troubleshooting is

finished


Most Common Errors – Examples


In Fiori application, there is a persistence layer that uses caching mechanism. To begin every

troubleshooting session, recommendation is to “Always clear the cache”

– Clear Metadata Cache:

▫ Transaction /IWFND/CACHE_CLEANUP on Frontend Server

▫ Transaction /IWBEP/CACHE_CLEANUP on Backend Server

– Synchronize Chip Cache (Frontend):

▫ Run report: /UI2/CHIP_SYNCHRONIZE_CACHE

▫ Run report: /UI2/DELETE_CACHE_AFTER_IMP or /UI2/DELETE_CACHE

Most Common Errors – ExamplesClearing Cache


Most Common Errors – Examples OData Services not active

Hint: Error loading tiles, error “403”

Resolution Steps:– Use task list

“SAP_GATEWAY_ACTIVATE_OData_SERV

to activate missing service

Manual Step:

– Transaction /n/IWFND/MAINT_SERVICE



Hint: Factsheet is not displayed, error

“403”


“SAP_GATEWAY_ACTIVATE_OData_SERV

to activate missing service

– SICF service will get activated as part of the

task list

Manual Step:




Hint: OData call error, “No service

found for namespace”


“SAP_GATEWAY_ACTIVATE_ODATA_SERV to

activate missing service

– SICF service will get activated as part of the

task list

Manual Step:



Most Common Errors – Examples Backend Authorization Issue – Hub Deployment

Hint: Request failed, error “500”

Resolution Steps:– In the backend server, the S_RFCACL

authorization object is missing in the user

– Logon to backend server and assign the

authorization object to the end user


Most Common Errors – Examples Web Dynpro and/or Web Gui

Hint: Launchpad Designer, “Reference lost”

Resolution Steps:– Logon to frontend server and run

program /UI2/GET_APP_DESCR_REMOTE

– Run for Catalog ID in test mode

– Run for Catalog ID in non test mode

2269272 - "Reference Lost" Error for FLP Tiles after applying new UI component version

https://launchpad.support.sap.com/


Authorizations – CDS Views


Starting in S/4HANA 1511 many Fiori Applications make use of Service Adaptation Definition Language

(SADL) based OData services in order to consume and expose CDS views

SADL models are entities that are used in business applications – for example, business objects, database

tables, search views.

A SADL model is a data model like:

▪ DDIC tables or views

▪ CDS

▪ BOPF

The authorization enforcement in this process is interposed between query specification by application or end

user and data retrieval from the database


Authorizations – CDS Views

Blog: Fiori for S/4HANA – Troubleshooting Authorization concept in SADL based OData Services

https://blogs.sap.com/2017/05/26/fiori-for-s4hana-troubleshooting-authorization-concept-in-sadl-based-odata-services/


1. Identify the OData request

executed by the app using

your browser’s developer

tools. In this example:

OData Service:

MM_PUR_PO_MAINTAIN

Collection: POHeaderLists

Fiori TroubleshootingAuthorizations – CDS Views


2. Based on the collection, try

to identify if the ABAP code

implements SADL

Navigate to the implementation

class using transaction

/IWFND/MAINT_SERVICE,

select the required service and

click in the “Service

Implementation” button.



3. Once the service details are

displayed, double click on

the “Data Provider Class”

name.

Try to identify any reference to

CDS coding.



4. Once you confirm that the

OData service consumes a

CDS view navigate to

transaction SEGW and

identify the associated

CDS.

In this example:

C_PURORDMAINTAINHEADE

RLIST



5. Using ADT, find the required

CDS view and open the

“Access Control” object.

In this example:

C_PURORDMAINTAINHEADER

LIST



6. The “Access Control” object will

display the required

authorization objects.

In this example:

C_PURORDMAINTAINHEADERLI

ST



7. In transaction PFCG generate

a new role with the required

authorization objects.



8. In transaction SACM use the

Runtime Simulator. Enter the name

of the CDS view you wish to test

and the user whose authorizations

need to be checked.


Tip:

You can skip steps 5–7 and jump directly

to transaction SACM to identify the

required authorization objects


9. When you run the

simulator you will notice

the required authorization

objects and the values

used for the query

execution

Notice that a result list will be

displayed and you will be able

to identify any clashing

authorization definitions .



Identify what’s being consumed by the

services


The first step to troubleshoot an OData service

is to identify which objects will be consumed by

the service.

However, not all OData services are the same,

we can classify them depending on the

artifacts they consume:

➢ Enterprise Search

➢ CDS view

➢ ABAP

Depending on the objects that are being

consumed you will need to define the

troubleshooting path.

Fiori TroubleshootingIdentify what’s being consumed by the services


Enterprise Search

You can easily find them as the technical name of the service starts with prefix: “CB_”


1


Enterprise Search


2

3


Enterprise Search


4


CDS

There are two ways to identify these type of services.

The first one, when the technical name of the service starts with prefix: “C_” and ends with suffix:

“_SRV”


1


CDS


2

3


CDS


4


CDS

There are two ways to identify these type of services.

The second one, when the technical name of the service starts with prefix: “C_” and ends with

suffix: “_CDS”


1


CDS


2

Tip:

This implies that the OData services was

generated using the annotation

“@OData.publish: true”


ABAP

Easiest to identify, technical service name does not start with “C_” or “CB_”


Identify what’s being consumed by the services

1


ABAP


23

Tip:

Note that an entity (collection) in this type

of service may end up consuming a CDS

view. This will depend on how the service

model was defined.


ABAP


4

Tip:

Add an “External Breakpoint” to the code

to perform debugging sessions


Enterprise Search


Transaction STC02:– During the configuration of task list, transaction STC01 was used to execute each task lists from the configuration guide.

– If for some reason, you logoff after saving a task list run, you can go back and modify a save task list run with transaction STC02 to

search for it.

Fiori TroubleshootingEnterprise Search


Starting point to troubleshoot enterprise search is by using transaction: ESH_TEST_SEARCH



To monitor the status of all search connectors and obtain useful troubleshooting information for the

whole Enterprise Search engine use transaction: ESH_DASHBOARD



Webdispatcher


To troubleshoot Webdispatcher you need OS access or a Webdispatcher Visual Administration

user.

Fiori TroubleshootingWebdispatcher


Check Configuration Profile (OS level only) with command sapwebdisp -checkconfig



Analyze Webdispatcher Logs (OS level)



Analyze Webdispatcher Logs (Visual Administration)



Web Dynpro ABAP


Fiori TroubleshootingWeb Dynpro ABAP

General Steps:

1. Make sure you are using a supported browser based on the backend system's SP level: Browser supporting

2. While running a debugging session, make sure the webdynpro content

calls are being redirected to the backend server. An important number of issues are caused by incorrect url dispatching.

3. Check the Common Issues, maybe it is already a known problem.

4. Run the webdynpro application without any outer framework (Portal, NWBC) and check if the issue persists that way.

• 2083790 - How to test a function outside NWBC environment

5. Look for notes using the keywords provided in the dump, or using the class and method involved in the application.

• How to find a solution for short dumps from ST22

• If no relevant results are displayed, run a new search removing the filter by

component.

6. Check the WDABAP Home page for other troubleshooting guides and

analysis documents.

https://wiki.scn.sap.com/wiki/display/WDABAP/Browser+supporting

https://wiki.scn.sap.com/wiki/display/WDABAP/Common+issues

https://service.sap.com/sap/support/notes/2083790

https://wiki.scn.sap.com/wiki/display/WDABAP/How+to+find+a+solution+for+short+dumps+from+ST22

http://wiki.scn.sap.com/wiki/display/WDABAP


Issue not solved, what needs to be provided when opening an Incident:

• URL of the Web Dynpro application

• Step-by-step description with screenshots about the exact reproduction of the issue.

• HTTPWatch trace of the issue being reproduced. For more details on the HTTPWatch or Fiddler traces, please refer

to Tools

• Screenshot of the report WDG_MAINTAIN_UR_MIMES ran from transaction SE38.

• If possible open R/3 and HTTP connections to the system. For the HTTP connection the URL must be set to the affected

application. e.g. http://yourdomain.com/sap/bc/webdynpro/sap/wdapplication

Fiori TroubleshootingWeb Dynpro ABAP

For more details on how to open the connections please refer to SAP

Notes:• HTTP - according to SAP Note 592085• R/3 - according to SAP Note 812732

• Store Customer logon data in Secure Area - according to SAP Note 508140

https://wiki.scn.sap.com/wiki/display/WDABAP/Tools







SAP GUI for HTML (WebGUI)


Most of the problems can be solved by following the below 5

STEPS in the affected system:

1. Configuration and Routing

• While running a debugging session, make sure the WebGUI content calls are being redirected to the backend server. An important

number of issues are caused by incorrect url dispatching.

• If you are using App Finder or App Descriptors make sure the

configuration and required notes have been set up properly

• Step-by-step guide to enable Transactions in Fiori Launchpad using Application Descriptors in S4HANA On-Premise

• Step-by-step guide to enable Easy Access Menu in S-4HANA On-Premise

2. Latest Kernel

• Try using the latest kernel version available.

• Component "disp+work" should be checked.

• Click here for more details on ITS-fixes delivered in the latest kernel

Fiori TroubleshootingSAP GUI for HTML (WebGUI)

https://wiki.scn.sap.com/wiki/display/HOME/ITS-fixes+delivered+in+the+kernel

http://bit.ly/2hwxo4u

http://bit.ly/2ADsdn8

https://wiki.scn.sap.com/wiki/display/HOME/ITS-fixes+delivered+in+the+kernel

https://wiki.scn.sap.com/wiki/x/gxceGg


3. Latest CL_HTTP_EXT_ITS

• The first point when an HTTP request meets the ITS layer is the ITS HTTP request handler, called CL_HTTP_EXT_ITS. This handler class is very important, because it is responsible to build ITS frameset. The ITS frameset handles session management, XSRF

protection, correct page sizing, parameter handling, rendering modes and more features.

• Newer versions of the class CL_HTTP_EXT_ITS are always delivered in the latest BASIS Support Packages (SAP_BASIS, SAPKB... or SAPK-...INSAPBASIS). But in certain cases it is also possible to apply correction instructions via transaction SNOTE for

this class. In order to use the latest version of the handler (CL_HTTP_EXT_ITS), please apply the appropriate SAP Note and all of its prerequisites.

4. Review ITS Service Configuration (GUI Configuration).

• Are the used GUI Parameters correct?

• Check ITS related profile parameters.

• Learn more about ITS feature flags: List of Features

5. Special Cases and Troubleshooting Tools

• If you believe, that all of the above are correct (i.e. latest kernel, latest handler and correct configuration), go trough the special cases and troubleshooting tools in the ITS Troubleshooting Guide.

Fiori TroubleshootingSAP GUI for HTML (WebGUI)

https://wiki.scn.sap.com/wiki/display/HOME/CL_HTTP_EXT_ITS

https://wiki.scn.sap.com/wiki/x/FLHiGg

https://help.sap.com/saphelp_nw74/helpdata/en/4c/3a85aeb48f1ca9e10000000a42189e/content.htm

https://wiki.scn.sap.com/wiki/display/HOME/ITS+Troubleshooting+Guide


Monitoring


▪ SAP Fiori activation status

– SAP Gateway

– ICF Nodes

– System Aliases

– OData Services

▪ Enterprise Search

▪ Embedded Analytics

▪ Running jobs

▪ Available logs

▪ Available traces

▪ Caches

Monitoring – What to check?


Always remember these facts and

transactions


1. Understand Landscape Architecture:

– Transactional Apps implement OData calls from the Frontend server but Webdynpro and Object Page

require a direct connection the Backend server.

– Hub Deployments: Several RFC connections are required.

▫ Firewall adjustments may be needed in complex network architectures.

2. Catalog Replication / Index Calculation:

– Set up Fiori Catalog Replication and Index Calculation jobs to run at least once a day, this will make sure

that Catalog and Application ID status is consistent.

▫ Report /UI5/APP_INDEX_CALCULATE

▫ Report /UI2/GET_APP_DESCR_REMOTE

3. Update UI libraries:

–Important corrections are delivered in UI libraries that will help stabilize Fiori apps.

TroubleshootingAlways remember these facts and transactions


4. Hub Deployments - One frontend for multiple backends:

– In this case, try to maintain 1 frontend client per backend client within the same landscape.

5. Hub Deployments - Security:

– Enabling trust relationship between the frontend and backend server requires all users to possess

authorization object: S_RFCACL

– Replication of user ID’s between frontend and backend clients is required.


100

200

300

Frontend

Launchpad

100

200

300

Backend

Backend Frontend

ID: JOHNDOE

Auth. Obj.

S_RFCACL

ID: JOHNDOE

Auth. Obj. S_RFCACL

Sys. Trust


6. Know your tools:


Transaction Code Description

SU01 User Maintenance

PFCG Role Maintenance

SICF Maintain Services

SM59 RFC Destinations (Display/Maintain)

SPRO Configure SAP System as per client requirement

SMICM ICM Monitor

SHMM System Shared Objects Monitor

STC01, STC02 Execute/Display Task List Runs

ST22 System Dumps

/UI2/CUST Customizing of UI Technologies

SACM Access Control Management

General Administration


6. Know your tools:


Frontend AdministrationTransaction Code Description

/UI2/FLP Launch SAP Fiori Launchpad

/UI2/FLC Fiori Launchpad Checks

/UI2/FLP_CUS_CONF Fiori Launchpad System Settings (client-specific)

/UI2/FLP_SYS_CONF Fiori Launchpad System Settings (cross-client)

/UI2/FLP_DEL_PERS Delete Personalization of SAP FLP

/UI2/CSU Cache Statistics Utility

/UI2/FSAC System Alias Consistency Check

/IWFND/CACHE_CLEANUP Cleanup of Model Cache

/IWFND/MAINT_SERVICE Activate and Maintain OData Services

/IWFND/ERROR_LOG SAP NetWeaver Gateway Error Log

/IWFND/GW_CLIENT Simulate OData Service execution

/IWFND/TRACES SAP NetWeaver Gateway: Tracing Tools

/IWFND/APPS_LOG Application Log Viewer

/IWFND/CACHE_REBUILD Rebuild Gateway Model Cache


6. Know your tools:


Frontend Administration (continued)Transaction Code Description

/IWFND/V4_ADMIN OData V4 Administration (for Notifications)

/IWNGW/R_HUB_CLEAR_CACHE OData Cache (for Notifications

SBGRFCMON Monitor bgRFC queues (for Notifications)


6. Know your tools:


Backend AdministrationTransaction Code Description

/IWBEP/CACHE_CLEANUP Cleanup of Model Cache

/IWBEP/ERROR_LOG SAP Gateway Backend Error Log

/IWBEP/TRACES SAP Gateway Backend Traces

/IWBEP/VIEW_LOG SAP Gateway Log Viewer

/IWBEP/CONFIG_CHECK Check Configuration of BEP

ESH_DASHBOARD Enterprise Search Connector Analysis and Troubleshooting

ESH_TEST_SEARCH Enterprise Search Connector Test

ESH_QUERY_LOG Enterprise Search Connector Query Log


6. Know your tools:


Business Role AdministrationTransaction Code Description

/UI2/FLIA Fiori Launchpad Intent Analysis

/UI2/FLC Fiori Launchpad Checks

/UI2/FLPCM_CUST Fiori Launchpad Content Manager (client-specific)

/UI2/FLPCM_CONF Fiori Launchpad Content Manager (cross-client)

/UI2/FLPAM Fiori Launchpad App Manager

/UI2/FLP_APPDESC_GET Replicate Backend Catalogs

/UI2/FLPD_CONF Fiori Launchpad Designer (cross-client)

/UI2/FLPD_CUST Fiori Launchpad Designer (client-specific)

/UI2/SEMOBJ Define Semantic Object – Customer

/UI2/SEMOBJ_SAP Define Semantic Object – SAP

SACMDCLS CDS Access Controls


6. Know your tools:

Tools listed in the SAP Reference

Implementation Guide

▪ SAP GUI Transaction SPRO >

SAP Ref IMG >

SAP NetWeaver >

UI Technologies >

SAP Fiori >

Launchpad Support Tools

In the SAP Help Portal

▪ SAP Fiori launchpad > Administration Guide

> Launchpad Support Tools


SAP Fiori Administrator Launchpad Support Tools

https://help.sap.com/viewer/a7b390faab1140c087b8926571e942b7/latest/en-US/af641fa4a8ba41379ca8c33f27ef35e9.html


7. Useful reports for FLP checks and system alias:



8. Many issues relate to cached content.

– Make sure to delete cache in case of issues and also particularly after deployment of corrections / FPS.

Run report /UI2/INVALIDATE_GLOBAL_CACHES to clear the FLP caches.

9. Intents (combination of semantic object and action) not resolving.

– Make use of FLP Intent Resolution Analyzer (TA code /UI2/FLIA)

10. Data missing in app typically related to Authorizations.

– TA code SU53 for authorization traces (see SAP Note 2147808)




11. Rapid Activation is the recommended

procedure to activate SAP Fiori since the

release of SAP S/4HANA 1709 FPS01

– Rapid Activation is available on any version

higher or equal to SAP S/4HANA 1709 FPS01.

12. Rapid Activation is available only on

embedded SAP Fiori deployments

13. Rapid Activation – Error Troubleshooting.

– Known issues and solutions are mentioned in the

Rapid Activation note for each version of SAP

S/4HANA. Overview note with links to version specific notes is available: 2902673 - Rapid

Activation for SAP Fiori in SAP S/4HANA -

Overview




14. Deploy App Support for the SAP Fiori Launchpad plugin in your landscape

– App support is available for SAP S/4HANA as part of the SAP_UI component from the following versions:

▫ SAP_UI 7.54 SP06 in S/4HANA 1909 SP04 or Frontend Server 6.0 SP04

▫ SAP_UI 7.55 SP02 in S/4HANA 2020 FPS01 or Frontend Server 2020 SP01

15. You can run SAP Fiori Launchpad health checks as a proactive maintenance activity in

your system

– Via task list /UI2/FLP_HEALTH_CHECKS

– Using Launchpad Content Manager


https://help.sap.com/viewer/a7b390faab1140c087b8926571e942b7/latest/en-US/04bc7b47932f4e689f7911901087a8f2.html

Fiori Performance

Tips and Tricks


Understanding the overall architecture of the solution is key to identify performance issues because

in the Fiori architecture, your browser is directly accessing the back-end via each Fiori tile. Each tile

on the FLP is making numerous calls to (and receiving) data from the server, which can cause

latency issues.

Note that when referring to the backends in the S/4HANA model we are talking about the

integration between 3 main components:

• Web Dispatcher

• Frontend Server

• Backend Server

Depending on the network configurations of these servers, network performance issues may arise.

Fiori PerformanceTips and Tricks

Blog: Fiori for S/4HANA – Performance tips and Tricks in S/4HANA On-Premise

https://blogs.sap.com/2017/06/08/fiori-for-s4hana-performance-tips-and-tricks-in-s4hana-1610-on-premise/


You will find some cases where performance issues may go deep into code or network debugging,

however, there are some quick actions you can take in every project to ensure the best

performance of your Fiori Launchpad (FLP).

We will list some performance tips and tricks for all your current implementations


Blog: Fiori for S/4HANA – Performance tips and Tricks in S/4HANA On-Premise

https://blogs.sap.com/2017/06/08/fiori-for-s4hana-performance-tips-and-tricks-in-s4hana-1610-on-premise/


Use what you need

✓ The more tiles you have on your FLP, the longer it will take to

load

✓ To lessen any latency issues, only add the tiles you need.

✓ It is recommended that you do not exceed 7x7 (49 tiles) per FLP

group, also notice the more catalogs you have assigned, the

longer it’s going to take to load the home screen.

✓ Go through Design Thinking workshops at the early stages of

the project in order to build “Personas” which will later help you

define the required business roles



All tiles are not equal

✓ KPI and dynamic tiles have a bigger impact on bandwidth,

as they are in constant communication with the back-end

servers to update.

✓ Static tiles do not change; once they are loaded onto the

FLP, they are not making any additional “calls” to update.

✓ For KPI and dynamic tiles try to define a refresh interval or

cache duration suitable to your end user needs and SAP

landscape capabilities.


https://help.sap.com/saphelp_uiaddon10/helpdata/en/92/dda11afc814a538a8ec626f4a74c8d/frameset.htm

https://blogs.sap.com/2017/02/11/kpi-tile-refresh-in-smart-business-service/


Introducing Tab Bar Navigation

✓ This feature changes the interaction of the end user

with FLP as tiles are displayed per group.

✓ Can be switched on for all users by the system

administrator or enabled through user

personalization.


Blog: Fiori for S/4HANA – What is Tab Bar?

https://blogs.sap.com/2017/06/08/fiori-for-s4hana-what-the-%C2%A2-is-tab-bar/


Improve Webdynpro, Webgui and App Finder performance

✓ Webdynpro, Webgui and App Finder → Check kernel version and try to update as this is

required by the new unified rendering concept.

✓ To load Webdynpro or Webgui apps FLP uses the NWBC runtime, it is recommended to update

NWBC runtime by implementing the following notes in order:

• 2408184

• 2405259

• 2433839

✓ Try running report /UI2/NWBC_DELETE_MENU_CACHE every now and then as you may find

wrong entries in table /UI2/NWBC_NAV_TR (column NWBC_VERSION will have the value

“LOADING”).







Improve Webdynpro, Webgui and App Finder performance - UPDATE

✓ As of August 25th, 2017 you no longer need to update the entire kernel package.

✓ A new package, called sapwebgui, is now delivered. It contains only the WEBGUI related files.

✓ If you have interest in this new approach, then you can find more information in

KBA 2221289 (How to install package sapwebgui).


Blog: Sapwebgui Package Now Available


https://blogs.sap.com/2017/08/25/sapwebgui-package-now-available/


Improve OData performance

✓ In some very specific cases you will find

that OData requests execution time is

longer than expected.

✓ This will usually occur for OData services

that expose very large data sets. If this is

the case, you can try configuring OData

services in Co-deployed mode.


Blog: How to take advantage of the performance improvements in SAP Gateway in SAP NetWeaver 7.50 SP04

https://blogs.sap.com/2016/10/10/take-advantage-performance-improvements-sap-gateway-sap-netweaver-7.50-sp04/


Make sure your browser’s cache is

optimized

✓ Ensure your browser cache settings are optimized for

maximum performance and try not to use any settings

that bypass the browser cache:

• Do not run the Fiori Launchpad in private mode

• Select a sufficient cache size limit

• Do not clear the cache history automatically when the browser closes

• Enable browser caching

• Do not disable the browser cache in the browser developer tools

• Enable HTTP compression

✓ You can find a detailed how-to document describing

these settings in all three major browsers (Chrome,

Firefox, Internet Explorer) in note 2447857




Get the right Certificates (HTTPS)

✓ Make sure HTTPS connectivity is correctly setup.

Monitor this in the browser’s dev tools – network tab.

✓ If you are using self-signed certificates or your

certificate has not been signed by a valid Certificate

Authority (CA) you will face performance issues as any

error with the certificate means that the webpage will

not be loaded. You can find additional details here and

here.

✓ Note that versions 58 or higher of Chrome now

mandatorily require that the SAN (Subject Alternative

Name) field of the server’s SSL certificate is correctly

populated, you’ll find the detailed issue and resolution

in this blog.


https://bugs.chromium.org/p/chromium/issues/detail?id=103875

https://bugs.chromium.org/p/chromium/issues/detail?id=110649

https://blogs.sap.com/2017/05/03/fix-chrome-missing_subjectaltname-error-with-sap-netweaver-application-server-abap/


Still facing performance issues?

✓ Take a look at note 2471635, you will find

some common performance issues and

their solution.

✓ Note that some solutions may require

additional development efforts.



Thank you!

© 2021 SAP SE or an SAP aff iliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose w ithout the express permission of

SAP SE or an SAP aff iliate company.

The information contained herein may be changed w ithout prior notice. Some software products marketed by SAP SE and its

distributors contain proprietary software components of other software vendors. National product specif ications may vary.

These materials are provided by SAP SE or an SAP aff iliate company for informational purposes only, w ithout representation or

w arranty of any kind, and SAP or its aff iliated companies shall not be liable for errors or omissions w ith respect to the materials.

The only w arranties for SAP or SAP aff iliate 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

w arranty.

In particular, SAP SE or its aff iliated 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 SE’s or its aff iliated companies’ strategy and possible future developments, products, and/or platforms, directions, and

functionality are all subject to change and may be changed by SAP SE or its aff iliated companies at any time for any reason

w ithout notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forw ard-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 forw ard-looking statements, and they

should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as w ell as their respective logos are trademarks or registered

trademarks of SAP SE (or an SAP aff iliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.

See www.sap.com/copyright for additional trademark information and notices.

www.sap.com/contactsap

Follow us

https://www.sap.com/copyright

https://www.sap.com/registration/contact.html

https://www.linkedin.com/company/sap

https://www.youtube.com/user/SAP

https://twitter.com/sap

https://www.facebook.com/SAP

SAP Fiori for SAP S/4HANA Troubleshooting Tips and Tricks

Documents