Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
KE (Package) Profitability Analysis
Basic Data
| Data Element | KALSM_COPA |
| Short Description | Costing sheet (CO-PA valuation) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KALSM | |
| Data Type | CHAR | Character String |
| Length | 6 | |
| Decimal Places | 0 | |
| Output Length | 6 | |
| Value Table | T683 |
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 sheet |
| Medium | 18 | Costing sheet |
| Long | 38 | Costing sheet (CO-PA valuation) |
| Heading | 18 | Costing sheet |
Documentation
Definition
Costing sheet used to calculate anticipated costs.
For more information about setting up valuation using condition types and costing sheets in Profitability Analysis (CO-PA), see Conditions and Costing Sheets in the Implementation Guide.
The function Create costing sheet lets you create a costing sheet for use specifically in CO-PA.
Each step in a CO-PA valuation strategy calls for either a costing sheet (and the appropriate application class), a material cost estimate, a user exit, or a transfer price variant together with the corresponding CO-PA value field.
Plan valuation using pricing procedures from Sales and Distribution (SD)
When you define a valuation strategy to be used solely in CO-PA planning, you can also use prcing procedures from Sales and Distribution (SD) (application class "V" in the field "Application"). Note that this is not allowed for valuation of actual data, since there the SD conditions are transferred directly from the billing document or sales order as defined in the value field assignments of the SD interface.
If you use an SD pricing procedure for valuation in planning, the system transfers the values of the conditions to the value fields as assigned in the SD interface.
Under certain circumstances, it may not be possible to use all conditions from SD to valuate data in CO-PA. For example, the access sequences used in the SD pricing procedures may contain condition tables with fields that are not defined as CO-PA characteristics. Consequently, before using an SD pricing procedure, be sure to check whether the fields required by the access sequence are defined as characteristics in your operating concern. Otherwise the system will not find the condition records, even if they have been maintained in SD.
History
| Last changed by/on | SAP | 19970902 |
| SAP Release Created in |
