How To Fix CK381 - Costing canceled due to locked cost estimate in company code &

SAP Error Message - Details

• Message type: E = Error

• Message class: CK - Product Costing Messages

• Message number: 381

• Message text: Costing canceled due to locked cost estimate in company code &

What causes this issue?

During costing, the system found that a material in company code &v1&
is being costed or changed.

System Response

You cannot cost the material at present.

How to fix this error?

When a costing run is being carried out in the background, or when more
than &v4& materials are selected by the system, make sure that
costing is not being carried out in company code &v1& on costing date
&V3&
no material master records are being changed in company code &v1&

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CK381 - Costing canceled due to locked cost estimate in company code & ?

  The SAP error message CK381 indicates that a cost estimate cannot be processed because it is locked in the specified company code. This typically occurs when a cost estimate is already being processed or has been finalized, preventing any further changes or new cost estimates from being created for that particular company code.
  Cause:
  
  
  Locked Cost Estimate: The cost estimate for the material or product in question is currently locked. This can happen if:
  
  A cost estimate is already being created or modified by another user.
  The cost estimate has been marked as "finalized" or "released," which locks it for further changes.
  There may be a background job or process that is currently using the cost estimate.
  
  
  
  User Lock: A user may have a lock on the cost estimate due to an open session or transaction that has not been completed.
  
  
  Solution:
  
  
  Check for Existing Processes:
  
  Verify if another user is currently working on the cost estimate. You can check transaction codes like SM12 (to see user locks) or SM21 (to view system logs) to identify any active sessions or locks.
  
  
  
  Release Locks:
  
  If you find that a user is holding a lock, you may need to wait for them to complete their process. Alternatively, if necessary and appropriate, you can release the lock using transaction SM12 (be cautious with this approach, as it may disrupt other users).
  
  
  
  Check Cost Estimate Status:
  
  Use transaction CK13N to check the status of the cost estimate. If it is finalized, you may need to create a new cost estimate instead of modifying the existing one.
  
  
  
  Re-run the Cost Estimate:
  
  If the cost estimate is not locked by another user and you have resolved any issues, you can attempt to re-run the cost estimate process.
  
  
  
  Consult with SAP Basis or Support:
  
  If you are unable to resolve the issue, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  CK11N: Create Cost Estimate
  CK13N: Display Cost Estimate
  CK40N: Costing Run
  SM12: Display and manage user locks
  SM21: System log
  
  
  
  Costing Variants: Ensure that the costing variant being used is correctly configured and that there are no issues with the settings.
  
  
  User Authorization: Ensure that the user has the necessary authorizations to create or modify cost estimates.
  
  
  Documentation: Refer to SAP documentation or help files for more detailed information on cost estimates and related processes.
  
  
  By following these steps, you should be able to identify the cause of the CK381 error and take appropriate action to resolve it.