How To Fix CK060 - Object was not costed

SAP Error Message - Details

• Message type: E = Error

• Message class: CK - Product Costing Messages

• Message number: 060

• Message text: Object was not costed

What causes this issue?

The system could not find any entries that are
<DS:GLOS.relevancy_to_costing>relevant to costing</>.

System Response

The system did not cost the object.

How to fix this error?

Check whether the following objects should be flagged as relevant to
costing:

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Items in the <DS:GLOS.bill_of_material>BOM</>
<DS:TRAN.CS03>Display BOM</>
<DS:GLOS.operation>Operations</> in the <DS:GLOS.routing>routing</>
<DS:GLOS.control_key>Control key</> in the routing
Look at the message log.
Check whether a quantity was specified in the
<DS:GLOS.confirmation>confirmation</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CK060 - Object was not costed ?

  The SAP error message CK060 ("Object was not costed") typically occurs in the context of product costing in SAP, particularly when trying to perform a costing run for a material or when attempting to display the cost estimate for a material that has not been costed yet. Here are the common causes, solutions, and related information for this error:
  Causes:
  
  No Cost Estimate Exists: The material or object you are trying to access does not have a cost estimate created for it.
  Costing Variant Issues: The costing variant used may not be set up correctly or may not be applicable for the material.
  Costing Run Not Executed: The costing run for the relevant period has not been executed, or the material was not included in the costing run.
  Material Status: The material may be in a status that prevents it from being costed (e.g., blocked for costing).
  Missing Master Data: Required master data (like BOM, routing, or work center) may be missing or incomplete, preventing the costing process from being completed.
  
  Solutions:
  
  Create a Cost Estimate: If no cost estimate exists, you can create one by executing the costing run (transaction CK40N or CK11N) for the relevant material.
  Check Costing Variant: Ensure that the costing variant used is correctly configured and applicable for the material. You can check this in the configuration settings (transaction OKKN).
  Execute Costing Run: If the costing run has not been executed, perform the costing run for the relevant period and ensure that the material is included.
  Review Material Status: Check the status of the material in the material master (transaction MM03) to ensure it is not blocked for costing.
  Verify Master Data: Ensure that all necessary master data (BOM, routing, work centers) is complete and accurate. You can check this using transactions like CS03 (BOM) and CA03 (Routing).
  Check for Errors in Previous Costing Runs: If there were errors in previous costing runs, they may need to be resolved before a new costing can be performed.
  
  Related Information:
  
  Transaction Codes:
  
  CK11N: Create Cost Estimate with Quantity Structure
  CK40N: Execute Costing Run
  MM03: Display Material Master
  CS03: Display BOM
  CA03: Display Routing
  
  
  Costing Variants: Review the configuration of costing variants in transaction OKKN to ensure they are set up correctly for your materials.
  Costing Types: Understand the different costing types (e.g., standard costing, actual costing) and how they apply to your materials.
  
  By following these steps, you should be able to identify the cause of the CK060 error and implement the appropriate solution. If the issue persists, it may be beneficial to consult with your SAP support team or a functional consultant specializing in controlling (CO) and product costing.