The following information can be found in this note:
Which tools are available
Which preconditions need to be met (authorizations, resources)
Operating the client copy program
Data types in the copy profiles
Copy profiles delivered by SAP
Known problems in the target client
This note supplements the information which you get via the 'I' button in the transactions of the client copy program or via the online documentation in the R/3 library (BC -> Change and Transport System -> Copy and transport client). Related information can be found in Note 19574 and other notes of key CC-INFO, CC-ADMIN and CC-TOPIC. For special errors there are notes of key CC_ERROR provided. Release-specific information and errors can be found in notes of key CC_RELEASE.
5 tools are provided:
1. Local client copy (Transaction SCCL)
2. Remote client copy between 2 sytems with RFC tools (Transaction SCC9); please refer to Note 557132
3. Client transport between 2 systems with tp transports (client export with SCC8 - client import postprocessing with SCC7); please refer to Note 70547
4. Delete client (SCC5)
5. Client copy according to transport requests (SCC1)
The first three tools are for setting up a new client in a system or for copying user master data.
The tool Delete client is for complete deletion of a client from a system.
The client copy, by means of transport requests (SCC1), enables you to copy the current state of a client acc. to the object list of a transport requirest to another client within a system. It is not necessary to release the transport request or to export it to the file system.
Setting up the new client consists of:
Copying the data of the source client into the target client
Deleting non-copied table contents in the target client, to generate a consistent environment (especially tables of the delivery classes W and L and - if application data was not selected - also tables from delivery class A). Further information on consistent data environments can be found in Note 19574.
This applies to all data except for the user master data i.e. in the case of a copy with SAP_USER (or SAP_USR) only users and authorization profiles are overwritten. In the case of a copy with e.g. SAP_CUST the users are maintained. (In Release 4.0B , however, the user address data is deleted. As of Release 4.5B a problem correction is made available via Support Packages. See also Note 130540 point 11. Concerning the Releases 4.0B to 4.6D the user data of the user is copied as well - see below.)
Regenerating the runtime environment using subsequent activities (client validation exits), which adjusts among other things reports, screens, number ranges and tables to the current status of the data. (in the case of client transports the postprocessing in the target client after the import of the transport requests must always be started with Transaction SCC7, or before Release 3.1 with SCC2.)
The following preconditions must be met:
1. You must neither work in the source nor in the target client. If you cannot prevent the work in the source client interconsistencies may occur in the target client e.g. if transaction data is stored consistent in different tables but some of the tables were already copied.
A client must not be the source client for several client copies at the same time. In a client transport, the data export of the transport request must have been finished before a new client copy or client transport is carried out.
Therefore, you should use Transaction SM02 to create a Request for logging off system message for the source as well as the target client and monitor the compliance.
2. The following authorizations are necessary to be able to carry out a client-copy:
S_TABU_CLI for cross-client maintenance of tables
S_TABU_DIS for the contents maintenance of table CCCFLOW
as of Release 4.5A S_CLNT_IMP for the tool client copy
The relevant authorizations for maintaining users and user profiles are necessary for copying user master data and user profiles:
S_USER_PRO for user profile
S_USER_GRP for user master data
If you want to transport your client into another system, and use the export/import procedure for this, you then need, in addition to these cross-client authorizations, a transport authorization: S_CTMS_ADMI TTYPE 'CLCP' ACTVT '01'You also need this if you copy object lists between two clients with transaction SCC1.
In order to be able to create the log file in the file system of the operation system, the following authorization is necessary:
As of Release 4. 5, you still need the following authorization for a remote copy in the source system:
The initial user SAP* has all the necessary authorizations. If necessary, delete the user SAP* in the target client to be able to use him as initial user. However, for the export another user must be used as he cannot create transport requests due to the '*' in the name.
3. Always pay attention to the following resources when starting the 'Client copy':
The time required to copy tables varies from table to table. Prior to Release 4.0 the maximum system runtime must be greater than the time needed to copy the largest table. The corresponding system parameter 'MAX_WPRUN_TIME'.
To avoid terminations due to exceeded runtime - in particular during analyses and post-processing - start the copy in the background.
For each database, the rollback segements need to be extended to be able to copy the largest table in the system. As of Release 3.1 this restriction only applies to deleting tables or remote copies and client transports, and as of Release 4.5 only for transports. The deletion can be converted according to Note 96296 for Release 3.1 and 4.0.
Once a test run of the client copier has been completed, you can test via the protocol whether the space in the database is sufficient to copy a client (as of Release 3.1 for Oracle, Informix and Adabas). Please refer to Note 35415.
The reports of Note 118823 offer additional options.
For a local client copy, no further main memory is required in general. For a remote copy prior to Release 4.0, the paging-memory must be sufficient for one table each in the source and in the target system.
How to use the client copy:
The client copy tools are started in the target client in general. The only exception is the client export (SCC8).
Note that you are not permitted to work in either the source client or the target client during the copy. Otherwise, incosistencies, especially with number ranges, can occur. You are recommended to create relevant system messages (transaction SM02) and to monitor the compliance. Note 562628 contains further information to this matter.
As large amounts of data may be copied (in particular with the option 'With master data & transaction data') SAP recommends executing the client copy in the background at a time when the workload is lowest (e.g. at night or weekend). For more information on the copying of large clients please refer to Note 489690).
Start via the menu path 'Tools' -> 'Administration' -> 'Administration' -> 'Client admin.', and choose the function you want.
Select the copy profile which corresponds to your needs. Some profiles could also be created before Release 4.0. As of Release 4.0 only profiles which begin with SAP_ may still be used. Profiles in the customer namespace and the profile 'RESTART' may no longer be used. (As a result of a program error before Release 4.6, profile 'RESTART' was used when the offered RESTART options were switched off and then switched on again. In this case restart the transaction. The RESTART option is then again predefined).
If you have selected a profile with customizing and user data, then for the local copy, you may select a different source client for the user. Authorization profiles and activity groups then continue to come with the customizing in this case.
You can see the status of a client copy that has just been run via Transaction SCC3 (log). The client copy monitor displays the current copy status. It can be started via the 'client copy log' menu (Transaction SCC3).
Data classes in the copy profiles:
All profiles, with the exception of SAP_USR/SAP_USER contain Customizing.
Customizing data is generally in tables of the delivery classes C, G, E and S.
Client-independent Customizing between two systems
Prior to WAS 6.10, client-independent Customizing can only be transported via Export/ Import. For this, a profile must be created with the corresponding option in the customer name space until Release 3.1I. As of Release 4.0, the following profiles are delivered for customer transport: SAP_EXBC, SAP_EXPA and SAP_EXPC.
As of Release WAS 6. 10, profiles SAP_RM are delivered in addition for remote copies, the profiles corresponding to profiles SAP_EX.. . For more information see Note 445195.
Apart from some special selections, the client-independent Customizing tables (delivery classes C, G, E, and S) are copied which are not contained in the exception list for system tables. For Basis tables (development class starts with 'S') the existence of a Customizing object is checked in addition (Transaction SOBJ) to make sure that those contain customizing that may be transported and no system settings.
Client-independent customizing must only be copied to create a new system. Client-independent data and thus all clients in the target system are affected by this and can be destroyed!
Authorization profiles and roles/activity groups
These data belong to the Customizing and are always copied as well (even if e.g. a different source client was chosen for the user master data).
Copy profile SAP_USER (or prior to Release 4. 0: SAP_USR) also contains these data in addition to the user master data (activity groups as of Release 4.5 only).
This way, all copy profiles contain authorizations (exceptions are the profiles SAP_APPX and SAP_CUSX available as of Release WAS 6.30).
User master data
User master data is only deleted in the target system if a profile is copied with user master data. Prior to Release 4.5B, however, the user addresses are lost when copying customizing without application data. For transports, this restriction still applies.
Authorization profiles belong to the Customizing and are always copied as well. It would be problematic to copy users without user profiles. For this reason, copy profile SAP_USR or SAP_USER additionally contains authorization profiles.
For a local copy, a separate source client can be specified for the user data.
In Releases 4.0B to 4.6D the users are copied with each copy including user data. If this is not wanted you must store the user prior to the
copy with profile SAP_USER to another client and retransfer it after the copy.
Application data (master & transaction data)
Application data is dependent upon Customizing data. Therefore, the data can only exist consistently together with it. Application data is always deleted in target clients, with the exception of a copy with SAP_USR or SAP_USER.
Application data is generally in tables of delivery class A.
If you want to mix the application data with the Customizing data of another client for test purposes, import the corresponding Customizing transports in the target client. You can create a transport of copies e.g. using the Transport Organizer Tools with "Combine object lists".
Via the client copy tools, copying the customizing without resetting the application data is no longer possible in general. When customizing is copied, the application data are either copied as well or deleted in the target client.
In Releases 4.0B to 4. 6D the users are always copied for each copy including application data. Detailed information can be found in the user master data.
System variants and user-defined variants
If variants are to be copied in a client copy, you need to specify a copy profile which contains variants. Since Release 3.0F, SAP has delivered profile SAP_ALL which contains variants. As of Release 3.1, profiles SAP_CUSV and SAP_UCSV have been provided as well.
Profiles containing variants select all variants.
The verification popup which is displayed before the start of the copy process shows whether a copy profile contains variants.
As of the Support Packages SAPKH40B74 ; SAPKH45B51 ; SAPKB46B40 ; SAPKB46C31 ; SAPKB46D20profiles without variants select variants that start with "SAP" (but not with "SAP&" -> system variants - Variants starting with "SAP" are common variants. Many of these variants were delivered as sample variants, however, which are still used).
As of WAS 6. 10, profiles without variants do not select variants. If you need variants, use a profile that contains variants (also from client 000). If required, you can copy missing variants using Report Z_VARI_COPY from Note 41475.
Copy profile SAP_USER (or prior to Release 4. 0: SAP_USR) does not contain variants.
In Releases 3.1 and 4. 0, all delivered profiles contain variants.
Releases 4.5 and 4.6:
With periodic scheduling, no variants are copied.
As of Release 4.5:
SAP_CUST and SAP_UCUS do not contain any more user-defined variants.
Activity groups are copied togehter with the Customizing.
As of Release 4. 5 they are also copied with the SAP_USER profile. In a former release, they must be transported, in this case, with the help of the report 'RHMOVE30'. Also refer to Notes 77607 and 87787 for this.
Copy profiles delivered by SAP:
As of Release 4.0, SAP only supports these profiles delivered by SAP.
SAP_ALL (as of Release 3.0F)
All client-dependent data
SAP_USER (or prior to Release 4.0: SAP_USR)
User master data and authorization profiles
Customizing - application data is deleted
Customizing and user data - application data is deleted
Customizing data and application data ( because of changed user address assignments as of Release 4.0 to 4.6D, including the user data, which corresponds the profile SAP_ALL without user defined variant).
As of WAS 6.10, the profile corresponds to SAP_ALL without the user master data.
Corresponds to SAP_ALL and is omitted after Release 4.6D.
The following profiles will be delivered additionally as of Release 4.0 (SCC8 only) in order to be able to copy client-independent Customizing data between two systems:
Customizing including client-independent customizing and user data
All client-dependent data and client-independent Customizing (as of Release 4.5 without change documents)
Customizing including client-independent Customizing
As of Release WAS 6.10, the following profiles are delivered for the remote copy (Transaction SCC9) which correspond to the profiles SAP_EXBC, SAP_EXPA, and SAP_EXPC:
SAP_RMBC ; SAP_RMPA ; SAP_RMPC
Please refer to Note 445195.
As of Release 4.0, the following profiles are additionally delivered, which contain the user defined variants (see above):
corresponds to SAP_CUST with a variant flag
corresponds to SAP_UCUS with a variant flag
As of Release 4.5B there is a specific profile to restore a client
(refer to Notes 31496 and 180949):
Specific copy profile (for remote copies and transports) which contains change documents, system tables (delivery class 'W' - e.g. the Central User Administration (CUA)), and local tables (delivery class 'L') in addition to SAP_ALL. The profile may only be used to restore a client which was accidentally deleted. The number of the source and target client and the system settings (for example, printer, etc.) should correspond.
Known restrictions in the target client
Addresses are partially not copied or deleted.
Up to Release 3.1I: Please see Note 25181.
Release 4.0B: Please see Note 130540.
As of Release 4.5B: Please see Note 350101.
Change documents can be incorrect or be deleted
Please see Note 180949.
Logs are sometimes not copied
Logs of the applications using the 'Application Log' are not copied. (The 'Application Log' is a generic Basis tool that supports log storage and analysis.)
The corresponding tables are deleted in the target client: BALHDR BALHDRP BALM BALMP BAL_INDX BALCand, in addition, as from release 4.6C BAL_HDR BALDAT BAL_AMODAL BAL_INDX
The change history of the user administration is not copied
Archived data cannot be accessed anymore
If the number of the target client does not correspond to the number of source client, archived data cannot be accessed anymore even, if they are available in the file system.
ALE distribution scenarios are no longer correct
The ALE landscape may have to be adjusted. If the logical system changes, open objects in the workflow cannot be used any longer, since they still use the old logical system names.