Skip to Content

How to Maintain SAP System Alias Entries in Productive Systems?

Updates:

  • April 13th, 2017 – Added information how to maintain SAP System Alias entries in test systems

Problem:

 

You want to maintain a system alias entry for a backend system in your productive SAP NetWeaver Gateway hub.

 

The client settings of your productive client do not allow changes of client-specific objects. As a result you find that table /IWFND/V_DFSYAL can not be maintained. Opening the productive client to allow changes is usually not an option.

 

Solution as of SP06:

 

As of SP06 of SAP NetWeaver Gateway 2.0 the flag “Current Settings” for the IMG activity “Manage System Aliases” is active. If you start the table maintenance via the IMG activity in the productive system changes can be performed without the need to record the same in a customizing request which is not allowed due to the client settings.

 

 

 

Flag Object belongs to current settings.png

 

Now, when starting table maintenance via the IMG (transcation SPRO –> SAP NetWeaver –> Gateway –> OData Channel –> Configuration –> Connection Settings –> Manage SAP System Alias) you will be able to maintain SAP system alias entries in your productive system.

 

04_Create a System Alias.png

 

 

Solution for SAP NetWeaver Gateway installations prior to SP06:

 

As a workaround (if the flag is not active) it would be possible to set this flag once and then you should be able to access the maintenance view
without being asked for a transport request as described in SAP Note 135028 – Transfer IMG activity to current setting
.

 

“… To do this, open the IMG and display the IMG structure. Position the cursor on the corresponding IMG activity and select the menu path “Edit
-> Display IMG activity”.
On the following screen, select the tab “Maint.objects”. A list of the assigned customizing objects is displayed. By double-clicking on the corresponding row, navigate to the customizing object and set the indicator “Current settings” directly.”

 

Caution:

Make sure that in transaction SCC4 (client maintenance), for that setting to work, “Client Role” must be set to “Production”. It is not sufficient to have entered  “no changes allowed” for the client settings. Therefore, make sure that client settings are set as shown in the following screen shot.

 

Client settings SCC4.png

How to perform these changes in test systems?

Please check SAP Note 356483 – Customizing: Current settings in the test system

https://launchpad.support.sap.com/#/notes/356483

 

19 Comments
You must be Logged on to comment or reply to a post.
  • Current settings is only true for productive client, but what about DEV & QA instances, if you have multiple clients in DEV ? You gateway customizing has the image of your dev system and cannot be change ?

    These tables needs to be change in all sap instances (dev, qa, prod)

    /IWFND/V_DFSYAL

    /IWBEP/C_SYSTEM

    Also they are protected against changes according to their namespace, so we can't change the recording routine in SE54

    Alex

  • Hello Andre,

    I was not able to locate the Assigned Object "Maintenance Object" in IMG activity on NW Gateway 7.4. Is there a transaction code, if not please guide me to the location in IMG.

    Thanks so much in advance,

    DN

  • Hi Andre.

    We recently have upgraded our Gateway to Sap Netweaver 7.50 SP04 and now there are not current setting enable for these views.

    When the system was in Sap Netweaver 7.50 SP3 these views were marked in standard as current setting.

    Anybody knows something about this change? Is there any note to revert these views to current setting again?.

    Best regards.

  • Hello,

    I'm trying to found a solution for put system alias in quality system working, when I searched many of tutorials have your link. But unfortunely don't resolve my problem.

    Have you can give on solution to my problem here if you know please: https://answers.sap.com/questions/49923/how-can-i-use-system-from-dev-to-qa.html ?

    I'm really disesperated.

    Thanks very much for your time

    Best Regards

    Cristina Rodrigues

  • Hello Andra,

    Thanks for a very useful information. I have a question. I am creating a system alias say GW_ECC with RFC destination as blank so that I can maintain the RFC destination in Quality and Production systems.

    Becuase we have current setting for Production, I will maintian the RFC destination in Production. But what about the quality system. How to maintain the alias in quality system.

    • Good question ;-).

      This is described in SAP Note 356483 - Customizing: Current settings in the test

      https://launchpad.support.sap.com/#/notes/356483

    • the note does not contain any restrictions with regards to the release. therefore it should be applicable to 7.40 as well. but i would recommend to simply try it out.

  • At my previous client, I configured the aliases and their corresponding RFC destinations to be environment-agnostic.

    That is, the aliases and destinations do not point to a specific sysid/client combination, but a generic, logical destination, e.g. just "ECC" instead of "ERDCLNT100" or whatever.

    That way, only the corresponding RFC destination in SM59 needs to be updated in each environment and will always point to the corresponding back-end system, i.e. alias "ECC" will point to ECC Dev from the GW Dev system and ECC Production from the GW Prod system.

    (Of course, other solutions can still have their own RFC destinations; this is just for Gateway services).

    In so doing, the services and their corresponding destinations need to be set up once only and can be transported through the landscape and will work correctly in each environment. No maintenance of system aliases is required in systems other than Dev.

    • If that is possible, this definitely an option.

      Since we worked under the assumption that lots of customers would not do that but would use RFC destination naming conventions that follow the naming convention SIDxxx where xxx is the client number we introduced the system aliases as a wrapper.

      In the end one has to enter the system specific information somewhere and do a mapping between the system alias name and the "real" hostname of a system.

      • Yes, of course the situation I am describing is the ideal. It is not always so straightforward.

        But only having to maintain a single RFC destination in each environment (at least in the context of Gateway services) does simplify matters significantly.