Show TOC

Launchpad Content Checks Locate this document in the navigation structure

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.

Troubleshooting

Correct standard issues with launchpad content

The tool analyses the current configuration for standard problems that appear during content preparation and helps you to fix errors and warnings effectively.

The table below lists the checks performed and the problems reported by the report and explains the necessary action by the user:

Table 1:
Check Test and Problem Type Action
Catalog checks (CAT*)
  • CAT01 (Error): Catalog does not have software component assigned

  • CAT02 (Error): Catalog does not have package assigned

  • CAT03 (Warning): Catalog does not have tiles (empty)

To be fixed in SAP Fiori launchpad designer
Group checks (GRP*)
  • GRP01 (Error): Group does not have software component assigned

  • GRP02 (Error): Group does not have package assigned

  • GRP03 (Warning): Group does not have tiles (empty)

  • GRP04 (Error): Tile in group has an error
  • GRP05 (Errror): Application launcher in the corresponding catalog was a reference to an original but the original application launcher was deleted. Therefore, the reference is broken.
To be fixed in SAP Fiori launchpad designer
Target mapping checks (TM*)

  • TM01 (Error): Semantic object used in target mapping does not exist

  • TM02 (Error): Action is not defined for target mapping

  • TM03 (Warning): Target mapping action does not start with lower case

  • TM04 (Error): Launchpad (transaction LPD_CUST) used in target mapping does not exist in this client

  • TM05 (Error): When specifying the navigation target in the target mapping definition for SAPUI5-based SAP Fiori apps, the SAPUI5 component was not entered correctly.
  • TM06: (Error): Target mapping was a reference to an original but the original target mapping was deleted. Therefore, the reference is broken.
To be fixed in SAP Fiori launchpad designer

TM07: Issues regarding the system alias that is referenced in the target mapping configuration

For the list of checks, see System Alias Checks.

To be fixed using the IMG activities Manage SAP System Aliases or Manage RFC Destinations.

Application launcher checks (AP*)
  • AP01 (Error): Semantic object targeted by application launcher does not exist

  • AP02 (Error): Application launcher has empty action

  • AP03 (Warning): Action used in application launcher does not start with lower case

  • AP04 (Error): Application launcher does not have valid target mapping for object or action within the same catalog

  • AP05 (Error): Application launcher was a reference to an original but the original application launcher was deleted. Therefore, the reference is broken.
To be fixed in SAP Fiori launchpad designer
ABAP launchpad checks (LP*)
  • LP01 (Error): Unspecified error in launchpad (transaction LPD_CUST)

  • LP02 (Error): Additional info field of launchpad definition must contain 'SAPUI5.Component=' (type URL)

  • LP03 (Error): System alias in launchpad definition is not empty (type URL)

  • LP04 (Error): System alias in launchpad definition is empty (type non-URL)

  • LP05 (Error): Target app parameters field is empty for launchpad definition with additional information equal "SAPUI5.Component=factsheet"

  • LP06 (Warning): Encoding of target app parameter is invalid

To be fixed in transaction (LPD_CUST)

Correct issues with translated launchpad texts

An end user of the launchpad has reported an issue with a translated text in a custom tile, catalog, or group title. You can use Fiori Launchpad Checks to easily find the relevant text in the translation system and correct it.

See Translating Tiles, Catalogs, and Groups.

Data Analysis and Monitoring

You want to analyze launchpad content and improve the content lifecycle.

For example, you can analyze the following questions:
  • Are the naming conventions for catalogs, groups and tiles applied consistently?
  • Are the settings for device types applied correctly?
  • Are there any tiles or target mappings which are not used in roles?

    If yes, you should either enhance the roles or delete the tiles and target mappings that are no longer required.
  • How many catalogs are available for each product area?
  • Which applications are used as navigation targets in a given launchpad?

    For example, how many Web Dynpro ABAP applications are referenced as opposed to SAPUI5 applications?
  • Which application types are referenced from a given catalog?

The content check report retrieves the following types of information:

Check

Description

INFO_AP Provides information on static app launcher tiles
INFO_DAP Provides information on dynamic app launcher tiles
INFO_CR Provides information on catalogs
INFO_GR Provides information on groups
INFO_GR_AP Provides information on tiles in groups
INFO_TM Provides information on target mappings