SAP Fiori Configuration
Configuring Fiori makes apps available and correct for users: activating services, assigning catalogs/groups to roles, and setting up the launchpad. It is where most Fiori "it doesn’t work" problems are solved.
Configuring a Fiori app is a checklist from the Fiori apps reference library: activate its OData services in the gateway, activate the ICF nodes and UI components it needs, add its catalog and group to the PFCG role, grant the backend authorisations, then confirm the tile appears and the app opens with data. The launchpad itself takes theming and spaces.
- Watch out: Service not activated, the top failure.
The configuration checklist
- Activate the app’s OData service(s) in the gateway.
- Activate the ICF nodes/UI components the app needs.
- Assign the app’s catalog and group to the appropriate PFCG role.
- Grant the backend authorizations the app checks.
- Verify the tile appears and the app opens with data.
Using the reference library
The Fiori apps reference library tells you exactly what each app needs, OData services, business role, catalog, and technical prerequisites. Following it turns Fiori configuration from guesswork into a checklist.
Common configuration errors
The recurring problems are: service not activated (errors/no data), missing catalog in the role (no tile), and missing backend authorization (error on open). Knowing these three failure modes makes Fiori troubleshooting fast.
Launchpad configuration
Beyond individual apps, you configure the launchpad itself, theming, spaces/pages, and default content, so users get a coherent, branded, role-appropriate home.
Common pitfalls
- Service not activated, the top failure.
- Catalog not in the role, no tile.
- Missing backend authorization, error on open.