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 | CCNOCASCAD |
| Short Description | Client control: No client cascade for upgrade import |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | X | |
| 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 | No cascade |
| Medium | 18 | No SAP upgrade |
| Long | 35 | Protection against SAP upgrade |
| Heading | 9 | NoCascade |
Documentation
Definition
By using this flag you can prevent the current client from being overwritten during an upgrade.
Use
If this flag is set, the client is no longer supplied with data during SAP upgrades. After an SAP upgrade, it is not possible to work actively in the client. The flag can only be set for a test client or an SAP reference client (Early Watch).
This functionality is only intended for exceptional cases, for example as the basis for carrying out an adjustment after an upgrade. Each "normal" client should, of course, be updated by an SAP upgrade, since otherwise data resources for system or customizing tables required by transactions could be missing. However, in the case of clients that contain certain tables for backup purposes (backup client), you can use the flag to prevent SAP upgrades from supplying such clients with data.
Note:
To maintain the flag, you need the full authorization for the Workbench Organizer (authorization S_CTS_ALL).
History
| Last changed by/on | SAP | 19981111 |
| SAP Release Created in |
