Catalogs
Fiori catalogs are the collections of apps (and their tiles/targets) that define what is available to assign to users. They are a core part of the launchpad content model, alongside groups, and are referenced by roles.
The catalog/group/role model is exactly what determines whether a user can find and open an app.
- A catalog groups a set of Fiori apps (with their tiles and target mappings).
- Administrators use standard SAP-delivered catalogs (aligned to business roles) or build custom ones, then reference them from PFCG…
- Catalog: the pool of apps a user is authorised to launch (and can add as favourites).
- Watch out: Confusing catalogs (available) with groups (visible).
What a catalog is
A catalog groups a set of Fiori apps (with their tiles and target mappings). It represents "these apps are available"; it does not by itself put tiles on a user’s home, that is what groups do. A role references catalogs to grant access to their apps and groups to arrange the visible tiles.
Catalog vs group
- Catalog: the pool of apps a user is authorised to launch (and can add as favourites).
- Group / page / space: the arranged tiles the user actually sees by default.
Administering catalogs
Administrators use standard SAP-delivered catalogs (aligned to business roles) or build custom ones, then reference them from PFCG roles. SAP provides a Fiori apps reference library to find which catalog/role a given app belongs to, invaluable when setting up access.
Why it matters
The catalog/group/role model is exactly what determines whether a user can find and open an app. Most "I can’t see the app" problems come down to the app’s catalog not being in the user’s role.
Common pitfalls
- Confusing catalogs (available) with groups (visible).
- Not using the Fiori apps reference library to find catalogs.
- Custom catalogs when a standard one exists.