How To Fix CK114 - Costing run & & is being deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: CK - Product Costing Messages

• Message number: 114

• Message text: Costing run & & is being deleted

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message CK114 - Costing run & & is being deleted ?

  The SAP error message CK114, which states "Costing run & & is being deleted," typically occurs during the costing run process in the Controlling (CO) module, particularly in Product Costing. This error indicates that the costing run you are trying to access or process is currently in the process of being deleted, which prevents any further actions on it.
  Cause:
  
  Concurrent Deletion: Another user or process may be in the process of deleting the same costing run.
  System Lock: The system may have a lock on the costing run due to ongoing processes or transactions.
  Incomplete Process: The costing run may not have been completed properly, leading to inconsistencies in the system.
  
  Solution:
  
  
  Check for Active Processes: Verify if another user or process is currently working on the same costing run. You can use transaction codes like SM12 (to check for locks) or SM66 (to view active processes) to identify any locks or active sessions.
  
  
  Wait and Retry: If another user is deleting the costing run, you may need to wait until that process is completed before attempting to access or delete the costing run again.
  
  
  Check Logs: Review the application logs (transaction SLG1) for any additional information related to the error. This may provide insights into what is causing the issue.
  
  
  Delete Manually: If you have the necessary authorizations and are sure that the costing run is not being used, you can attempt to delete it manually using transaction CKR1 (for deleting costing runs).
  
  
  Consult Basis Team: If the issue persists, it may be necessary to involve your SAP Basis team to check for any underlying system issues or to clear any locks that may be causing the problem.
  
  
  System Restart: In some cases, a system restart may help clear any temporary locks or issues.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CK11N (Create Cost Estimate), CK40N (Costing Run), and CKR1 (Delete Costing Run).
  User Authorizations: Ensure that you have the necessary authorizations to perform actions related to costing runs.
  Documentation: Refer to SAP Help documentation for detailed information on costing runs and related processes.
  
  If the problem continues after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.