You can provide end users with the option to select SAP GUI and Web Dynpro ABAP
applications retrieved from the SAP Easy Access menu in the ABAP backend and add them to the
launchpad home page
Context
The SAP Easy Access menu provides access to SAP GUI and Web Dynpro ABAP applications.
There are two types of menus:
Here is a high-level overview of the configuration steps
you need to perform if you want to offer SAP Easy Access menu feature to launchpad
end users:
Define the list of SAP systems for which SAP Easy Access menu entries should
be retrieved.
During launchpad runtime, a dialog with the list of defined
systems will be displayed. End users select a system to get the SAP Easy Access
menu entries displayed as tiles on the launchpad homepage.
-
Establish connections between frontend server and relevant backend
systems.
-
Activate OData services to retrieve the relevant menu entries from the
backend system.
-
Enable that, during launchpad runtime, users can navigate from the launchpad
to the backend applications.
Perform
the following steps on the ABAP front-end server:
Procedure
- Establish connections to backend systems.
- Create or select a system alias for each backend system to which you
want to connect.
In Customizing, choose and launch the IMG activity Manage SAP
System Aliases.
- (Optional) Map the connections. This step reduces the maintenance
effort if you have several system aliases pointing to the same physical
source system. See Map the Connections.
- Create RFC and HTTP connections pointing to the system alias:
-
In Customizing, choose and launch the IMG activity Manage
RFC Destinations or directly launch
transaction SM59.
- For each system alias identified in step 1, create two RFC connections:
ABAP connection (type 3):
This connection
type is used to extract SAP Easy Access menu entries
from the back-end server to the front-end server.
Use the following naming convention:
<Logical System
Alias>_RFC
- HTTP(S) connection (type H):
This connection type
is used during the launchpad runtime to start the
Web Dynpro applications and SAP GUI transactions
from the launchpad.
Use the following naming
convention: <Logical System
Alias>_HTTP or <Logical
System Alias>_HTTPSNote
We recommend to use a HTTPS connection.
- Activate OData services.
- In Customizing, choose and activate the following OData services:
Table 1:
/UI2/EASY_ACCESS_MENU
|
Retrieves the menu entries of the SAP menu.
|
/UI2/USER_MENU
|
Retrieves the menu entries of the user menu.
|
- To add a service, choose .
- Select the system alias of the backend system (see step 1), then select a service from
the table above.
For information about activating OData services, see the SAP Gateway
Developer Guide at .
- To allow navigation from the launchpad to SAP GUI transactions and Web Dynpro
ABAP applications, for each back-end system, you create one target mapping for
transactions and one for Web Dynpro applications.
- Start the launchpad designer.
- Select a catalog or create a new one.
- Create two target mappings as described under Creating Target Mappings for the SAP Easy Access Menu.
- Configure authorization roles.
- Make sure the catalog is assigned to a PFCG user role. See Assign Tile Catalogs to Roles.
- Make sure the users for whom you want to offer SAP Easy Access menu entries are assigned
to the same role as the catalog. See Assigning Users to Roles.
Results
If a user who is assigned the role of the catalog to which you added the target mappings
opens the app finder in the launchpad, all SAP GUI and Web Dynpro ABAP applications
integrated in an SAP GUI user menu or SAP menu are retrieved from a selected back-end
system. The user can add these applications to the launchpad homepage.
For more
information, see Adding Apps to Your Launchpad.