Map the Connections

You reuse system alias configurations by mapping the source system alias of a backend catalog to a target system alias with existing RFC connections.

Context

The business catalogs shipped by SAP contain system aliases which are used to call an app in a specific system. In your system landscape, several system aliases may point to one and the same physical source system. To reduce administrative effort, SAP recommends to create entries in table /UI2/SYSALIASMAP. This table is used to map SAP system aliases to logical system aliases, which stand for the physical back-end systems connected to the front-end system. The logical system is resolved to a concrete RFC or HTTP connection by adding the suffix _RFC or _HTTP. If your Fiori launchpad is run in HTTPS mode, the connection needs the suffix _HTTPS. To integrate backend applications into SAP Fiori launchpad, you need to establish RFC and HTTP connections between the frontend and the backend server. You can reuse existing connections by mapping them to the source system alias.

The mapping data is stored in a cross-client customizing database table (/UI2/SYSALIASMAP).

Procedure

Log on to the backend ABAP system.
Identify the source system alias of the backend application:
1. Start Maintain Table Views (transaction SM30)
2. In the Table/View field, enter /UI2/V_SYSALIAS.
3. Choose Display to display the content of the view.
Use Configuration of RFC Connections (transaction SM59) to identify a target system alias that you can use for your mapping.

Indeally, RFC and HTTP connections are already available for the selected system alias.
If neccessary, create missing RFC and HTTP connections in transaction SM59.

Enter the mapping data:

Start Maintain Table Views (transaction SM30).
In the Table/View field, enter the view /UI2/V_ALIASMAP and choose Maintain.
Choose Edit New Entries .

Provide the following:

Table 1:
Field	Description
Client	Leave blank to define that the system alias is mapped to a different value for all clients.
Source	Enter the source system alias identified in step 1.
Target System Alias	Enter the target system alias identified in step 3.

Save your changes.

Results

Before extracting applications from a backend system, the RFC connection is retrieved from the target system alias that you specified in step 5. At runtime of the launchpad, the source system alias is replaced by the target system alias and then mapped to an existing HTTP connection.

Note

Changes to the mapping table will cause cache invalidations and recalculation of cache buster tokens. See Client-Side Caching of Target Mappings.

Example

The backend catalog which you want to integrate has the following system alias FIORI_BE. Rather than creating an RFC and an HTTP connection for this system alias, you want to reuse the system alias FIORI_BE2, which already has an RFC connection FIORI_BE2_RFC and FIORI_BE2_HTTP.

Enter the following mapping data in the view /UI2/V_ALIASMAP:

Table 2:
Field	Description
Client
Source	`FIORI_BE`
Target System Alias	`FIORI_BE2`

In this example, the system alias is mapped to FIORI_BE2 instead of FIORI_BE for all clients.