Purpose
You can activate special client copy copy options and exclude tablesfrom the copy.
Tables which you put in the exclusion list are ignored by the clientcopy, i.e. neither copied nor deleted. (An exception is the exclusionof a table in the source system of a remote copy. This exclusion isonly active if the table does not exist in the target system.)
You can also put packages in the exclusion list in the source system inremote copies. Missing tables in this package then no longer causecancellation in the target system. This can, for example, be useful ifthere is a non-modified Add-On in the source system, which cannot beimported into the target system.
You can specify for each table or package, the Basis release untilwhich the exclusion applies. The default is the current release, i.e.the exclusion no longer applies after a basis component upgrade in thesystem. You can deactivate the check by entering the value '999'.

Caution
All changes are immediately active system-wide, and apply in all futurecopies in this system, until they are reset, so you should reset thecopy options and exceptions to the original settings, if necessary,after a client copy.
The options affect the runtime behavior of the client copyconsiderably, and can cause cancellation because of lack of memory,runtime errors or database problems.
Excluding tables from the copy usually causes inconsistencies in thetarget client, because the program logic usually differs, as well asthe table definitions, especially when you copy between two systems.
Tables delivered by SAP can therefore only be excluded from the copywhen SAP explicitly asks you to do so. Otherwise SAP cannot support thetarget client.

Activities
Read the warnings and notes in note 446485 for up-to-dateinformation about the use and potential problems of the variousoptions.
Note 557132 contains further information about the behavior ofremote copies.