cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

FIORI: Backend references for Odata services are not getting updated after Transport

BharathM
Participant
0 Kudos
1,757

Hi guys,

I was configuring a standard Fiori application and I am facing this issue after importing TR to the Quality system.

Architecture Type: HUB

Error in: /IWFND/MAINT_SERVICE

Problem: As we are having hub architecture instead of LOCAL system alias I was referring to my backend system through a trusted RFC connection, In development it was working fine. But when I transport the Request (TR) to Quality they are transporting with development references only. In general, they should automatically convert to corresponding Quality reference. But in our case, this is not happening, So my applications were unable to fetch the data.

Any workaround / Solution is appreciated.

Thanks for spending your time on my Question.

Accepted Solutions (1)

Accepted Solutions (1)

saurabh_vakil
Active Contributor

In case your System Alias (using which you register your OData services) is named the same in the DEV and QA landscapes (with some generic name like GWTOERP) then the transported services should work fine, you may just need to ensure that the corresponding ICF nodes are active in the gateway quality system.

However, if the System alias has been named using the naming convention <SYSTEMID>CLNT<CLIENT> (for e.g. GD1CLNT100, GQ1CLNT200 and so on) then since the DEV and QA system ids would be different your transported services would not work in the QA system, it will also not automatically convert to the quality references (how do you expect this to happen automatically?). The option in this case would be to manually remove the DEV system alias reference from the OData services in the Quality gateway system and assign the quality system alias.

BharathM
Participant
0 Kudos

Hi Saurabh,

Thanks for your Reply, Instead of Creating extra Transport Request in quality system i created a generic Name and it was working fine.

Regards,

Bharath

saurabh_vakil
Active Contributor

You can prevent creation of transport in the Quality system while changing the system alias (in case your system alias names are different in Dev and QA) by turning off change recording in the Quality gateway system.

Answers (1)

Answers (1)

imsuryapandiyan
Participant

Hi Bharath,

Goto tocode: /IWFND/MAINT_SERVICE

After clicking on your service from the list, you will see the system aliases of the service. Check whether it is proper. If not, you can delete that alias and add the correct one.

BharathM
Participant
0 Kudos

Hi Suriya,

Thanks for your reply, The solution you have provided will work for sure But the problem is it will create an extra Transport Request in Quality which is not possible in our system.

Regards,

Bharath