SAP's web interface, what it replaces, and why rolling it out is mostly a change-management problem.
Fiori is SAP's design system and web user interface. Instead of transaction codes and dense screens, users get role-based apps presented as tiles on a launchpad, each doing one task. Technically it is SAPUI5 running against OData services. Practically it is the difference between a user who needs training on SAP and one who does not.
Fiori is often introduced as a visual upgrade, which undersells it and then disappoints. The value is that a task is exposed as a single app to the roles that need it, which removes the training burden of navigating a transaction hierarchy. The risk is rolling out hundreds of standard apps nobody asked for and concluding that users prefer the old interface.
The entry point. Tiles are grouped by role, and some display live figures rather than only linking somewhere.
Create, change and approve. These replace the transaction codes users run most often.
Real-time KPIs reading from HANA directly, drillable to the underlying documents.
A contextual view of a single object — a supplier, a material — with its relationships.
Built in SAPUI5 where standard apps do not fit, exposed through the same launchpad.
A goods receipt in the classic GUI runs through a transaction built to cover every scenario SAP supports. The warehouse user needs perhaps six of its fields, but has to tab past the rest, know which tab holds the batch, and remember a transaction code to get there at all.
The Fiori equivalent for the same task shows the expected items from the purchase order, lets the user confirm quantities, capture batch where required, and post. The field set is the same subset of data; the difference is that the screen was designed for that role rather than for the superset of all roles. Typical measured outcomes are a halving of clicks and a far shorter training time for new starters, because there is nothing to memorise.
The caution is that this benefit is role-by-role rather than system-wide. Rolling out the launchpad without designing catalogues per role gives users a screen of two hundred tiles, which is the same navigation problem in a nicer font. The work that produces the gain is deciding what each role actually does — which is business analysis, not a technical deployment.
| Term | What it means |
|---|---|
| Tile | The entry point on the launchpad. One tile is one task for one role, not one transaction code. |
| Launchpad | The role-based home screen. What a user sees is driven by their catalogue and group assignment. |
| OData service | The protocol Fiori apps use to read and write SAP data. Activating the right service is a routine cause of blank screens. |
| App types | Transactional for doing work, analytical for numbers with drill-down, fact sheet for viewing an object and its relationships. |
| Fiori elements | A framework that generates standard app layouts from metadata, so most apps need little custom UI code. |
Users faced with hundreds of unexplained tiles revert to the GUI. Start with the handful of tasks each role performs daily.
Fiori's benefit is role-based access. Without role design it is a different-looking menu.
Fiori depends on OData services and the gateway being correctly sized and configured. Performance problems usually originate here.
If every user keeps unrestricted GUI access, adoption stalls, because the familiar path is still there.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Tiles per role | Whether catalogues have been designed or everything was switched on. Double figures per role is usually too many. | |
| App adoption rate | Share of transactions done through Fiori rather than the classic GUI. Low adoption usually means a missing app, not resistance. | |
| Launchpad load time | User experience at the first screen, which sets the tone for everything after it. | |
| Custom app count | How much bespoke UI you are maintaining. High counts suggest standard apps were not evaluated first. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.