5.1 The Role of the Launchpad in the Fiori Experience

The SAP Fiori Launchpad is the central, web-based entry point for all Fiori applications. It serves as a modern, intuitive homepage for users, providing a consistent and personalized experience across both desktop and mobile devices. Its role is critical in the Fiori ecosystem, as it organizes applications into a role-based, easy-to-navigate interface of tiles, moving away from complex menu structures and toward a user-centric hub for all business tasks.

5.2 Analyzing the Launchpad’s Functionality and Value

Technically, the Fiori Launchpad operates as a single-page application. When a user accesses it, only one HTML document, fiorilaunchpad.html, is loaded into the browser. This document acts as the SAPUI5 root application, which then manages all subsequent navigation and page transitions internally. This architectural choice enables a more holistic and fluid user experience compared to older web applications that required a full page reload for every action.

The Launchpad provides significant value to both users and administrators through a rich set of features:

• Personalization: Users can customize their Launchpad by rearranging, adding, or removing tiles and grouping them as they see fit.
• Single Sign-On (SSO): Provides seamless access to all integrated applications after an initial login.
• Theming: Allows organizations to apply corporate branding and custom themes for a consistent look and feel.
• Search: Offers a powerful, integrated search capability to find apps and business objects.

These features collectively contribute to the Launchpad’s key values. It is Simple and intuitive, Role-based in what it presents, Contextual by providing real-time information on tiles, Responsive across all devices, and designed to be Multi-platform.

5.3 The Process of Launchpad Configuration

Configuring the Fiori Launchpad to display a new application is a logical, multi-step process that transforms back-end application definitions into user-facing tiles. It involves linking technical details to user roles and visual elements.

1. Defining the Application: The first step is to identify the technical details of the Fiori application. Using transactions like SICF (for the URL path) and SE80 (to find the BSP application), an administrator locates the application’s unique URL and its corresponding SAPUI5 component name. These details are the technical foundation for making the app accessible.
2. Creating Launchpad Content: Next, using the Launchpad Customizing tool (LPD_CUST), an administrator creates a new Launchpad instance. Within this instance, an application link is defined. This link acts as a pointer, specifying the application’s type (e.g., SAPUI5 Fiori App), its URL, and the UI5 component name identified in the previous step.
3. Designing the User View: With the technical link established, the focus shifts to creating the user-facing elements in the Launchpad Designer. This involves two critical creations:
   • Tile: This is the visual, clickable representation of the application that the user will see on their Launchpad. It is configured with a title, icon, and other visual properties.
   • Target Mapping: This is the crucial logical link. Target mapping connects a user’s intent (e.g., “display timesheet”) to the specific application that fulfills that intent. It links the tile to the application link created in the previous step.
4. Assigning User Access: The final step is to grant users access to the new application. Using the Profile Generator (PFCG), an administrator assigns the Catalog—a collection of tiles and their associated target mappings—to a specific user role. When a user with that role logs in, the tiles from the assigned catalog will appear on their Fiori Launchpad, ready for use.

After configuring the user-facing Launchpad, it is important to understand the broader lifecycle of implementing the underlying Fiori applications themselves.