How To Fix CK060 - Object was not costed

CK060 - Overview

• 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.

CK060 - Details

• 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,