System aliases

[Former Member]

It is the same question answered multiple times. The issue I have is

From Gateway

on ECC side ODATA is activated

System Alias on Backend ECC (EHP7 NW 7.4 SP13)

System Alias on Gateway (NW 7.4 SP13)

I believe it is a problem with aliases. It is a hub architecture.

SMT1 ->trusted connection work OK both ways. Authorisation check successful.

Sorry to ask the same question again. Suggestions welcome !

[former_member182967 · Accepted solution]

Hi Bocaj,

For system alias defined in SAP Gateway, do not need to input SID and client.

If you want to configure it for SAP Fiori, make sure all the prerequisite steps are done mentioned in SAP Service Marketplace - SAP Fiori Apps -> EE0_NWG20_BB_ConfigGuide_EN_XX.

Additionally, check if the component required in gateway is installed or not.

Regards,

Ning

[Former Member]

Hello,

It was solved by following the RDS document.

EE0_NWG20_BB_ConfigGuide_EN_XX

kind regards,

Jacob

[lynn_lin]

Hi,

Please check KBA 2136247 - Fiori OData Service is missing in /IWFND/MAINT_SERVICE

Regards,

Lynn

[former_member184867]

You need to configure the system alias only at the Gateway HUB. Now depending on the deployment scenarios the configuration settings will change. Refer to the System alias setting configuration here at

Hub deployment can be of 2 types, refer to them here . Based on that you need to configure the System Alias.

Even though you can register your service in the back end (ECC) itself (which you have done), it is not needed and remains unused. Activation of OData in back end ECC has no relation with activation of the same service in GW Hub.

Message was edited by: Atanu Mallik