How To Fix KU345 - CKRCT records were not completely deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: KU - Costing: Rollup

• Message number: 345

• Message text: CKRCT records were not completely deleted

What causes this issue?

A system error occurred.

How to fix this error?

Please inform your system administrator or contact the SAP hotline with
details of the message.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message KU345 - CKRCT records were not completely deleted ?

  The SAP error message KU345, which states "CKRCT records were not completely deleted," typically occurs in the context of the Controlling (CO) module, particularly when dealing with cost object records in the Costing (CK) area. This error indicates that there are inconsistencies or issues with the deletion of records related to cost estimates or cost object records.
  Causes:
  
  Incomplete Deletion Process: The deletion process for CKRCT records (which are related to cost estimates) may not have been completed successfully due to system interruptions or errors during the process.
  Database Locking Issues: If the database is locked or if there are ongoing transactions that are preventing the deletion of records, this error may occur.
  Referential Integrity Issues: There may be dependencies or references to the CKRCT records that prevent their deletion.
  Custom Code or Enhancements: If there are custom programs or enhancements that interact with the CKRCT records, they may not be handling deletions correctly.
  
  Solutions:
  
  Check for Open Transactions: Ensure that there are no open transactions or locks on the records you are trying to delete. You can use transaction codes like SM12 to check for locks.
  Run Deletion Program Again: If the deletion process was interrupted, try running the deletion program again. This can often resolve the issue if it was a temporary glitch.
  Check for Dependencies: Investigate if there are any dependencies or references to the CKRCT records that need to be addressed before deletion. This may involve checking related tables or records.
  Use Transaction CKR1: You can use transaction CKR1 to manually delete cost estimates and related records. Ensure that you follow the correct procedure and check for any error messages during this process.
  Database Consistency Check: Perform a consistency check on the database to identify any issues that may be causing the error. This can be done using transaction codes like SE14 or DB02.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues.
  Contact SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance. They can provide more specific guidance based on your system configuration and the context of the error.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CKR1 (Delete Cost Estimates), CKM3 (Display Material Costing), and CK11N (Create Cost Estimate).
  Documentation: Review SAP documentation related to cost accounting and cost object management for a better understanding of how CKRCT records are managed.
  System Logs: Check system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  By following these steps, you should be able to diagnose and resolve the KU345 error in your SAP system.