faq product cost controlling note.pdf

13.03.2012 of 6

SAP Note 552486 - FAQ Product Cost Controlling note

Note Language: English Version: 5 Validity: Valid Since 11.12.2002

Summary

Symptom

1. Although the 'Always recost material' flag is set in the costing run(CK40N) in the 'Selection' flow step, the system transfers an existingcost estimate.

2. How does the system determine the quantity structure for the costestimate (CK11N)?

3. The system displays 'incorrect' results in the detail reports of CostObject Controlling.

4. The results analysis for sales document items returns unexpectedresults.

5. The settlement process is unclear.

6. How does report SAPKKA12 work?

7. How does the cross-company costing work? If the cross-company costingis active, the system generates error message CK240 if a material fromanother 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 andpreliminary costing of a production order?

10. In the case of a split valuation, why can the prices only be updatedin the internal segment?

11. I have questions about various topics of the material ledger/actualcosting.

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

13. If the ML is active, why does the system generate more than one FIdocument for average moving price materials (transaction-basedmaterial ledger settlement) for the goods receipt?

14. What do I have to consider for the quantity-based application ofoverhead?

Other terms

Reason and Prerequisites

Solution

Question 1: Although the 'Always recost material' flag is set in the

13.03.2012 of 6


costing run (CK40N) in the 'Selection' flow step, the systemtransfers an existing cost estimate.

Answer: In this case, a transfer in the background occurred for a costestimate with the same key. In other words, there is already a costestimate on the database for the material in question in the same periodwith the same costing type, costing variant and costing version. Youcanfind more information on this topic in SAP Note 484892.

Question 2:How does the system determine the quantity structure forthe cost estimate (CK11N)?

Answer: The following priority sequence applies to the determination of thequantity structure.

Priority 1:If you assign a quantity structure on the initial screen ofthe cost estimate, the system uses it in any case.

Priority 2:The system determines the quantity structure data that youhave entered in the cost estimate view of the material.

Priority 3:Via the selection method indicator in Materials Planningview 4 in the material master, you can control whether the quantitystructure occurs according to validity (lot size, period) or accordingto production version.

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

Question 3:The system displays 'incorrect' results in the detailreports of Cost Object Controlling.

Answer:In several cases, the reports correctly display the data which hasbeen updated on the database.To verify this, you can use analysis reportRKACSHOW.Execute this report via the ABAP Editor (Transaction SE38).Use theobject to be analyzed as a selection criterion.The system generates anoverview of all tables relavant to cost accounting and their entriesconcerning the object for analysis (you can find more information on how touse this analysis report in SAP Note 28145).

Question 4:The results analysis for sales document items returnsunexpected results.

Answer: This is often due to the use of an unexpected status.Generally, thesystem dynamically determines the 'Final billing' status (FNBL) and the'Delivered' status (DLV) from the document flow at the time of the resultsanalysis.This status may differ from the active status of the salesdocument item.In the individual processing of results analysis (TransactionKKA3), you can display the status used by results analysis via the log. Ifthis status does not correspond to the document flow, the cause is in thedynamic status determination in most cases.In these cases, you can searchfor relevant notes in the SAPNet Frontend for the key wordSD_ORDER_GET_DATA (in any case, SAP Note 444448 is to be implemented in thesystem with the required corrections).If the status is correct, you canalso check the result via the explanation facility in the individual

13.03.2012 of 6


processing with an activated full log.In this case, all calculated resultsanalysis data is described in detail.An additional approach for theanalysis of the results analysis results is available in SAP Note 212899.

Question 5: The settlement process is unclear.

Answer: The settlement processes the objects in two steps. In the firststep, all objects are selected that correspond to the selection criteriaand that are not marked for deletion or not archived. In the second step,the settlement sender and receiver are checked.This means that the systemeven selects objects that are not relevant for settlement (for example, dueto the status).Therefore, to exclude an object from processing, set thedeletion flag.SAP Note 309588 provides additional information on this topic(for example, how to use order groups or report RKO7CO88).

Question 6: How does report SAPKKA12 work?

Answer:Report SAPKKA12 is used to set statuses for sales document items inmass processing.As a rule, SAP recommends that you use the most currentversion of the report (refer to SAP Note 350290).You can find thedocumentation for this report in SAPNet under the address specified in SAPNote 398627 (alias CO-MTO -> Frequently asked questions (FAQs) forCustomizing in results analysis -> SAPKKA -> SAPKKA12).All settings andtheir effects are explained there.

Question 7: How does the cross-company costing work? Ifthecross-company costing is active, the system generates errormessage CK240 if a material from another plant (company code) is tobe transferred.

Answer: You can activate the 'Cost Across Company Codes' functioninTransaction OKYV for certain costing variants (costing type + valuationvariant). If the function is activated, either an existing cost componentsplit is transferred from the issuing plant according to the transfercontrol, or a new costing is carried out in the issuing plant and the costcomponent split generated in this case is transferred to the transferplant. If error message CK240 occurs, check whether cross-company costingis activated. Then you have to ensure that either an error-free costcomponent split exists in the issuing plant or that it can be generated bya 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 canbasically only consider info records with category 'N' (normal) and 'L'(subcontracting). To determine the info record, the system determines thevendor (source of supply) first. In this case, the system runs a definedstrategy. For the source of supply found,the corresponding info record isused. You can find more information on this topic in SAPNote 351835.Special cases are:

a) It is not possible to include a valid source list entry byspecifying an outline agreement -> a function is missing.In this

13.03.2012 of 6


context, refer to SAP Notes 409960 and 499699.

b) Error: Price from an info record with deletion flag -> SAP Note301418

c) The valuation with price via condition table does not work forsubcontracting.

Question 9:What is the difference between product costing/salesorder costing and preliminary costing of a production order?

Answer:Product costing in CK11* and sales order costing in VA02 aremulti-level.In contrast to that, production order costing in CO02 issingle-level.

Question 10: In the case of a split valuation, why can the pricesonly be updated in the internal segment?

Answer:In the initial standard SAP System, only the header segment iscalculated and the price is updated only here.However, if the "Valuationtype 'in-house production' mandatory" flag is set for the categories inCustomizing (Transaction OMWC), it is also possible to update the price inan internal segment.For external segments (procured externally) this doesnot make any sense in general.However, mixed costings can also be createdand updated for several segments via procurement alternatives.

Question 11: I have questions about various topics of the materialledger/actual costing.

Answer:Check the consulting notes and additional information notes that areavailable with key word CNACT in the SAP R/3 Frontend or in the SAP ServiceMarketplace.In the SAP Service Marketplace you can also find basicinformation under the alias CO-ACT.

Question 12: The material ledger is not active, so why does thesystem nevertheless write ML documents and/or use ML tables, forexample CKMLMV0xx?

Answer: Even standard transactions partially belong to or use objects fromdevelopment area CO-PC-ACT.A typical example for this is Transaction MR21and the price change document which was implemented in Release 4.5A.In thesame way, the mixed costing and product cost collector use the procurementalternative function (table CKMLMV0xx).

Question 13: If the ML is active, why does the system generate morethan one FI document for average moving price materials(transaction-based material ledger settlement) for the goodsreceipt?

Answer:If the ML is active, this is not an average moving price controlsuch as for MM but it is simulated. In this case, the system firstevaluates the GR with the average moving price in the material master.Thedelta is posted as a price difference.The transaction-based material ledger

13.03.2012 of 6


settlement posts this difference to the balance sheet account. Thus,theresult is the same for each balance.Depending on the data constellation, upto eight follow-on documents can be created in FI for one goods receipt.

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

Answer: First of all, you must set the 'Record qty' indicator in the masterdata of the cost elements for which the overhead is to be applied(Transaction KA02). If the system calculates overhead rates for materialquantities consumed, you must set the 'Material Origin' indicator for theaffected materials in the material master (Transaction MM02). Todifferentiate the materials with the same cost element according to theunit of measure (for example, piece or KG), they must be assigned todifferent origin groups. In the costing sheet, overhead rates must bedefined that refer to certain cost elements with an origin group. In thiscontext, also refer to Note 424465.

Header Data

Release Status: Released for CustomerReleased on: 11.12.2002 11:48:13Master Language: GermanPriority: Recommendations/additional infoCategory: FAQPrimary Component: CO-PC Product Cost Controlling

Secondary Components:CO Controlling

The Note is release-independent

Related Notes

Number Short Text

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

13.03.2012 of 6


Number Short Text

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

faq product cost controlling note.pdf

Documents