How To Fix PSISSO022 - Exceptions were not changed

SAP Error Message - Details

• Message type: E = Error

• Message class: PSISSO - PS Logistic Information System: Individual Overviews

• Message number: 022

• Message text: Exceptions were not 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 PSISSO022 - Exceptions were not changed ?

  The SAP error message PSISSO022, which states "Exceptions were not changed," typically occurs in the context of the SAP Project System (PS) module. This error can arise when there are issues related to the handling of exceptions in project management, particularly when trying to change or update exceptions for a project or a network.
  Causes:
  
  Authorization Issues: The user may not have the necessary authorizations to change exceptions in the project.
  Status of the Project: The project or network might be in a status that does not allow changes to exceptions (e.g., if it is locked or in a closed status).
  Data Integrity Issues: There may be inconsistencies or issues with the data related to the project or network that prevent changes from being made.
  Technical Errors: There could be underlying technical issues, such as problems with the database or application logic.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to make changes to exceptions. This can be done by reviewing the user's roles and permissions in the SAP system.
  Review Project Status: Check the status of the project or network. If it is locked or in a closed status, you may need to unlock it or change its status to allow modifications.
  Data Consistency Check: Perform a data consistency check to identify any issues with the project or network data. This may involve using transaction codes like CJ20N (Project Builder) to review the project structure and data.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
  Technical Support: If the issue persists, consider reaching out to your SAP support team or consulting with SAP support for further assistance. They may be able to provide insights based on system logs or specific configurations.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ20N (Project Builder), CJ02 (Change Project), and CJ03 (Display Project) to navigate and manage project data effectively.
  SAP Documentation: Review SAP documentation related to the Project System module for best practices and guidelines on managing exceptions and project data.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to diagnose and resolve the PSISSO022 error effectively.