How To Fix RFM_PSST_MSG060 - No PSST group rules found for selected criteria.Enter different criteria.

SAP Error Message - Details

• Message type: E = Error

• Message class: RFM_PSST_MSG - Message Class for PSST

• Message number: 060

• Message text: No PSST group rules found for selected criteria.Enter different criteria.

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 RFM_PSST_MSG060 - No PSST group rules found for selected criteria.Enter different criteria. ?

  The SAP error message RFM_PSST_MSG060 indicates that there are no PSST (Project System Status Tracking) group rules found for the criteria you have selected. This typically occurs when you are trying to execute a report or transaction that relies on specific criteria to retrieve data related to project status tracking, but the system cannot find any matching rules.
  Causes:
  
  Incorrect Selection Criteria: The criteria you have entered may not match any existing PSST group rules. This could be due to incorrect values, such as project numbers, status types, or other parameters.
  Missing Configuration: The PSST group rules may not be configured properly in the system. This could mean that the necessary rules have not been defined or activated.
  Data Issues: There may be no data available in the system that meets the criteria you have specified, leading to the absence of matching rules.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view certain PSST group rules, which can lead to this error.
  
  Solutions:
  
  Check Selection Criteria: Review the criteria you have entered and ensure they are correct. Try using broader or different criteria to see if any results are returned.
  Review PSST Configuration: Check the configuration settings for PSST group rules in the system. Ensure that the necessary rules are defined and active. This may require access to the configuration settings in the SAP system.
  Consult with a Functional Consultant: If you are unsure about the configuration or the criteria, it may be helpful to consult with an SAP functional consultant who specializes in Project System (PS) or Status Tracking.
  Check for Data Availability: Ensure that there is relevant data in the system that matches your criteria. You may need to create or update project data to ensure it aligns with the PSST group rules.
  Authorization Check: Verify that you have the necessary authorizations to access the PSST group rules. If not, contact your system administrator to request the appropriate access.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes related to Project System and PSST, such as CJ20N (Project Builder) or CJI3 (Project Actual Line Items).
  Documentation: Refer to SAP documentation or help files for more information on PSST group rules and how they are configured.
  SAP Notes: Check SAP Notes for any known issues or updates related to the PSST functionality that may address this error.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.