PUBLIC

2019-07-10

SAP Fiori Launchpad Content Manager

© 2019 SAP SE or an SAP affiliate company. All rights reserved.

THE BEST RUN

Content

1 Setting Up Catalogs with the Launchpad Content Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.1 About Launchpad Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
1.2 Scopes for Adapting Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Tools for Setting Up Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.4 Running the Launchpad Content Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.5 Exploring Launchpad Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Searching for Launchpad Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Tile/Target Mapping Combinations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
References and their Originals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.6 Creating and Configuring Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Read-Only Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Creating Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Copying Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Adding and Removing Catalog Content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Renaming Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Deleting Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.7 Transporting Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
1.8 Displaying Issues with Launchpad Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Scope-Related Catalog Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Issues with Tiles and Target Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.9 Best Practices for Managing Catalogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

SAP Fiori Launchpad Content Manager

2 PUBLIC Content
1 Setting Up Catalogs with the Launchpad
Content Manager

Administrators use the SAP Fiori launchpad content manager to browse launchpad content and to set up
catalogs according to their needs.

System Requirements

For more information on the system requirements for using the launchpad content manager, see SAP Note
2772270 .

Feature Scope

The launchpad content manager complements the launchpad designer. It offers the following features:

Feature Description

Exploring Launchpad Content [page 10] For example, you can explore available tile/target mapping
combinations for an app or search for tiles and target map­
pings across all available catalogs.

Creating and Configuring Catalogs [page 14] Create, copy, rename or delete catalogs. Add or remove ref­
erence tiles and target mappings to/from the catalogs (also
in a mass operation).

The following is not supported in the launchpad content

manager:

● Changing cross-client catalogs in the customizing

scope.
This is supported in the launchpad designer but not rec­
ommended because it can lead to inconsistencies.
● Creating, changing or deleting original tiles and target
mappings.
Please use the launchpad designer or the Mass Mainte­
nance tool instead.
● Managing custom tiles (displaying information about
custom tiles and adding them to catalogs).
Please use the launchpad designer instead.

See Tools for Setting Up Content [page 8].

Displaying Issues with Launchpad Content [page 21] The launchpad content manager displays content issues de­
tected during catalog loading and matching of tiles and tar­
get mappings.

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 3
  Note

You can launch the launchpad designer from the launchpad content manager. In the Catalogs tab, select a
catalog and choose Open in Designer. The launchpad designer is started in the same system and scope,
displaying the selected catalog.

Typical Use Case

A typical use case is creating your own custom catalogs by copying the business catalogs delivered by SAP as
templates/samples and adjusting them to your needs. Here are the required steps:

1. Search for a suitable catalog that you can use as the basis for your own catalog. For example, you can
search for the target applications you are interested in and find out to which catalogs they are assigned and
which tiles and target mappings have been created for them.
2. Copy the SAP catalog. Your copied catalog will include references to the tiles and target mappings in the
SAP catalog.
3. Remove the reference tiles and target mappings you don’t need from your copied catalog.
4. Identify which apps are missing in your catalog and add references to the corresponding tiles and target
mappings to your catalog.

UI Overview

In the launchpad content manager, tiles and target mappings in the same catalog which refer to the same
intent and target application are automatically matched and displayed in one row. See Tile/Target Mapping
Combinations [page 11]. Depending on your focus, you can display them in the following tabs:

● Catalogs:
The upper table displays all catalogs available in the ABAP system to which you are logged on. When you
select a catalog, all tiles and target mappings assigned to it are displayed in the lower table. You can assign
additional reference tiles and target mappings to the selected catalog or remove reference tiles and target
mappings that are not needed. In addition, you can create, delete, copy and rename catalogs.
● Tiles/Target Mappings:
The upper table displays available tile/target mapping combinations. Selecting an entry shows the
catalogs to which the selected tiles and target mappings are assigned in the lower table. You can add a
selected combination of tile and target mapping as references to another catalog or remove reference tiles
and target mappings from a selected catalog.

 Note

You can adjust the displayed list content, for example by adding or removing columns or setting filters. See
Working with SAP List Viewer (ALV)

SAP Fiori Launchpad Content Manager

4 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
Related Information

SAP Fiori Launchpad Administration Guide

UI Technology Guide for SAP S/4HANA
Best Practices for Managing Catalogs [page 26]

1.1 About Launchpad Content

This section explains how the different entities required to set up launchpad content relate to one another.

To make an app available to a user in the launchpad, several entities have to be configured by an administrator.
The graphic below provides an overview of the involved entities. The arrows indicate the direction in which
these entities are assigned.

Entity Description

Role Used to control access to launchpad content. Administrators assign catalogs and groups to a
role which can be assigned to users.

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 5
Entity Description

Group Consists of tiles (and links) representing a subset of apps. Administrators assign tiles to a group
and groups to a role. Users that have this role assigned, can view the group and the contained
apps on their launchpad homepage. Users can personalize their launchpad by adding or remov­
ing apps from the out-of-the-box groups or self-defined groups.

Catalog A collection of apps that are available for a specific role (or for multiple roles). Administrators
assign apps (via tiles and target mappings) to a catalog and catalogs to roles. Users that have a
particular role assigned, have access to all the apps that are contained in the catalogs assigned
to this role.

Tile A visual representation of an app on the launchpad home page. When a user clicks a tile in their
launchpad, an intent (including optional parameters) navigates to the app and opens it. Adminis­
trators create tiles in catalogs.

Target mapping Mapping of a navigation target to the intent (combination of semantic object and action). The
target mapping is a prerequisite for the navigation to an app in the launchpad. It can refer to only
one target application which can be built with different UI technologies (SAPUI5, Web Dynpro,
SAP GUI for HTML or a plain URL). Administrators create target mappings in catalogs by defin-
ing the intent, the navigation target, the device types supported by the target, and additional pa­
rameters.

Related Information

Tools for Setting Up Content [page 8]

1.2 Scopes for Adapting Content

As an administrator you can adapt the launchpad content delivered by SAP for the roles within your company.

Scopes for Launchpad Content

SAP delivers predefined content like catalogs and groups for the SAP Fiori launchpad. As an administrator you
can copy and adapt the content in the configuration and customizing scopes.

SAP Fiori Launchpad Content Manager

6 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
The predefined SAP Fiori launchpad content uses the Web Dynpro configuration as persistence tool. The
content is stored in the following scopes:

Scope Description

Configuration System-wide settings

The content delivered by SAP is stored in the configuration scope.

Administrators can use the configuration scope to create their own technical catalogs with
tiles and target mappings. They then adapt their business catalogs in the customizing scope
by adding references to the content of the technical catalogs.

Customizing Client-specific settings

Content changes are valid only for the current client.

Administrators can use the customizing scope to copy a catalog and to adapt it for a selected
client.

These settings supersede configuration settings, but can be superseded by personalization

settings.

Personalization User-specific settings

At launchpad runtime, end users can use the personalization scope to adapt a group that con­
tains predefined content and that has been assigned to their user role by an administrator.
They can rearrange the tiles in the SAP Fiori launchpad and save their preferences in the per­
sonalization layer.

These settings supersede customizing and configuration settings.

If the content exists in more than one scope and you change it in a more specific scope (for example,
personalization), the changes supersede the content stored in a more generic scope (for example,
configuration).

For example, if you make changes to a catalog in the content delivered by SAP and stored in the configuration
scope after you personalized the content, these changes are not visible in the personalization scope.

If you delete the whole group or catalog in the personalization scope or in the customizing scope, the system
displays the original data of the less specific scope. To delete content, drag an entity (for example, a group) to
the trash can in the launchpad designer.

If you delete a catalog or group in the customizing scope, the launchpad designer tries to load the object from
the layer of the configuration scope. If this is successful, a message will let you know that the object has been
reloaded from a lower layer.

Selecting the Scope for a Design Time Tool

Here is how you access the available design time tools in the configuration or customizing scope:

● Launchpad content manager

Use transaction /UI2/FLPCM_CONF to run the launchpad content manager in the configuration scope and
transaction /UI2/FLPCM_CUST for the customizing scope.

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 7
 See Running the Launchpad Content Manager [page 9].
● Launchpad designer
To access the launchpad designer in the configuration scope, add parameter scope=CONF to the URL.
If you access the launchpad designer without providing any scope parameter in the URL, the customizing
scope is selected by default. The parameter you can add to the URL is scope=CUST.
The client information for the relevant scope is displayed in the launchpad designer header next to the

icon:
○ A specific client (for example, 000) for the customizing scope
○ Client: ALL for the configuration scope
● Mass maintenance tool
The mass maintenance tool is always run in the configuration scope.

Related Information

Tools for Setting Up Content [page 8]

1.3 Tools for Setting Up Content

Find out which tool is recommended for which task.

What do you want to do? Which tool is recommended? Where to find more information?

Explore launchpad content and get key SAP Fiori apps reference library https://fioriappslibrary.hana.onde-
information for each app, including all mand.com/sap/fix/externalViewer/
the technical data you need for installa­
tion and configuration.

Manage business catalogs: Add or re­ Launchpad content manager Setting Up Catalogs with the Launch­
move references to tiles/target map­ pad Content Manager [page 3]
pings

Manage technical catalogs: Create orig­ Launchpad designer

Setting Up Content With the Launchpad
inal tiles/target mappings for SAP Fiori
Designer
UI5 apps and URLs

Manage technical catalogs: Create orig­ Mass Maintenance tool Integrating Web Dynpro and SAP GUI
inal tiles/target mappings for Web Dyn­ Applications Using Mass Maintenance
pro and SAP GUI apps.

Manage groups Launchpad designer Creating and Configuring Groups

Manage roles Role maintenance (transaction PFCG) Configuring Roles for Tile Catalogs and
Groups

SAP Fiori Launchpad Content Manager

8 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
Related Information

About Launchpad Content [page 5]

1.4 Running the Launchpad Content Manager

The launchpad content manager allows you to make system-wide or client-specific changes.

Prerequisites

The launchpad content manager uses the page cache to load persisted content. Therefore, the page cache
should be active when you work with the launchpad content manager. To check this, in User Maintenance
(transaction SU01), go to the Parameters tab and make sure the user parameter /UI2/PAGE_CACHE_OFF is
not set to “X”.

The launchpad content manager only loads persisted content when the session is started. During a running
session, there is no further check whether the displayed entities are still up to date. This can lead to data
inconsistencies when changes are made in another session of the launchpad content manager or in the
launchpad designer.

It might take up to several minutes to load the persisted data from the cache. You cannot work in the launchpad
content manager while the cache build process is ongoing. You have to restart the transaction when the cache
build is completed.

Transactions for the Launchpad Content Manager

System-wide changes are stored in the configuration scope and client-specific changes are stored in the
customizing scope. Depending on the scope of your changes, use one of the following transactions:

Transaction Code Description

/UI2/FLPCM_CONF
Allows you to make system-wide changes (configuration
scope).

SAP delivers predefined catalogs in the configuration scope.

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 9
Transaction Code Description

/UI2/FLPCM_CUST
Allows you to make changes for the current client (customiz­
ing scope). These changes supersede configuration settings.

Displays content available on the current client. In addition,

cross-client content is displayed but cannot be edited here.
You can filter the Scope column for “CUST” to display only
client-specific content.

 Note
The launchpad designer allows you to change cross-cli­
ent content in the customizing scope. However, this is
not recommended since it can lead to outdated catalogs
in the customizing scope. See Scope-Related Catalog Is­
sues [page 21].

End users can adjust content defined by the administrator and save their preferences in the personalization
scope. These settings supersede customizing and configuration settings.

Related Information

Scopes for Adapting Content [page 6]

1.5 Exploring Launchpad Content

The launchpad content manager helps you to explore existing content that you can use as the basis for your
own catalogs.

You can adjust the displayed list content by adding more columns. Select a row and choose Details in the
toolbar above the table to get all available information about a tile/target mapping combination or a catalog.

For example, you can get information to the following questions:

● Which tiles and target mappings in a given catalog match according to their intent (combination of
semantic object and action) and target application?
● Which matching tiles and target mappings are assigned to a given catalog?
● To which catalogs is a tile/target mapping combination assigned?
● Is the displayed tile or target mapping an original or a reference? In which catalog were original tiles and
target mappings created?

SAP Fiori Launchpad Content Manager

10 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
Related Information

Searching for Launchpad Content [page 11]

Tile/Target Mapping Combinations [page 11]
References and their Originals [page 12]

1.5.1 Searching for Launchpad Content

The launchpad content manager offers a search across all catalogs or tile/target mapping combinations
available in the system in which you are logged on.

Use the Search Catalogs and the Search Tiles/Target Mappings field to search across all visible columns of the
upper table of the respective tab. The search result list displays all items where at least one column is filled with
a text that contains the string you entered.

 Note

You can perform a wildcard search by adding the asterisk (*) symbol anywhere in the search string. For
example, entering my*cata*g* would return mycatalog, my_catalog56, my_brand_new_cata_good,
but not this_is_mycatalog as a search result. If you don't specify any wildcards, the system
automatically adds an asterisk before and after your search input.

You can use the standard SAP List Viewer (ALV) search and filter options to further restrict your search. See
Functions in the List.

 Example

You enter the string sales order in the Search Tiles/Target Mappings field. The search result table
displays all tile/target mapping combinations where at least one visible column is filled with a text that
contains the string you entered (for example, one item with the tile title Manage Sales Orders and one
item with the tile subtitle sales order_1). You add a filter for column Application Type to only display tile/
target mapping combinations that were defined for SAPUI5 apps. Select a tile/target mapping combination
and the catalogs to which it is assigned are displayed in the lower table. You can now select a catalog in the
lower table and choose Catalog View to find out which other tiles and target mappings are assigned to this
catalog.

1.5.2 Tile/Target Mapping Combinations

The launchpad content manager automatically maps matching tiles and target mappings and displays them in
the same row.

To make an app available to launchpad end users, administrators configure a tile to define its visual
representation on the launchpad home page, and a target mapping to define the navigation. See About
Launchpad Content [page 5].

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 11
To create or configure original tiles and target mappings, you use the launchpad designer or the Mass
Maintenance tool. The launchpad content manager allows you to reuse existing tiles and target mappings by
creating references to them.

The launchpad content manager displays matching tiles and target mappings as a combination in the same
row if the following applies:

● They have the same intent.

● They exist in the same catalog (as a reference or as an original).

The Tile/Target Mapping Matching field in the list of tiles and target mappings indicates whether a given row
displays a tile/target mapping combination or a single tile or target mapping without matching partner:

Value Description

Tile + TM The entry is a tile/target mapping combination.

If several tiles have the same intent as a single target mapping and vice versa, a
new row is created for each combination.

Tile Only There is no matching target mapping in the same catalog.

For example, when an application of type URL should be launched, no target map­
ping is needed.

TM Only There is no matching tile in the same catalog.

For example, when an app should not be launched from the launchpad home
page but from another app (app-to-app navigation), no tile is needed.

The Reference Detail field in the list of catalogs in the Tiles/Target Mappings tab indicates whether the tile/
target mapping was originally defined in a catalog or only exists as a reference. See References and their
Originals [page 12].

1.5.3 References and their Originals

The launchpad content manager allows you to find out in which catalog a tile or target mapping was originally
defined.

In the launchpad content manager, you can copy a catalog to create a new catalog with references to the tiles
and target mappings in the original catalog. Alternatively, you can create a catalog from scratch and add
references to tiles and target mappings to it.

To create or configure original tiles and target mappings, you use the launchpad designer. Tile and target
mapping can have different original catalogs.

To get information on the originals for a tile/target mapping combination and the catalog in which they were
defined, you have the following options:

● In the list of catalogs in the Tiles/Target Mappings tab, check the Reference Detail field to get an overview of
the catalog assignments and whether the selected tile/target mapping combination was created in the
catalog or is only a reference:

SAP Fiori Launchpad Content Manager

12 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
 Value Description

Original (Tile + TM) Tile and target mapping were originally defined in this cat­
alog.

Original (Tile Only) The tile was originally defined in this catalog. There is no
matching target mapping in this catalog.

Original (TM Only) The target mapping was originally defined in this catalog.
There is no matching tile in this catalog.

Reference (Tile + TM) Tile and target mapping only exist as a reference in this
catalog. The originals are located in another catalog.

Reference (Tile Only) The tile only exists as a reference in this catalog. The origi­
nal tile is located in another catalog. There is no matching
target mapping in this catalog.

Reference (TM Only) The target mapping only exists as a reference in this cata­
log. The original target mapping is located in another cata­
log. There is no matching tile in this catalog.

Mixed (Tile Original, TM Reference) The tile was originally defined in this catalog. The target
mapping only exists as a reference in this catalog. The
original target mapping is located in another catalog.

Mixed (Tile Reference, TM Original) The target mapping was originally defined in this catalog.
The tile only exists as a reference in this catalog. The origi­
nal tile is located in another catalog.

● In the list of tiles/target mappings, check the fields Original Tile ID and Original Target Mapping ID to find
the IDs of the originals.
● In the list of tiles/target mappings, check the fields Original Tile Catalog ID and Original Target Mapping
Catalog ID to find the catalogs in which the originals are located.
● In the list of tiles/target mappings, check the field Original Tile Repository to find out with which tool the
original tile was created and where it is stored:

Value Description

Web Dynpro The original tile was created in the launchpad designer
and is stored in the Web Dynpro repository.

Replicated The original tile was created in the backend using the
Mass Maintenance Tool and replicated to the front-end
server.

● In the list of tiles/target mappings, check the field Original Target Mapping Repository to find out with which
tool the original target mapping was created and where it is stored:

Value Description

Web Dynpro The original target mapping was created in the launchpad
designer and is stored in the Web Dynpro repository.

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 13
 Value Description

Replicated The original target mapping was created in the backend

using the Mass Maintenance Tool and replicated to the
front-end server.

LPD_CUST The original target mapping was created with transaction

LPD_CUST.

 Note
This approach is obsolete. See SAP Note 2614740 .

If the original tile or target mapping from which a reference tile or target mapping was created is deleted, the
reference is broken. In the launchpad content manager, this is indicated as a content error in the Status column
of the tile/target mapping list. See Issues with Tiles and Target Mappings [page 23].

1.6 Creating and Configuring Catalogs

Administrators use the launchpad content manager to set up catalogs according to their needs.

Related Information

Searching for Launchpad Content [page 11]

Creating Catalogs [page 15]
Copying Catalogs [page 16]
Adding and Removing Catalog Content [page 17]
Renaming Catalogs [page 19]
Deleting Catalogs [page 19]
Transporting Catalogs [page 20]

SAP Fiori Launchpad Content Manager

14 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
1.6.1 Read-Only Catalogs

Some catalogs cannot be edited in the launchpad content manager.

A marked checkbox in the Read-Only column of the catalog list indicates that the launchpad content manager
does not allow you to change the catalog. Here is how you can work with read-only catalogs in the launchpad
content manager:

Why the Catalog is Read-Only What you Can Do

The catalog was created in the backend using the Mass Create a new catalog with references to the tiles and target
mappings in the backend catalog.
Maintenance tool (transaction MM_APP) and replicated to the
front-end server.

The catalog is cross-client, i.e. stored on the configuration To change the cross-client catalog, launch transac­
tion /ui2/flpcm_conf. To make changes for the current
scope. You launched the client-specific launchpad content
client only, stay in transaction /ui2/flpcm_cust and copy
manager (customizing scope).
the catalog.

You are not logged on in the original language of the catalog. Re-start the launchpad content manager in the original lan­
guage of the catalog.

The catalog ID starts with "SAP" and the system is not an Create a new catalog with references to the tiles and target
SAP system. mappings in the SAP catalog.

1.6.2 Creating Catalogs

You can set up your content from scratch by creating a new catalog and adding content to it.

Procedure

1. In the Catalogs tab, choose Create.

2. Enter an ID and a title.

 Note

The ID must follow these conventions:

○ Max. 35 characters
○ Allowed characters: uppercase letters [A-Z], numbers [0-9], underscore [_]
○ May start with a reserved namespace (for example "/UI2/CATALOG_EXAMPLE")
See Development in Reserved Namespaces.

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 15
Results

An empty catalog is created. To add content to the catalog, see Adding Reference Tiles and Target Mappings to
a Catalog [page 17].

1.6.3 Copying Catalogs

You can create a copy of a catalog using the configuration or the customizing scope and then adapt it to your
needs by changing the title or by adding or removing reference tiles and target mappings.

Context

When you copy a catalog, the copied catalog references the tiles and target mappings in the original catalog.
Any changes to the tile or target mapping configuration in the original are reflected in the reference. You can
change the catalog without breaking the reference of the tiles and target mappings. You can make a copy of a
copied catalog.

 Note

You can only copy catalogs that do not contain content issues. See Issues with Tiles and Target Mappings
[page 23].

Procedure

1. Search for the catalog you want to copy. You can use the Search Catalogs field to search across all visible
columns. See Searching for Launchpad Content [page 11].
2. In the Catalogs tab, select the catalog to display its content.
3. Choose Copy.
4. Enter an ID and a title for the new catalog.

 Note

The ID must follow these conventions:

○ Max. 35 characters
○ Allowed characters: uppercase letters [A-Z], numbers [0-9], underscore [_]
○ May start with a reserved namespace (for example "/UI2/CATALOG_EXAMPLE")
See Development in Reserved Namespaces.

SAP Fiori Launchpad Content Manager

16 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
Results

A new catalog containing references to the tiles and target mappings in the original catalog is created.

You can adjust the catalog by changing its title or by adding or removing reference tiles and target mappings.

Related Information

Adding and Removing Catalog Content [page 17]

1.6.4 Adding and Removing Catalog Content

In the launchpad content manager, you can add or remove reference tiles and reference target mappings to
catalogs.

You can define whether only the tiles or only the target mappings should be added to or removed from the
catalog.

 Note

Adding and removing content is disabled for read-only catalogs. See Read-Only Catalogs [page 15].

In the launchpad content manager, you cannot create or delete original tiles and target mappings. Use the
launchpad designer for this action. See Adding or Removing Tiles or Target Mappings.

Related Information

References and their Originals [page 12]

1.6.4.1 Adding Reference Tiles and Target Mappings to a

Catalog

 Note

You can only add tiles and target mappings that do not contain issues. See Issues with Tiles and Target
Mappings [page 23].

To add reference tiles and target mappings to a catalog, you can first search for a catalog and then select the
content you want to add:

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 17
1. In the Catalogs tab, select the catalog to which you want to add reference tiles or target mappings.
2. In the toolbar of the lower table, choose Add Tiles/Target Mappings.
3. In the screen that opens, select one or more rows from the list of available tile/target mapping
combinations.
4. Choose one of the following buttons:
○ Add Tile/TM Reference to add the tile/target mapping combination
○ Add Tile Reference to only add the tile
○ Add TM Reference to only add the target mapping

Alternatively, you can first search for the relevant tiles and target mappings and then select the catalog to
which you want to add them:

1. In the Tiles/Target Mappings tab, select one or more rows from the upper table.
2. Choose Add Reference to Catalog.
3. In the screen that opens, select the catalog to which the tiles and target mappings should be added.
4. Choose one of the following buttons:
○ Add Tile/TM Reference to add the tile/target mapping combination
○ Add Tile Reference to only add the tile
○ Add TM Reference to only add the target mapping

1.6.4.2 Removing Reference Tiles and Target Mappings

from a Catalog

To remove reference tiles and target mappings from a catalog, you can first search for a catalog and then select
the content you want to remove:

1. In the Catalogs tab, select a row from the upper table. The lower table displays the content of the selected
catalog.
2. In the lower table, select one or more rows and choose Remove.

Alternatively, you can first search for the relevant tiles and target mappings and then select the catalog from
which you want to remove them:

1. In the Tiles / Target Mappings tab, select one row from the upper table. The lower table displays the
catalogs to which the selected tiles and target mappings are assigned.
2. In the lower table, select the relevant catalogs and choose Remove.

SAP Fiori Launchpad Content Manager

18 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
1.6.5 Renaming Catalogs

You can change the title of a catalog.

Context

 Note

This option is disabled for read-only catalogs. See Read-Only Catalogs [page 15].

Procedure

1. In the Catalogs tab, choose the catalog you want to rename. You can use the Search Catalogs field to search
across all visible columns. See Searching for Launchpad Content [page 11].
2. Choose Change Title.
3. Adjust the title as needed.

1.6.6 Deleting Catalogs

In the launchpad content manager, you can delete catalogs that do not contain original tiles or target
mappings.

Context

 Note

Catalogs can only be deleted if they do not contain any original tiles or target mappings. See References
and their Originals [page 12].

Procedure

1. Search for the catalog you want to delete. You can use the Search Catalogs field to search across all visible
columns. See Searching for Launchpad Content [page 11].
2. In the Catalogs tab, choose a catalog from the upper table.

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 19
3. Choose Delete.

1.7 Transporting Catalogs

Use the launchpad content manager to transport catalogs.

If you want to transport catalogs, make sure a relevant transport request is available:

Scope Required Transport Request

Launchpad Content Manager: Client-Specific (Customizing) Customizing request

(transaction /UI2/FLPCM_CUST)

Launchpad Content Manager: Cross-Client (Configuration) Workbench request

(transaction /UI2/FLPCM_CONF)

Transports for Client-Specific Catalogs

The client-specific launchpad content manager (transaction /UI2/FLPCM_CUST) takes the settings in Display
View "Clients": Overview (transaction SCC4) into account. These settings control whether objects can be
changed and whether the changes can be transported.

Setting in SCC4 Description

Changes without automatic recording The launchpad content manager does not display a prompt
for customizing request when you make changes.

Automatic recording of changes The launchpad content manager displays a prompt for cus­
tomizing request when you make changes.

No changes are allowed The launchpad content manager runs in read-only mode.

Changes w/o automatic recording, no transports allowed The launchpad content manager allows you to make
changes but not to transport them.

Manually triggering transports

You can use this feature to trigger the transport of changes when the option Changes without automatic
recording is set for the client. This feature also allows you to transport catalogs independent of a change, for
example, to make catalogs that were created locally in the launchpad designer available in other clients or
systems.

The option to manually trigger transports is available if the following prerequisites are met:

● In transaction SCC4, the client role is set to Customizing.

● In transaction SCC4, the option Changes w/o automatic recording, no transports allowed is not set for your
client.
● The catalog you want to transport is client-specific (customizing scope). This is indicated in the Scope
column.

SAP Fiori Launchpad Content Manager

20 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
To trigger the transport, proceed as follows:

1. In the Catalogs tab, choose a catalog from the upper table.

2. In the toolbar above the upper table, choose Transport.
3. In the dialog box that appears, select the customizing request that should be used for the transport.

Transports for Client-Independent Catalogs

When you trigger a change in the client-independent launchpad content manager (transaction /UI2/
FLPCM_CONF), a dialog box is displayed in which you define whether you want to save your changes locally or
transport them to other systems. To transport your changes, select a package and a workbench request.

1.8 Displaying Issues with Launchpad Content

The launchpad content manager displays issues with launchpad content.

The following issues are displayed:

● The catalog state is different on the configuration and the customizing scope.
● References to tiles and target mappings cannot be resolved.
● There are issues with the configuration of tile and target mapping.

For further analysis of content issues, use the tools described under Support Tools.

Related Information

Scope-Related Catalog Issues [page 21]

Issues with Tiles and Target Mappings [page 23]

1.8.1 Scope-Related Catalog Issues

The launchpad content manager indicates if the state of a catalog differs on the configuration and the
customizing scope.

The launchpad designer allows you to make client-specific changes to cross-client catalogs (for example,
changing the catalog title or adding tiles). In this case, a copy of the cross-client catalog is created in the
customizing scope. This copy has the same ID as the original catalog in the configuration scope. If the original
catalog contains original tiles/target mappings, the copied catalog includes these objects as originals with the
same ID. The copied catalog in customizing is now decoupled from the catalog in the configuration scope. Any
changes made in the configuration scope (except changes of texts in tiles or target mappings) are no longer
reflected in the customizing scope.

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 21
  Note

To prevent these inconsistences, cross-client catalogs cannot be changed in the client-specific launchpad
content manager. We recommend you to change the cross-client catalog in the configuration scope
(transaction /ui2/flpcm_conf) or to copy the catalog in the customizing scope (transaction /ui2/
flpcm_cust) and make changes for the current client only. See Read-Only Catalogs [page 15].

How to Display the Issue

1. Launch the client-specific launchpad content manager (transaction /ui2/flpcm_cust).

2. Open the Catalogs tab.
3. Filter the Scope column for Customization.
4. Check the value of the Status in Current Client column:

Value Description

Original The catalog was created in the current client and does not exist in the configuration scope.

Changed The catalog was created in the configuration scope and changed in the current client using the
launchpad designer, which means that it is now decoupled from the original catalog on the con­
figuration scope. If the original catalog is now changed in the configuration scope, these changes
will not be reflected in the current client.

Outdated The catalog was created in the configuration scope and changed in the current client using the
launchpad designer, which means that it is now decoupled from the original catalog on the con­
figuration scope. The original catalog was then changed in the configuration scope. The catalog
on the current client is outdated because the changes in the configuration scope are no longer
reflected. If the catalog is now changed in the customizing scope, its status will be set to
"Changed" again.

How to Deal with the Issue

If a catalog is outdated, you have the following options:

● Update the catalog to the latest changes of the configuration scope. Changes made in the customizing
scope will be lost.
○ If the catalog does not contain any original tiles or target mappings, you can use the launchpad content
manager to delete the client-specific catalog in the customizing scope.
See Deleting Catalogs [page 19].
○ In the launchpad designer, you can reset the outdated catalog. This also works if the outdated catalog
contains originals.
See .
● Continue working with the existing changes of the customization scope. In this case, you do not receive the
latest changes provided in the configuration scope.

SAP Fiori Launchpad Content Manager

22 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
1.8.2 Issues with Tiles and Target Mappings

The launchpad content manager indicates broken references and issues with the configuration of tiles and
target mappings.

To display the issues, proceed as follows:

1. In the list of tiles and target mappings, filter the Status column for warnings and errors.
2. Check the Title / Subtitle / Information column to get a first hint about the issue:
○ {Reference Lost to Backend Catalog}
○ {Reference Lost}
○ {Configuration Error}
3. To get further information on the issue, open the context menu for a selected row and choose Status
Details.

The launchpad content manager detects the following issues with tiles and target mappings:

Issue Category Status Description How to Deal With the Issue

Reference Lost to Tile/target map­ Warning The selected tile/ If the referenced content is still rele­
Backend Catalog ping reference is­ target mapping re­ vant, proceed as follows:
sue fers to an original
1. Identify the catalog in which the
tile/target map­
original tile/target mapping was
ping which was de­
defined using the Original Tile
fined in the back­
Catalog ID and Original Target
end using the
Mapping Catalog ID columns.
Mass Maintenance
2. Replicate the catalog to the front-
tool.
end server.
The reference is See Extract Back-End Catalogs.
broken because
the original tile/
target mapping or
the catalog in
which the originals
were defined do
not exist on the
front-end server.

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 23
Issue Category Status Description How to Deal With the Issue

Reference Lost Tile/target map­ Error The selected tile/ If the referenced content is still rele­
ping reference is­ target mapping re­ vant, proceed as follows:
sue fers to an original
1. Identify the catalog in which the
tile/target map­
original tile/target mapping was
ping which was de­
defined using the Original Tile
fined in another
Catalog ID and Original Target
catalog.
Mapping Catalog ID columns.
The reference is 2. Check whether the original catalog
broken because and tile/target mapping definition
the original tile/ can still be found in another sys­
target mapping or tem or whether it was accidentally
the catalog in deleted. Make sure to check both
which the originals the customizing and the configura-
were defined do tion scope.
not exist in the 3. If you can find the catalog in an­
system or client. other system, transport it to the
system in which you found the bro­
ken reference.
4. If this does not help, remove the
broken reference and create a new
one.

Configuration Er­ Tile/target map­ Error An instance of the Check the tile configuration in the
ror: Tile Configura- ping configuration tile was created in launchpad designer and maintain it cor­
tion Does not Exist issue the catalog, but rectly. See Configuring Tiles.
the tile configura-
tion form was not
filled out.

Configuration Er­ Tile/target map­ Error An instance of the Check the target mapping configuration
ror: Target Map­ ping configuration target mapping in the launchpad designer and maintain
ping Configuration issue was created in the it correctly. See Configuring Target
Does not Exist catalog, but the Mappings.
target mapping
configuration form
was not filled out.

Configuration Er­ Tile/target map­ Error The tile configura- Check the tile configuration in the
ror: Invalid Tile ping configuration tion contains er­ launchpad designer and maintain it cor­
Configuration issue rors. rectly. See Configuring Tiles.

Configuration Er­ Tile/target map­ Error The target map­ Check the target mapping configuration
ror: Invalid Tile/ ping configuration ping configuration in the launchpad designer and maintain
Target Mapping issue contains errors. it correctly. See Configuring Target
Configuration Mappings.

Configuration Er­ Tile/target map­ Error The configuration Open the catalog in the launchpad de­
ror: Custom tile ping configuration of the custom tile signer to display information on the
data could not be issue could not be ex­ custom tile.
read tracted. This leads
to incomplete in­
formation about
this item.

SAP Fiori Launchpad Content Manager

24 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
Issue Category Status Description How to Deal With the Issue

Configuration Er­ Tile/target map­ Error The LPD_CUST ● In the launchpad designer, check
ror: LPD_CUST ping configuration entry referenced
the configuration of the target
data could not be issue by the tile/target
mapping for application type SAP
read mapping configu-
ration in the Fiori App using LPD_CUST. See
launchpad de­ Configuring Target Mappings.
signer was not ● In transaction LPD_CUST, check
found. the respective settings. See
Changing LPD_CUST Entries for
Navigation Targets.

App descriptor not Tile/target map­ Warning The app descriptor Depending on the root cause, proceed
found ping configuration for the SAPUI5
as follows:
issue component ID was
not found by the ● No SAPUI5 Fiori app with the refer­
SAPUI5 applica­ enced ID exists:
tion index. In the launchpad designer, check
the entry of the ID field of the tile/
target mapping configuration. See
Configuring Target Mappings.
● A SAPUI5 Fiori app with this ID ex­
ists in the SAPUI5 ABAP reposi­
tory, but the app index is not set up
correctly
Ensure the app index is set up cor­
rectly. See SAPUI5 Application In­
dex.
● A SAPUI5 Fiori app exists outside
the SAPUI5 ABAP repository. An
app descriptor exists but for this
case is not returned by the app in­
dex search.
● Known case: SAPUI5 Fiori apps
provided by /ui2/ushell library
Open the target mapping configu-
ration in the launchpad designer
and check the value of the URL
field. See Configuring Target Map­
pings.

Related Information

Displaying Issues with Launchpad Content [page 21]

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 25
1.9 Best Practices for Managing Catalogs

Catalogs are the smallest entities that define the set of apps you want to assign to your users for selection and
authorization.

SAP delivers apps (tiles and target mappings) in technical catalogs and business catalogs:

● Technical catalogs, naming convention <...>_TC_<...>

Technical catalogs serve as a repository of all apps delivered by SAP. They contain all target mappings and
app launcher tiles relevant for apps per application area. They contain original tiles and target mappings
which can be referenced from business catalogs. Technical catalogs are not intended to be assigned
directly to users.
● Business catalogs, naming convention <...>_BC_<...>
Business catalogs contain a sample collection of target mappings and app launcher tiles relevant for a
business role. The content of the business catalog is a subset of the content of the technical catalog. This
subset reflects the requirements of a specific business user.

The distinction into technical catalogs and business catalogs is only a convention; there is no difference from a
technical point of view.

The following graphic shows the relation between these two entities:

SAP catalogs are always located in the configuration scope (CONF). The SAP business catalogs (SAP_BC in the
graphic) contain references to the tiles and target mappings contained in the technical catalogs (SAP_TC).
These references exist only on tile/target mapping level; there are no references on catalog level. The
references ensure that any changes to the original tile or target mapping can be made centrally in the technical
catalog and are propagated to the business catalog.

Using SAP Catalogs Without Changes

You can reuse the business catalogs delivered by SAP as they are by assigning them directly to roles.

1. Browse the SAP Fiori apps reference library for the applications of interest and find out the relevant PFCG
roles.
2. In transaction PFCG, copy the roles delivered by SAP and assign them to your users. See Assigning Users to
Roles.

SAP Fiori Launchpad Content Manager

26 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
Recommendations for Adapting SAP Catalogs

If you want to adapt the content delivered by SAP, use the SAP business catalogs as a starting point. We
recommend the following:

● Do not change SAP catalogs. Instead, copy SAP business catalogs to use them as the starting point for
creating your own business catalogs.
This will ensure to get a consistent set of SAP Fiori apps that supports app-to-app navigation by including
the relevant target mappings. This will not necessarily be the case when you select only a set of single apps
from the technical catalogs.
Exception: Some apps (mainly SAP GUI for HTML apps) are not contained in any business catalog and are
only delivered as part of technical catalogs. In these cases, you need to select a single app (tile/target
mapping) from the technical catalog and add it as a reference to your custom business catalog.
● Create separate catalogs for the provisioning and usage of tiles and target mappings:
○ Technical catalogs: Contain original tiles and target mappings
○ Business catalogs: Contain references to the tiles and target mappings in the technical catalogs
This facilitates the reuse of catalog content because one original tile/target mapping can be referenced
from several catalogs. Any changes to the original tiles and target mappings are automatically reflected in
the reference (unless the configuration of the reference tile/target mapping was changed).
● Create and change your catalogs in the following scopes:
○ Technical catalogs: Configuration scope
This allows you to reuse the tiles and target mappings created in the technical catalogs in all clients.
○ Business catalogs: Customizing scope
This allows you to manage business catalogs for a selected client.
Do not change catalogs that were created in the configuration scope while you work in the customizing
scope since this could lead to outdated catalogs.
● Use the following tools to create and change your catalogs:
○ Technical catalogs: Launchpad designer or Mass Maintenance tool
○ Business catalogs: Launchpad content manager
See Tools for Setting Up Content [page 8].
● A catalog should not contain more than 100 apps (tile/target mapping combinations).
This helps prevent performance issues at design time (for example, when the catalog is copied).

The following graphic shows a setup that takes these recommendations into account:

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 27
The SAP business catalog (SAP_BC) residing in the configuration scope (CONF) contains references to the tiles
and target mappings in the SAP technical catalog (SAP_TC). The SAP business catalog (SAP_BC) was copied
to the customer namespace in the customizing scope (CUST). The copied catalog (Customer_BC) contains
references to the tiles and target mappings in the SAP technical catalog (SAP_TC). The content of the copied
catalog (Customer_BC) was then adjusted by adding references to the tiles and target mappings in SAP
technical catalogs and custom technical catalogs (Customer_TC).

Procedure

The following procedure shows the recommended steps for adjusting an SAP business catalog by adding and
removing apps.

SAP Fiori Launchpad Content Manager

28 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
● #unique_11/unique_11_Connect_42_subsection-im1 [page 29]
● #unique_11/unique_11_Connect_42_subsection-im2 [page 29]
● #unique_11/unique_11_Connect_42_subsection-im3 [page 30]
● #unique_11/unique_11_Connect_42_subsection-im4 [page 30]
● #unique_11/unique_11_Connect_42_subsection-im5 [page 30]
● #unique_11/unique_11_Connect_42_subsection-im6 [page 31]

Click a step to display more information.

Explore SAP content

Use the SAP Fiori apps reference library to search for relevant apps and find an SAP business catalog that is
suitable as a template for your own business catalog.

See SAP Fiori apps reference library.

You can also use the launchpad content manager to find catalogs that best suit your needs.

See Searching for Launchpad Content [page 11].

Copy SAP business catalog

1. In your ABAP system, start transaction /UI2/FLPCM_CUST to open the launchpad content manager in the
customizing scope. This allows you to make client-specific changes.
See Running the Launchpad Content Manager [page 9].
2. In the Catalogs tab, use the Search Catalogs field to find the SAP business catalog you want to use as a
template.
See Searching for Launchpad Content [page 11].
3. Copy the catalog. Your copied catalog will include references to the tiles and target mappings in the SAP
catalog.
See Copying Catalogs [page 16].

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 29
You can now adjust the content of the copied catalog.

Remove apps from your business catalog

In the launchpad content manager, select your business catalog and remove the references to the tiles and
target mappings you don’t need.

See Adding and Removing Catalog Content [page 17].

Change tiles/target mappings

You can make changes to the tile/target mapping combination for your app. For example, you can adjust the
tile title or the parameters passed between related apps.

1. Depending on the app type, use one of the following tools to change tiles/target mappings:
○ Web Dynpro ABAP and SAP GUI apps: Use the Mass Maintenance tool.
See Create Application Descriptors Using the Mass Maintenance Tool.
○ SAP Fiori UI5 apps and URLs: Use the launchpad designer.
See Configuring Tiles and Configuring Target Mappings.
2. If the original tile/target mapping resides in an SAP catalog, you cannot change it directly. You need to first
make it available in your own technical catalog:
○ Mass Maintenance tool: Create a new tile/target mapping based on the existing one.
Be careful if you copy app descriptors from one technical catalogue to another. You must ensure that
all relevant columns (those that contain data) are visible before you select an app descriptor in the
MMT to copy and paste; some columns might be hidden (use the Settings button to check this).
Additionally, check the Parameters and Tile Parameters tabs for relevant information that you also
need to copy over.
○ Launchpad designer: Add a reference to the tile/target mapping to your technical catalog and make
the required changes in the reference. Note that once you make changes to the reference tile/target
mapping, it is decoupled from the original.
See Copying Tiles or Target Mappings.

You can now add the changed tiles/target mappings as references to your business catalog.

Create tiles/target mappings

If there is no suitable tile/target mapping combination for your app, create a technical catalog with the original
tiles/target mappings in the configuration scope.

For SAP Fiori apps that should be visible as tiles in the SAP Fiori launchpad, you add the app launcher tile and a
target mapping to the catalog. For SAP Fiori apps not visible as tiles, as for example object pages, you only add
the target mapping to the catalog. Object pages correspond to business objects. They are started by navigating
from other applications or by using the search. By choosing a business object representation in an app or a
search result, users navigate to the corresponding object page.

Depending on the app type, we recommend the following tools:

● Web Dynpro ABAP and SAP GUI apps: Use the Mass Maintenance tool.
See Integrating Back-End Applications Using Mass Maintenance.
● SAP Fiori UI5 apps and URLs: Use the launchpad designer in the configuration scope (transaction
Integrating Applications Using Mass Maintenance/UI2/FLPD_CONF).
See Setting Up Content With the Launchpad Designer

You can now add the changed tiles/target mappings as references to your business catalog.

SAP Fiori Launchpad Content Manager

30 PUBLIC Setting Up Catalogs with the Launchpad Content Manager
Add apps to your business catalog
1. Re-start the launchpad content manager (transaction /UI2/FLPCM_CUST) to get the content changes
made in other tools.
2. Add references to the desired tile/target mapping combinations.
See Adding Reference Tiles and Target Mappings to a Catalog [page 17].

Next Steps

1. In the launchpad designer, add the apps from your catalogs to groups to have them displayed on the user’s
launchpad homepage.
See .
2. In transaction PFCG, assign groups and catalogs to users' PFCG roles to define which users have access to
them.
See Configuring Roles for Tile Catalogs and Groups.

Related Information

About Launchpad Content [page 5]

Scopes for Adapting Content [page 6]
Tools for Setting Up Content [page 8]

SAP Fiori Launchpad Content Manager

Setting Up Catalogs with the Launchpad Content Manager PUBLIC 31
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:

● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.

Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

SAP Fiori Launchpad Content Manager

32 PUBLIC Important Disclaimers and Legal Information
SAP Fiori Launchpad Content Manager
Important Disclaimers and Legal Information PUBLIC 33
www.sap.com/contactsap

© 2019 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. The information contained herein may be changed
without prior notice.

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 or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP 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.

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. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

THE BEST RUN