SAP S/4 Fiori Launchpad

You are an SAP S/4HANA Fiori administrator. The user wants to configure the Fiori Launchpad by creating and managing catalogs, groups, and spaces/pages to organize applications for end users.

What to check first

• Access the Fiori Launchpad admin tile: Tile name: "Manage Launchpad Settings" in the SAP Fiori Launchpad
• Verify you have the SAP_UI5_ADMIN or equivalent role assigned in transaction SU01
• Check that the SAP_UI_FIORI_CONF library is deployed in your SAP Gateway system

Steps

1. Log into SAP S/4HANA and navigate to the Fiori Launchpad homepage
2. Click the Manage Launchpad Settings tile (or use transaction /ui2/flp_settings directly)
3. In the left panel, select Catalogs to create a new catalog; click Add and enter catalog ID (e.g., Z_FINANCE_CAT) and title
4. Within the catalog, add individual applications by selecting Add in the Catalog Content section; choose apps from the available app repository
5. Create Groups by clicking the Groups section; assign a group ID (e.g., Z_FIN_GROUP) and add the catalog you just created
6. Configure Spaces (in S/4HANA 2021+) by navigating to Spaces & Pages and creating a new space; assign groups and catalogs to spaces for role-based access
7. Use transaction PFCG to assign Fiori Launchpad catalog roles to user groups; the naming convention is typically Z_<CATALOG_ID>_CAT_DISPLAY
8. Test the configuration by logging in as a test user with the assigned roles and verify apps appear in the correct groups and spaces

Code

*& Fiori Launchpad Configuration via OData Service
*& This code creates a catalog, adds apps, and assigns it to a group

DATA: lt_catalog_items TYPE TABLE OF zcl_fiori_cat_item,
      lt_apps          TYPE TABLE OF zcl_fiori_app,
      ls_catalog       TYPE zcl_fiori_catalog,
      lv_catalog_id    TYPE string,
      lv_group_id      TYPE string.

lv_catalog_id = 'Z_SALES_CATALOG'.
lv_group_id = 'Z_SALES_GROUP'.

* Create catalog structure
ls_catalog-catalog_id = lv_catalog_id.
ls_catalog-title = 'Sales Applications'.
ls_catalog-description = 'Fiori apps for sales team'.

* Add applications to catalog
DATA(lo_odata) = NEW zcl_fiori_odata_client( ).

* App 1: Sales Order Management (transaction VA01)
DATA(ls_app1) =

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change