Logical system name changes

[Former Member]

All,

Has anyone faced a scenario where you need to change the logical name for any SAP system?

For instance:

System Logical Name System Logical name B

BW A system is pointing to ECC B

ECC will be upgraded and system name will changed to C

Is that possible? If so do you forsee any issues? Can we switch ECC B to ECC C with no issues?

I appreciate any help.

Regards

[Former Member]

We do this regularly after system refreshes using BDLS.

Need to redo source-system defs if connected to BW/SCM.

May also need to update liveCache table /SAPAPO/ORDMAP if SCM is connected.

[Former Member]

Stephen,

Have you ever done this in any prodcution system? This is what we need to do at this point and we found some SAP notes saying that changing logical names in production systems -in other words running BDLS tools- is not supported.

Could you please let me know?

Thank you!

[Former Member]

Hi Mike,

I haven't read such notes saying not supported in a prod environment.

Have read note 544509. SAP don't recommend for Prod but they don't 'not support it'.

Anyway, the last time I did this in a Prod system was 7 years ago.

It went without any hitch. This was in a BW 3.1C system.

I had already tested it in a DEV system first though so knew it would not cause any issues.

I actually had to do it twice in 1 day as I got the name wrong during the first rename.

As I said, we do it in Dev etc whenever we do a system copy.

We don't have any java components.

cheers,

Stephen

Edited by: Stephen Kerr on Sep 7, 2010 3:23 PM

[Former Member]

Hi stephen,

This is kind of confusing but not too surprising though. Please see below note:

Note 886102 - System Landscape Copy for SAP NetWeaver BW

Scenario C1

You want to copy a single source system of a BW system; the BW system is not copied. You want to replace a productive source system of a BW system [PRD to PRD].

Phase 6: Final Activities in Target Environment

Step 6.4: Correct RFC destinations

Modify the RFC destinations in the copied source system and all connected BW systems. Change the hosts in the appropriate RFC destinations so that they refer to the correct system. See Note 524554.

Since SAP does not support the renaming of productive systems, step 6.7 "Execute Transaction BDLS if you want to rename a system" is omitted here.

Another thing that I noticed is the nore you are reffering to kind of out dated 2002. The note I mention above is 2010.

I appreciate your inputs, please let me know your thoughts.

Mike

Edited by: mike curtis on Sep 7, 2010 5:31 PM

[Former Member]

Hi,

The change in the logical system name should not be an issue as u will be creating the source systems based on the RFC destinations.

Hope this clarifies.

Regards,

Varadharajan M

[tomas_black]

Hello Mike,

please elaborate a little more your inquiry. Are you talking about the ALE logical name changing? For this, please check the following notes:

#544509 ALE: Converting the name of the "logical system"

#121163 UTI: Logical System names

If you're referring to a domain name changing (like a Windows domain name change) or a hostname change, please refer to the following notes:

#96317: Host names during R/3 upgrade, tips & tricks

#1275273: Hostname change on 7.10/7.11 java stacks

#757692: Changing the hostname for J2EE Engine 6.40/7.0 installation

#8307: Changing host name on R/3 host: What do you do?

#1070561: SMD: Best practice for planned domain name changes

and on the following SDN threads:

/message/9196590#9196590 [original link is broken]

Or, lastly, you're talking about a SID change? On this case, you must perform a system copy to change de SID, please refer to the following note:

#11692: Renaming the system ID

(Sorry for the long and generic answer)

I hope this information helps.

Best regards,

Tomas Black