FAQ Product Cost Controlling

8/10/2019 FAQ Product Cost Controlling

http://slidepdf.com/reader/full/faq-product-cost-controlling 1/4

SAP Note

Header Data

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 systemgenerates error message CK240 if a material from another plant (company code) is to betransferred.

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 ofa production order?

10. In the case of a split valuation, why can the prices only be updated in the internalsegment?

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 documentsand/or use ML tables, for example CKMLMV0xx?

13. If the ML is active, why does the system generate more than one FI document for averagemoving 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) inthe '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 thesame period with the same costing type, costing variant and costing version. Youcan find moreinformation 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 inthe cost estimate view of the material.

552486 - FAQ Product Cost Controlling note

Version 5 Validity: 11.12.2002 - active Language English

Released On 11.12.2002 11:48:13

Release Status Released for Customer

Component CO-PC Product Cost Controlling

CO ControllingPriority Recommendations / Additional Info

Category FAQ

Other Components



Priority 3:Via the selection method indicator in Materials Planning view 4 in thematerial master, you can control whether the quantity structure occurs according to validity (lotsize, period) or according to production version.

Priority 4:The quantity structure is determined via the settings in the quantitystructure control (Transaction OKK5).

Question 3:The system displays 'incorrect' results in the detail reports of Cost ObjectControlling.

Answer:In several cases, the reports correctly display the data which has been updated on thedatabase.To verify this, you can use analysis report RKACSHOW.Execute this report via the ABAPEditor (Transaction SE38).Use the object to be analyzed as a selection criterion.The systemgenerates an overview of all tables relavant to cost accounting and their entries concerning theobject for analysis (you can find more information on how to use this analysis report in SAP Note28145).

Question 4:The results analysis for sales document items returns unexpected results.

Answer: This is often due to the use of an unexpected status.Generally, the system dynamicallydetermines the 'Final billing' status (FNBL) and the 'Delivered' status (DLV) from the document flowat the time of the results analysis.This status may differ from the active status of the salesdocument item.In the individual processing of results analysis (Transaction KKA3), you can displaythe status used by results analysis via the log. If this status does not correspond to the documentflow, the cause is in the dynamic status determination in most cases.In these cases, you can searchfor relevant notes in the SAPNet Frontend for the key word SD_ORDER_GET_DATA (in any case, SAP Note444448 is to be implemented in the system with the required corrections).If the status is correct,you can also check the result via the explanation facility in the individual processing with anactivated full log.In this case, all calculated results analysis data is described in detail.An

additional approach for the analysis of the results analysis results is available in SAP Note212899.

Question 5: The settlement process is unclear.

Answer: The settlement processes the objects in two steps. In the first step, all objects areselected that correspond to the selection criteria and that are not marked for deletion or notarchived. In the second step, the settlement sender and receiver are checked.This means that thesystem even selects objects that are not relevant for settlement (for example, due to thestatus).Therefore, to exclude an object from processing, set the deletion flag.SAP Note 309588provides additional information on this topic (for example, how to use order groups or reportRKO7CO88).

Question 6: How does report SAPKKA12 work?

Answer:Report SAPKKA12 is used to set statuses for sales document items in mass processing.As arule, SAP recommends that you use the most current version of the report (refer to SAP Note350290).You can find the documentation for this report in SAPNet under the address specified in SAPNote 398627 (alias CO-MTO -> Frequently asked questions (FAQs) for Customizing in results analysis -> SAPKKA -> SAPKKA12).All settings and their effects are explained there.

Question 7: How does the cross-company costing work? If thecross-company costing is active,the system generates error message CK240 if a material from another plant (company code) isto be transferred.

Answer: You can activate the 'Cost Across Company Codes' functionin Transaction OKYV for certaincosting variants (costing type + valuation variant). If the function is activated, either anexisting cost component split is transferred from the issuing plant according to the transfercontrol, or a new costing is carried out in the issuing plant and the cost component split generatedin this case is transferred to the transfer plant. If error message CK240 occurs, check whethercross-company costing is activated. 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.

Question 8:How does the valuation with purchasing info record (strategy L) work?

Answer: For the valuation with a price from the info record, the system can basically only considerinfo records with category 'N' (normal) and 'L' (subcontracting). To determine the info record, thesystem determines the vendor (source of supply) first. In this case, the system runs a definedstrategy. For the source of supply found,the corresponding info record is used. You can find moreinformation on this topic in SAPNote 351835. Special cases are:

a) It is not possible to include a valid source list entry by specifying an outlineagreement -> a function is missing.In this context, refer to SAP Notes 409960 and 499699.

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.

Question 9:What is the difference between product costing/sales order costing andpreliminary costing of a production order?

Answer:Product costing in CK11* and sales order costing in VA02 are multi-level.In contrast to that,production order costing in CO02 is single-level.

Question 10: In the case of a split valuation, why can the prices only be updated in the



internal segment?

Answer:In the initial standard SAP System, only the header segment is calculated and the price isupdated only here.However, if the "Valuation type 'in-house production' mandatory" flag is set forthe categories in Customizing (Transaction OMWC), it is also possible to update the price in aninternal segment.For external segments (procured externally) this does not make any sense ingeneral.However, mixed costings can also be created and updated for several segments via procurementalternatives.

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 wordCNACT in the SAP R/3 Frontend or in the SAP Service Marketplace.In the SAP Service Marketplace you

can also find basic information under the alias CO-ACT.

Question 12: The material ledger is not active, so why does the system nevertheless writeML documents and/or use ML tables, for example CKMLMV0xx?

Answer: Even standard transactions partially belong to or use objects from development area CO-PC-ACT.A typical example for this is Transaction MR21 and the price change document which wasimplemented in Release 4.5A.In the same way, the mixed costing and product cost collector use theprocurement alternative function (table CKMLMV0xx).

Question 13: If the ML is active, why does the system generate more than one FI documentfor average moving price materials (transaction-based material ledger settlement) for thegoods receipt?

Answer:If the ML is active, this is not an average moving price control such as for MM but it issimulated. In this case, the system first evaluates the GR with the average moving price in thematerial master.The delta is posted as a price difference.The transaction-based material ledgersettlement posts this difference to the balance sheet account. Thus,the result is the same for eachbalance.Depending on the data constellation, up to eight follow-on documents can be created in FIfor one goods receipt.

Question 14: What do I have to consider for the quantity-based application of overhead?

Answer: First of all, you must set the 'Record qty' indicator in the master data of the costelements for which the overhead is to be applied (Transaction KA02). If the system calculatesoverhead rates for material quantities consumed, you must set the 'Material Origin' indicator forthe affected materials in the material master (Transaction MM02). To differentiate the materialswith the same cost element according to the unit of measure (for example, piece or KG), they must beassigned to different origin groups. In the costing sheet, overhead rates must be defined that referto certain cost elements with an origin group. In this context, also refer to Note 424465.

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (11)

499699 CK11N error CK380, 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, 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

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



350290 Program SAPKKA12

409960 CK11: error CK380, 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

Documents

FAQ Product Cost Controlling