How To Fix TG780 - *** RDDPURIF: cleanup system before switch

TG780 - Overview

• Message type: E = Error

• Message class: TG - Messages for Upgrade Repository Switch

• Message number: 780

• Message text: *** RDDPURIF: cleanup system before switch

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 TG780 - *** RDDPURIF: cleanup system before switch ?

  The SAP error message TG780, specifically "RDDPURIF: cleanup system before switch," typically indicates that there are issues related to the system's background job processing or the state of the system that needs to be addressed before proceeding with a switch operation, such as a system upgrade or a transport request.
  
  Cause:
  
  Background Jobs: There may be background jobs that are still running or have not been properly completed. This can prevent the system from switching to a new state.
  Incomplete Cleanup: The system may have not been properly cleaned up after previous operations, leading to residual data or jobs that need to be addressed.
  Lock Entries: There might be lock entries in the database that are preventing the switch from occurring.
  Transport Requests: Pending or incomplete transport requests can also lead to this error.
  
  
  Solution:
  
  
  Check Background Jobs: 
  
  Use transaction code SM37 to check for any running or failed background jobs. Ensure that all jobs are completed