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_CFMENUORKEKE4H | Assign Costing Keys to Products |
| Transaction Code | S_ALR_87005760 | IMG Activity: SIMG_CFMENUORKEKE4H |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUORKEKE4H | Assign Costing Keys to Products |
| Customizing Activity | SIMG_CFMENUORKEKE4H | Assign Costing Keys to Products |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUORKEKE4H |
Here you assign up to three costing keys to a single product for a specific point of valuation, record type, Planversion.
This assignment determines when and for which record type and plan version the system should read the product cost estimate specified in the costing key for that product.
For any "Valid to" date, you can assign up to three costing keys to one product. This means that you can access up to three cost estimates at the same time during valuation, and thus update the results of three valuation methods in parallel. The individual cost estimates are processed in the order in which they are entered here.
Example
PV Rec. Plan ver. Product Valid to C.key 1 C.key 2 C.key 3
01 F MAT01 31.12.2002 001 002
01 F MAT02 31.12.2002 001
Further notes
In order to valuate CO-PA line items using material cost estimates in Product Cost Planning, you must define your valuation strategy so that the system accesses product costing for the desired point of valuation.
If you are valuating using more than one costing key, note that a value field can only be filled by valuation if it is empty. In other words, each value field can only be filled once, and is never overwritten.
The system follows certain rules for determining which costing keys to use:
- First it checks whether one or more costing keys has been assigned to the product being valuated. If so, it valuates the data using only those costing keys.
- If no costing key is assigned to the product, the system checks whether any costing keys have been assigned to the material type of the product. If so, the data is valuated only using those costing keys.
- If no costing keys have been assigned to the material type, the system then checks whether any costing keys have been assigned to other characteristics using the flexible assignment function. If no costing keys are found in this manner, the transaction cannot be valuated using a material cost estimate.
Likewise, no valuation is carried out if an entry exists in one of these assignment tables but does not contain a costing key.
Activities
Specify which costing keys you want to use to valuate your individual products. If you do not want to specify this separately for each product, proceed to the next steps.
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_CFMENUORKEKE4H | 0 | HLA0009405 | Profitability Analysis |
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 |
| V_TKEVA03A | V - View | KE4H | 9999999999 | Maintain view V_TKEVA03A |
History
| Last changed by/on | SAP | 19990630 |
| SAP Release Created in |
