/UI2/FLPD_CUST — Fiori Launchpad Designer (Client-Specific)

Every Fiori app reachable from the launchpad needs a tile and a target mapping in a catalog that the user's role includes. The launchpad designer is where custom catalogs are built, standard catalogs are referenced and target mappings are adjusted. Client-specific changes are recorded in customizing requests, so they can be transported through the landscape.

It is used when adding custom or standard apps to business catalogs, when adjusting tiles or parameters, and when troubleshooting 'could not open app' errors caused by missing or wrong target mappings. In S/4HANA projects, teams often copy SAP's business catalogs into custom ones here.

Open the designer, select or create a catalog, add tiles and target mappings, and assign the customizing request when prompted. Target mappings need the semantic object, action, application type and component or URL. After saving, assign the catalog to a role in PFCG and test with a user who has only that role.

For an app that does not start, find its intent in the browser address or console, then look for a target mapping with the same semantic object and action in a catalog assigned to the user's role. If none exists, or the parameters or device types do not match, intent resolution fails exactly as the user reports.

Still used in S/4HANA on-premise and private cloud. Newer releases favour the launchpad content manager and spaces and pages, and SAP recommends working with business catalogs and roles rather than editing tiles directly where possible.

Most problems are missing references between catalogs, roles and mappings.

Owned by the Fiori content or security team, which keeps catalogs, roles and transports consistent. Functional teams define which apps each role needs, and changes should follow the same transport discipline as other customizing.