Introduction in SAP Fiori

Introduction

SAP Fiori is SAP’s modern, role-based user experience: a design language and a set of web apps that replace the classic SAP GUI screens with clean, task-focused, responsive interfaces. It is the face of S/4HANA.

Quick answer

Fiori dramatically improves usability and adoption over SAP GUI, and in S/4HANA many capabilities are delivered as Fiori apps.

Key takeaways

Fiori is both a design system (principles: role-based, responsive, coherent, simple, delightful) and a large library of apps…
Transactional: perform business tasks (create/change objects).
Analytical: show real-time KPIs and insights (on HANA).
Watch out: Expecting Fiori to replace all GUI, config and long-tail transactions remain in GUI.

What Fiori is

Fiori is both a design system (principles: role-based, responsive, coherent, simple, delightful) and a large library of apps delivered through the Fiori launchpad. Built on SAPUI5 web technology, Fiori apps run in a browser on any device and are organised around user roles and tasks rather than the old transaction menu.

Types of Fiori apps

Transactional: perform business tasks (create/change objects).
Analytical: show real-time KPIs and insights (on HANA).
Fact sheet: display an object and its related data with drill-down.

Why Fiori matters

Fiori dramatically improves usability and adoption over SAP GUI, and in S/4HANA many capabilities are delivered as Fiori apps. Understanding the launchpad, roles/catalogs and the OData backend connection is essential for users, functional consultants and developers alike.

Common pitfalls

Expecting Fiori to replace all GUI, config and long-tail transactions remain in GUI.
Ignoring the role model that controls which apps appear.
Treating Fiori as only cosmetic, it changes how users work.

Practice challenge

+0 XPStreak ×0

Question 1 of 3

Which statement is true of Introduction?

Frequently asked questions

What does the term Introduction refer to in SAP?

Where does Introduction sit in the Fiori stack?

Fiori is both a design system (principles: role-based, responsive, coherent, simple, delightful) and a large library of apps delivered through the Fiori launchpad.

What else is worth knowing about Introduction?

Fiori dramatically improves usability and adoption over SAP GUI, and in S/4HANA many capabilities are delivered as Fiori apps.

What tends to go wrong with Introduction?

Expecting Fiori to replace all GUI, config and long-tail transactions remain in GUI. Ignoring the role model that controls which apps appear. Treating Fiori as only cosmetic, it changes how users work.