System copy questions

[Former Member]

Let's assume we have two CRM systems CRD(dev&qas system) & CRP(prd system), and corresponding R/3 systems R3D & R3P, As I read some documents concenring system copy within CRM, I still have doubt on the transport strategy.

on CRD, After making the manual customizing and finish test replication of customizing/master data/transaction data from R3D, we would like to transport the customzing to CRP, and corresponding customizing from R3D to R3P. But I am not sure:

1. Only manual customizing in CRD will be transported to CRP? how about the customizing object download from R3D(e.g. condition customizing), are they also transported to CRP or need replication again from R3P?

2. the organizational model transported or need replication again?

3. internet user transported or need replciation again?

4. RFC destination transported or need cusotomizing again in CRP?

5. If I use the same logical system name in CRD & CRP, is there anything I should pay attention to?

6. number range transported or need cusotomizing again in CRP?

7. how about the java applications, like ISA web shop xcm settings?

Patrick

[Former Member · Accepted solution]

Hi Patrick,

Your CRM PRD system will receive customising from transports and from the download of customising from your R/3 system. On some occassions you may need to open the system to do config start in your PRD system. This is not recommended but ususally occurs when people make mistakes and has to be done.

3 - For Internet Users you could create a program that creates all the Internet users and generates initial passwords from a spreadsheet. This is normally part of data conversions.

5 - Hopefully you created a CRM PRD system from scratch so it should have been set up with a different logical name. SAP does not recommend changing the logical name when doing a system copy in a production environment but does provide tools to help out when copying a production system to replace your test system for example. If you have already set up your CRM PRD system with the same logical name as your dev system then you may have to live with your mistake.

Cheers

Andrew

[Former Member]

Hi Patrick,

your list is spot on.

Question I have is have you downloaded data from R/3 PRD into CRM PRD (i.e. customers or products)? Makes it easier if you haven't.

You can have different logical system names for the different clients in dev as well if you want. Usuallly this is the case but up to you what you do.

Cheers

Andrew

[Former Member]

Hi Patrick,

Is your PRD system live? If so then best not to touch it, change the dev system instead.

If you have never done this before best always to test first. Alot of the data in the CRM has the logical system connected to it so where changing it you have to change this data as well. Transaction BDLS is used for this purpose. For example business partners and products have it stored against it. Have a go at it for a trial, gives you a good skill anyway.

Cheers

Andrew

[Former Member]

No, not live, I am imagining what will happen when live.

So I think the way of transport may like the follows:

1. customize everything in CRD & R3D.

2. transport requrest CRD->CRP, R3D->R3P(if I omit the QA system)

3. change the logical system name respectively in CRP & R3P, as well as the RFC destination...

4. run BDLS both in CRP & R3P to check and convert anything logical system related issues

5. replicate datas from R3P to CRP

6.....

Am I right?

but in another client for CRD, I think it's better not change the logical system, right?

Patrick

[Former Member]

Hi Patrick,

I just want to add to not take any of the comments I made personally. Good consultants are the ones that learn by our mistakes and are willing to learn, which you are showing. We are all human and make mistakes especially when we don't have the right information. I have made many mistakes over my years in consulting.

Cheers

Andrew

[Former Member]

Thank you Andrew, I just need help here in sdn and I will make my decision after collecting all the information:-)

OK, I think I will change the logical system in PRD, but if I would like to copy another client in DEV system for test purpose, shall I change the logical system in another client to test for the whole logic?

Thanks!

Patrick

[Former Member]

Hi Patrick,

1 - You must do an initial download of the R/3 adapter objects such as customising and business data in each system.

2 - Manually set it up in each system. If it is large then there is a transport program RHMOVE30.

3 - Users must be created in each system.

4 - RFC destination created in each system and all initial set up done (table CRMRFCPAR for example in R/3 prd)

5 - Create a new logical system name, don't use the same as dev.

6 - Transport the number range (this should have been done when creating it). If this hasn't been done already then best to do it start in production due to the current number will not be at the start in dev

7 - should be on different server so would require new xcm settings to point to the different production server

Cheers

Andrew

[Former Member]

Hi Andrew

As normal way, PRD system should not allow manual customizing adjustment, it should be transported from other already customized systems. If so many manual works should be done in PRD, does it disobey the normal rule?

3. is it possible to mass create internet user? since we have 500+ business parnters to logon the web shop.

5. As I read the document <mySAP CRM system landscape copy>(version 2002), it strongly recommends not to change the logical system in different systems:-( , and I fear some logical system-related customizing or anything else related will cause problem after changing the logical system?

Thanks.

Patrick