Configuration Steps for Design Studio in Distributed S/4HANA Environments 

Please call transaction SICF.

Now activate and test following in InA services:

• sap/bw/ina/GetServerInfo
• sap/bw/ina/GetResponse

call t-code SMICM. Select Goto > Services in Menu.

Now call InA Service from your browser using host and port from protocol HTTPS.

You must see the response. The tag ServerInfo must have the correct backend system id and client.

Recommended:

It is advised by the experts the configuration of an RFC destination to route InA Requests from the Frontend System to the desired Backend System.

Reason:

In Fiori Launchpad it is possible for setting and storing the application specific information (Cost Center Area etc.). This information is saved on the Frontend System and is only applicable in case all the requests are forwarded to the frontend system and then are routed via RFC destinations to the backend system.

Important Point

If the user is utilizing SFIN and has configured SFIN for using the alias "S4FIN" for routing all the SFIN application requests via the RFC to the SFIN target system then user cannot use the WebDispatcher configuration listed below. User should configure a RFC destination on his SFIN system for routing InA Requests to the desired Backend System.
Another option alternative will be creating the system alias on your Backend System with RFC destination "NONE".

Reason:

SFIN applications always specify the system to be "S4FIN". This refers that all the requests launched within these applications comprise of the parameter system=S4FIN. Generally, the Frontend/Gateway system is called with this information. On the Frontend/Gateway system, this leads to the service to be routed to the definite target system configured for alias "S4FIN".

If user is using the WebDispatcher then the requests forwarded to the backend system will also comprise of the parameter system=S4FIN as the SFIN applications have listed this as default. However, the Backend System has no knowledge of this configuration and will display an error message "System alias S4FIN does not exist".
The new configuration guideline of SFIN causes this issue.

One of the following methods can be used for the Configuration of routing of InA requests to Backend Server, but NOT both of them

Configuration of an RFC Destination on the Frontend Server to route InA requests through the Frontend Server to the desired Backend Server
Important:  User should not combine this with the Web Dispatcher approach below.
Note: on the basis of our past experience, we advise this is the easier configuration as compared to the Web Dispatcher alternative as it is alike to other S4 Odata configuration steps.

As a precondition to this step, user should have configured the following on his Frontend Server. Generally, these tasks would have already been done during ODATA configuration:

• An RFC destination for the appropriate CLIENT on the Backend Server call transaction SM59 and creating an ABAP connection or call transaction SPRO > open the SAP Reference IMG and navigate to: SAP NetWeaver > SAP Gateway > OData Channel > Configuration > Connection Settings > SAP Gateway to SAP System > Manage RFC Destinations

• A System Alias pointing to the RFC destination mentioned in point 1call transaction SPRO > open the SAP Reference IMG and navigate to: SAP NetWeaver > SAP Gateway > OData Channel > Configuration > Connection Settings > SAP Gateway to SAP System > Manage SAP System Aliases

Setting up the Default System Alias which should be utilized by the InA service for data access. The Default System Alias is set by the RSADMIN parameter RSBICS_INA_RFC_DEFAULT_ALIAS.

This can be set by utilizing the Report SAP_RSADMIN_MAINTAIN (on the front-end server).  User should Simply specify RSBICS_INA_RFC_DEFAULT_ALIAS as OBJECT and the desired System Alias (from point 2 above) as VALUE.
Provided RSADMIN settings can be seen by calling transaction SE12 with database table RSADMIN and then viewing the Table contents.

call transaction SMICM. In Menu select Goto > Services. Using host and port from protocol

User should view a response. The tag ServerInfo should encompass the correct backend system id and client.

Configuration of a Web Dispatcher to route InA requests directly to the desired Backend Server
Important:  User should not combine this with the above-listed approach.

For more detailed information regarding the SAP Web Dispatcher, please refer to the section SAP Web Dispatcher: Setup of Communication in the UI Technology Guide for the appropriate version of SAP S/4HANA

In the Web Dispatcher configuration, the following path is required to be configured for getting routed to the Backend Server:

• /sap/bw/ina

It is very important that Single Sign-On is correctly configured between the Frontend / Gateway Server and the Backend Server.

A target CLIENT should be specified for the entries which route to the Backend Server should also be kept in mind.

User should ensure that the GetServerInfo URLs do not comprise of a parameter o=S4FIN which narrates the INA implementation of GetServerInfo to go to the RFC target defined by the S4FIN alias.

User can utilize the Chrome Network Tools (F12) for checking whether the parameter is contained.
http://host:port/sap/bw/ina/GetServerInfo;o=S4FIN?sap-client=...

The error message is a 400 with body text: "...System alias 'S4FIN' does not exist"}]}"

If the GetServerInfo URLs do comprise of a parameter o=S4FIN then WebDisptacher Configuration is impossible. User must configure an RFC destination as listed above. Another option would be creating the system alias on your Backend System with RFC destination "NONE".