Assigning SAP System Alias to OData Service

You can assign SAP system aliases to a service. With this assignment, an OData request from an SAP Gateway consumer can be routed to the corresponding backend system. The system can correctly identify the SAP system that is responsible for processing (managing and storing) the data of an inbound request. Thus, OData Channel based content which is developed either on the SAP Gateway hub system or on a SAP Business Suite backend system is based on the service.

The SAP system alias can have a specific role or a specific host name associated to itself, so that you can specify different roles or host names for the same system alias for a service. If you leave the User Role or the Host Name field empty, the setting is valid for all roles/host names. Different backend systems are supported, if you specify corresponding roles/host names and system aliases. The roles are only for user grouping and do not need to have any special authorization.

Example

It is possible to separate the development, the quality and the production landscape via dedicated clients on the SAP Gateway hub system.

The user will be directed as follows if he or she does not have special roles: If there is a system alias maintained without any role assignment then it is used for all users.

The user will be directed as follows if he or she has two or several roles relative to different system aliases: If a user is assigned to more than one system alias the system alias which is marked as default wins. If more than one system alias is found and either none of the system aliases or more than one of these aliases are flagged as default an error is raised.

Ideally you have a system alias without any role assignment for all users without a role assignment and disjunct roles for the system aliases for all other users to the different backend systems (development, quality, productive). The system aliases with role assignment should be marked as default in this case.

For this an IMG activity is available in the SAP Gateway Implementation Guide (IMG): in transaction SPRO open the SAP Reference IMG and navigate to Start of the navigation path SAP Gateway End of the navigation path :

For applications based on backend OData Channel system navigate to OData Channel Administration General Settings Assign SAP System Aliases to OData Service .
For applications based on OData Channel with IW_BEP on the hub navigate to OData Channel Development with IW_BEP Registration Assign SAP System Aliases to OData Service .

Note

In previous support packages OData Channel based content was routed via GSDO groups which are no longer relevant in SAP Gateway 2.0 SP03.