Fiori installation
Setting up SAP Fiori makes the modern, role-based web experience available to users. Fiori setup involves the front-end server, the launchpad, and the activation of apps and their OData services, and it is essential for a good S/4HANA user experience.
Confirm the launchpad loads, tiles appear for the right roles, and apps open and fetch data.
- Fiori setup activates the Fiori launchpad, configures the SAP Gateway/OData services, and activates the specific apps users need…
- Embedded: the Fiori front-end runs on the S/4HANA system itself, simplest for many.
- Standalone (hub): a separate front-end server serves Fiori for one or more backends, better for larger or multi-system landscapes.
- Watch out: Inactive OData services breaking apps.
Deployment options
- Embedded: the Fiori front-end runs on the S/4HANA system itself, simplest for many.
- Standalone (hub): a separate front-end server serves Fiori for one or more backends, better for larger or multi-system landscapes.
What setup involves
Fiori setup activates the Fiori launchpad, configures the SAP Gateway/OData services, and activates the specific apps users need, then assigns them via catalogs and groups to roles. Each app depends on its OData service being active and the user having the right role.
Key steps
- Activate the gateway and OData services (the app’s backend).
- Activate the Fiori apps and their UI components.
- Assign apps to users through catalogs, groups and PFCG roles.
- Configure the launchpad appearance and theming.
Verify
Confirm the launchpad loads, tiles appear for the right roles, and apps open and fetch data. The most common issues are inactive OData services or missing role assignments, which show as missing tiles or "service not available" errors.
Common pitfalls
- Inactive OData services breaking apps.
- Missing role/catalog assignment, tiles do not appear.
- Wrong deployment choice (embedded vs hub) for the landscape.