How To Fix DPR_SHARED806 - Could not lock all phases; scheduling is not possible

SAP Error Message - Details

• Message type: E = Error

• Message class: DPR_SHARED - Development Projects: Messages for Shared Objects

• Message number: 806

• Message text: Could not lock all phases; scheduling is not possible

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 DPR_SHARED806 - Could not lock all phases; scheduling is not possible ?

  The SAP error message DPR_SHARED806 indicates that the system is unable to lock all phases of a project, which prevents scheduling from being executed. This error typically arises in the context of project management within SAP, particularly when using the Project System (PS) or the Project Management (DPR) module.
  Causes:
  
  Concurrent Access: Another user or process may be currently accessing or modifying the project phases, leading to a lock conflict.
  Lock Table Issues: The SAP lock table may be full or experiencing issues, preventing new locks from being acquired.
  Incomplete Project Setup: The project or its phases may not be fully set up or may have inconsistencies that prevent proper locking.
  System Performance Issues: High system load or performance issues may lead to delays in acquiring locks.
  
  Solutions:
  
  Check for Concurrent Users: Verify if other users are currently working on the same project or phases. If so, coordinate with them to avoid conflicts.
  Release Locks: If you have access, you can use transaction code SM12 to check for and release any unnecessary locks held by users. Be cautious when doing this to avoid disrupting other users.
  Review Project Setup: Ensure that the project and its phases are correctly configured. Check for any missing or incorrect data that might prevent locking.
  System Performance: Monitor system performance and check for any issues that might be affecting the lock table. If necessary, consult with your SAP Basis team to resolve performance issues.
  Retry Scheduling: After addressing any lock conflicts or system issues, try to schedule the project again.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage lock entries.
  SM21: To check system logs for any related errors or warnings.
  SE11: To check the database table definitions if you suspect data issues.
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to project management and locking mechanisms for a deeper understanding of how locks work in SAP.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP support team or consult SAP support for further assistance.