SAP Fiori Launchpad Designer Basics: Catalogs, Groups, Tiles, and Troubleshooting

SAP Fiori Launchpad Designer is an administration tool for maintaining launchpad content such as catalogs, tiles, target mappings, and groups. A reliable configuration separates reusable business content from the role assignments that make that content visible to users.

This guide focuses on the administration workflow: identify the content object, edit it in the correct scope, assign it through roles, and validate the result with the affected user.

01Understand the launchpad content model

A launchpad arrangement usually involves four related objects:

• A catalog contains apps and their target mappings. It is the reusable content repository for launchpad applications.
• A tile provides the visual entry point that users select.
• A target mapping connects an intent, such as a semantic object and action, to an application or navigation target.
• A group organizes selected tiles for display in a traditional home-page layout.

A catalog can contain an application without making that application visible on a user's home page. Visibility depends on the assigned role, the content exposure model in use, and whether the relevant tile or space is available to the user.

For a broader platform orientation, see SAP Fiori overview. Use the launchpad administration process to establish the content model before troubleshooting individual tiles.

02Prepare before editing content

Record the business requirement before opening the designer. Capture the application name, intended users, navigation intent, required backend system, and whether users need a tile, a direct navigation target, or both.

Check the following before changing an existing catalog or group:

1. Identify whether the object is a standard-delivered object or a customer-maintained copy.
2. Confirm the target system and client used by the launchpad connection.
3. Check which role provides the catalog or group to the affected user.
4. Confirm that the application is active and that its backend authorizations are available.
5. Decide whether the change belongs in a development system and transport path rather than directly in production.

Use SAP Fiori Launchpad Admin Setup when the launchpad itself, system aliases, or administrator access still require configuration.

03Edit a catalog in Launchpad Designer

Open SAP Fiori Launchpad Designer with an administrator account that has the required launchpad content permissions. Select the relevant catalog and inspect its existing tiles and target mappings before making a change.

To add an application, use this sequence:

1. Open the catalog in edit mode.
2. Add or select the application tile definition.
3. Maintain the tile title, subtitle, icon, and related display properties.
4. Maintain the target mapping with the correct semantic object and action.
5. Confirm the application type and required navigation parameters.
6. Save the catalog.
7. Assign the catalog through the appropriate role or content structure.
8. Test the navigation with a user who has the intended business role.

A tile and its target mapping solve different parts of the user experience. The tile supplies the launchpad entry point; the target mapping determines where the intent resolves. A tile that appears but fails to navigate usually requires target-mapping, system-alias, application-activation, or authorization analysis.

04Configure groups and tile visibility

Groups determine which assigned tiles appear together in a classic launchpad home-page layout. Create or edit a group when users need a curated collection of tiles rather than access to every tile in an assigned catalog.

A practical group workflow is:

1. Open the group assigned to the relevant role.
2. Add the required tile from an available catalog.
3. Arrange tiles in a sequence that matches the user's daily work.
4. Remove obsolete or duplicate entries.
5. Save the group.
6. Confirm that the group is assigned to the user's role.
7. Test with a fresh launchpad session.

The catalog supplies the available application content, while the group controls the selected presentation for users. A user can have access to a catalog and still lack a visible tile when the tile has not been placed in an assigned group or exposed through the configured launchpad content model.

For authorization structure, compare the content assignment with SAP Fiori role and catalog assignment. This check is especially useful when administrators can see a tile but business users cannot.

05Choose between Fiori and SAP GUI access

Use an SAP Fiori tile when the task has a suitable role-based application and users benefit from intent-based navigation, a focused user experience, or responsive access. Use SAP GUI when the required function remains transaction-oriented, has no suitable Fiori application, or depends on a detailed classic transaction workflow.

The choice affects launchpad design. A GUI transaction tile must resolve to the correct transaction target and backend connection, while a native Fiori application may require an application-specific target mapping and service activation. Document the selected access pattern so that role administrators can distinguish an intentional GUI entry from a missing Fiori application.

The related guide SAP Fiori versus SAP GUI transaction choice provides a decision framework for selecting the appropriate entry point.

06Validate a new tile end to end

Test a launchpad change in layers instead of checking only whether the tile is visible:

• Content check: confirm the tile belongs to the intended catalog or group.
• Role check: confirm the user receives the catalog, group, or spaces and pages through the expected role.
• Navigation check: select the tile and verify that the target intent resolves correctly.
• Backend check: confirm the application service, system alias, and backend function are available.
• Authorization check: verify that the user can execute the application and read the required business data.
• Session check: clear stale browser state or start a new session after content changes.

Test with a representative business user rather than only with the administrator account. Administrator visibility can conceal missing role assignments, backend permissions, or user-specific restrictions.

07Troubleshoot common designer issues

The tile is missing. Confirm that the user receives the catalog and group through an assigned role. Check that the tile is included in the group or exposed through the active content model, then start a fresh session.

The tile is visible but navigation fails. Inspect the target mapping, semantic object, action, system alias, application activation, and required URL or navigation parameters. Test the same intent from a controlled administrator session and then with the affected user.

The application opens but shows an authorization error. Separate launchpad content authorization from backend business authorization. The role can expose a tile while the backend role or authorization object still prevents data access.

The old title or icon remains visible. Save the content change, verify that the change was made in the active catalog or group, and reload the launchpad session. Browser cache and launchpad client state can preserve earlier content during testing.

The catalog edit is unavailable. Check the administrator's content-maintenance permissions and confirm that the selected object is maintained in the correct system and client. Use a controlled customer copy when the change must remain independent of standard-delivered content.

08Transport and change control

Treat launchpad content as a managed system change. Record the catalog, group, tile, target mapping, role, semantic object, action, and backend dependency in the change documentation.

Move changes through the normal development, quality, and production process used by the SAP landscape. After import, validate both administrator visibility and business-user behavior. Include a rollback description that identifies the previous target mapping or content assignment.

Separate content changes from unrelated theme or authentication changes. For presentation settings, see SAP Fiori theme personalization; keeping these concerns separate makes tile and navigation incidents easier to isolate.

09Use a repeatable operating checklist

Before closing a launchpad content change, confirm:

• The correct catalog and group were edited.
• The tile has the intended title, icon, and application reference.
• The target mapping resolves the intended semantic object and action.
• The assigned role exposes the content to the correct user population.
• Backend services and authorizations support the application.
• A representative user completed the navigation test.
• The change record contains transport and rollback information.

This checklist turns Launchpad Designer from a visual editing task into a controlled administration procedure.