Skip to Content
Technical Articles
Author's profile photo Mario Nadegger

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.

Assigned Tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Cameron Hunt
      Cameron Hunt

      So useful and necessary !!!

      Why doesn't SAP provide this information ????

      Author's profile photo Norbert Frühwein
      Norbert Frühwein

      Thanx, also helpful, when copying aliases via scc1 between different clients.

      Be aware, that version "_000x" is added to technical name in database & transport.

       

      Author's profile photo Dmitry Bondarev
      Dmitry Bondarev

      Why you not use method from Note 2816116 { How to transport an OData Service from one System/Client to another System/Client } ?