The Fiori Launchpad is the entry point for every S/4HANA user, so FLP questions appear in Fiori, UI5, and Basis interviews alike. These are the questions interviewers actually ask, with answers that show you have configured one — not just read about one.
Launchpad Basics
What is the SAP Fiori Launchpad?
The Fiori Launchpad is the role-based entry point to SAP Fiori apps. It gives users a single home page for their tiles, cross-app search, and notifications. Every S/4HANA user starts their day here, which is why its configuration matters so much.
What is the difference between the ABAP launchpad and the launchpad on BTP?
The ABAP launchpad runs inside the S/4HANA or Gateway system and reads its configuration from that system's PFCG roles. The launchpad service on BTP runs in the cloud and aggregates apps from multiple backends.
How does a user get access to launchpad content?
Through PFCG roles. A role contains launchpad catalogs (and historically groups), and the user assigned to the role sees the tiles those catalogs provide. No role assignment means an empty launchpad — the most common "my tiles are missing" root cause.
Spaces, Pages, Catalogs
What are spaces and pages in the Fiori Launchpad?
Spaces and pages are the current structuring model for launchpad content, replacing the older groups concept. A space is a themed area (like "Procurement"), and a page is a tab-like section within it holding tiles.
What is the difference between a catalog and a group (or page)?
A catalog is an administrative collection of tiles — it defines what exists and who may see it. A group or page is a visual arrangement of tiles on the user's home page. Catalogs are assigned via roles for authorization; groups and pages control what the user actually sees and can be personalized.
Where do you configure spaces, pages, and catalogs?
In the Fiori Launchpad Designer (transaction /UI2/FLPD_CUST for customizing, /UI2/FLPD_CONF for configuration) on the ABAP system. You create catalogs, define tiles within them, and assemble pages and spaces.
Can end users personalize the launchpad?
Yes — users can add tiles from catalogs they are authorized for, rearrange tiles on pages, and hide tiles they do not use. Administrators can lock down personalization per role if a standardized layout is required. Personalization is stored per user and survives upgrades.
Key takeaway: catalog = what exists and who may see it; page/space = how it is arranged. Mixing these up is the classic interview trap.
Tiles and Navigation
What types of tiles exist in the launchpad?
Static tiles show a fixed title and icon. Dynamic tiles display live data from an OData service, such as a count of open purchase orders. News tiles show feed content. KPI tiles visualize a key figure. The tile type determines both the visual and the data binding behind it.
What are semantic objects and actions in Fiori navigation?
Semantic objects and actions implement intent-based navigation — instead of linking to a URL, a tile targets an intent like SalesOrder-display. The launchpad resolves the intent to the actual app at runtime. This decoupling means apps can be replaced or moved without changing every tile.
How does cross-application navigation work in code?
Through the CrossApplicationNavigation service of the unified shell container. Your UI5 controller calls toExternal with a target intent and parameters, and the launchpad navigates to the matching app.
var oCrossAppNav = sap.ushell.Container.getService("CrossApplicationNavigation");
oCrossAppNav.toExternal({
target: { semanticObject: "SalesOrder", action: "display" },
params: { SalesOrder: "12345" }
});What is the difference between a URL tile and an app launcher tile?
An app launcher tile opens a Fiori app via intent-based navigation within the launchpad shell. A URL tile simply opens an external or internal URL, optionally in a new tab. URL tiles are the quick way to link legacy transactions or external tools from the launchpad.
Administration and Troubleshooting
A user reports an empty launchpad. What do you check?
First, verify the user has PFCG roles containing launchpad catalogs assigned and that the roles are generated. Then check the /UI2/ OData services are active and the user is authorized for them.
How do you transport launchpad content between systems?
Launchpad customizing — catalogs, tiles, pages, spaces — is captured in transport requests from the customizing client. Never configure content directly in production; always build in development and transport.
How do notifications work in the launchpad?
Apps push notifications through the notification channel to the launchpad's notification center. Users see a bell icon with a count and can act on items directly. The backend workflow or app must be configured as a notification provider, and the user needs the relevant subscription.
Key takeaway: most FLP troubleshooting questions are really authorization and role questions in disguise.
Faced a Fiori Launchpad question that stumped you? Post it in the comments.