Start of Content Area

Procedure documentation Setting Up Launchpad  Locate the document in its SAP Library structure


You use a launchpad to provide the user with a clear, role-specific summary of links to other applications. For more information, see Launchpad.

The following steps are required when setting up a launchpad:

      Add Launchpad Application to Role

      Adjust Launchpad in the Transaction LPD_CUST


In the portal administration, you have configured all necessary system alias entries.

Add Launchpad Application to Role


       1.      Start the transaction PFCG and select the role for which you want to set up a launchpad. Choose Change in the context menu of the role.

       2.      Choose the Menu tab page.

       3.      Add a node in the second level. For the Folder Name, select the name Analytics, for example (this name is also used in the automatic roles delivered by SAP).

       4.      Move the new node to the end of the menu structure. In the automatic roles provided by SAP, the ANALYTICS node also has this position.

       5.      Assign a Web Dynpro application to the node. To do so, choose Other and then select the Web Dynpro Application entry from the object list.

       6.      Enter the required values in the Web Dynpro Applicationwindow as follows:

Specifications for the Web Dynpro Application when Setting Up a Launchpad



Web Dynpro Application



Start Launchpad


Do not set the HTTPS indicator

Start Mode

Set the Browser indicator


Enter the ROLE and INSTANCE parameters.

Both parameters are given the same value. Select the value according to the role name for which you are setting up the launchpad. If the role is called SAP_EP_RW_FSMN_1, for example, you select RWFSMN1 as the value.


The values for the ROLE and INSTANCE parameters cannot be longer than 10 characters. You cannot enter longer character strings in the following step in the transaction LPD_CUST.

Adjust Launchpad in the Transaction LPD_CUST


       1.      Start transaction LPD_CUST. In the initial screen, the system displays a list of all existing launchpads.

       2.      Choose New Launchpad. In the Role and Instance fields, enter the same values that you used in the previous section for the Web Dynpro application (for example, RWFSMN1). In the Description field, you can enter a value of your own choosing.

       3.      Save your entries. You can now see the settings for the launchpad you created.

       4.      Create the folders you require and add the necessary applications. The following application types are available:

       Portal Page (POP)

       Transaction (TRA)

       URL (URL)

       SAP BI Report (Query) (BW)

       SAP BI Report (Web Template) (BWT)

       Report Writer (RW)

       Manager’s Desktop (MDT)

       Web Dynpro Java (WDJ)

       Web Dynpro ABAP (WDA)

       KM Document (KD)

       Visual Composer Xapps (DAB)

       InfoSet Query (ISQ)

Depending on the application type selected, the system displays input fields for other required parameters.

       5.      Enter the required parameters for the selected application.

In many cases, you must enter the System Alias parameter. This system alias is used by the portal component to refer to the correct system in the backend. You must also enter a system alias that suits your desired report.

For the automatic roles provided by SAP, the following system aliases are used in launchpad entries:





Always enter the alias SAP_BW for reports from the area of Business Intelligence.


Some of the automatic roles provided by SAP already contain a launchpad. You can use these roles and the associated launchpads as examples for adjusting your own roles.


You can see which automatic roles already contain a launchpad by using the description text *SAP_EP_* to filter the list of launchpads displayed in the Overview of Launchpads (transaction LPD_CUST).


You have created a launchpad and added it to a specific user role. If you also made the other adjustments in the backend system (see Adjustment and Activation of Automatic Roles), you can now upload the objects to the portal.


End of Content Area