How To Fix CK071 - Costing run locked by another user

SAP Error Message - Details

• Message type: E = Error

• Message class: CK - Product Costing Messages

• Message number: 071

• Message text: Costing run locked by another user

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 CK071 - Costing run locked by another user ?

  The SAP error message CK071, which states "Costing run locked by another user," typically occurs when a costing run is being executed by another user, preventing you from starting a new costing run for the same material or set of materials. This is a common issue in environments where multiple users may be working on cost estimates simultaneously.
  Cause:
  
  Concurrent Execution: Another user is currently executing a costing run for the same material or set of materials.
  Session Lock: The system has a session lock on the costing run due to an incomplete or long-running process.
  User Session: A previous session may not have been properly closed, leaving the costing run locked.
  
  Solution:
  
  Wait and Retry: If another user is running the costing process, you may need to wait until they complete their run. You can check with your colleagues to see if they are currently processing a costing run.
  Identify the Lock: Use transaction code SM12 to check for locks in the system. You can filter by your user ID or the relevant material number to see if there are any active locks.
  Release the Lock: If you find that a lock is held by a user who is no longer active or if the session is stuck, you may need to release the lock. This should be done with caution and typically requires authorization. You can delete the lock entry in SM12 if you have the necessary permissions.
  Check Background Jobs: If the costing run was initiated as a background job, check the job status in transaction SM37. If the job is still running or has failed, you may need to address that issue.
  System Administration: If you are unable to resolve the issue, contact your SAP system administrator for assistance. They can provide insights into the system's current state and help resolve any locks.
  
  Related Information:
  
  Transaction Codes:
  
  CK11N: Create Cost Estimate with Quantity Structure
  CK40N: Costing Run
  SM12: Display and Delete Locks
  SM37: Job Monitoring
  
  
  Documentation: Refer to SAP Help documentation for detailed information on costing runs and handling locks.
  User Training: Ensure that users are trained on how to properly execute costing runs and handle potential conflicts with other users.
  
  By following these steps, you should be able to resolve the CK071 error and proceed with your costing run.