How To Fix CK669 - Deleting current standard cost estimates can cause inconsistencies

SAP Error Message - Details

• Message type: E = Error

• Message class: CK - Product Costing Messages

• Message number: 669

• Message text: Deleting current standard cost estimates can cause inconsistencies

What causes this issue?

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

If you delete a current standard cost estimate, the fields for the cost
estimate are set to zero in the material master record. If you use the
material ledger, the standard prices in the material ledger master data
are also deleted when you delete the current standard cost estimate.
The material master record for the material thus does no longer
contains a current standard price from a standard cost estimate.
If you delete an active standard cost estimate, you can no longer
determine scrap, work in process and variations for previous periods.
In certain countires, it is a legal requirement to maintain records of
standard pricing. Therefore, you should check whether you are obliged
by law to keep records of your standard cost estimates. Please also
contact the relevant accounting and inventory management departments.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CK669 - Deleting current standard cost estimates can cause inconsistencies ?

  The SAP error message CK669, which states "Deleting current standard cost estimates can cause inconsistencies," typically occurs when you attempt to delete a standard cost estimate that is currently in use or has dependencies in the system. This error is a safeguard to prevent potential inconsistencies in financial reporting and inventory valuation.
  Cause:
  
  Current Standard Cost Estimate: The cost estimate you are trying to delete is marked as the current standard cost estimate for one or more materials.
  Dependencies: There may be transactions or processes that rely on the current standard cost estimate, such as inventory valuation, financial postings, or production orders.
  Period Closing: If the period is closed or if there are open transactions that reference the cost estimate, deletion may lead to inconsistencies.
  
  Solution:
  
  
  Check Dependencies: Before attempting to delete a standard cost estimate, check if it is being used in any transactions. You can do this by reviewing:
  
  Material master records
  Open production orders
  Purchase orders
  Sales orders
  Inventory valuations
  
  
  
  Change the Standard Cost Estimate: Instead of deleting the current standard cost estimate, consider creating a new standard cost estimate and marking it as the current one. This way, you can maintain historical data while ensuring that the new estimate is in use.
  
  
  Use CKR1 Transaction: If you need to delete a cost estimate, you can use the transaction CKR1 (Delete Cost Estimate) to remove the cost estimate, but ensure that it is not the current one or that it is not being referenced by any open transactions.
  
  
  Consult with Finance/Controlling Team: If you are unsure about the implications of deleting a cost estimate, consult with your finance or controlling team to understand the potential impact on financial reporting and inventory valuation.
  
  
  System Configuration: In some cases, system settings or configurations may prevent the deletion of cost estimates. Review the configuration settings in the controlling module (CO) to ensure they align with your business processes.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CK11N (Create Cost Estimate), CK40N (Change Cost Estimate), and CKR1 (Delete Cost Estimate).
  Documentation: Review SAP documentation and notes related to cost estimates and their management to understand best practices and guidelines.
  Testing: If you are in a development or testing environment, you can experiment with creating and deleting cost estimates to understand the process better before making changes in the production environment.
  
  By following these steps, you can address the CK669 error effectively while ensuring that your cost management processes remain consistent and reliable.