How To Fix DPR_SHARED804 - System cannot lock &1 phases at present

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 804

• Message text: System cannot lock &1 phases at present

What causes this issue?

You are editing the project definition in change mode, but it is not
currently possible to lock &V1& phases.

System Response

You cannot edit the unlocked phases.

How to fix this error?

When you trigger an action for the whole project, the system tries again
to lock the unlocked phases. Possible actions are:
Schedule
Delete
Check threshold value violations
Aggregate severities
Change the status of the project definition

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 DPR_SHARED804 - System cannot lock &1 phases at present ?

  The SAP error message DPR_SHARED804 indicates that the system is unable to lock certain phases in the project management module, specifically in the context of the SAP Project System (PS) or the SAP Portfolio and Project Management (PPM) module. This error typically arises when there are concurrent processes trying to access or modify the same project phases, leading to a locking conflict.
  Cause:
  
  Concurrent Access: Multiple users or processes are trying to access or modify the same project phases simultaneously.
  Long-Running Transactions: A transaction that takes a long time to complete may hold a lock on the project phases, preventing other transactions from accessing them.
  System Configuration: Incorrect configuration of locking mechanisms or settings in the SAP system can lead to this issue.
  Database Locks: Locks at the database level can also cause this error if they are not released properly.
  
  Solution:
  
  Wait and Retry: If the error is due to concurrent access, waiting for a few moments and then retrying the operation may resolve the issue.
  Check Active Sessions: Use transaction codes like SM12 (to check for locks) and SM21 (to check system logs) to identify any active sessions that may be holding locks on the project phases.
  Release Locks: If you identify a session that is holding a lock unnecessarily, you may need to release the lock using transaction SM12. However, be cautious when doing this, as it may disrupt other users.
  Optimize Long Transactions: Review and optimize any long-running transactions that may be causing locks. Ensure that they are designed to complete as quickly as possible.
  System Configuration Review: Consult with your SAP Basis team to review the locking configuration and ensure it is set up correctly.
  Check for Background Jobs: Sometimes, background jobs may be running that could be causing locks. Check for any scheduled jobs that might be affecting the project phases.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SM12: To view and manage locks.
  SM21: To view system logs for any related errors or warnings.
  SE11: To check the database table definitions if needed.
  
  
  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 are managed in the system.
  
  If the issue persists after trying the above solutions, it may be necessary to engage SAP support for further assistance.