Hierarchy
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ KE (Package) Profitability Analysis
Basic Data
Data Element | KALAW1 |
Short Description | First costing key (CO-PA) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | KALAW | |
Data Type | CHAR | Character String |
Length | 3 | |
Decimal Places | 0 | |
Output Length | 3 | |
Value Table | TKEVA03 |
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 | Cstg key 1 |
Medium | 18 | First costing key |
Long | 25 | First costing key |
Heading | 25 | First costing key |
Documentation
Definition
In valuation in Profitability Analysis, you can valuate each line item with up to six different costing keys simultaneously. The costing keys, which are used to read the data in Product Cost Controlling, are stored in the fields
- "First costing key (CO-PA)" (technical name: KALAW1)
- "Second costing key (CO-PA)" (technical name: KALAW2)
- ...
- "Sixth costing key (CO-PA)" (technical name: KALAW6)
These costing keys are processed in the order specified according to the numbers assigned to them.
If one of these fields KALAW1 ... KALAW6 does not contain a costing key, no product cost estimate is read for that field.
The resulting values for the costing keys in fields
KALAW1 ... KALAW6 are passed on to the value fields assigned in the transaction Assign costing components to value fields to the fields labeled Field name 1 ... Field name 6.
Thus, for example, the value found for the costing key in
KALAW1 is passed on to the value field entered in the column Field name 1.
Further information
History
Last changed by/on | SAP | 19970812 |
SAP Release Created in |