Shell Bar

When end users launch apps from the SAP Fiori launchpad, the apps run within a shell. The shell
bar is the outer frame of the SAP Fiori launchpad.

The shell bar contains header and footer areas with various buttons, icons, and a logo.

What will I see in the default header bar?

The following table lists the standard icons available in the shell header of the launchpad.

Icon Name Description

 Me Area launcher Opens the Me Area.

NoteThis icon is replaced with your profile picture if SAP Jam

is integrated in your environment and you have a picture
defined in SAP Jam.

See: Me Area

 Back Navigates from an app back to the previous screen where you
were working.

 Home Displays the launchpad home page with the apps that you can
launch.

See: Home Page

Company or Displays the default SAP logo that you can replace with your
brand logo own logo using the UI theme designer.

 Search Opens a global search user interface for finding apps and
objects.

See: Searching for Business Objects and Apps

 Icon Name Description

 Notifications Opens the Notifications area with the alerts, tasks, or requests
that are related to your business role.

The icon also shows a badge with the number of new

notifications you have received.

Issues with Tiles, Groups or Catalogs

This section helps you to analyze and solve issues that may occur for tiles, groups and catalogs.

Issue Possible Reasons Error Analysis and Possible

Solution

A tile is displayed with the
error “Cannot load tile”.
An administrator deleted the
tile from the catalog which is
referenced by a group.
An end user personalized the
group (e.g. by moving,
deleting or adding tiles).
The end user needs to
remove the orphaned tile
from the group.
See Personalizing the Home
Page.
To prevent this issue, an
admin can switch off the
personalization of groups.
See Editing Groups.

An administrator deleted the Use Fiori Launchpad Checks

tile from the catalog which is
referenced by a group.
After deleting the tile, the
administrator did not clean
up customized or configured
groups which use the tile.
(transaction /UI2/FLC) to
identify the orphaned tiles in
groups.
Delete these tiles in the SAP
Fiori launchpad designer.
 Issue Possible Reasons
A tile is not displayed. There is no matching target
mapping (semantic
object/action) or device type.
The tile is a reference tile and
the reference is broken
because the original tile was
deleted.
An admin has added a tile to a
group. End users cannot see
the new tile because they
personalized the group.
Error Analysis and Possible
Solution
Use Fiori Launchpad Intent
Analysis
(transaction /UI2/FLIA) for
error analysis.
In the SAP Fiori launchpad
designer, make sure the
target mapping configuration
is correct.
See Configuring Target
Mappings.
Use Fiori Launchpad Checks
(transaction /UI2/FLC) to
identify broken references.
Broken references cannot be
restored. The tile needs to be
created from scratch.
The end user can delete the
personalization in the SAP
Fiori launchpad by resetting
the group.
See Personalizing the Home
Page
To prevent this issue, an
admin can switch off the
personalization of groups.
See Editing Groups.
 Issue
A group or catalog is not
displayed.
An administrator has changed
groups but the change is not
reflected for an end user.
Maintaining your Default User Values
Some applications can be launched with user-specific default values. You can view these values and edit
the default values if necessary.
Possible Reasons
The catalog or group is not
assigned to a PFCG role.
The group or catalog is
assigned to a composite role.
Settings for composite roles
override the settings of
included roles.
The end user has personalized
the group before the
administrator made the
changes.
Error Analysis and Possible
Solution
Use Fiori Launchpad Checks
(transaction /UI2/FLC) for
error analysis.
Assign the group or catalog to
a PFCG role. See Assign Tile
Catalogs to Roles.
Use Fiori Launchpad Checks
(transaction /UI2/FLC) to
find out to which role the
group or catalog is assigned.
You can then search for the
role in transaction PFCG to
check whether it is a
composite role.
Assign the group or catalog to
a specific role rather than a
composite role.
The end user can reset the
group. See Personalizing the
Home Page.
Procedure
1. In the Me Area, click or tap the Settings option in the menu bar.

2. Select Default Values.
3. You can change the value of any of the displayed parameters, or just view the values.

Some parameters allow you to specify additional values. Click Additional Values to add
values to the parameter.

4. If you have changed any of the values, click Save.

Setting the Language in the ABAP System

To set or change the logon language in the ABAP system, proceed as follows:

1. Start Maintain User Profile (transaction SU01).

2. Enter your user name and choose Display.

3. Open the Defaults tab.
4. Enter your preferred logon language (e.g. EN for English).

Setting Language Preferences in a Browser

Browsers offer the option to define a list of preferred languages. This list is specified using the
HTTP header field Accept-Language. With Microsoft Internet Explorer, you can for
example set the language you require by choosing Tools  Internet Options  Languages.

Setting Language Preferences for the

Launchpad

To view your logon language, open the Settings  Language & Region

Launchpad Content Checks
This report is available to check the consistency of delivered and customized content created for
use with SAP Fiori launchpad.

The report Fiori Launchpad Checks (transaction /UI2/FLC) provides an overview of all

existing content in a given area based on development packages and exposes consistency errors
in these packages. It allows you to check to which authorization role the content is assigned and
if a given user is assigned to this role. You can filter for content assigned to a given user.

The data retrieved by the report can be used for troubleshooting as well as for data analysis and
monitoring.

Determining Target Mappings for an

Intent
Use the report Fiori Launchpad Intent Analysis to determine the target mapping for a given
intent.

Context
When the target mapping for a given intent is not configured correctly, the launchpad will not
navigate to the expected application when an end user clicks a tile. To correct this issue, you
might first have to find out which target mapping belongs to the affected intent.

Procedure
1. Start Fiori Launchpad Intent Analysis (transaction /UI2/FLIA) in the back-end
ABAP system.

2. Enter the name of the intent for which you want to determine the target mapping (e.g.
SalesOrder-display).
3. Enter the form factor, for example, Phone.
4. Optional: Enter a user name.
5. Optional: Select the Restrict to assigned roles checkbox.
6. Optional: Enter the development package for which you want to review the data.
7. Optional: Select the Include Subpackage checkbox.

Use this setting if you use a main package or a structure package and want a full content
overview.

8. Select an Adaptation Layer. You have the following options:

a. Select Configuration to check delivered content (client-independent).

b. Select Customization if you want to check customized (client-dependent)

content, and to verify that Configuration content is not overwritten by
customized content.
c. Select Personalization if you want to check personalized (user-specific) content.
This is the default setting.

9. Run the report. The result of the check is displayed.

10. Copy the entry in the Tile ID column.
11. Double-click the entry of the ID of a Catalog column.

The SAP Fiori launchpad designer is launched, displaying the selected catalog.
 12. In the launchpad designer, switch to Target Mappings.
13. In the search field, enter the tile ID you copied from the Fiori Launchpad Intent
Analysis result list.
14. You can change the settings for the target mapping by choosing Configure.

Display Logs in the Browser

If an error occurs during processing, you can use the developer tools available for browsers to
display the message.

For Internet Explorer, Google Chrome and Firefox, this is done by pressing the  F12  key.

Display Logs for SAP NetWeaver User

Interface Services
OData services, REST services and utilities (such as reports) write important information to the
UI2 log.

Context
These logs can be displayed using transaction /UI2/LOG. It is a variant of the standard
application log (transaction SLG1) that is easier to use as the screen contains fewer fields and
some fields have default values. In addition, it provides the option to download the logs to a local
file.

Procedure
1. In Customizing, choose SAP Fiori  Support Tools  SAP UI2 Application Log.

Transaction /UI2/LOG is launched.

Note
You can also access the UI2 logs using transaction SLG1 and object /UI2/BE.
2. Enter a subobject:

Table 48:

Subobject What is logged

/UI2/INTEROP
 Transfer personalization from Web Dynpro
Configuration to database
 Delete expired personalization
 Setting up end user feedback
 Errors in navigation link resolution
 Cleanup of application states

/UI2/PFCG An application used in the assigned catalog is not available

in the ABAP system when an administrator determines
authorization defaults in Role Maintenance
(transaction PFCG). See Assign Tile Catalogs to Roles.

/UI2/PAGE_BUILDER Entities in the launchpad designer or in the launchpad

home page are created, updated, or deleted.

/UI2/CLEANUP_CACHES All server-side caches are invalidated.

/UI2/TRACE When the trace is activated, steps executed by an OData

or REST service provided by SAP NetWeaver User
Interface services are logged.

See Tracing for SAP NetWeaver User Interface Services.

/UI2/SANITY_CHECKS Messages from Fiori System Alias

Check (transaction /UI2/FSAC).

See System Alias Checks.

/UI2/BC_COLLECTOR) Shows which SAP Gateway hubs were contacted and

whether an invalidation of the OData metadata cache took
 Table 48:

Subobject What is logged

place.

See Cache Buster for OData Metadata of SAP Fiori Apps.

/UI2/CSU Cache statistics. See Analyzing Cache Statistics.

Tracing for SAP NetWeaver User

Interface Services
Use this trace to record specific steps executed by SAP Netweaver user interface services (e.g.
the ones generated by the UI2 OData/REST requests).

Context
Trace files are mainly used by developers or support (engineers) to record and analyze the occurrence of
certain events at runtime. Therefore, tracing is normally turned off. Traces can be switched on if a
problem has occurred and a detailed analysis of a distinct aspect of the launchpad is necessary.

You can download the trace to a local file to, for example, attach it to an incident.

Procedure
1. To activate the trace, go to Maintain User Profile and set user
parameter /UI2/TRACE to value X.

2. To display the trace file, launch transaction /UI2/LOG and specify

subobject /UI2/TRACE.

See Display Logs for SAP NetWeaver User Interface Services.

3. Once you are done with your analysis, switch off the trace by removing the value of user
parameter /UI2/TRACE.

Writing to the trace does not affect the performance of a service but adds unnecessary
information to the UI2 log.