Fiori Fundamentals
What is SAP Fiori, and how is it different from SAP GUI?
Fiori is SAP's role-based, responsive UX design system delivered through web apps on the Fiori launchpad. Unlike SAP GUI's transaction-centric screens, Fiori apps are task-focused, work on any device, and follow consistent design guidelines. From a functional view: one role, one launchpad, only the apps that role needs.
What are the three Fiori app types, and when is each used?
Transactional apps handle structured tasks like creating a purchase order — the successor to GUI transactions. Analytical apps provide KPI insight with charts and drill-down, often powered by Smart Business or embedded analytics. Fact sheets display the 360-degree view of a business object, like a customer, with navigation to related objects. Know one example of each.
What is the Fiori launchpad, and what are its main areas?
The launchpad is the single entry point: a home page of tiles grouped by business area, plus the app finder for searching the catalog. Tiles can be static or dynamic (showing live KPI numbers). The Me Area holds user settings and the shell bar provides search, notifications, and navigation. Functional consultants configure which tiles appear per role.
Key takeaway: Fiori is role-based UX, not transaction-based. If you can explain tiles, groups, and catalogs clearly, you have the launchpad story down.
Roles, Catalogs, and Authorization
How do business catalogs and business roles control app access?
Business catalogs bundle apps by business function — e.g. a "Purchasing" catalog holds all purchasing apps. Business roles (maintained in PFCG) reference catalogs and groups, and users get roles assigned to them. A user sees a tile only if their role includes the catalog containing that app. Catalogs are content; roles are access.
What is the difference between a technical catalog and a business catalog?
Technical catalogs contain the raw app definitions and OData service authorizations shipped by SAP. Business catalogs are customer-facing groupings created by referencing technical catalog content. Best practice: never assign technical catalogs directly to end-user roles — always go through business catalogs so SAP updates don't disrupt your role design.
How do you find which Fiori app covers a business requirement?
Use the Fiori apps reference library (fioriappslibrary.hana.ondemand.com): search by business process or old transaction code, and it shows the app, required catalogs, and product version. This is the functional consultant's first stop in any fit-gap workshop. Mention it by name — interviewers expect it.
What PFCG authorizations does a Fiori app need beyond the catalog?
The role needs the OData service authorization (S_SERVICE for the service) and the underlying business authorizations the app checks — e.g. purchasing authorization objects. A common interview trap: the tile is visible but the app errors on launch, which usually means the OData service authorization is missing from the role.
App Types in Functional Detail
How does a functional consultant handle a requirement with no standard Fiori app?
First check the apps library for a close match or a newer app version. If none exists, evaluate key-user extensibility: custom fields and custom logic in S/4HANA Cloud, or in-app extensibility on-premise. Only then consider custom development via a custom Fiori app or a side-by-side extension on BTP. The order matters — standard first, extend second, build last.
What is the difference between in-app extensibility and side-by-side extensibility?
In-app extensibility changes the standard app itself: custom fields added through the Custom Fields app, or UI adaptations via key-user tools — no code deployment needed. Side-by-side extensibility builds separate apps on BTP that call S/4HANA APIs, keeping the core clean. Functional consultants drive the first; developers own the second.
What are adaptation projects in the context of Fiori?
Adaptation projects let key users rearrange, hide, or rename fields and controls in a standard Fiori app through the UI Adaptation editor at runtime. The changes are stored as flexibility layers tied to roles, so different roles can see different layouts. This is the clean-core answer to "can we move this field?"
Key takeaway: The functional extensibility ladder is standard app, key-user adaptation, custom fields, then custom development. Recite it in that order.
Implementation and Operations
What is the Fiori launchpad content manager's role in a project?
Someone — usually the functional or security consultant — must assemble business catalogs, groups, and roles per business role defined in the blueprint. This includes mapping old GUI transaction authorizations to new app catalogs and testing tile visibility per role. It is a discrete workstream in every S/4HANA project, not an afterthought.
How do dynamic tiles and KPI tiles get their data?
Dynamic tiles refresh numbers from an OData service or a KPI model defined in the KPI workspace. From the functional side, you configure the tile's data source, refresh interval, and semantic object for navigation. If a tile shows no data, check the OData service activation and the user's authorization before anything else.
What is a semantic object and why does it matter?
Semantic objects (like PurchaseOrder or Customer) plus actions (display, manage) define intent-based navigation between apps. Instead of hardcoding URLs, apps navigate via semantic object + action, and the launchpad resolves the target. This decoupling is what lets SAP replace apps without breaking navigation — a favorite conceptual interview question.
How do notifications work in the Fiori launchpad?
The notification center in the shell bar aggregates workflow and alert notifications pushed by backend systems. Functional consultants configure notification providers and subscription per app. For approval workflows — purchase requisitions, leave requests — the My Inbox app consumes these notifications, so its setup is part of workflow configuration.
What should a functional consultant know about Fiori on mobile?
Fiori apps are responsive by design and run in the mobile browser; the SAP Mobile Start app provides a native launchpad shell with offline-capable apps. Functionally, the point is that the same role and catalog assignments apply — no separate mobile role concept. Offline scenarios need explicit app support, so confirm per app.
Preparing for a functional interview? Share the question that stumped you in the comments.