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 | CCSELMODE |
| Short Description | Table selection mode ('A' / 'T') |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | 8 | Selmode |
| Medium | 8 | Selmode |
| Long | 20 | Table selection mode |
| Heading | 7 | Selmode |
Documentation
Definition
With the entry 'A', you carry out the normal client copy, during which, all ("A") relevant tables are selected. Which table this is, is explained in the following (see below.)
Alternatively, you can use the single table selection mode "T", for which the table names must be entered generically in a following parameter.
A special variant is the selection of data via a predefined command file (input "C"). For example, the command file, via which you recorded your activities of Customizing (see menu point 'Transport' in your Customizing maintenance menu). In this way, you can transfer table entries maintained in the Customizing client into another client.
Which tables are selected (mode A) ?
The selection of the tables occurs exclusively due to the table categories as they were determined by the SAP application department. The maintenance responsibility of every table should be controlled clearly by this classification, that is, it is determined to what extent, the contents of a table belong to the customer completely or partially. You can derive from this how the table prevents the overwriting of customer data in the context of an SAP update, that is, which one of the alternatives
- Do not import table at the customer
- Only import table in SAP client 000, however not into the customer clients
- Table is imported into all customer clients.
The class therefore is a means for preventing the customer's entries being overwritten during release upgrade for the customer.
Also for the client copy (report RDSCLICOP), the delivery class is used, namely for determining the Customizing environment. All classes except L ("empty": should be available empty in the new system environment), A ("application table") and W (system table updated internally, purely technical contents) belong to the Customizing environment. For a description of the remaining Customizing relevant classes, refer to the following description.
Short description of the delivery class
In the following class description, typical questions on the use attributes and transport attributes will be answered, such as the questions
- 1) Delivery: Is the table delivered with default or empty? A default contains either a sample without obligation, which is only used for better illustration in the Customizing phase or it is a productively usable default with procedure parameters.
- 2) Update: Are entries imported into the customer system or into the customer clients during SAP update or not?
- 3) Client copy: Is the table copied for the client copy ?
Description of the classes
Class S
Description: System table, program character. Consider changes here as program changes. Transport attributes:
- delivered with sample,
- update: is imported and distributed into all customer clients
- client copy: is copied
Class W
Description: System table, contents maintained directly via maintenance transactions, for example, software development environment (workbench). Transported via separate transport objects (for example, R3TR PROG, R3TR TABL, and so on). Transport attributes:
- delivery: always with contents (in particular entire workbench),
- update: is imported via the respective transport objects, no client distribution !
- client copy: is copied, however mostly client-independently.
Class E
Description: System table with separate name ranges for customer entries, thus can be expanded by customers. Consider SAP name range as class S (changes here have characters of program changes), by convention, customer name range are not changed by SAP. Transport attributes:
- delivery: with default (SAP name range) ,
- update: is imported (SAP name range), distributed in clients,
- client copy: is copied.
Class C
Description: Customer table ("Customer only"). Responsibility for maintaining exclusively at the customer, must never be overwritten by SAP during update. Transport attributes:
- delivery: mostly with sample (making Customizing easier)
- update: is only imported into SAP client 000, no import, if table
is client-independent !
- client copy: is copied.
Class G
Description: Customer table with protected contents. Like class C, however, new entries can be created by SAP. Existing entries are always protected against overwriting or deletion. Transport attributes:
- delivery: with sample,
- update import: Client 000 with update, customer client only
insert. Only insert mode, if table is client-independent.
- client copy: is copied.
Class L
Description: Table for storing temporary data which can be regarded as preliminary results with validity limited in time. Transport attributes:
- delivery: always empty,
- update: no import, cannot be transported.
- client copy: is not copied.
Class A
Description: Application data which is updated by the customer by application transactions (master and transaction data). A transport of such data is generally not useful. It is nevertheless supported to enable the transfer of an entire client environment including application data of a system into another one. Transport attributes:
- delivery: empty (presentation sample in SAP client 000)
- update: is imported, however, see above note
- client copy: only by request (parameter option).
History
| Last changed by/on | SAP | 19950209 |
| SAP Release Created in | 50A |
