SAP ABAP Data Element CCCORACTIV (Changes and Transports for Client-Specific Objects)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-CTS-CCO (Application Component) Client Copy
⤷ STRM (Package) Client Copy & Adjustment Tools
⤷ BC-CTS-CCO (Application Component) Client Copy
⤷ STRM (Package) Client Copy & Adjustment Tools
Basic Data
Data Element | CCCORACTIV |
Short Description | Changes and Transports for Client-Specific Objects |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CCCORACTIV | |
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 | Corr. Sys. |
Medium | 18 | Transp. Connection |
Long | 30 | Changes and Transports |
Heading | 7 | CorrSys |
Documentation
Definition
Feature to control whether table changes should be recorded within the transport system. Only the changes in client-specific Customizing tables are recorded.
Use
The changes are recorded implicitly for each change within the maintenance tool. The changed table entries are recorded in the current transport request. The request is entered the first time this object is maintained in an interactive window. However it can also be set explicitly in the Development Organizer maintenance window.
The current request number is transferred as the default value for all subsequent changes. This default request number can be explicitly changed to another request number in the Development Organizer.
Procedure
Choose one of the possible values:
- Changes without automatic recording
There is no control by the Development Organizer here. Changes are not recorded. This variant can be used for pure test, training and demo clients. - Automatic recording of changes
In this mode, changes are analyzed by the Development Organizer and the changed keys of each table are recorded in a transport request. The transport request must be created with the first change and is then used implicitly for all subsequent actions. This variant should be selected for clients in which Customizing is performed and for productive clients. - No changes
Customizing is locked in this client. Changes are rejected. Only the display is permitted. Possible for demo or training systems. - No transports
Examples
Dependencies
History
Last changed by/on | SAP | 19981111 |
SAP Release Created in |