Knowledge Base > Automation Engine and Target Systems > SAP > SAP R/3 Client Copies

SAP R/3 Client Copies

Like the Automation Engine, SAP R/3 is a client-capable application. The individual clients are completely separate units. In some cases, periodical data exchange between clients is necessary. AE can be used to automate these processes.

The "client" is the top-level hierarchy in R/3 applications. Settings on client level apply to all structures in the R/3 enterprise organization. The client is a self-contained unit in technical, economical and organizational terms.

This client concept can be used for:

Managing many data center customers in one R/3 system.
Setting up several clients with different tasks on one R/3 System. For example:

Standard client (client 000)
Customizing client (001)
Test client
Quality assurance client
Production client

In such an environment it is often required to supply a QA or test client with consistent data. The most suitable way to obtain this data is copying the production client. Regularly copy this client in order to establish a realistic test environment.

Client Copies in SAP R/3

Copying clients in SAP R/3 involves some effort, especially the creation of periodical copies for supplying test systems with current data.

SAP R/3 supports the online copying and transportation of clients. These transactions are not suitable for periodical execution (SAP Release 4.0 to 4.6D).

The R/3 background job control cannot perform such periodical transactions because dynamic variants are used.

Problem Definition

Huge amounts of data are transferred when a client is copied. A client without application data allocates about 500 MB databaseA database is an organized collection of data including relevant data structures. memory. The copying process can therefore take several hours with one or more dialog processes being busy during this process.

Users should not use the source and target client during the copying process. Active users in other clients consume additional resources and extend the time required for copying.

A test run should be performed before starting the copying process. In doing so, you can determine which tables need to be modified and the available database memory is also checked.

The target client is often deleted before a client is copied, thus deleting all master user data. Therefore, only the user SAP* can log on to the target client.

R/3 Client Copies with AE

Using AE for the periodical creation of client copies makes this process easier and more secure. Test run and copying process can be automated and the normal operation is not interrupted.

The copying process starts depending on test results and resource availability. AE informs the operator immediately if an error occurs.

The SAP system must meet the following requirements before AE can create client copies:

Master user data must not be deleted before the copying process
AE uses a normal user account for logging on to SAP. It cannot use the SAP* user. In SAP, it is not possible to delete the target client before copying it. Alternately, you can use custom ABAPs in order to delete large tables (see SAP Service Marketplace, note no. 365304).
The report RSCLXCOP must be modified in order to enable the maintaining of report variants.
A job for copying clients obtains its information from a variant. This variant is overwritten with data from the source client or deleted during the copy process. During a client export the number of the copy is entered in the variant, thus causing problems with periodical scheduling. Identical variants (using identical names) for the report RSCLXCOP must therefore be created in source and target client. Detailed information is provided in note no. 303007 of the SAP Service Marketplace.

If all the above requirements are met, you can create an AE job for copying clients. Dependencies can be represented within a workflow. Test run and the actual copy process can run in automated form. AE ensures sufficient system resources. Periodical client copies can so be created in an easy and secure way.