CJ073 - Project &1 (sub-tree &2) is being changed

SAP Error Message - Details

• Message type: E = Error

• Message class: CJ - Project master data and structure

• Message number: 073

• Message text: Project &1 (sub-tree &2) is being changed

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 CJ073 - Project &1 (sub-tree &2) is being changed ?

  The SAP error message CJ073 indicates that a project (or a sub-tree of a project) is currently being changed or edited by another user or process. This can occur in the context of project management within SAP, particularly when dealing with project structures, WBS (Work Breakdown Structure) elements, or network activities.
  Cause:
  
  Concurrent Access: Another user is currently editing the project or sub-tree, which locks the project for other users to prevent data inconsistencies.
  Background Jobs: A background job might be processing changes to the project, which can also lead to this error.
  Transaction Locking: The project might be locked due to a previous transaction that has not been completed or has encountered an error.
  
  Solution:
  
  Wait and Retry: If another user is editing the project, you may need to wait until they finish their changes. You can try to access the project again after some time.
  Check Locks: Use transaction code SM12 to check for any locks on the project. If you find a lock that seems to be stale or unnecessary, you may need to contact the user who holds the lock or your SAP administrator to release it.
  Review Background Jobs: Check if there are any background jobs running that might be affecting the project. You can use transaction code SM37 to monitor background jobs.
  Transaction Completion: Ensure that any previous transactions related to the project have been completed successfully. If a transaction was interrupted, it might have left the project in a locked state.
  Contact Support: If the issue persists and you cannot identify the cause, consider reaching out to your SAP support team for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ20N (Project Builder), CJ03 (Display Project), CJ02 (Change Project), SM12 (Display and Delete Locks), and SM37 (Job Monitoring).
  User Roles: Ensure that you have the appropriate permissions to access and modify the project.
  Documentation: Review SAP documentation or help files related to project management for additional insights on handling project locks and errors.
  
  By following these steps, you should be able to resolve the CJ073 error and continue working with your project in SAP.