Show TOC

 Review Definition of Target Mapping in Launchpad Designer


All Web Dynpro apps must have a target mapping defined in the launchpad designer. This target mapping maps the intent defined in the app definition to a target application.

In this activity, you can review the definition of the target mapping.


You have collected the following information from the SAP Fiori apps reference library:

  • Business Catalog (Launchpad)

  • Semantic Object

  • Action

  • LPD_CUST Role

  • LPD_CUST Instance

To access this information, follow the procedure Collect Web Dynpro Information from the SAP Fiori Apps Reference Library.


  1. In the Implementation Guide (IMG) on the front-end server, choose Start of the navigation path SAP NetWeaver Next navigation step UI Technologies Next navigation step SAP Fiori Next navigation step Adding Apps to SAP Fiori Launchpad (Using SAP Fiori Launchpad Designer) Next navigation step SAP Fiori Launchpad Designer (Current Client) End of the navigation path or open the following URL with your web browser:


  2. Select the Catalogs view in the top left corner and search for the catalog with the technical name you retrieved from the Business Catalog (Launchpad) field from the SAP Fiori apps reference library. Choose the catalog.

  3. You are on the catalog view displaying the catalog you selected. Choose Target Mapping.

  4. The launchpad designer displays all target mappings in the selected catalog. Click the line starting with the semantic object and the action entered in the Configure screen of your app. Choose Configure.

  5. The launchpad designer displays the Configure Target Mapping screen.

    • On the Intent screen area, you see the Semantic Object and the Action, which was entered in the tile definition respectively retrieved from the SAP Fiori apps reference library.

    • On the Target screen area, the Application Type dropdown field should contain SAP Fiori App using LPD_CUST. This selection makes the Launchpad Role field, The Launchpad Instance field, the Application Alias field, and the Application ID field available for input.

      Review the following fields:

      • Launchpad Role: <LPD_CUST Role>

      • Launchpad Instance: <LPD_CUST Instance>

      Remember the entry in the Application Alias field.

  6. If all fields contain the correct values, leave the launchpad designer.