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
IMG Activity
| ID | SIMG_CFMENUORKEKE46 | Maintain Calculation Procedures |
| Transaction Code | S_ALR_87005727 | IMG Activity: SIMG_CFMENUORKEKE46 |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORKEKE46 | Maintain Calculation Procedures |
| Customizing Activity | SIMG_CFMENUORKEKE46 | Maintain Calculation Procedures |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORKEKE46 |
In this step, you define CO-PA-specific costing sheets.
A costing sheet contains the conditions which are used to calculate expected values. It also determines the order in which the conditions are processed and how the conditions are related to one another. For example, you can specify that sales commission should be calculated on the basis of the sales revenue. The costing sheet is particularly used to determine base values that are to be used to calculated percentage markups or reductions, to calculate subtotals, and to define how the conditions relate to one another (such as the sequence within the costing sheet.
Example
The following costing sheet calculates sales commission (condition "PROV") and costs for outgoing packaging ("OUPA") and freight ("OUTF").
Step Counter C.type Name From To
---------------------------------------------------------------------
10 0 KB00 Revenue 0 0
20 0 DISC Customer discount 0 0
30 0 DISP Price reduction 0 0
40 0 Net revenue 10 30
50 0 COGS Cost 0 0
60 0 Base for sales commission 40 50
110 0 PROV Sales commission 60
300 0 OUPA Outgoing packaging 0 0
310 0 OUTF Outgoing freight 50 0
The step numbers determine the order in which the conditions are processed. The column "Counter" is only used when you want to work with more than one condition type in the same step. The fields "From" and "To" determine which steps the system should use as a basis for calculating increases or reductions in that step. If you enter different "From" and "To" values, the system adds together the values found in those steps plus any steps between them. This sum is then used as the reference base for calculating that step.
The conditions "REVN", "DISC", and "DISP" in this example are base conditions, that are taken from the billing document transferred from Sales and Distribution (SD). You therefore do not need to reference other steps of the costing sheet. This is also true of the condition type "COGS".
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 1 | Mandatory activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | SIMG_CFMENUORKEKE46 | 0 | HLA0100169 | Valuation |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| COPA_KSCHM | C - View cluster | KE46 | 1 | Costing Sheets for Profitability Analysis | ||
| KE46 | T - Individual transaction object | KE46 | 01 | Costing Sheets for Profitability Analysis |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
