sap client copy

16.02.2012 of 6

SAP Note 552711 - FAQ: Client copy

Note Language: English Version: 13 Validity: Valid Since 21.11.2006

Summary

Symptom

1. Which authorizations are required to execute a client copy?

2. Which data is actually copied with a client copy?

3. Can I only copy the Customizing and therefore receive the applicationdata in the target client?

4. Can I copy between systems with different R/3 releases/add-ons?

5. Can I create client copies in a heterogeneous system landscape?

6. How can I improve the performance of a client copy?

7. Which is better or faster, a client transport or a remote copy?

8. How much space does the new client require?

9. Can I exclude certain tables from a client copy?

10. Where do I find the cause of an error or a copy termination?

11. How does a client copy behave during a termination or database error?When does the system offer a restart?

12. How do I create a new client? Which copy profile and which sourceclient should I use?

13. Why does a remote copy terminate, referring to DDIC differences?

14. Why there are still differences between the systems, for instance withthe programs, even after I copy with the copy profile SAP_ALL?

15. What is client 001 used for?

16. Can I delete client 001?

17. Can I use client 001 in production?

18. Can I use more than one client for production in a system?

19. After a client copy, there are problems with number ranges in thetarget client. Why is this?

Other terms

FAQ, Q+A, CC-INFO, CC_ADMIN, SCCL, SCC5, SCC7, SCC8, SCC9

Reason and Prerequisites

16.02.2012 of 6


Solution

1. Which authorizations are required to execute a client copy?

The authorizations for executing a client copy are listed in Note24853.

2. Which data is actually copied with a client copy?

The data is selected by means of copy profiles. Notes 24853 and 19574contain information about copy profiles.

3. Can I only copy the Customizing and therefore receive the applicationdata in the target client?

This is not possible. Note 19574 contains information about therelationship between client-specific Customizing, cross-clientCustomizing and the corresponding application data.

A further problem, for which there is no solution, is the existence ofmixed number ranges. For instance, both Customizing and applicationaddresses appear in the central address management.

4. Can I copy between systems with different R/3 releases/add-ons?

Notes 19574 and 24853 provide basic information on this subject. Themain or Basis release must always be identical. Support Packages andADD-ONS should also have the same status in both systems. Only thencan the consistency of the data be guaranteed.

For instance, if an add-on is only installed in the source system, theremote copy will terminate with a reference to differences in thedictionary or missing tables in the analysis phase, and will not makethe copy. The remote copy terminates if not all data can be copied, inother words if, for instance, a field is missing in the target system,a field is too small or a complete table is missing. You can includeindividual tables and, from Release WAS 6.10, also developmentpackages (formerly development classes) in the source system in anexception list, to avoid the termination. See Note 557132 for furtherinformation.

The export does not experience this problem with the transport becausethe target system is not checked during the export. On the other hand,differences in the dictionary or missing tables are subsequentlyreported as errors during the import but this does not result in anytermination. All of the data that can be imported is imported. In thisrespect, different ADD-ONs would not pose a problem for the clienttransport. To what extent is the data then consistent or useable?

5. Can I create client copies in a heterogeneous system landscape?

Remote copies or client transports can also be carried out betweendifferent database and operating systems.

6. How can I improve the performance of a client copy?

In general, refer to Notes 489690 or 67205. The following notes also

16.02.2012 of 6


contain additional recommendations in special cases:

o First delete the target client -> 70643

o Execute a parallel copy -> 541311 or 212727

o System copy instead of a client copy for very large clients -> notefrom the corresponding area BC-INS

o Copy texts before 4.6C -> Note 180541

7. Which is better or faster, a client transport or a remote copy?

Prior to Release 4.6, there are no differences concerning the runtime.The advantage of a client transport is that the source client isavailable again for users relatively soon after the export of thedata, while with the remote copy, you are only allowed to work in thesource client when the copy has been completed.

In addition, during the client transport you have a 'frozen' datasetof the client that can no longer be changed, and which you can accessor restart repeatedly during the import.

Prior to Release WAS 6.10, a client transport is more error-tolerantwhere there are differences in the table definitions (DDIC). BeforeWAS 6.10, only individual tables can be ignored in the source systemif you are included in the exception list in the source system (note70290). As of Release WAS 6.10, complete development packages(formerly development classes) can be included in an exception list.There is also a special option that prevents a termination altogether.

With parallel processes from Release 4.6, the remote copy is fasterthan a client transport. Usually the entire copying time for a remotecopy is in fact well below the pure export time of a client transport.However, a LAN link is required for this. With a remote copy via aWAN, you must check very critically whether the link does not slowdown the copy too much.

You will find further information on client transports and remotecopies in Notes 70547 or 557132.

8. How much space does the new client require?

Note 118823 provides information on the memory space for a client.

9. Can I exclude certain tables from a client copy?

The required procedure is described in Note 70290.

10. Where do I find the cause of an error or a copy termination?

Note 22514 describes that data required for error analysis as well asthe location of this data. In addition, the syslog in both the targetsystem and source system, which you can call using transaction SM21,also provides valuable information.

11. How does a client copy behave during a termination or database error?When does the system offer a restart?

16.02.2012 of 6


Note 560552 contains this information.

12. How do I create a new client? Which copy profile and which sourceclient should I use?

Note 550894 contains this information.

13. Why does a remote copy terminate, referring to DDIC differences?

The DDIC (data dictionary) belongs to the repository of the system(programs, system variables etc.). For a client copy, a repository isusually demanded on the same development level.

A remote copy terminates if not all data could be copied, so forinstance if a field is missing in the target system, a field is toosmall or an entire table is missing. See Note 557132 for furtherinformation.

14. Why there are still differences between the systems, for instance withthe programs, even after I copy with the copy profile SAP_ALL?

The functional scope of the tools of the client copy is explained inNote 24853. A client copy only copies Customizing and where necessaryapplication data. A client copy only copies Customizing and possiblyapplication data. Repository (for example, programs and tabledefinitions) and other cross-client data is not copied and must reachthe system via the corresponding transport routes.

15. What is client 001 used for?

Client 001 is created as a practice client or a reference clientduring the initial installation of a system. Apart from this, it is nodifferent to other clients. Therefore, it is dealt with in the sameway as every other customer client.

The Solution Manager up to Version 3.2 is an exception. In this case,client 000 does not have Customizing for setting up the service desk.You then have to use client 001 as a copy template. The error iscorrected with Solution Manager 4.0.

Another exception is NetWeaver as of Version 2004S. With a newinstallation, a client 001 is created to provide storage for the Javausers. If necessary, you can copy the users from client 001 with aclient copy. However, we still urgently recommend that you use client000 as a copy template for Customizing. This applies especially to allproducts that run on NetWeaver (such as ECC). Some incorrectinstallation guides are unfortunately still available. Obtain thelatest version, if necessary.

After the copy, you may have to log onto the J2EE Engine and set theume.r3.connection.master.client parameter on the new PI/XI client. Formore information, see Note 937323.

16. Can I delete client 001?

Yes. (Except for the Solution Manager before Version 4.0. Ifnecessary, you must first copy the Java users. Refer to the previous

16.02.2012 of 6


point in this case.)

17. Can I use client 001 in production?

To set up a new client, a Customizing copy from client 000 isrecommended. On the one hand, a customer client should be set upwithout any other application data, on the other hand, client 001becomes noticeably more obsolete with every Support Package and withevery language installation. See Note 550894 for further information.

However, if you have already used client 001 for production, there isno reason not to retain this client.

18. Yes. There are certain restrictions, however. See Note 31557 forfurther information.

19. Work was carried out in the source or target client during the copy.The client is inconsistent and the copy must be repeated.

Header Data

Release Status: Released for CustomerReleased on: 21.11.2006 10:16:21Master Language: GermanPriority: Recommendations/additional infoCategory: FAQPrimary Component: BC-CTS-CCO Client Copy

The Note is release-independent

Related Notes

Number Short Text

1398718 CC:INFO-Client copy between different EHP'S

1166677 FINBASIS/SEM-BW customizing transports - errors & help

937323 Changing Production Client in an ABAP+Java System

921593 (Outdated) Inst. SAP NetWeaver 7.0 (2004s) SR1 - UNIX

757093 FAQ: Analyzing CRM Client Copy problems

582955 Configuration of TMS transport workflow in client 001

560552 CC-INFO: Restart and "Copy error"

557132 CC-TOPIC: Remote client copy

550894 CC-ADMIN: Setting up a new client

541311 CC-INFO: Parallel processes FAQ

16.02.2012 of 6


Number Short Text

489690 CC INFO: Copying large production clients

337623 Customizing after installation or upgrade

118823 CC-ADMIN: Size of a client

70290 CC-INFO: Excluding tables with 'RSCCEXPT'

31557 The Multiple-Client concept of mySAP.com Solutions - Short O

24853 CC-INFO: Client copy, functionality

22514 CC-INFO: Error analysis for client copy

19574 CC-ADMIN: Controlling data selection during client copy

sap client copy

Documents