Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-CCO (Application Component) Client Copy⤷
STRM (Package) Client Copy & Adjustment Tools
Basic Data
| Data Element | CCDELTABS |
| Short Description | Client copy: Delete non-selected application tables |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CCDELTABS | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Del_table |
| Medium | 15 | Delete tables |
| Long | 30 | Initialize and recreate |
| Heading | 40 | Reset non-copied tables |
Documentation
Controlling the amount of data and resetting:
- Can you transport the customizing data of a source client into an existing target client which contains application data which is to be retained during copying?
- Why should the contents of the client be reset before copying?
Summary:
You cannot copy customizing in client copy, without deleting the application data in the target client.
A client copy cannot mix data of one type from different sources. If, for example, the user is copied, existing users in the target client are deleted.
1. What data belongs to a client?
(a) client-specific application data, i.e. data which occurs when operating the application system
(b) client-specific customizing data, on which the application data is based
(c) cross-client customizing data and system data, which is only mentioned here for completeness, but which is of no further interest in the client copy
(d) user data
Application data is produced when application transactions are executed. A number of plausibility and consistency checks are performed. The checks are mainly based on the customizing data of type (b), less frequently also (c). This means that there are dependencies between application data (a) and customizing data (b). Since customizing data does not access application data, there is only one direction for dependencies, namely from (a) to (b), meaning "(a) depends on (b)".
User data (d) is handled separately by the client copy. It can be copied, or not, independently of the other data types.
2. What is a consistent data environment of a client?
Consistency is given if all the dependencies between (a) and (b) are satisfied. When application data is entered in online operation, this is ensured by the checks in the maintenance transaction. Certain rules must be adhered to when copying clients.
3. Which rules apply when copying a client?
In order to ensure consistency also when copying, only the following two methods for copying are supported:
- All the customizing and application data is copied. During the copy, the tables are completely replaced, so data which was in the target client before the copy, but is not in the source client, is deleted by the copy, i.e. the table is recreated consistently. This ensures consistency between (a) and (b).
- Only customizing data is copied. At the same time, the contents of all the application tables which are not copied are reset. This also ensures consistency between (a) and (b).
These two methods imply that the copy resets any application data in the target client .
Quality tests test the consistency of a changed customizing environment with an existing (productive) client. This combines a customizing environment with an application environment. The test attempts to verify the consistency of the two environments, or to prove their inconsistency.
You can not copy customizing in client copy without resetting the application data, because it can cause too many complex problems, e.g. all objects with addresses are assigned incorrect addresses, etc.
To test new customizing, you must transport it into the test system with customizing transports. You can, for example, combine all customizing transports into one object list in the customizing development system, with the Transport Organizer tools (transaction SE03). You can then transport copies between systems or clients, with this object list.
Number ranges:
Number ranges have to be reset if there is no application data in the target client after the copy. This is the case if you copy only customizing data. Otherwise number range states remain unchanged, or are also copied from the source client. The decision to reset is derived implicitly from the copy parameters, and need not, and cannot, be specified externally.
History
| Last changed by/on | SAP | 19950407 |
| SAP Release Created in | 610 |
