SAP ABAP Data Element RKE_FLGDSTR (Delete Data Structures for the Operating Concern)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KE0C (Package) Customizing for Profitability Analysis
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KE0C (Package) Customizing for Profitability Analysis
Basic Data
Data Element | RKE_FLGDSTR |
Short Description | Delete Data Structures for the Operating Concern |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR1_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 | Data str. |
Medium | 15 | Data Structures |
Long | 20 | Data Structures |
Heading | 3 | Str |
Documentation
Definition
The tables containing transaction data for the operating concern are going to be deleted (CEyxxxx and CEyxxxx_zzzz, whereby y stands for figures 0...8, xxxx for the operating concern, and zzzz for any sequence of characters). This means that all of the data posted to the operating concern in all clients is lost. The data cannot be reproduced.
Archived data is not lost, but you cannot reload it.
The operating concern is then no longer in the system. You can create a new operating concern with the same name.
It is not possible to transport the deletion.
History
Last changed by/on | SAP | 20010221 |
SAP Release Created in | 46C |