Technical Background (SAP Library - Change and Transport System)

Technical Background

Number Ranges

When you copy a client, the number ranges are taken into account. The following cases are distinguished:

Case	Effect on Number Range
customizing and application data is copied	The number ranges are copied with the data because they are required by the application data.
Only Customizing data is copied	The number ranges are reset because the application data that refers to them is deleted and then reconstructed.

Table selection and table classes

Depending on the copy option you have selected, the client copy tool determines the purpose of the table in the system when the table is copied. For example, if you selected the Customizing option and the table belongs to Customizing, then the table is copied to the target client. If the table contains application data, however, the table contents are deleted not copied.

To determine the purpose of a table, the client copy tool uses the delivery class assigned. The client copy tool assumes that all tables belong to Customizing except those that have classes L, A, and W:

L These tables should be empty in the new system and are deleted in the target client.

A Application tables copied if desired.

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

Identity of Table Structures

Note

The following statements only apply to cross-system client copies.

To set up a new client by client copy, the structures of all tables to be copied must be identical in the source and the target system.

Remote client copy: Before the client copy process is started, a consistency check is automatically made. If inconsistencies are detected, the copy process is not started and an error message is logged. You can also perform the consistency check yourself with the RFC System Comparison pushbutton.

Client transport: If an RFC connection can be established between the systems, you can use the report RSCLICHK to compare the structures. If they differ, transport errors and inconsistencies may occur. You can run the program directly in the transaction SCC8 with the RFC System Check pushbutton.