How To Fix RFM_PSST_MSG066 - PSST group &1 &2 not destroyed due to runtime error.

RFM_PSST_MSG066 - Overview

• Message type: E = Error

• Message class: RFM_PSST_MSG - Message Class for PSST

• Message number: 066

• Message text: PSST group &1 &2 not destroyed due to runtime error.

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_MSG066 - PSST group &1 &2 not destroyed due to runtime error. ?

  The SAP error message RFM_PSST_MSG066 indicates that a PSST (Process Scheduling and Simulation Tool) group could not be destroyed due to a runtime error. This error typically occurs in the context of process scheduling or simulation tasks within SAP systems.
  
  Cause:
  The error can be caused by several factors, including but not limited to:
  
  Data Integrity Issues: There may be inconsistencies or corruption in the data associated with the PSST group.
  Locking Issues: The PSST group might be locked by another process, preventing it from being destroyed.
  Configuration Errors: Incorrect configuration settings related to the PSST group or its dependencies.
  System Resource Limitations: Insufficient system resources (memory, processing power) to complete the operation.
  Programming Errors: Bugs in the custom code or standard SAP code that handles the destruction of PSST groups.
  
  
  Solution:
  To resolve the issue, you can take the following steps:
  
  
  Check for Locks: Use transaction codes like SM12 to check if there are any locks on the PSST