Technical Articles
Transport ODATA Services – System Aliases
ODATA is very helpful common language that allows systems a standardized communication.
Also in SAP BW Context data could be consumed via ODATA as described in https://blogs.sap.com/2016/02/08/bex-queries-and-odata-in-bw-74/.
When transporting the service and checking /IWFND/MAINT_SERVICE the System Aliases are most likely not set in target system.
One option is to set this in target system directly. In case of system with restricted access to customizing tables this is only possible with additional authorizations and/or an opening of the system.
Another option is to add this manually to the transport.
The System Aliases are stored in table /IWFND/C_MGDEAM and can be added manually to the transport.
This table entry can be added manually to transport
After transport the System Aliases is set in target system.
So useful and necessary !!!
Why doesn't SAP provide this information ????
Thanx, also helpful, when copying aliases via scc1 between different clients.
Be aware, that version "_000x" is added to technical name in database & transport.
Why you not use method from Note 2816116 { How to transport an OData Service from one System/Client to another System/Client } ?
Thanks, very useful !
Definitely it is useful information. Thanks for sharing.!
In my scenario, We have multiple client setup for fiori, In dev system I have two client 100 (Development client) and 110(unit test client) , Also My QA Client number is different from DEV.
I see in your request you are mentioning client. Is it mandatory to add client? How will it work in my scenario if we need to add client.
Also the table : /IWFND/C_MGDEAM is a client dependent table.
Thanks,
Sid
This is very useful information. I want to add that it is not possible to do this if you have a RAP Service that you published via Eclipse.
For this you first need to remove it from the list in /IWFND/MAINT_SERVICE completely and then add it again via add service. But at least then you can an automated popup for transport request and all necessary objects are added to it.
However, it might still be necessary that BASIS activates your ICF node in the target system, if you cannot do so yourself.