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:
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.
SAP Fiori Launchpad Content Aggregator
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.
SAP Fiori Launchpad Content Check Report
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.
SAP Fiori Launchpad Intent Analysis
/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.
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.