Target mapping is part of the SAP Fiori launchpad configuration. It defines for a given intent (semantic object/action) and device type the target application which is launched when clicking on a tile, on a link or via an app-to-app navigation. With SAP UI Add-On 2.0 for SAP Netweaver navigation targets for the application types SAPUI5 Fiori apps, transactions, Web Dynpro applications and URLs can be defined completely within the SAP Fiori launchpad designer without using transaction LPD_CUST.

This is an important simplification for the target mapping configuration with an additional positive impact on the performance.

 

Tiles and Target Mapping

A Fiori tile catalog can include two components:

  • Tiles which represent the visual part of a tile such as a title, subtitle, information, icon and the semantic object and action for the intent-based navigation.
  • Target mappings which define the target application which is launched when an intent is triggered

TILES_TM_new.jpg

 

Configuration of Target Mappings

Before SAP NetWeaver 7.50 for the configuration of target mappings launching non-SAP Fiori applications as transactions, Web Dynpro applications or URLs you had to use transaction LPD_CUST in addition to the SAP Fiori launchpad designer. As of SAP UI Add-On 2.0 SP01 you can perform the target mapping configuration completely within in the SAP Fiori launchpad designer – without using transaction LPD_CUST, see also Configuration of Target Mapping.

In the following find some examples how to set up the configuration of target mappings for the different application types.

Target Mapping for SAPGUI transactions

Use Case: When the respective intent is triggered on a desktop device the transaction FTRBP03 in system S4FIN shall be launched. The transaction can be launched with parameters as e.g. BusinessPartner.

Target mapping configuration can be set up as follows:

TM_SAPGUI_BCP1.PNG

To rename the URL parameter to the parameter name as it is used by the target application the column Target Name within the parameter table can be used.

 

Target Mapping for Web Dynpro applications

Use Case: When the respective intent is triggered on a desktop device, the Web Dynpro application WCM_WDA_WP in system S4EAM shall be launched with several optional parameters for which default values are defined.

Target mapping configuration can be set up as follows:

TM_WDA_WP.PNG

 

Target Mapping for URLs

Use Case: When the respective intent is triggered the SuccessFactors application to display my goals is launched for company I0300.

Target mapping configuration can be set up as follows:

TM_URL_new.PNG

Recommendation

Generally it’s recommended to use the target mapping configuration within the SAP Fiori launchpad designer – without LPD_CUST.

It’s not only easier to configure because you have to use only one tool, but it also leads to a better performance during runtime.

 

Further Information

SCN Blog: Control visibility of tiles via separation of tiles and target mapping

New NetWeaver Information at SAP.com

Very Helpfull

User Rating: Be the first one !