
In the tile configuration, provide the parameter sap-system=<SYSTEM_ALIAS> in the Parameters field.
The URL fragment for navigating to the application will then look like this:
#SemanticObject-action?sap-system=<SYSTEM_ALIAS>
If you want to enable users to access your application on all systems, you only need to create one target mapping for all tiles created in step 1.
If you want to prevent navigation to a system for users who do not have any authorizations for this application on this system, we recommend to create a filter in the target mapping. In the Parameters table of the target mapping configuration, enter the following settings:
|
Field |
Value |
|---|---|
|
Name |
sap-system |
|
Mandatory |
Active |
|
Value |
Enter the system alias of the system for which you want to use this target mapping. |
Then, assign the target mappings to the respective roles.
Example: /sap/opu/finsrv;o=<SYSTEM_ALIAS>
If you use SAPUI5 1.30 or higher, and if you use the data source mechanism of the app descriptor to create the OData model, the framework takes care of propagating the segment parameter.
In other cases the application code has to take care of propagating the value of the sap-system parameter into the service URL. The SAPUI5 service function sap.ui.model.ODataUtils offers the setOrigin method, which provides a convenient way to append an OData segment to a service URL.
In SAP Reference IMG (transaction SPRO), select the following paths:
SAP NetWeaver
Gateway
OData Channel
Configuration
Connection Settings
SAP NetWeaver Gateway to SAP System
Manage SAP System Aliases 
SAP NetWeaver
Gateway
OData Channel
Administration
General Settings
Assign SAP System Aliases to OData Service 