How to Enable SAP Easy Access Menu for Fiori Launchpad Step-by-Step

www.sap.com

How to Enable SAP Easy

Access Menu for Fiori
Launchpad Step-by-Step
SAP S/4HANA 2020

Jessie Xu
Document History

Document Version Authored By Description Date Created

1.0 Jessie Xu Fiori White Paper Oct 13, 2021

Document Version Reviewer Description

1.0 Wilson Wei Review Documentation October 6, 2021

2
TABLE OF CONTENTS

INTRODUCTION .............................................................................................................................................4
CHAPTER 1 CONFIGURE TRUST RELATIONSHIP ...............................................................................................5
1.1 Assign authorization S_RFCACL to end user on backend system ........................................................................ 5
1.2 Create RFC connection from backend system to frontend system ................................................................... 12
1.3 Define the frontend system as a trusted system on backend system............................................................... 16
CHAPTER 2 CONFIGURE RFC CONNECTIONS AND SYSTEM ALIAS ................................................................... 20
2.1 Create RFC connection – ABAP connection ....................................................................................................... 20
2.2 Create RFC connection – HTTP(S) connection ................................................................................................... 24
2.3 Create System Alias ........................................................................................................................................... 27
CHAPTER 3 ACTIVATE ODATA SERVICES ....................................................................................................... 30
CHAPTER 4 ENABLE SAP EASY ACCESS MENU ................................................................................................ 33
4.1 Role-free option................................................................................................................................................. 33
4.2 Role-based option.............................................................................................................................................. 35
CHAPTER 5 TEST SAP EASY ACCESS MENU ON FIORI LAUNCHPAD ................................................................. 44

3
 Introduction

Welcome to How to Enable SAP Easy Access Menu for Fiori Launchpad Step-by-Step for 2020. In this white paper
you will find all the details needed to enable SAP Easy Access Menu for your Fiori Launchpad so that you can
select SAP GUI and Web Dynpro ABAP applications from a user menu or SAP menu in the ABAP backend and add
them to the Fiori Launchpad home page.

Requirement • You have installed software component version SAP_UI 751 SP00 or higher
• Fiori Launchpad has been configured on frontend system

• In this white paper, we will use the following environment:

Front-end: SAP S/4HANA 2020, SAP_UI 755 SP01
Note Back-end: SAP S/4HANA 1909
Please note the steps & UI may be different if you are using the different
environment

4
 Chapter 1
Configure Trust Relationship

• In this white paper, the frontend system is S4M and the backend system is S4D
• Before creating an RFC connection in section 2.1, you have to make sure that
the frontend systems’ calls are trusted on backend system. The configurations
Note in this chapter need to be done on back-end system
• You can skip this chapter if the trust relationship has already been defined or
you are using embedded deployment

1.1 Assign authorization S_RFCACL to end user on backend system

Note • In transaction SU56, you can check if the user already has the authorization
S_RFCACL

1. Run transaction PFCG on backend system, enter the role name ZRFCCALL and click Single Role button

Figure 1 Create role ZRFCCALL

2. Navigate to Authorizations tab and click Yes on the pop-up dialog

5
 Figure 2 Save the role

3. Click Change Authorization Data button then click Continue on the pop-up dialog

Figure 3 Change authorization data

4. Click Do not select templates

6
 Figure 4 Do not select templates

5. Click Manually, enter the authorization object S_RFCACL then click Continue

Figure 5 Manually add the authorization object

7
6. Click Expand subtree button to expand the tree then click Change button of RFC_EQUSER (RFC same
user ID)

Figure 6 RFC same user ID

7. Select Y Call by the same user is possible then save the change

Figure 7 Call by the same user is possible

8
8. Edit other options and choose Full authorization

Figure 8 Full authorization

• You may get the message below. You can change it according to your system
Note and not give the full authorization. In this white paper, as we are using the test
environment, here I choose Yes to give the full authorization

Figure 9 Confirm the change

9. Save the role

9
 Figure 10 Save the role

10. Click Execute on the pop-up dialog to assign the profile name

Figure 11 Assign profile name

11. Click Generate to generate the profile then click Back button

10
 Figure 12 Generate the profile

12. Navigate to User tab, enter the User ID of the user(s) you want to assign the authorization to, then click
Save

Figure 13 Assign the role to user(s)

13. If the User Comparison button is in red, click on it and then click on Full Comparison.
11
 If it is in green, skip this step.

Figure 14 User Comparison button is in red

Figure 15 Full Comparison

1.2 Create RFC connection from backend system to frontend system

1. Run transaction SM59 on backend system then click on the Create button

12
 Figure 16 Create the RFC

2. Enter the destination name and connection type then click on Continue

1 RFC Destination: Name of the RFC destination, it is recommended to use the naming
convention <system id>CLNT<client>_RFC
2 Connection Type: 3 RFC connection to ABAP system

Figure 17 Create ABAP Connection

13
3. Configure the RFC destination with the following details

1 Description 1: Description of this RFC destination

2 Load Balancing: Choose “Yes” if you have one or choose “No”
3 Target Host: The host of frontend system
4 Instance No.: The instance number of frontend system

Figure 18 Technical Settings of ABAP connection

4. Navigate to tab “Logon & Security” and configure with the following details

1 Client: The client of frontend system

2 User: Current User
3 Trust Relationship: No

14
 Figure 19 Logon & Security settings of ABAP connection

5. Save this RFC destination and then click Connection Test to test the connection

Figure 20 Save and test the connection

15
 Figure 21 Connection is OK

1.3 Define the frontend system as a trusted system on backend system

1. Run transaction SMT1 on backend system then click on the create button

Figure 22 Create trust relationship

2. Click Continue to start

16
 Figure 23 Start to create trust relationship

3. Select With existing RFC destination, enter the RFC destination created in section 1.2 then click
Continue

Figure 24 Enter Destination

17
4. It will jump to the logon screen of frontend system, enter the logon data then click Enter

Figure 25 Log on frontend system

5. Click Continue

Figure 26 Display information

18
6. Click Continue

Figure 27 Configuration

7. Click Complete

Figure 28 Complete
19
 Chapter 2
Configure RFC Connections and System Alias

2.1 Create RFC connection – ABAP connection

• If you are using embedded deployment, the system alias should be LOCAL and
Note RFC destination should be set to NONE. As it should already be preconfigured,
you can skip the section 2.1 and 2.3, but section 2.2 is still required.

• This connection type is used to extract SAP Easy Access menu entries from the
backend server to the frontend server
• Use the following naming convention to create the ABAP connection:
Note <System Alias>_RFC
• System Alias will be created in section 2.3. It is recommended to use the
following naming convention for System Aliases:
<system id>CLNT<client>

1. Run transaction SM59 on frontend system then click on the create button

Figure 29 Create the RFC

20
2. Enter the destination name and connection type then click on Continue

1 RFC Destination: <System Alias>_RFC

2 Connection Type: 3 RFC connection to ABAP system

Figure 30 Create ABAP Connection

3 Configure the RFC destination with the following details

1 Description 1: Description of this RFC destination

2 Load Balancing: Choose “Yes” if you have one or choose “No”
3 Target Host: The host of backend system
4 Instance No.: The instance number of backend system

21
 Figure 31 Technical Settings of ABAP connection

5 Navigate to tab “Logon & Security” and configure with the following details

1 Client: The client of backend system

2 User: Current User
3 Trust Relationship: Yes

22
 Figure 32 Logon & Security settings of ABAP connection

4 Save this RFC destination and then click Remote Logon to test the connection

Figure 33 Test the connection

23
 Figure 34 Connection is OK

2.2 Create RFC connection – HTTP(S) connection

• This connection type is used during Launchpad runtime to start the Web
Dynpro applications and SAP GUI transactions from the Launchpad
Note • Use the following naming convention to create the HTTP connection:
<System Alias>_HTTP or <System Alias>_HTTPS
• We recommend using an HTTPS connection

1. Run transaction SM59 on frontend system then click on the create button

24
 Figure 35 Create the RFC

2. Enter the destination name and connection type then click on Continue

1 RFC Destination: <System Alias>_HTTPS

If it is embedded system, as system alias is LOCAL, enter LOCAL_HTTPS
2 Connection Type: H HTTP connection to ABAP system

Figure 36 Create HTTP connection

25
3. Configure the RFC destination with the following details

1 Description 1: Description of this RFC destination

2 Host: The host of backend system
If it is embedded system, enter the same hostname as the Fiori Launchpad
3 Port: The port number of backend system
If it is embedded system, enter the same port as the Fiori Launchpad

Figure 37 Configure Technical Settings of HTTP connection

a. Navigate to tab Logon & Security and configure with the following details, then click Save

1 Client: The client of backend system

2 User: Current User
3 SSL: Active

26
 Figure 38 Logon & Security settings of HTTP connection

Note • If you need to configure HTTP connection <System Alias>_HTTP, set the SSL
inactive here

2.3 Create System Alias

1. Run transaction SPRO on frontend system then click on the SAP Reference IMG button

Figure 39 Initial screen of transaction SPRO

27
2. Navigate to SAP Customizing Implementation Guide -> SAP NetWeaver -> SAP Gateway -> OData
Channel -> Configuration -> Connection Settings -> SAP Gateway to SAP System -> Manage SAP
System Aliases, then click on the execute button

Figure 40 IMG structure

3. Click Create System Alias

Figure 41 Create system alias

28
4. Input the following information, leave other fields empty, then click Continue

1 System Alias: <system id>CLNT<client>

2 RFC Destination: The RFC destination configured in section 2.1
3 Software Version: DEFAULT
4 Description: Description of this system alias

Figure 42 System alias details

29
 Chapter 3
Activate OData Services

• In this chapter, you are going to activate 2 OData services:

Note /UI2/EASY_ACCESS_MENU: Retrieves the menu entries of the SAP menu
/UI2/USER_MENU: Retrieves the menu entries of the user menu

1. Run transaction /IWFND/MAINT_SERVICE on frontend system then click on the Add Service button

Figure 43 Add OData services

2. Input the following information and click Get Service

1 System Alias: System alias defined in section 2.3. If it is embedded system, system alias
should be LOCAL.
2 External Service Name: EASY_ACCESS_MENU

30
 Figure 44 Get OData service

3. Select the service then click Add Selected Services

Figure 45 Add selected OData service

4. Assign a package. Or click Local Object if no transport is required. Then click Continue

31
 Figure 46 Local Object

5. Click Continue on the following pop-up dialog

Figure 47 OData service is created successfully

6. Use the same steps above to add another OData service /UI2/USER_MENU
(External Service Name is USER_MENU)

32
 Chapter 4
Enable SAP Easy Access Menu

• You have the following two options to enable the SAP Easy Access Menu. You
can choose one of the options based on your needs.
Note Role-free: Enable the feature for all users in the selected client or system. This
option is available since S/4HANA 1909 and SAP_UI 754 SP02.
Role-based: Enable the feature for all users assigned to a specific role.

4.1 Role-free option

Note Use this option if you want to enable SAP Easy Access Menu on Fiori Launchpad
for all users

1. Run transaction SPRO on frontend system then click on the SAP Reference IMG button

Figure 48 Initial screen of transaction SPRO

2. Navigate to SAP Customizing Implementation Guide -> SAP NetWeaver -> UI Technologies-> SAP Fiori -
> SAP Fiori Launchpad Settings -> Change Client-Specific Settings, then click on the execute button

33
 Figure 49 Change Client-Specific Settings

3. Click on New Entries

Figure 50 New Entries

34
 4. Create a new entry with the following details and click Save

1 FLP Property ID: FLP_EAM_ALIASES

2 Property Value: System alias created in section 2.3. If it is embedded system, system
alias should be LOCAL.

Figure 51 Parameter FLP_EAM_ALIASES

4.2 Role-based option

Note Use this option if you want to enable SAP Easy Access Menu on Fiori Launchpad
for users assigned to a specific role

1. Open Fiori Launchpad Designer and click Create Catalog button

Note • You can also create the target mappings in an existing catalog, in this case
please skip the step 1 and 2

35
 Figure 52 Fiori Launchpad Designer

2. Enter the title and ID of the catalog then click Save

Figure 53 Create catalog

3. Navigate to Target Mappings tab on the catalog page then click Create Target Mapping

36
 Figure 54 Create target mapping

4. Create the target mapping Shell-startGUI with the following details

1 Semantic Object: Shell

2 Action: startGUI
3 Application Type: Transaction
4 Title: The title you want to display to end users on Fiori Launchpad
5 Transaction: Enter a dummy value (This field must NOT be empty, but its value will be
ignored)
6 System Alias: This field must be empty
7 Device Type: Desktop (Make sure Tablet and Phone are deselected)

Figure 55 Configure target mapping Shell-startGUI

5. Enter the parameter sap-system with following details

37
 1 Name: sap-system
2 Mandatory: Active
3 Value: System alias of the backend system created in section 2.3. If it is embedded
system, system alias should be LOCAL.
4 Is Regular Expression: Inactive

Figure 56 Parameter sap-system

6. Click Add then enter the parameter sap-ui2-tcode with following details

1 Name: sap-ui2-tcode
2 Mandatory: Active
3 Value: .*
4 Is Regular Expression: Active

Figure 57 Parameter sap-ui2-tcode

7. Make sure the Allow additional parameters option is DESELECTED and click Save

38
 Figure 58 Target mapping Shell-startGUI

8. Refer to step 3-7, Create another target mapping Shell-startWDA with the following details

1 Semantic Object: Shell

2 Action: startWDA
3 Application Type: Web Dynpro
4 Title: The title you want to display to end users on Fiori Launchpad
5 Application: Enter a dummy value (This field must NOT be empty)
6 System Alias: This field must be empty
7 Device Type: Desktop (Make sure Tablet and Phone are deselected)
Parameter sap-system:
8 Name: sap-system
9 Mandatory: Active
10 Value: System alias of the backend system created in section 2.3. If it is embedded
system, system alias should be LOCAL.
11 Is Regular Expression: Inactive
Parameter sap-ui2-wd-app-id:
12 Name: sap-ui2-wd-app-id
13 Mandatory: Active
14 Value: .*
15 Is Regular Expression: Active

39
 16 Allow additional parameters: Active

Figure 59 Target mapping Shell-startWDA

• For the same backend system, we recommend that you use the same title as in
Note the target mapping Shell-startGUI
• In case both target mappings are specified, the title in the Shell-startGUI target
mapping will be preferred over the title in the Shell-startWDA target mapping

Note • Skip step 9-14 if you created the target mappings in the catalog you already
have the authorization

9. Run transaction PFCG on frontend system

10. Enter a role name then click on the Create Single Role button

Note • You can also use an existing role to assign the authorization

40
 Figure 60 Create a PFCG role

11. Enter a description of this role then navigate to Menu tab, click Yes on the pop-up dialog

Figure 61 Save the role

12. Click Insert Node then select SAP Fiori Launchpad -> Launchpad Catalog

41
 Figure 62 Insert node

13. Enter the Catalog ID of the catalog you used to create target mappings in step 2, then click Continue

Figure 63 Assign tile catalog

Note • You can use F4 help to select the catalog ID

14. Navigate to User tab, enter the User ID of the user(s) you want to offer SAP Easy Access menu entries,
then click Save

42
Figure 64 User assignment

43
 Chapter 5
Test SAP Easy Access Menu on Fiori Launchpad

1. To ensure fast loading times of SAP menu apps in the app finder, we recommend you to schedule the
report /UI2/EAM_BUILD_CACHE periodically. See Scheduling Caching of SAP Menu Entries.

2. Log on Fiori Launchpad then open the App Finder

Figure 65 Fiori Launchpad home page

3. Navigate to User Menu tab on App Finder page, you can see the same user menu the current user has
on the backend system

Figure 66 User Menu

44
 Figure 67 User menu on backend system

4. Navigate to SAP Menu tab on App Finder page, you can see the same SAP menu the current user has on
the backend system

Figure 68 SAP Menu

45
 Figure 69 SAP menu on backend system

5. By clicking on the ‘Add tile’ button, users can add the applications retrieved from the SAP Easy Access
menu to the launchpad homepage

46