An SAP system alias maps together:
- A logical RFC destination pointing to an SAP business system.
- A Web service provider system pointing to the same SAP business system.
- The software version of that SAP business system. The supported versions are shipped by SAP and cannot be changed.
Below are the requirements to have before you can create the SAP alias.
- Create the logical RFC destinations.
- Create the Web service provider systems.
Launch transaction code SPRO. Go to below directory,
SAP NetWeaver > SAP Gateway > OData Channel > Configuration > Connection Settings > SAP Gateway to SAP System
Click on Manage SAP System Aliases. Click on New Entries (F5).
Enter the information as per below description and click on save. You might want to capture the changes in the transport request, for later import in the subsequent systems.
| Field | Description |
|---|---|
| SAP System Alias | Name of the system alias. |
| Description | Descriptive text for the system alias. |
| Local SAP GW | The system that is responsible for processing (managing and storing) the data of an inbound request is the local SAP Gateway instance itself. This option is typically used for testing scenarios for example when using the BOR Generator locally.If you activate Local SAP GW for a SAP System Alias called LOCAL the RFC Destination is usually NONE. |
| For Local App | The system alias is to be used by the backend. |
| RFC Destination | Specify the RFC destination defined for your SAP system. |
| Software Version | This setting is specified by the content scenario you are using. Typically it is DEFAULT. |
| System ID | Name of the SAP target system. Recommend to enter the system ID. |
| Client | Target client. |
| WS Provider System | Name of the Web service provider business system. Here you only need to enter a setting if you use content scenarios which are configured via Web services. |
