
SAP Fiori is part of the SAP Reference Implementation Guide (IMG). Transaction /UI2/CUST can be used to access only the UI-relevant parts of the IMG. The main parts for SAP Fiori are as follows:
- Initial Setup for system administrators
- SAP Fiori Launchpad Settings for content and system administrators
- Setting Up Launchpad Content for business specialists, content administrators, and developers
- Setting Up Launchpad Layout and Structure for business specialists and content administrators
- Setting Up Roles for content administrators, business specialists, and authorization specialists
- Launchpad Support Tools for business specialists, content administrators, and developers
- Launchpad Data Administration for content and system administrators
- Exposing Content to SAP BTP for business specialists and content administrators
Note
The SAP BTP service handling SAP Fiori content is called SAP Build Work Zone, standard edition.
Overview Roles, Spaces, Pages

Since SAP S/4HANA 2021, transaction /UI2/RSP_LIST provides an overview of spaces and pages per business role. With that it is possible to get a list of the tiles the users see in their SAP Fiori launchpad (FLP) spaces. It is possible to research the apps and their origin catalogs or if there are pages assigned but hidden.

Since SAP S/4HANA 2020, transaction /UI2/FLPCA shows all content assigned to business roles. This is very useful for getting an overview of everything a user gets in the SAP Fiori launchpad (FLP) when assigning roles:
- Sort by catalogs to show the content in the app finder.
- Sort by semantic object to show the intent-based navigation links.
- Sort by services to show the technical prerequisites.
- Sort by successor transaction to show deprecated apps.
Note

An important support tool for the FLP configuration is transaction /UI2/FLC. It checks the consistency of delivered and customized catalogs and groups for configuration and customizing. It quickly identifies problems in target mappings and tiles concerning elements of the intent-based navigation and parameters.

Transaction /UI2/FLIA also shows errors and problems in target mappings, but it goes deeper. It offers a full intent analysis for semantic objects and actions per role and user. Through this analysis, duplicated intents pointing to different targets can also be found. A full intent resolution analysis takes some time, depending on the number of semantic objects and actions in the system. It is recommended to restrict the analysis to the assigned roles of a user.

Since SAP S/4HANA 2023, every change to a technical catalog or an app descriptor can be seen in transaction /UI2/FLPAM_LOG. The changes were already being logged before in the Application Log (SLG1 with object FLPAM). But the new transaction makes it easier to find the relevant information by offering more selection options and a better visibility.

There are many other transactions available for logging, tracing, cache handling, cleanup, and so on, in the areas of SAP Fiori, SAPUI5, and SAP Gateway. There is no need to know them all by heart. Transaction /UI2/CUST organizes all of them as a tree in the implementation guide.
Note