Skip to Content

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

To report this post you need to login first.

20 Comments

You must be Logged on to comment or reply to a post.

  1. Ninad Thakur

    Hello,

    We have installed Netweaver 7.5 SP3. We do not see the simplified configuration shown in screenshots above. In the above blog, it’s not clear whether the simplification is part of NW 7.5 or whether there is additional component required to be able to use the simplified target mapping.

     

    Do we have to install SAP UI Add-On 2.0 SP01 in addition to Netweaver 7.5 in order to get the simplified target mapping functionality?

     

    Thanks,

    (0) 
    1. Carola Steinmaier Post author

      Hello,

      In fact it’s part of the SAP NetWeaver Stack 7.50. The relevant software component within this stack is the SAP_UI 7.50 component.

      Please check the version of the SAP_UI component.

      For SAP Netweaver 7.50 no additional Add-On is needed.

      Kind regards.

      Carola

      (0) 
  2. Owen Carnes

    Hello Carola,

     

    Is SAP S/4 HANA required for this new functionality (it appears in the release notes as though it is)?  We do not have HANA at all, but are currently on SAP_UI 7.4 SP 14, and trying to figure out if this functionality would be available to us with an upgrade.

     

    Thanks,

    Owen

    (0) 
  3. Simon Perstorfer

    Hey Carola,

    is it possible to create multiple target mappings for the same semantic object and action?

    I have created a target mapping for a standard semantic object and a standard action in a custom tile catalog and and want to use this custom target mapping for a custom tile.
    Unfortunately the custom tile uses the standard target mapping.

    Is it possible to create multiple target mappings for the same device type and the same semantic object and action?

    Regards
    Simon

    (0) 
    1. Carola Steinmaier Post author

      Hi Simon,

      it’s technically possible but then it’s undetermined, which target mapping is used.

      There should be only one target mapping assigned to the user.

      Kind regards.

      Carola

      (0) 
  4. Jens Schwendemann

    Would be possible to use target mapping (either using new flavor directly entered in Launchpad Designer or old fashioned via LPD_CUST) in order to presesnt different (intranet) URLs (no Fiori / UI5 Applications) depending on whether the user is on Desktop or Mobile? All I read (including this blog) point to the direction that this should be possible, but I cannot make this happen.

    I particularly struggle on the “semantic object – action” part. I have created a custom semantic object “MyTimeOffRequest” and (currently try to) reuse an standard action “display”. If I’m on the desktop, the URL “https://timeoffrequest.mycompany.com” should open. If I’m on mobile (Tablet or Phone) “mibrowsers://timeoffrequest.mycompany.com” should open (mibrowsers URL schema points to MobileIrons Web@Work browser leveraging app tunneling.)

     

    Is this even possible using the same semantic object – action combination or do I need different actions for desktop and mobile? And in either case, how to set up?

     

    Any push to the right direction would be highly appreciated

    Cheers

    Jens

    (0) 
    1. Carola Steinmaier Post author

      Hi Jens,

      you can use the same intent (semantic object/action) for mobile and desktop.

      Just maintain two two target mappings with the same intent which differ only in the checkbox for the device ‘mobile’ and ‘desktop’ and in the target application.

      Hope that helps.

      Kind regards.

      Carola

      (0) 
  5. Julian Bonillo

    Hi Carola and everyone!

    your blog post is very clear and helpful.   I am currently playing with my Fiori 2.0 launchpad in an S/4HANA 1610 on premise system and wondering:

    Is there a way to launch FioriWave1 apps inside the launchpad ?     So far I tried using Semantic navigation and also URL (as in your post), but they always open in a new browser tab.

    Thank you very much for your advice, kind regards,

    Julian

    (0) 
    1. Jens Schwendemann

      Not sure if this applies to S/4HANA but there is this Parameter “managed=FioriWave1”, see here: https://launchpad.support.sap.com/#/notes/2302199/E. What would be interesting is, if this is also possible when using the simplified target mapping, as this parameter seems to be entered in LPD_CUST, maybe Carola or somebody else can weigh in here.

       

      Cheers

      Jens

      (2) 
      1. Technical Team

        Hello Jens,

        I tried use the ‘managed=FioriWave1’ in our Fiori 2.0 installation on ECC, but had no luck getting it to work. Yes, maybe someone knows how to do this and will comment.

        Cheers,

        Mike

        (0) 
  6. Technical Team

    Hello Carola,

    I’m wondering if it is possible to launch a transaction from the Fiori Launchpad with a flavor (defaulted by role) without using LPD_CUST?

    There is documentation here detailing how to use LPD_CUST to do what I’m trying to achieve, but I would rather not use LPD_CUST at all given we are on S/4 1610.

    Thanks,

    Mike

    (0) 
  7. Alexander Schinnes

    Hello Carola,

    I can see you have used the Target Mapping parameter DYNP_OKCODE = /08 to skip the first screen and execute the transaction.

    In S/4 1610 it automatically executes the transaction when passing parameters. Do you know if it is possible to NOT skipping the first screen and only passing parameters to prefill fields?

    Thanks,

    Alexander

    (0) 
      1. Alexander Schinnes

        Hi Carola,

        Thank you for reply! It still goes to the next screen if I remove the DYNP_OKCODE parameter. I think parameter DYNP_OKCODE with value “/08” is set as default, and that this have to be turned off in a way.

        Best regards,

        Alexander

        (0) 

Leave a Reply