How To Fix RSDA354 - Could not find any archiving requests for copying to near-line storage

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDA - BW Archiving: Messages

• Message number: 354

• Message text: Could not find any archiving requests for copying to near-line storage

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 RSDA354 - Could not find any archiving requests for copying to near-line storage ?

  The SAP error message RSDA354 indicates that the system could not find any archiving requests that are eligible for copying to near-line storage (NLS). This typically occurs in the context of data archiving and management, particularly when using the Near-Line Storage feature in SAP.
  Cause:
  
  No Archiving Requests: There may not be any archiving requests available for the specified criteria or selection parameters.
  Incorrect Selection Criteria: The selection criteria used to find archiving requests may be too restrictive or incorrect, leading to no results being found.
  Archiving Process Not Completed: The archiving process may not have been completed successfully, or there may be no data that has been archived yet.
  Configuration Issues: There may be configuration issues with the Near-Line Storage setup or the archiving object.
  Data Retention Policies: The data retention policies may not allow for the archiving of certain data, leading to no eligible requests.
  
  Solution:
  
  Check Archiving Requests: Verify if there are any archiving requests available. You can do this by checking the relevant archiving logs or using transaction codes like SARA (Archive Administration).
  Review Selection Criteria: Ensure that the selection criteria used for copying to NLS are correct and not overly restrictive. Adjust the parameters if necessary.
  Complete Archiving Process: If the archiving process has not been completed, ensure that it is executed successfully. You may need to run the archiving job again.
  Check Configuration: Review the configuration settings for Near-Line Storage and ensure that they are set up correctly. This includes checking the connection to the NLS system and the relevant archiving objects.
  Consult Documentation: Refer to SAP documentation or notes related to the specific archiving object you are working with to ensure that all prerequisites and configurations are met.
  Check for Errors: Look for any errors in the archiving logs that might indicate why requests are not being found or processed.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SARA (for archiving), SARI (for managing NLS), and SLG1 (for application logs) to troubleshoot and manage archiving processes.
  SAP Notes: Check SAP Notes for any known issues or updates related to the specific archiving object or NLS functionality.
  Documentation: Review SAP Help documentation for detailed guidance on configuring and using Near-Line Storage and archiving processes.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or technical team for further investigation.