How To Fix RSARCH235 - Records selected from requests (&1) that are not yet compressed

SAP Error Message - Details

• Message type: E = Error

• Message class: RSARCH - BW Archiving: News

• Message number: 235

• Message text: Records selected from requests (&1) that are not yet compressed

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 RSARCH235 - Records selected from requests (&1) that are not yet compressed ?

  The SAP error message RSARCH235 indicates that there are records selected from requests that have not yet been compressed. This typically occurs in the context of SAP's data archiving process, particularly when dealing with the archiving of data in the SAP system.
  Cause:
  The error message RSARCH235 is triggered when you attempt to access or process data that has been archived but not yet compressed. In SAP, archiving is a process that moves data from the database to an archive file, and compression is a subsequent step that reduces the size of the archived data. If the data has been archived but not compressed, it can lead to inconsistencies or issues when trying to access or manage that data.
  Solution:
  To resolve the RSARCH235 error, you can follow these steps:
  
  
  Check Archiving Status: Verify the status of the archiving process for the specific requests mentioned in the error message. You can do this by using transaction codes like SARA (Archive Administration) to check the status of the archived objects.
  
  
  Compress the Archived Data: If the data has been archived but not compressed, you need to run the compression process. This can typically be done using the transaction code SARA:
  
  Go to transaction SARA.
  Select the appropriate object for which the archiving was done.
  Choose the option to compress the archived data.
  
  
  
  Review Archiving Logs: Check the archiving logs for any errors or warnings that might indicate why the compression did not occur. This can provide insights into any underlying issues that need to be addressed.
  
  
  Re-run the Archiving Process: If necessary, you may need to re-run the archiving process for the affected requests to ensure that they are properly archived and compressed.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to archiving and compression for specific guidance and best practices.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA (Archive Administration), SARI (Archive Information System), and others that are used for managing archiving processes.
  SAP Notes: Check for any SAP Notes related to the RSARCH235 error for additional troubleshooting steps or patches that may address known issues.
  Archiving Strategy: Review your organization's archiving strategy to ensure that it includes regular compression of archived data to prevent similar issues in the future.
  
  By following these steps, you should be able to resolve the RSARCH235 error and ensure that your archived data is properly managed within the SAP system.