Client copy is used to replace data of client with other client.
Local Client Copy
Copy of client within the same system.
Both local and remote client copy must be initiated from the target clientusing the following steps:
- To create an entry for the target client in the client maintenance table, choose transaction SCC4.
- Log on to the target client as SAP* with the initial password pass. Perform the client copy using transaction SCCL. Select the data to be copied using a profile.
Note: The user name SAP* with the password pass is only active if the profile parameter login/no_automatic_user_sapstar does not have the value 1.
3. Assign the source client for Customizing data, application data, and user master records.
4. Begin the client copy. Because copying is a lengthy process, use background processing.
Remote Client Copy
A remote client copy allows you to copy data between clients in different SAP systems.
It proceeds in the same way as a local copy, but sends the data through a remote function call (RFC) connection to the target client.
Remote client copy also does not create a file at the operating system level, so there is no hard copy of the client to be copied.
Cross-client customizing objects can be copied during a remote client copy, depending on the client copy profile.
During copy, an automatic repository consistency check is performed. If inconsistencies are detected, the client copy is terminated and an error message is displayed. You can also perform the consistency check yourself with the RFC System Comparison push-button.
The client copy function can be used with multiple parallel processes, which speeds up the copying process.
You must specify the maximum number of processes you want to use in the client copy program, use transaction SCCL for a local copy or transaction SCC9 for a remote copy
Client Export & Import
To perform a client export, follow these steps:
- Log on to the source client. Choose transaction SCC8 (client export). Select the data to be copied using a profile.
- Indicate the target system to which the client will be copied. The target system must be defined in TMS as part of the transport domain.
- Begin the client export. Because copying is a lengthy process, use scheduled background processing.
Client Import is done by importing transport in STMS_IMPORT.
SCC7 is used for post processing steps.
Client copy profiles
Monitoring client copy
- To ensure data consistency in the target client, users, except for SAP* and DDIC, cannot log on to the target client during copying. Similarly, no one should work in the source client during the client copy.
- Database size estimation should be done properly before start of client copy. We can use program to analyse the storage.
- The maximum online runtime (parameter rdisp/max_wprun_time) must be longer than the time needed to copy the largest table.
- SCC3 tcode is used to monitor the logs, all log files are physically stored in the transport log directory at operating system level.
- When performing client copy error analysis, check not only the copy log, but also the system log, which tells you whether database problems are responsible for the client copy error.
- When a client copy run terminates abnormally, the restart option is proposed by default, which continues the run from the point at which it was terminated.
- If a termination in an exit program (the termination is explained in an ABAP runtime error) occurs, run the log display RSCCPROT to determine the name of the last exit program that caused the termination.
Client Comparison and Adjustment
SCU0tcode is used to do comparison between two clients and this transaction lists:
- Table entries
Through the displayed comparison we can do adjustment of objects using some of the tables and views in SM30.
To delete a client from within an SAP system:
- Log on to the client to be deleted.
- Use transaction SCC5.
- Start the deletion of the client, preferably using background processing.