SAP ABAP Data Element CCNKTRESET (Client copy: Prevent number range reset)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-CTS-CCO (Application Component) Client Copy
⤷
STRM (Package) Client Copy & Adjustment Tools
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-CCO (Application Component) Client Copy⤷
STRM (Package) Client Copy & Adjustment Tools
Basic Data
| Data Element | CCNKTRESET |
| Short Description | Client copy: Prevent number range reset |
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 | 10 | No NRreset |
| Medium | 15 | No NR reset |
| Long | 32 | Prevent number range reset |
| Heading | 10 | No NRreset |
Documentation
Definition
The current client cannot contain application data for the normal standard client copy. If the client already exists, you must ensure that all application data is deleted first. For example, the R3trans offers a function 'client remove' (see R3transdoku). For RSCLICOP, "normal standard client copy" means execution mode 'A' (third parameter; A = "all", meaning the entire data environment of the source client).
The reason for this requirement is that, at the end of the client copy, number range statuses are reset in all applications. If application data exists, abnormal terminations can occur during later transactions because of "duplicate key" situations.
History
| Last changed by/on | SAP | 19950209 |
| SAP Release Created in |
