Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KBAS (Package) Overhead Cost Controlling
Basic Data
| Data Element | TKSTA |
| Short Description | Transport flag: cost elements |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | FLAG | |
| 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 | CostElems |
| Medium | 15 | Cost elements |
| Long | 20 | Cost elements |
| Heading | 31 | Cost elements (COAr dependent) |
Documentation
Definition
Indicator for choosing the customizing settings during transport.
Supplementary Documentation - TKSTA 0001
Use
If you select this indicator, the following customizing settings are activated or deactivated in the correction:
- Cost elements (CSKB - dependent on controlling area)
Procedure
- To include the settings in the correction request number specified, choose Include in Correction.
- To remove the settings from the correction request, choose Delete from Correction.
In both cases the system may display a screen on which you can restrict your selection of entries to be transported (by controlling area or chart of accounts, for example).
Caution
The transport of master data (cost elements, cost centers, activity types, statistical key figures) occurs in two steps:
- Firstly, in the target system, the system deletes any master data in the same controlling area or in the same chart of accounts.
- Then it imports the master data contained in the correction request.
If you have already created master data in the target system either manually or through a different transport, this data is lost when you execute the current transport.
As the master data is not deleted in the target system, but the transaction data is deleted, transport to a system that is not empty can lead to inconsistencies. It is therefore safer to maintain the master data manually in the target system.
Example
You have manually created cost centers in controlling area 0001 in the target system. You want to transport cost centers in controlling area 0001 from the Customizing client to the target system.
- When you execute the transport, the system deletes the manually created cost centers in the target system.
- The new cost centers are then imported into the target system.
Dependencies
The following objects are logically related and should therefore always be transported together:
- Cost elements (CSKB - controlling area dependent part)
- Allocation segments (CSKA - chart of accounts dependent part)
- Texts (CSKU - chart of accounts dependent part)
Transports of allocation segments always include the texts.
Caution
If you are working with more than one controlling area that is using the same chart of accounts, and you want to transport cost elements, proceed as follows:
- Maintain the cost elements in all controlling areas with this chart of accounts.
- Always transport the following together:
- the chart-of-accounts-dependent part of the cost elements
- the controlling-area-dependent part of the cost elements for all controlling areas with this chart of accounts.
History
| Last changed by/on | SAP | 20130529 |
| SAP Release Created in |
