Mon – Sat: 9:00 AM – 7:00 PM IST
SAP

What is SAP Fiori?

SAP's web interface, what it replaces, and why rolling it out is mostly a change-management problem.

In short

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.

Why It Matters

Why this matters in practice

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.

Role-based: users see the apps their job needs, not the whole menu
Responsive, so approvals genuinely work on a phone
Built on OData services, which are reusable for integration
Standard apps can be extended rather than rebuilt
How It Works

How it works in practice

1

The launchpad

The entry point. Tiles are grouped by role, and some display live figures rather than only linking somewhere.

2

Transactional apps

Create, change and approve. These replace the transaction codes users run most often.

3

Analytical apps

Real-time KPIs reading from HANA directly, drillable to the underlying documents.

4

Fact sheets

A contextual view of a single object — a supplier, a material — with its relationships.

5

Custom apps

Built in SAPUI5 where standard apps do not fit, exposed through the same launchpad.

Worked example

A worked example: eleven clicks becomes three

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.

Key terms

The vocabulary, briefly

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.
What Goes Wrong

Common mistakes worth avoiding

Deploying every standard app

Users faced with hundreds of unexplained tiles revert to the GUI. Start with the handful of tasks each role performs daily.

No role design

Fiori's benefit is role-based access. Without role design it is a different-looking menu.

Ignoring the gateway layer

Fiori depends on OData services and the gateway being correctly sized and configured. Performance problems usually originate here.

Leaving the GUI fully open

If every user keeps unrestricted GUI access, adoption stalls, because the familiar path is still there.

What to measure

Numbers worth tracking

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.
FAQ

Questions we are asked about this

Not in practice. Configuration and many specialist transactions still use the GUI. Fiori targets the high-volume, role-specific tasks that most users perform.
Yes, a subset of Fiori apps works on ECC with the right gateway setup, though the full app catalogue and the analytical apps assume S/4HANA and HANA underneath.
Not in most landscapes. Fiori covers the high-frequency, role-specific tasks extremely well, while deep configuration, mass maintenance and specialist transactions often remain in the GUI. The realistic target is that the people doing repetitive operational work live in Fiori and the specialists keep both. Planning for total replacement tends to produce a long tail of custom apps built to replicate transactions that three people use twice a year.
No. Fiori apps exist for ECC and are delivered through the front-end server, so you can improve the user experience ahead of a migration. The app catalogue is substantially richer on S/4HANA, and some apps depend on the newer data model, so you get more of the benefit after moving. Deploying Fiori on ECC first is nonetheless a reasonable way to get users familiar before a larger change.
Less than teams expect, if standard apps are evaluated properly first. Fiori elements generates most standard layouts from metadata, so extending an existing app is often configuration plus a small annotation change rather than UI development. Freestanding custom apps written in SAPUI5 should be the exception, because every one of them is something you maintain through every future upgrade.
Almost always an activation or authorisation gap rather than a defect. The usual suspects are the OData service not being activated, the user not having the required catalogue or role, or the back-end authorisation object missing even though the tile is visible. Because the tile and the data come from different layers, a visible tile is not evidence that the app is wired up.
Related

Where to read next

What is SAP S/4HANA?

Read more

What is ABAP?

Read more

Our SAP consulting services

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.