System Landscape

[Former Member]

Dear All,

We are running ECC 6.0 on Solaris 10 with Oracle Database 10g.

Ours is a two-system landscape - DEV (development server) and PRD (production server).

In DEV we have three clients:

300 (Development Client)

400 (Customization Client)

700 (Test Client)

And in PRD, we have 300 client (Production Client).

Following are the problems with the current system landscape:

1) 300 client exists in both DEV and PRD and creating confusion. We want to change it to a unique number.

2) 300 client in DEV has application data. We want to remove the application data from it.

3) 400 client in DEV also has application data. We want to remove the application data from it.

After analysing, we came to the following solutions:

1) We make a fresh client lets say, 200 in DEV which will be a remote client copy from PRD (300) using SAP_CUST profile and then, we will drop client 300 from DEV. (We hope if we delete client 300 from DEV, all the ABAP development and repository objects will not get deleted). We release this new 200 client to the Development Team.

2) We drop client 400 in DEV and recreate it by performing a remote client copy from PRD (300) using SAP_CUST profile. We release this new 400 client in DEV to the Customization Team.

Could we request you all to throw some light on our proposed solutions?

Regards.

Wolfgang.

[Former Member]

Dear Rishi,

Thanks for your brilliant suggestion. We think this would be the safest bet.

1) Creating a new client on the DEV server, lets say, client 200. This would be the remote client copy from PRD (client 300) using SAP_CUST (only customization and without any application data).

2) Transporting all the requests (released and not released) from client 300 on DEV server to the new client 200 using transaction SCC1.

3) Performing client comparison between clients 300 and 200.

4) Finally, deleting client 300 from the DEV server.

However, we still feel that simply deleting client 300 will neither result in the loss of any development objects since they are stored in the Repository at database level nor result in the loss of different versions of these objects.

Although Rishi's suggestion is the safest one, lets not close this thread and be open for more inputs / suggestions just for the sake of knowledge sharing and better understanding of the SAP System Landscape.

Regards.

Wolfgang.

[Former Member]

Thanks Rishi for your inputs.

However, we do not think that deleting client 300 from DEV will lead to any crisis because of the following reasons:

a) All the ABAP development reside in Repository, which is not client-specific. Therefore, even if we delete client 300 from the DEV, the repository objects and development objects still reside in the database. Therefore, we can make a fresh client and do the further modifications as well as new developments to the existing repository through it. We guess, version information of earlier developments will also not be affected by deleting the original client (in our case, client 300) since the same also get stored in the repository (Database).

b) Yes, you are right that our DEV server has more development than the PRD server. We treat all the development which transported to the PRD server as final development. The rest of the development is treated as R&D performed by ABAPers. Had these extra development of any importance, they should have transported to the PRD server as well. Therefore, we can safely remove those developments which had never make it to the PRD server after ensuring that these extra developments are never required in the future.

We would appreciate your views / suggestions on this.

Regards.

Wolfgang.

[Former Member]

To be on a safer side Please if you want you can first go with the client copy from production and then copy all the new coustimising request through local client copy on to 200 client(New client in Dev) using transport through Scc1.You need not move all the R&D transport to production.

After that you can do client comparission and then delete the client 300.

Thanks

Rishi Abrol

Edited by: RishiAbrol on May 22, 2009 10:04 AM

[Former Member]

As per me i shall not suggest you to delete the client 300 as 300 would have some development thet shall not bee in production.This is because you have to do all testis in developmnet and then move to production .if you had quality server then the testing could have beed done in Quality.

Thanks

Rishi Abrol