Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FBAS (Package) Financial accounting 'Basis'
Basic Data
| Data Element | F020CODA |
| Short Description | Delete CO Transaction Data |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | CO data |
| Medium | 15 | Delete CO data |
| Long | 20 | Delete CO data |
| Heading | 2 | CO |
Documentation
Definition
In the standard system, both the actual and planning data in Controlling is reset in this program run if you set this switch. It is generally recommended, however, that you use the CO resetting program RKSCUS01, in particular if you want to keep the planning data. You then take the "Delete CO data" indicator out and use RKSCUS01 for transaction data in the controlling area. This program gives you the option of excluding planning data from being reset.
Note
If the "Delete CO data" indicator is active, the controlling area assigned is determined from the company code and its data reset completely, independent of whether other company codes which are not reset are also assigned. Data is not limited only to that which flows from one company code into the controlling area.
History
| Last changed by/on | SAP | 19940827 |
| SAP Release Created in |
