cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to configure SAP Tcode as Custom Tile in Fiori Launchpad

0 Kudos
1,603

Hi All,

I am trying to configure custom t code which is exist in ECC through Fiori launchpad. But unable to do it and getting an error message as "T Code does not exist" in Gateway.

System landscape details: Central Hub Deployment where GW and ECC are in different clients and below attachment will give the component details.

ecc-and-gateway-components-details.png

I followed the below link and did configuration in Fiori designer cockpit with Gateway client.

http://www.saplearners.com/how-to-configure-sap-tcode-as-custom-tile-in-fiori-launchpad/

also followed below link

https://blogs.sap.com/2016/12/21/open-your-sap-gui-transaction-in-fiori-launchpad/

Since my custom T Code is in ECC client, I am getting error as T COde XXXX does not exist as the system is trying to execute in Gateway client where T code does not exist.

Could anyone, let me know, how to achieve same output in case Central hub deployment where T code is exist in ECC server .

Below is errror screen shot.

error-screen-shot.png

Kindly let me know the solution If anyone have any idea about it.

Kind regards,

Chetan

View Entire Topic
0 Kudos

Hi All,

Finally, I got the solution. Below are the observations which I came across during finding the solution.

1. We need to follow below links to set up configurations

http://www.saplearners.com/how-to-configure-sap-tcode-as-custom-tile-in-fiori-launchpad/

also followed below link

https://blogs.sap.com/2016/12/21/open-your-sap-gui-transaction-in-fiori-launchpad/

2. The only thing we need to be sure is, naming standard for System alias and name of RFC connection and also choosing Type of RFC which we establish between gateway and ECC or corresponding backend system.

You can follow below help.sap.com links to know more on this.

https://help.sap.com/viewer/a7b390faab1140c087b8926571e942b7/1709.001/en-US/db3c067c1bf3454eaf1f8ab9...

For example, If your System alias name is AliasECC then your RFC connection name should be AliasECC_RFC in case of RFC connection between GW and ECC.

In case, If you are using HTTP port of Target then it should be AliasECC_HTTP with Type H .

In case If you are using HTTPS port of Target then its should be AliasECC_HTTPS with Type H.

3. Also, make sure, you have maintained the right entries in view /UI2/VC_SYSALIAS.

It's better to set up the configuration using SCOPE = CONF. Even CUST is also fine.

Kind regards,

Chetan