How To Fix PSHLP_MSG_CL120 - &2 &1: Changes are not saved to the operative project

SAP Error Message - Details

• Message type: E = Error

• Message class: PSHLP_MSG_CL - Message Class for PS EhP4 Developments

• Message number: 120

• Message text: &2 &1: Changes are not saved to the operative project

What causes this issue?

The changes are not saved to the operative project because of
restrictions in drafts. For more information, see
<DS:TX.DRAFT_RESTRICTIONS>Considerations for Draft Handling</>.

System Response

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

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PSHLP_MSG_CL120 - &2 &1: Changes are not saved to the operative project ?

  The SAP error message PSHLP_MSG_CL120 with the text "Changes are not saved to the operative project" typically occurs in the context of Project System (PS) when there are issues related to saving changes made to an operative project. Here are some common causes, solutions, and related information for this error:
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to make changes to the operative project.
  Project Status: The project might be in a status that does not allow changes (e.g., "Completed" or "Closed").
  Locking Issues: The project or certain elements of the project may be locked by another user or process.
  Data Consistency: There may be inconsistencies in the data that prevent saving changes.
  Missing Required Fields: Certain mandatory fields may not be filled out, leading to a failure in saving changes.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to modify the project. This can be checked in transaction SU53 or by consulting with the security team.
  Review Project Status: Check the status of the project. If it is closed or completed, you may need to change its status to allow modifications. This can be done in transaction CJ02 (Change Project).
  Release Locks: If the project is locked, identify the user or process that has locked it. You can use transaction SM12 to view and delete locks if necessary.
  Data Validation: Review the data being entered for any inconsistencies or missing mandatory fields. Ensure all required fields are filled out correctly.
  Check for Errors: Look for any additional error messages or logs that may provide more context on why the changes are not being saved. This can be done in transaction SLG1 (Application Log).
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ02 (Change Project), CJ03 (Display Project), and SM12 (Display and Delete Locks).
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Documentation: Review the SAP Project System documentation for best practices on managing project statuses and authorizations.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or technical support team for further investigation.