How To Fix CK062 - Additive cost estimate locked by another user

SAP Error Message - Details

• Message type: E = Error

• Message class: CK - Product Costing Messages

• Message number: 062

• Message text: Additive cost estimate 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 CK062 - Additive cost estimate locked by another user ?

  The SAP error message CK062, which states "Additive cost estimate locked by another user," typically occurs when a user attempts to access or modify a cost estimate that is currently being edited or processed by another user. This locking mechanism is in place to prevent data inconsistencies and ensure that cost estimates are not simultaneously modified by multiple users.
  Cause:
  
  Concurrent Access: Another user is currently working on the same cost estimate, which locks it for editing.
  Session Timeout: A previous session may not have been properly closed, leaving the cost estimate locked.
  System Error: Occasionally, system errors or crashes can lead to a lock not being released properly.
  
  Solution:
  
  
  Wait and Retry: If another user is working on the cost estimate, the simplest solution is to wait until they finish and release the lock. You can check with your colleagues to see if they are currently editing the estimate.
  
  
  Identify the Lock: Use transaction code SM12 to view and manage locks in the system. You can check for the user who has locked the cost estimate and, if necessary, contact them to release the lock.
  
  
  Release the Lock: If you have the necessary authorizations, you can manually release the lock in transaction SM12. However, this should be done with caution, as it may lead to data inconsistencies if the other user is still working on the estimate.
  
  
  Check for Background Jobs: Sometimes, background jobs may also hold locks. You can check transaction SM37 to see if any background jobs are running that might be causing the lock.
  
  
  Session Management: Ensure that all sessions are properly closed after use. If a session is left open, it may inadvertently keep a lock on the cost estimate.
  
  
  Contact Support: If the issue persists and you cannot identify the cause, it may be necessary to contact your SAP support team for further assistance.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  CK11N: Create Cost Estimate
  CK40N: Change Cost Estimate
  SM12: Display and manage locks
  SM37: Monitor background jobs
  
  
  
  User Training: Ensure that all users are trained on how to properly manage cost estimates and understand the implications of locking mechanisms in SAP.
  
  
  System Configuration: Review system settings related to locking behavior, if applicable, to ensure they align with your organization's needs.
  
  
  By following these steps, you should be able to resolve the CK062 error and continue working with cost estimates in SAP.