# SAP Fiori

> Source: https://netray.co/glossary/sap-fiori
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Glossary

## Short answer

SAP Fiori is SAP's role-based web user experience. It presents business tasks as apps in a launchpad, built on SAPUI5 and served by OData services, and is the default front end for S/4HANA alongside the classic SAP GUI.

## Aliases

- Fiori
- Fiori launchpad
- SAP Fiori apps
- SAPUI5

## Category

erp-core

## Full Definition

The Fiori launchpad is the entry point: users see tiles and groups assigned through roles and catalogs, and each tile opens an app. App types include transactional apps (for example Create Purchase Order), analytical apps built on CDS views, and fact sheets for searching and navigating objects. Classic GUI transactions can also be launched from tiles, so Fiori and SAP GUI coexist during migration.

Technically, Fiori apps are SAPUI5 front ends that call OData services exposed through the SAP Gateway. Services are activated in /IWFND/MAINT_SERVICE, and the app, catalog and role configuration is done with the launchpad designer and PFCG. Core Data Services (CDS) views provide the analytical and transactional data model in S/4HANA, and the Fiori elements framework generates standard UI from annotations.

Fiori matters in manufacturing because shop floor and warehouse users get task-specific screens that work on tablets and phones, such as Confirm Production Order Operation or Post Goods Receipt. It does not by itself change business logic: the same posting rules, authorizations and validations from the backend apply.

For ECC customers, Fiori apps can run through an embedded or hub gateway deployment, but app availability differs from S/4HANA, which has the larger and more current catalog. The SAP Fiori Apps Reference Library lists apps, required backend versions, and the OData services each app needs.

## Why It Matters

- It decides user adoption: role-based apps reduce the transaction-code knowledge needed by occasional users.
- Authorization problems often appear as empty tiles or missing apps, caused by catalog and role assignment instead of missing software.
- OData services behind Fiori are a clean, supported integration surface for read access and for assistants.
- Fiori is the standard front end for S/4HANA conversions, so the app catalog shapes project scope.

## In Practice

A warehouse supervisor needs the Post Goods Receipt for Purchase Order app. The tile does not show up. The cause is that the business catalog was not assigned to the PFCG role and the OData service was inactive in /IWFND/MAINT_SERVICE. After activating the service and assigning the catalog, the tile appears and posts through the same backend logic as MIGO.

## Faq

### Is SAP Fiori a replacement for SAP GUI?

**Answer:** It is the strategic front end for S/4HANA, but SAP GUI is still used for many transactions and configuration. Both can be launched from the same launchpad during a long transition.

### Why are Fiori tiles missing for a user?

**Answer:** Usually the user lacks the role or business catalog containing the tile, or the OData service is not activated in /IWFND/MAINT_SERVICE. Check PFCG and the launchpad designer first.

### Does Fiori work with SAP ECC?

**Answer:** Partly. A gateway deployment can serve Fiori apps on ECC, but the app catalog and CDS based apps are larger on S/4HANA.

## Search terms

SAP Fiori, Fiori launchpad, SAPUI5 OData, Fiori apps S/4HANA, Fiori tiles not showing, Fiori vs SAP GUI, Fiori apps reference library

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json