SAP Note 552486 - FAQ Product Cost Controlling note Version 5 Validity: 11.12.2002 - active Language English Header Data Released On Release Status Component 11.12.2002 13:48:13 Released for Customer CO-PC Product Cost Controlling Other Components CO Controlling Priority Category Recommendations / Additional Info FAQ Symptom 1. Although the 'Always recost material' flag is set in the costing run (CK40N) in the 'Selection' flow step, the system transfers an existing cost estimate. 2. How does the system determine the quantity structure for the cost estimate (CK11N)? 3. The system displays 'incorrect' results in the detail reports of Cost Object Controlling. 4. The results analysis for sales document items returns unexpected results. 5. The settlement process is unclear. 6. How does report SAPKKA12 work? 7. How does the cross-company costing work? If the cross-company costing is active, the system generates error message CK240 if a material from another plant (company code) is to be transferred. 8. How does the valuation with purchasing info record (strategy L) work? 9. What is the difference between product costing/sales order costing and preliminary costing of a production order? 10. In the case of a split valuation, why can the prices only be updated in the internal segment? 11. I have questions about various topics of the material ledger/actual costing. 12. The material ledger is not active, so why does the system nevertheless write ML documents and/or use ML tables, for example CKMLMV0xx? 13. If the ML is active, why does the system generate more than one FI document for average moving price materials (transaction-based material ledger settlement) for the goods receipt? 14. What do I have to consider for the quantity-based application of overhead? Other Terms Reason and Prerequisites Solution Question 1: Although the 'Always recost material' flag is set in the costing run (CK40N) in the 'Selection' flow step, the system transfers an existing cost estimate. Answer: In this case, a transfer in the background occurred for a cost estimate with the same key. In other words, there is already a cost estimate on the database for the material in question in the same period with the same costing type, costing variant and costing version. Youcan find more information on this topic in SAP Note 484892. Question 2:How does the system determine the quantity structure for the cost estimate (CK11N)? Answer: The following priority sequence applies to the determination of the quantity structure. Priority 1:If you assign a quantity structure on the initial screen of the cost estimate, the system uses it in any case. Priority 2:The system determines the quantity structure data that you have entered in the cost estimate view of the material. you can display the status used by results analysis via the log. all objects are selected that correspond to the selection criteria and that are not marked for deletion or not archived.If the status is correct. you can use analysis report RKACSHOW.Generally.In these cases. Then you have to ensure that either an error-free cost component split exists in the issuing plant or that it can be generated by a new costing. To determine the info record. Priority 4:The quantity structure is determined via the settings in the quantity structure control (Transaction OKK5). Question 8:How does the valuation with purchasing info record (strategy L) work? Answer: For the valuation with a price from the info record. If error message CK240 occurs. Question 4:The results analysis for sales document items returns unexpected results.Use the object to be analyzed as a selection criterion.the corresponding info record is used. production order costing in CO02 is single-level. you can also check the result via the explanation facility in the individual processing with an activated full log. due to the status). how to use order groups or report RKO7CO88). refer to SAP Notes 409960 and 499699. Answer: This is often due to the use of an unexpected status. In the second step. Answer:In several cases. or a new costing is carried out in the issuing plant and the cost component split generated in this case is transferred to the transfer plant. you can control whether the quantity structure occurs according to validity (lot size.In this context.In contrast to that. the cause is in the dynamic status determination in most cases. set the deletion flag.The system generates an overview of all tables relavant to cost accounting and their entries concerning the object for analysis (you can find more information on how to use this analysis report in SAP Note 28145).Therefore.All settings and their effects are explained there. Question 10: In the case of a split valuation. Answer: You can activate the 'Cost Across Company Codes' functionin Transaction OKYV for certain costing variants (costing type + valuation variant). the system generates error message CK240 if a material from another plant (company code) is to be transferred.Execute this report via the ABAP Editor (Transaction SE38). check whether cross-company costing is activated. Priority 3:Via the selection method indicator in Materials Planning view 4 in the material master. If the function is activated. b) Error: Price from an info record with deletion flag -> SAP Note 301418 c) The valuation with price via condition table does not work for subcontracting. the settlement sender and receiver are checked.This status may differ from the active status of the sales document item. Question 6: How does report SAPKKA12 work? Answer:Report SAPKKA12 is used to set statuses for sales document items in mass processing. either an existing cost component split is transferred from the issuing plant according to the transfer control. SAP recommends that you use the most current version of the report (refer to SAP Note 350290). If this status does not correspond to the document flow.In this case. the reports correctly display the data which has been updated on the database. period) or according to production version. the system dynamically determines the 'Final billing' status (FNBL) and the 'Delivered' status (DLV) from the document flow at the time of the results analysis. Answer: The settlement processes the objects in two steps. the system determines the vendor (source of supply) first. the system can basically only consider info records with category 'N' (normal) and 'L' (subcontracting).An additional approach for the analysis of the results analysis results is available in SAP Note 212899. Question 9:What is the difference between product costing/sales order costing and preliminary costing of a production order? Answer:Product costing in CK11* and sales order costing in VA02 are multi-level. you can search for relevant notes in the SAPNet Frontend for the key word SD_ORDER_GET_DATA (in any case.In the individual processing of results analysis (Transaction KKA3).To verify this.You can find the documentation for this report in SAPNet under the address specified in SAP Note 398627 (alias CO-MTO -> Frequently asked questions (FAQs) for Customizing in results analysis > SAPKKA -> SAPKKA12). You can find more information on this topic in SAPNote 351835.This means that the system even selects objects that are not relevant for settlement (for example. all calculated results analysis data is described in detail. Question 3:The system displays 'incorrect' results in the detail reports of Cost Object Controlling. In the first step. why can the prices only be updated in the . to exclude an object from processing. SAP Note 444448 is to be implemented in the system with the required corrections). In this case. the system runs a defined strategy. Special cases are: a) It is not possible to include a valid source list entry by specifying an outline agreement -> a function is missing. For the source of supply found.As a rule. Question 5: The settlement process is unclear. Question 7: How does the cross-company costing work? If thecross-company costing is active.SAP Note 309588 provides additional information on this topic (for example. internal segment? Answer:In the initial standard SAP System.However.The delta is posted as a price difference. this is not an average moving price control such as for MM but it is simulated.The transaction-based material ledger settlement posts this difference to the balance sheet account. why does the system generate more than one FI document for average moving price materials (transaction-based material ledger settlement) for the goods receipt? Answer:If the ML is active. outline agreement in source list 398627 INFO: CO-PC-OBJ (Results analysis/WIP calculation) 351835 Valuation variant w/ purchasing info record strategies 350290 Program SAPKKA12 309588 Order selection period-end closing "manufact orders & PCCs" 301418 Price from info record with deletion flag determined 212899 Results analysis calculates incorrect values 28145 Using technical inspection report RKACSHOW This document is referenced by: SAP Notes (11) 444448 Results analysis by period with delivery-related billing 301418 Price from info record with deletion flag determined 309588 Order selection period-end closing "manufact orders & PCCs" 351835 Valuation variant w/ purchasing info record strategies .A typical example for this is Transaction MR21 and the price change document which was implemented in Release 4. Question 12: The material ledger is not active.5A. up to eight follow-on documents can be created in FI for one goods receipt. mixed costings can also be created and updated for several segments via procurement alternatives.For external segments (procured externally) this does not make any sense in general.the result is the same for each balance.In the SAP Service Marketplace you can also find basic information under the alias CO-ACT. Question 14: What do I have to consider for the quantity-based application of overhead? Answer: First of all. for example CKMLMV0xx? Answer: Even standard transactions partially belong to or use objects from development area CO-PCACT. piece or KG). Question 11: I have questions about various topics of the material ledger/actual costing. Answer:Check the consulting notes and additional information notes that are available with key word CNACT in the SAP R/3 Frontend or in the SAP Service Marketplace. overhead rates must be defined that refer to certain cost elements with an origin group.In the same way. also refer to Note 424465. the mixed costing and product cost collector use the procurement alternative function (table CKMLMV0xx). the system first evaluates the GR with the average moving price in the material master. In this context. Thus.Depending on the data constellation. you must set the 'Material Origin' indicator for the affected materials in the material master (Transaction MM02). In this case. In the costing sheet. so why does the system nevertheless write ML documents and/or use ML tables. it is also possible to update the price in an internal segment. outline agreement in the source list II 484892 Info: Transfer cost estimates with the same key 444448 Results analysis by period with delivery-related billing 424465 Information: Quantity-based overheads 409960 CK11: error CK380. To differentiate the materials with the same cost element according to the unit of measure (for example. you must set the 'Record qty' indicator in the master data of the cost elements for which the overhead is to be applied (Transaction KA02). Question 13: If the ML is active. Validity This document is not restricted to a software component or software component version References This document refers to: SAP Notes 499699 CK11N error CK380. only the header segment is calculated and the price is updated only here.However. If the system calculates overhead rates for material quantities consumed. they must be assigned to different origin groups. if the "Valuation type 'in-house production' mandatory" flag is set for the categories in Customizing (Transaction OMWC). outline agreement in source list 398627 INFO: CO-PC-OBJ (Results analysis/WIP calculation) 212899 Results analysis calculates incorrect values 28145 Using technical inspection report RKACSHOW 499699 CK11N error CK380. outline agreement in the source list II 484892 Info: Transfer cost estimates with the same key .350290 Program SAPKKA12 409960 CK11: error CK380.