Client Copy and Client Transport Tools

SAP offers client copy and client transport tools.

You can use the client copy to create, for example, the following clients:

• New clients from the SAP reference client 000, during initial implementation of an SAP system
• Training clients
• Demonstration clients
• Test clients
• Production clients

The target client can be copied from a source client that is located either in the same or in another system.

(Copy) profiles define the tables to be copied through the delivery class of the table. Special data such as user master data can be selected by specifying criteria.

With the client copy tools, you can copy selected parts of an existing client into another client, for example, the user master data with the copy profile SAP_USER.

To construct a client, use the (copy) profile SAP_CUST, which copies client-specific customizing only, to copy client 000, because the consistency of the application data in the SAP delivery client 000 can't be guaranteed.

The client copy tools can copy the following components of the source client into the target client:

• User master data: user master data is only deleted in the target system if a (client copy) profile with user master data is copied. Authorization profiles and roles belong to customizing and are, therefore, always copied together with the customizing. Copying users without authorization profiles is problematic. The (client copy) profile SAP_USER therefore also contains authorization profiles and roles.
• Customizing: many client copy profiles contain customizing. Customizing data is generally stored in tables with delivery classes C,G,E, and S.
• Cross-client customizing: when performing a remote client copy or a client transport, also cross-client customizing can be copied. Remote Client Copy is copying the contents of a hole client or parts of it (according to the client copy profile used) from one client to another client in a different SAP system via RFC. Client Transport is creating a transport request out of the contents of a hole client or parts of it (according to the client copy profile used) and then importing this transport request into a client either of the same SAP system or of a different SAP system.
  Caution

  Inconsistencies can arise in the target system after copying cross-client tables. Copying cross-client customizing can only be used to create a new SAP system because existing clients can be corrupted by changes in their context.

• Master/transaction (application) data: select this option, for example, if you want to set up a test client from the production client.

Copying clients requires a large amount of system resources. To avoid premature termination due to bottlenecks, ensure that enough resources are available by:

• Database storage space: Perform a test run before copying a client. The log contains the total copied and deleted data (in MB). Storage requirements can only be estimated, because space already allocated, but not yet used, is not taken into account.
• Runtime: Depending on the volume of application data, copying a client can take several hours or even days. Active users or background processes in clients other than the source or target clients can extend this time even more. For example, locks in a third client in the same system can delay the processing of objects. In principle, work in the system is technically possible during the client copy. However, it is strongly recommended that you do not do this (or only in exceptional cases), since this can lead to inconsistencies. If you use parallel processes for client copy, dialog processes are used even if the client copy job is scheduled in the background.
  Hint

  The standard timeout value is usually sufficient. If the database is used by additional processes, it can be advisable to increase the profile parameter.
• System load: Copying or transporting a client can take a long time because large amounts of data are moved. One or more dialog processes are occupied for this time. The database interface is heavily used.
• Protecting clients against user log ons: You must ensure that no users log on to the system during the copy. For technical reasons, the source client (optional) and target client (mandatory) are locked.
  Note

  The source client lock can be removed in the expert settings. For the new client copy tools available as of SAP_BASIS 754, it can be removed on the selection screen. SAP recommends that you unlock the source client in exceptional situations only (when constructing sandbox or test systems).

  The logon lock also applies to HTTP and not just to SAP GUI log ons. The only way to access a locked client is to use RFC. Users who have been logged on to the target client before the start of the copy cannot be locked automatically, so you must ensure that they leave the system. The source and target clients should both be additionally protected by a system message (SM02). Monitor compliance in both clients (for example, in transaction SM04). You should not work in the source client either during the copy.

• Clean Up: If you want to use SAP Query in the new client, you must do some post processing.
• Constraints: You can't access archived data in the target client if the target client number is not the same as the source client number.
• Change documents (tables CDHDR, PCDHDR, CDPOS, and PCDPOS): Change documents from user administration and logs from the generic log repository (application log tables BAL*) are not copied.
• Effect on Number Ranges: If customizing and application data is copied, the number ranges are copied with the data because they are required by the application data. If only customizing data is copied, the number ranges are reset because the application data that references them is deleted and then reconstructed.

Changes with SAP_BASIS 754

Note

This section is valid only for SAP systems based on SAP_BASIS 754 or higher.

Starting with SAP_BASIS 754, the client copy procedures were changed and enhanced. See SAP Note 2962811 – New Client Copy Tool: General Information for details.

The new Client Copy Tool comes with new transaction codes and APIs (RFC). Furthermore the tool now offers task lists for execution in STC01.

New authorization objects S_CLNT_CPY (Client Copy Process Execution, activity 60 for client copy, activity 03 for client comparison) and S_CLNT_EXI (Client Copy Exit Execution in RFC for exits in remote systems) and are available.

The figure "Client Copy Tools – Overview" shows both tools that have been re-factored as successors of old transactions and new tools. These tools can be accessed either using transaction codes or with the help of task lists (transaction STC01).

The Client Copy Tool contains the following improvements:

• Improved performance: Up to 10 times faster than before by using native SAP HANA DB capabilities. The Remote Client Copy tool is up to 5 times faster than before.
• Improved security and reduced manual effort: User SAP* is no longer needed to perform client copies so that system does not need to be restarted. Task lists are available for automation.
• Improved stability: The Client Copy application exits now run in isolated environments. Failed exits and tables are stored in the log.
• Improved log: The Client Copy log has been transformed from a file-based to a table-based UI with additional information and better persistence. The tool offers multiple tabs for different sections of the log, such as Header Data, Processed Tables, Application Exit Messages, and Runtime Measurements.

Note

Client copies need no longer be executed from the target client. Instead, SAP recommends that you run the Client Copy tool from a third client that is not affected by the tool. For example, when copying from client 100 to 200, you could run the tool in client 000.

The client copy always locks the target client. By default, the source client is also locked. You may choose not to lock the source client at the risk of concurrent write access to the source client resulting in inconsistent copies. Note that a client lock now not only prevents new log ons using SAP GUI, but also HTTP access.

You can search for task lists using transaction STC01. You have two options:

• Enter a task list and choose Display Task List.
• Open the drop-down list and select Task List, Description, or Task List Group.

Once you have completed one of these actions, choose Search.

Note

To avoid a long process duration when copying large amounts of data, execute the client copy as task list.

Before copying clients or tables from one system to another, you can determine their size and how much space is required for them in the memory. To do this, use transaction SCC_CLIENT_SIZE.

For this, proceed as follows:

1. Call transaction SCC_CLIENT_SIZE.
2. Enter a client and the number of processes that are to run in parallel.
3. To select a single table, enter a client-specific table or use the search function.
4. Execute the transaction.

Transport requests for customizing are usually created in the development system. They are then released in the development system and imported into the quality assurance system. It can be a good idea to additionally perform some pre-testing in a separate client of the development system. This should be done before releasing the transport request.

Before releasing a customizing transport request, perform a unit test to:

• Test the functionality of the transport request.
• Verify that the contents of the transport request is complete.

Maintaining a separate client for testing allows both true unit testing and the maintenance of test data without the risk of creating customizing-dependent data.

Transaction SCC1 copies changes from one client to another based on either:

• A task
• A transport request
• A transport request and its tasks

To copy the contents of a transport request from one client to another client, use transaction SCC1 from within the target client. Enter both the source client and the transport request of which the objects should be copied.

With FP01 for SAP S/4HANA 2020 (that is SAP_BASIS 755 SP01), SAP ships transaction SCC1N as successor for transaction SCC1. With the help of this new transaction, you can copy customizing objects recorded in transport requests to several target clients. A transport request in this context can also be a local transport request or an imported transport request from another system. In contrast to transaction SCC1, SCC1N can be executed in any client. In addition, a large number of new parameters are available.

If you want to copy transport requests with transaction SCC1N that have not been released, proceed as follows:

• In the Export / Import Time of the Transport Request area, select the Local Import/Update Date radio button.
• If it is a mandatory field (this depends on the release / SP level), enter a date that is far in the past in the Export/Import Date field.

For more information, see the blog New Tool to Copy Configuration Data to Clients (SCC1N) (available at https://blogs.sap.com/2022/02/15/new-transport-based-client-copy-scc1n/)

A local client copy copies data between clients within the same SAP system.

Transaction SCCL

When using transaction SCCL and / or transaction SCC8 (local and remote client copy using the "classical" tools), the client copy must be initiated from the target client using the following steps:

1. Create an entry for the target client in the client maintenance table. For this, choose transaction SCC4.
2. Because no user exists in the new target client right now, no SAP* user exists. In this case, you can log on to the target client as SAP* with the hard coded 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 is set to the value 0.

3. Assign the source client(s) for customizing data, application data, and user master records.
4. Start the client copy. Because copying takes a long time, use background processing.

Caution

To ensure data consistency, you can't work in the target client during a client copy. SAP recommends that you don't work in the source client during a client copy.

Note

SAP delivers the software with standard client 000. You can't work in client 000, but you can use client 001 as your productive client, if it exists. Client 001 is a copy of client 000. However, if you don't want to use client 001, SAP recommends that you begin the SAP system implementation by creating a new client as a copy of client 000. Don’t forget to delete client 001 in this case.

You can improve the performance of the client copy, for example, by excluding tables or packages, with Edit → Expert Settings. You can exclude tables from the client copy, for example if they are not relevant for the target client, in the Tables tab. For further information about excluding tables from the client copy, choose the Documentation button in the application toolbar of the expert settings. For further information about expert settings in the client copy, see SAP Note 446485 – CC-ADMIN: Special copying options.

Transaction SCCLN (as of SAP_BASIS 754)

Starting with SAP_BASIS 754, the local client copy procedure was changed and enhanced. To perform a local client copy with transaction SCCLN, proceed as follows:

1. Call transaction SCCLN.
2. Select a source client and a target client.
3. Define the scope for the client copy. You can use either select a client copy profile or you can specify selected tables.
   Note

   SAP recommends that you copy individual tables only in exceptional circumstances.
4. Define the processing setting, for example, check the copy by selecting Test Mode, lock the source client for logons, define the number of processes running in parallel.
5. Specify whether you want to schedule the client copy as a task list (either in dialog box or as a background job) or to start it immediately.

A remote client copy allows you to copy data between clients of different SAP systems. You can use a remote client copy to, for example, copy client-specific and cross-client customizing data between SAP systems.

A remote client copy proceeds in the same way as a local client copy, but gets the data from a Remote Function Call (RFC) destination to the source client.

A client transport differs from a client copy in that it does not use RFC. Like a client copy, however, a client transport is used to copy data between different clients. A client transport can be used to replace a local or a remote client copy.

A client transport consists of two steps. First, a client export extracts client data from the source client to files at the operating system level. Then the data is imported from these files into the target client.

Client Transport with the Help of Transactions SCC8 and STMS

To perform a client export with the help of transaction SCC8, follow these steps:

1. Log on to the source client. Choose transaction SCC8 (client export). Select the data to be copied using a (client copy) profile.
2. Specify the target system to which the client will be copied. The target system must be defined in the Transport Management System (TMS) as part of the transport domain.
3. Start the client export. Because copying may take a long time, use scheduled background processing.

The client export performed in the source system <SID> exports the client data asynchronously by calling the transport program tp at operating system level. This export process will generate up to three data files at the operating system level:

• RO< number >.<SID>: this file contains cross-client data
• RT< number >.<SID>: this file contains client-specific data
• RX< number >.<SID>: this file contains SAPscript texts

Hint

The data export is asynchronous and still runs even after transaction SCC8 has already finished. Don't run any other client copy tool before the data export is finished. As usual, you can check the status of the export with transaction SCC3. You can also check the status of the client export with the transaction SE01. Here, display the logs for the transport request <SID>KT<number> on the Client tab.

Note

During the client export, there might be no information available in transaction SCC3, (Client) Exports area, because the export is done with R3trans. Depending on the release of SAP_BASIS it may say Aborted in transaction SCC3 while the client export is running , instead of Processing..., as you would expect.

Depending on the type of data selected through the client transport profile, up to three client copy transport files are added to the buffer of the target system. Those files are related to the data files on operating system level described earlier.

The client export transport requests are not imported when an Import all takes place. You can import these requests into the target client using import single in TMS: Choose one of the transport requests of the client transport in the Transport Management System (TMS). The other transport requests belonging to this client transport are then automatically imported in the correct order.

After the import process has completed, post-import activities are required for object generation steps. For this, after completing the import, log on to the target client. Choose transaction SCC7 for the post-processing steps.

To display client transport logs, use the Transport Organizer – Extended View (transaction SE01), Client tab.

During client export, a repository consistency check can be performed by choosing RFC system check in transaction SCC8. If inconsistencies are detected, a list of the ABAP Dictionary table definitions missing or different in the target system will be generated. This will help you to recognize in advance problems that may occur during the import of the source data.

Client Export with Transaction SCC8N (as of SAP_BASIS 754)

Starting with SAP_BASIS 754, the client transport procedure was changed and enhanced.

A client transport with the help of the new client tool comprises three steps:

1. Client export (SCC8N):
   1. Call transaction SCC8N.
   2. Select the source client.
   3. Select the Export/Import Route. To do this, you can, for example, select the target of a transport request.
   4. Define the scope for the client copy. You can either use the previously defined profile of the client copy (direct entry or selection from the drop down list) or select table(s) or package(s).
   5. Define the processing settings, for example, Test Mode, Tolerate Failed Exits, Automated Import Post Processing or Release Transport Requests on Exports.
   6. Specify whether you want to schedule the client copy as a background job (Execute as Tasklist) or to start it immediately (Direct Execution).
2. Client import (STMS):
   1. Choose one of the transport requests of the client transport in the Transport Management System (transaction STMS, Import Queue Overview). The other transport requests belonging to this client transport are then automatically added in the correct order.
   2. Import these transport requests into the target client. For this, you may need to be logged on to the target client.
3. Client import post processing (SCC7N):
   Note

   You need to perform post processing activities to adapt the runtime environment to the current state of the data.

   1. Call transaction SCC7N.
   2. Select the Target Client of the Import.
   3. Select the Export/Import Route. To do this, you can for example select the target of a transport request.
   4. Check the Client Import Information: Client-Specific Transport, Cross-Client Transport, Profile, Source System, and Source Client.
   5. Define the Processing Settings: Test Mode, Tolerate Failed Exits, Tolerate Failed Tables, Use Exclusive Locks, and Number of Parallel Processes.
   6. Specify whether you want to schedule the client copy as a background job (Execute as Tasklist) or to start it immediately (Direct Execution).

Note

Client import post processing is always required and must be performed in the target client after the import of the transport requests. When you have selected Automated Imp. Postprocessing in the client export (transaction SCC8N), it is not necessary to start the client import post processing manually.

Don't use the same client as the source for multiple copies or client transports at the same time.

When copying, you can use copy profiles that simplify selection and combination of the objects to be copied. SAP delivers the following copy profiles in the table below. The customizing and application data is deleted in the target client before copying for all profiles except SAP_USER and SAP_UONL. This is, technically, unavoidable.

Roles are also copied with the user master records using the profile SAP_USER.

For all typical client copy scenarios, SAP provides profiles affecting various kinds of data in the SAP system and using various copy functions (as shown above).

Depending on the client copy option you have selected, the client copy tool determines the purpose of the table in the SAP system when the table is copied. For example, if you selected the Customizing profile and the table belongs to customizing, then the table would be copied to the target client. If the table contains application data, however, the table contents will not be copied (and existing data will be deleted in the target client).

To understand the effect of table delivery classes during upgrading, transport, or client copy, especially if there are development projects that create new tables, see the SAP Online Documentation and SAP Note 2857 – What table delivery classes exist? What do they mean?.

Table delivery classes are assigned to tables as follows:

• In general, tables containing application data should have delivery class A.
• Tables containing customizing data have different delivery classes, depending on how SAP changes the customizing settings in them.
• Tables of delivery class C may not contain new entries from SAP.
• Tables of delivery class G may be changed by SAP.
• Delivery classes S, E, and W are for tables containing control data and SAP system data, such as tables TADIR, VARI, TSTC, and CCCEXIT.
  Note

  W tables are SAP system tables that are filled internally. Their contents are purely technical. W tables are not taken into account by the client copy tool.

• Delivery class L is for tables for temporary data such as spool data and background processing data, for example, tables TSP* and TBTCJOB*.
  Note

  These tables should be empty in a new SAP system and its contents should be deleted in the target client.

To display all log files for a completed local or remote client copy, choose transaction SCC3. Here you can select the relevant target client and the relevant copying process. These copy logs provide the following information:

• Table statistics
• Control information
• Information about each table copied, including the link to the appropriate IMG component

Up to (and including) SAP_BASIS 753, double-click the highlighted entries for further information. You get a selection list in which you can see information about the copied tables (for example, runtime and the number of entries copied) and the exit programs from other application components used. If you had tables with copy problems in a local or remote client copy, you can recopy them with the Recopy Errors function. You can display the original log in the file system with the File Log button. You can also display the export and import logs of the main transport request.

To display client transport logs, use the Transport Organizer (Extended View), transaction SE01, tab Client.

All log files are physically stored in the <transport directory>/log directory at operating system level. Log files are named CC<number>.<SID>, where <number> is the serial client copy number, and <SID> is the source system ID.

If copying is unexpectedly terminated, the SAP system uses the name of the table being currently copied to restart the copy process.

When performing client copy error analysis, check not only the copy log, but also the SAP system log (transaction SM21), which tells you whether database problems are responsible for the client copy error. Correct any database problems before restarting the client copy.

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 the original run was recent, as indicated by the status line, it is advisable to choose Restart. Alternatively, to start the run from the beginning, choose Restart → New Start.

To avoid the problem of insufficient free space in the database, perform a simulation test run or a resource check.

• A simulation test run estimates the space required by reading all records to be copied without updating them in the database.
• A resource check estimates the space required by counting the records to be copied.

For more information about error analysis with client copy tools, see SAP Note 22514 – CC-INFO: Error analysis for client copy.

If you discover a write error in the target client, it is usually due to insufficient space in the database or simultaneous processing in the target client. In this case, check the SAP system log (transaction SM21) to determine the error. Don't work in either the source or target client during the copy.

If a termination in an exit program (the termination is explained in an ABAP runtime error) occurs, run the log display program RSCCPROT to determine the name of the last exit program that has caused the termination. The client copy program has not crashed; this is an application error.

If you discover an unexplained cancellation or error, check the:

• Copy log (transaction SCC3)
• SAP system log (transaction SM21)
• Dump analysis (transaction ST22)
• Job overview (transaction SM37)
• Spool requests (transaction SP01)