How To Fix CKCC301 - Costing run &1 / &2 blocked. Repeat run for &2 not created.

SAP Error Message - Details

• Message type: E = Error

• Message class: CKCC - Messages in the Costing Run Cockpit

• Message number: 301

• Message text: Costing run &1 / &2 blocked. Repeat run for &2 not created.

What causes this issue?

For the costing run &MSGV1&, the creation of a repeated run was planned
for the date &MSGV2&. The costing run for the date &MSGV2& is currently
locked by another user. ,,

System Response

The repeated run could not be created.

How to fix this error?

Execute the costing step of the costing run &MSGV1& for the date &MSGV3&
again so that the repeated run can be created.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CKCC301 - Costing run &1 / &2 blocked. Repeat run for &2 not created. ?

  The SAP error message CKCC301 indicates that a costing run has been blocked, and as a result, a repeat run for the specified costing variant has not been created. This error typically occurs in the context of product costing in SAP, particularly when using the CK40N transaction for cost estimates.
  Causes:
  
  Previous Costing Run Not Completed: The most common cause is that a previous costing run for the same variant is still in progress or has not been completed successfully.
  Locking Issues: There may be database locks or other processes that are preventing the costing run from being executed.
  Configuration Issues: Incorrect configuration settings in the costing variant or master data can lead to blocking issues.
  Authorization Issues: The user may not have the necessary authorizations to execute the costing run.
  Errors in Master Data: Issues with material master data, such as missing or incorrect information, can also lead to this error.
  
  Solutions:
  
  Check Running Processes: Use transaction SM66 or SM50 to check if there are any active processes related to the costing run. If a previous run is still active, you may need to wait for it to complete or terminate it if it is stuck.
  Review Logs: Check the logs for the previous costing run (transaction CK40N) to identify any errors that may have occurred. This can provide insights into why the run was blocked.
  Clear Locks: If there are locks preventing the costing run, you may need to clear them. This can be done using transaction SM12 to delete any unnecessary locks.
  Verify Configuration: Ensure that the costing variant and related configuration settings are correct. This includes checking the costing type, valuation area, and other relevant settings.
  Check Authorizations: Ensure that the user executing the costing run has the necessary authorizations. You can check this using transaction SU53 or by consulting with your security team.
  Correct Master Data: Review the material master data for any inconsistencies or missing information that could be causing the issue.
  
  Related Information:
  
  Transaction Codes: 
  
  CK40N: Cost Estimate with Quantity Structure
  CK11N: Create Cost Estimate
  CK24: Display Cost Estimate
  SM12: Display and Delete Locks
  SM66: Global Work Process Overview
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the CKCC301 error message.
  Documentation: Review SAP documentation on product costing and costing runs for best practices and troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.