Welcome !

SAP FIORI
Administration
SAP FIORI
Troubleshooting
Why troubleshooting is important?

Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting

is to determine why something does not work as expected and explain how to resolve
the problem.
 How can I identify if any issue in
FIORI

Leave it to me! I will pull up

my hands here

ABAP Senior Consultant

 Troubleshooting
Performance Issues
TUNING FIORI
PERFORMANCE
Understanding the overall
architecture of the
Note that when referring to the
back ends in the S/4HANA model
we are talking about the
integration between 3 main
components:

•Web Dispatcher

Web Dispatcher
•Frontend Server Backend Frontend
•Backend Server Server Server
Tuning SAP Fiori
Performance

• Add the tiles based on nature of

your work

• 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.
• Tiles have different impact on how data is used

• 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.
• Tuning Webdynpro, Webdynpro, Webgui and App Finder → Check kernel version and try
Webgui and App Finder to update as this is required by the new unified rendering concept.
performance
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”).
 OData performance tuning

• In some very specific cases you will find that OData requests execution time is longer
Tuning Fiori Performance 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.
Troubleshooting Connectivity
Issues & 403, 500 Errors
 • Understand Landscape Architecture:
Important • –Transactional Apps implement OData calls from the Frontend

Facts and server but Webdynpro and Object Page require a direct connection
the Backend server.
• –Several RFC connections are required.

transactions • Firewall adjustments may be needed in complex network

architectures.

• 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
• Update UI libraries:

• –Important corrections are delivered in UI libraries (+1.40.x) that will help stabilize Fiori apps.

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

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

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

• Data missing in app typically related to Authorizations.

• –TA code SU53 for authorization traces (see SAP Note 2147808)
Troubleshooting tools
Important Facts and transactions
➢ One frontend for multiple back ends:

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

Backend Frontend

Launchpad
100 100
200 200
300 300

➢ 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.
Backend Frontend

ID: JOEL System Trust ID: JOEL

Auth. Obj. Auth. Obj.
S_RFCACL S_RFCACL
Tools Description

/IWFND/MAINT_SERVICES (transaction) OData Frontend Service Activation / Alias Assignment / SICF (/sap/opu/OData/sap)

/IWBEP/ERROR_LOG (transaction) OData Backend Error Log

/IWFND/ERROR_LOG (transaction) OData Frontend Error Log

/IWFND/GW_CLIENT (transaction) OData Frontend Service Execution

SE80, SE37, SE38(transaction) ABAP Object/Code Analysis

Chrome Browser Chrome Browser Developer Tools works best for troubleshooting

OData Browser Debugging Add parameter: “?sap-ds-debug=true” to OData calls

SACM Troubleshoot CDS Authorizations

Important Facts and

• Know your troubleshooting tools:
transactions –
Contd.
Tools Description

Fiori Launchpad Checks (transaction /UI2/FLC) Check the consistency of delivered and customized content created for use with SAP Fiori
Launchpad

Orphaned Catalogs and Groups (transaction /UI2/FLC1) Checks launchpad content in the customizing scope for orphaned objects and offers tools
to clean up the content

Fiori Launchpad Intent Analysis (transaction /UI2/FLIA) Check the assignment of a given intent (semantic object – action pair) to a user in the
context of SAP Fiori launchpad

Fiori System Alias check (transaction /UI2/FSAC) Check the consistency of system aliases configured for the launchpad

Application Log: Display Logs (transaction SLG1) Display messages for OData services and utilities (eg. reports) of the SAP Netweaver User
Interface Services

• Useful reports for FLP checks and system alias:

• /UI2/FLIA

• Used to analyze intent (target mapping)

resolution
• Filter by intent and form factor
• Additional filters similar to those in
/UI2/FLC
 Troubleshooting
Enterprise Search
 • Transaction STC02:

Troubleshooting • –During the configuration of task list, transaction STC01 was used to execute each
task lists from the configuration guide.
Enterprise Search
• –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.
 • Easiest way to troubleshoot enterprise search is by
Troubleshooting using transaction:
Enterprise Search • ESH_TEST_SEARCH
Troubleshooting Enterprise
Search
Troubleshooting Web
Dispatcher
Troubleshooting • To troubleshoot Webdispatcher you need OS access or a Webdispatcher
Web dispatcher Visual Administration user.
Troubleshooting • Check configuration profile (OS Level only)
Webdispatcher
Troubleshooting • Check configuration profile (OS Level only)
Webdispatcher
Troubleshooting • Analyze Web dispatcher Logs (OS Level)
Webdispatcher
Troubleshooting • Analyze Web dispatcher Logs (Visual Administration)
Webdispatcher
Detailed Troubleshooting
Fiori Troubleshooting

How to start a troubleshooting session :

• Once the “Developer Tools” are open, go to Console & clear old logs, reload
the Fiori launchpad and replicate the issue.

• Check Console & Network section as they offer valuable details of the error.
Identify errors highlighted in Red and read the error description.
• Initial Analysis : ODATA service is not active, or configuration is missing.
 1

3
4
 1

3
 3
4

5
How to start a troubleshooting session :

Fiori Troubleshooting Step 1: In the network area select entry in Red, navigate to
Body → Response body and expand the error details to find
the “Error Message”.
 /IWFND/MAINT_SERVICE 1

2
Error
SAP FIORI Activities after
System Refresh Steps
 Reconfigure Trusted Update RFC ABAP
Adjust Web
Reconfigure and RFC between and HTTP
1 2 Dispatcher instance 3
Validate SSL backend and Destinations for
profiles
frontend systems classic UI Apps

Replicate App Reconfigure System

Reconfigure SAML if 5
Descriptors from 6
Update logical 7
Alias for SAP OData
required Back-End System system names services if Alias name
need to be changed

Regenerate ESH 9
Running cache
indexes cleaning reports
Thank you.
Take a short break before starting the next
session