FAQ: Client copy

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 application data 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 source client 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 with the 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 the target client. Why is this?

Other terms

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

Solution

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

              The authorizations for executing a client copy are listed in Note 24853.

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

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

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

              This is not possible. Note 19574 contains information about the relationship between client-specific Customizing, cross-client Customizing and the corresponding application data.
              A further problem, for which there is no solution, is the existence of mixed number ranges. For instance, both Customizing and application addresses 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. The main or Basis release must always be identical. Support Packages and ADD-ONS should also have the same status in both systems. Only then can the consistency of the data be guaranteed.
              For instance, if an add-on is only installed in the source system, the remote copy will terminate with a reference to differences in the dictionary or missing tables in the analysis phase, and will not make the copy. The remote copy terminates if not all data can be copied, in other 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 include individual tables and, from Release WAS 6.10, also development packages (formerly development classes) in the source system in an exception list, to avoid the termination. See Note 557132 for further information.
              The export does not experience this problem with the transport because the target system is not checked during the export. On the other hand, differences in the dictionary or missing tables are subsequently reported as errors during the import but this does not result in any termination. All of the data that can be imported is imported. In this respect, different ADD-ONs would not pose a problem for the client transport. 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 between different 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 contain additional recommendations in special cases:

• First delete the target client -> 70643

• Execute a parallel copy -> 541311 or 212727

• System copy instead of a client copy for very large clients -> note from the corresponding area BC-INS

• 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 is available again for users relatively soon after the export of the data, while with the remote copy, you are only allowed to work in the source client when the copy has been completed.
              In addition, during the client transport you have a 'frozen' dataset of the client that can no longer be changed, and which you can access or restart repeatedly during the import.
              Prior to Release WAS 6. 10, a client transport is more error-tolerant where there are differences in the table definitions (DDIC). Before WAS 6.10, only individual tables can be ignored in the source system if you are included in the exception list in the source system (note 70290). 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 faster than a client transport. Usually the entire copying time for a remote copy 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 a WAN, you must check very critically whether the link does not slow down the copy too much.
              You will find further information on client transports and remote copies 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 as the location of this data. In addition, the syslog in both the target system 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?

              Note 560552 contains this information.

12. How do I create a new client? Which copy profile and which source client 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 is usually demanded on the same development level.
              A remote copy terminates if not all data could be copied, so for instance if a field is missing in the target system, a field is too small or an entire table is missing. See Note 557132 for further information.

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

              The functional scope of the tools of the client copy is explained in Note 24853. A client copy only copies Customizing and where necessary application data. A client copy only copies Customizing and possibly application data. Repository (for example, programs and table definitions) and other cross-client data is not copied and must reach the system via the corresponding transport routes.

15. What is client 001 used for?

              Client 001 is created as a practice client or a reference client during the initial installation of a system. Apart from this, it is no different to other clients. Therefore, it is dealt with in the same way 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 is corrected with Solution Manager 4.0.
              Another exception is NetWeaver as of Version 2004S. With a new installation, a client 001 is created to provide storage for the Java users. If necessary, you can copy the users from client 001 with a client copy. However, we still urgently recommend that you use client 000 as a copy template for Customizing. This applies especially to all products that run on NetWeaver (such as ECC). Some incorrect installation guides are unfortunately still available. Obtain the latest version, if necessary.
              After the copy, you may have to log onto the J2EE Engine and set the ume.r3.connection.master.client parameter on the new PI/XI client. For more information, see Note 937323.

16. Can I delete client 001?

              Yes. (Except for the Solution Manager before Version 4.0. If necessary, you must first copy the Java users. Refer to the previous point in this case.)

17. Can I use client 001 in production?

              To set up a new client, a Customizing copy from client 000 is recommended. On the one hand, a customer client should be set up without any other application data, on the other hand, client 001 becomes noticeably more obsolete with every Support Package and with every language installation. See Note 550894 for further information.
              However, if you have already used client 001 for production, there is no reason not to retain this client.

18. Yes. There are certain restrictions, however. See Note 31557 for further 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.

h_tp://www.saptechies.com/faq-client-copy/