Assigning alias system to OData services

[Kishore]

Hello All,

In our landscape, we have three systems (Dev, QA and Prod). All the three systems are having three different alias system names.

When a service gets moved to QA and Production, I want the service to be pointed to QA and Production system aliases respectively.

How to assign these alias systems to OData services. Do we need to manually assign them in Quality and Production system?

The entries are available in view /IWFND/V_MGDEAM. This view is not marked as a current setting.

Please suggest how to assing different aliases in different systems.

[AshwinDutt · Accepted solution]

Hello Kishore,

Can you please have a look at the below ?

https://blogs.sap.com/2013/05/31/how-to-maintain-sap-system-alias-entries-in-productive-systems/

Also you can open up the client for a small period, create and assign system alias to your service in the respective systems.

At times we have encountered the cases where for some reason client does not want to open the client in that case you can create generic system alias say like GW_ECC, assign this to your service and transport from Dev and carry all the way till QA and Prod systems. Once moved to QA and Prod systems, create RFC destination in SM59 to point to appropriate back-end and assign this to the transported System Alias GW_ECC in SPRO.

This way you need not to open the client and assign system alias in QA and Prod systems. All you need is creating RFC destination and assign this to the transported system alias in SPRO.

Regards,

Ashwin

[Kishore · Accepted solution]

Hello Ashwin,

Thank you for your inputs. This approach works. One last question. If not current setting and client opening what are the other options to maintain the system alias. Can this be done from 000 client. If so will it ask for transport as well.

Thanks,

Kishore.

[AshwinDutt · Accepted solution]

Hello Kishore,

Yes you need a Customizing TR to transport the System Alias settings from Dev to QA and Prod systems.

Create generic system alias say like GW_ECC in Dev, assign this to your service and transport from Dev to QA and Prod systems. Once moved to QA and Prod systems, create RFC destination in SM59 to point to appropriate back-end and assign this to the transported System Alias GW_ECC in SPRO.

This way you need not to open the client to assign system alias to your services in QA and Prod systems. All you need is to create RFC destination and assign this to the transported system alias in SPRO.

Regards,

Ashwin