How To Fix CJ806 - &1 &4 &2 is currently being processed by &3

SAP Error Message - Details

• Message type: E = Error

• Message class: CJ - Project master data and structure

• Message number: 806

• Message text: &1 &4 &2 is currently being processed by &3

Project &V2& is being processed by
<DS:TRAS.PS_USER(USR.&V3(P)&)>USER:</>&V3(P)&.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CJ806 - &1 &4 &2 is currently being processed by &3 ?

  The SAP error message CJ806 indicates that a particular project or WBS (Work Breakdown Structure) element is currently being processed by another user or session. This typically occurs in scenarios where multiple users are trying to access or modify the same project data simultaneously, leading to a lock situation.
  Cause:
  
  Concurrent Access: Another user is currently editing or processing the same project or WBS element.
  Session Lock: The system has locked the project data due to an ongoing transaction or process.
  Long-running Transactions: A transaction that takes a long time to complete may hold the lock longer than expected.
  
  Solution:
  
  Wait and Retry: If the lock is temporary, waiting for a few moments and then retrying the operation may resolve the issue.
  Identify the Lock: Use transaction code SM12 to check for locks on the project or WBS element. You can see which user is holding the lock and the transaction that is causing it.
  Contact the User: If you identify the user holding the lock, you may contact them to see if they can complete their transaction or release the lock.
  Release the Lock: If necessary and if you have the appropriate authorizations, you can manually delete the lock from transaction SM12. However, this should be done with caution, as it may disrupt the other user's work.
  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.
  System Performance: If this issue occurs frequently, it may be worth investigating system performance or reviewing the design of the processes to minimize concurrent access issues.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM37: To check background jobs.
  CJ20N: To manage project structures.
  
  
  User Training: Ensure that users are trained on how to properly manage project data to minimize conflicts.
  System Configuration: Review system settings related to locking mechanisms and transaction handling to optimize performance.
  
  If the problem persists after trying the above solutions, it may be necessary to consult with your SAP Basis team or technical support for further investigation.