How To Fix CK139 - Cost estimate for marked period does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: CK - Product Costing Messages

• Message number: 139

• Message text: Cost estimate for marked period does not exist

What causes this issue?

Costing has to be carried out with costing type &V1&, version &V2&, and
valuation variant &V3&.

How to fix this error?

You must first cost the relevant assembly or material, or carry out the
relevant costing run in this period before you can mark the costing
results in the material master.
<DS:TRAN.CK11N>Create Material Cost Estimate</>
<DS:TRAN.CK40N>Create Costing Run</>

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CK139 - Cost estimate for marked period does not exist ?

  The SAP error message CK139, which states "Cost estimate for marked period does not exist," typically occurs in the context of cost accounting and product costing. This error indicates that the system is unable to find a cost estimate for a specific period that has been marked for processing or analysis.
  Causes:
  
  Missing Cost Estimate: The most common cause is that a cost estimate has not been created for the specified period. This can happen if the cost estimate was not run or if it was deleted.
  Incorrect Period Selection: The user may have selected a period for which no cost estimate exists. This could be due to a typo or misunderstanding of the period range.
  Costing Variant Issues: The costing variant used may not be configured correctly, or it may not be applicable for the selected period.
  Data Migration Issues: If data has been migrated from another system, there may be inconsistencies or missing data in the cost estimates.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or access the cost estimates for the selected period.
  
  Solutions:
  
  Create a Cost Estimate: If a cost estimate does not exist for the marked period, you will need to create one. This can be done using transaction code CK11N (Create Cost Estimate) or CK40N (Mass Cost Estimate).
  Check Period Selection: Verify that the period you are trying to access is correct. Ensure that you are looking for the right fiscal year and period.
  Review Costing Variants: Check the configuration of the costing variant to ensure it is set up correctly for the intended period.
  Data Consistency Check: If data migration is involved, perform a consistency check to ensure that all necessary cost estimates have been migrated correctly.
  Authorization Check: Ensure that you have the necessary authorizations to access the cost estimates. You may need to contact your SAP security team for assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CK11N (Create Cost Estimate), CK40N (Mass Cost Estimate), and CK24 (Display Cost Estimate).
  Costing Variants: Understand how costing variants work in SAP and how they can affect the creation and retrieval of cost estimates.
  SAP Documentation: Refer to SAP Help documentation for detailed information on cost estimates and related processes.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or bugs related to cost estimates.
  
  By following these steps, you should be able to resolve the CK139 error and ensure that cost estimates are available for the required periods.