Skip to Content
1
Feb 26, 2020 at 10:41 AM

Fiori Tile accessing BEx query- Unknown service

593 Views

Hello Experts

We are seeing a strange behavior, when Fiori tiles are trying to get data from BW BEx query.

We have two environments:

1. Fiori & S4H (Embedded server) and Separate BW server. This scenario is working as expected.

2. Fiori, S4H and BW -> are running on different servers. This scenario is not working.

Please find few screen shots, with the issue highlighted.

In First scenario, in Network tab, when calling BEx from the Tile. We could see the Alias name passed as a parameter in the URL, We have configured the ALIAS name in the Tile

sce1-alias-inurl.png

alias-tile-configuration.png

When we remove the alias from the tile configuration, then the InA service picks the default alias configured in the RSADMIN table. We see no parameter is passed in the call to the /bw/ina service

url-without-alias.png

In Second Scenario, it is a Hub deployment i.e we have separate configurations for Fiori, S4 and BW, all on different servers.

alias-tile-configuration.png

The /bw/ina service call does not contain any system alias parameter, even though our tile configuration has got it configured:

url-without-alias.png

It is hitting the default alias system (which is S4 in our case). Hence, the report fails to bring BW data from the separate BW system. The response looks like this:

response-bwquery.png

When we change this default alias to point to the alias “BWALIAS”, the service starts pointing to the new default alias, and thus looks for the BW queries using this default alias, and the tile starts working, but this process affects the standard tiles which need S4 system objects. In this process, the service is not picking up the system alias parameter configured in the fiori target mapping for the tile

We are trying to understand why the service is able to take the system alias parameter in the Scenario 1, but not in Scenario 2, and how can it be configured so that o=<system_alias> parameter is added to the /bw/ina service call for BW(in Scenario 2), just like it is working in Scenario 1, as that will solve the problem.

I tried to give as much info, I can. Please let me know, if you need any other details so that any of you can help me resolve this issue.

Regards

Giri