Changing Logical System Names

[Former Member]

Currently, each instance(SID) in an entire landscape all have the same logical system name and the RFC name that corresponds is all the same. You really don't know what system the RFC is pointing to until you open it up and see which server, etc. is listed in the RFC. So, we are working on a project so that each instance has it's own unique logical system name. The biggest problem we are concerned about is making sure that we change all the places where these definitions exist. I have a small list of transactions that need these items changed (SM59, SALE, SCC4, RSA1, SMQR, SMQS, SBIW, SPRO (this is a tough one)). We realize we will depend on our application teams heavily to know where they changed any configuration to use logical systems. My question is to see if anybody has done this type of change, if they have any tips/guidance, to see if anybody can give some good direction on where to find all the places these LS names are used, and if anybody else can throw out any other transaction suggestions that we should check. Thanks in advance.

-Marsha

[Former Member · Accepted solution]

Hi Marsha,

Hope these Notes will be Useful.

446294 CC INFO: Logical system name and client copy

121163 BDLS: Converting logical system names

962674 BDLS: Inconsistency in log tables

Thanks,

Tanuj

[Former Member]

The problem is that we would really like all the landscapes to have the same standard for their names. We also have one system where the name reflects and old SID name and it is very confusing for everyone. We may be ok not changing it on every production system, but for the R/3 we believe it definitely needs to be changed because of the confusion it has/is causing to people. Any other ideas? Thanks.

[Former Member]

Marsha,

I think you should examine the reasons why it would not work before asking if you can do it. One reason for us was archiving. We regularly archive off data only keeping the last 3-7 years of data in the system for some tables. Changing the logical system ID for us would mean it would be impossible to reload some of that archived data, without customizing or a new development effort.

So if your questions is can you do it? Yes, you can do it.

If the question is should you do it? .....Well, then you need to examine why or why not in your own environment. There are likely to be pitfalls especially if its usage is widespread at your company as you indicate.

-jwise

[Former Member]

SAPs recommendation on the help screen for transaction BDLS recommends not running BDLS in a production system. So, now I am wondering how we are going to change the logical system name in our production system so we have a standard across our landscapes without running BDLS. Does anybody have an recommendations as to how we get everything straightened out in the production system after changing the logical system name? Thanks in advance.

[Former Member]

How about changing it everywhere else except production? That is what we did when faced with a similar situation.

-jwise