How To Fix RSDA384 - No archiving requests are flagged for deletion

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDA - BW Archiving: Messages

• Message number: 384

• Message text: No archiving requests are flagged for deletion

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 RSDA384 - No archiving requests are flagged for deletion ?

  The SAP error message RSDA384 indicates that there are no archiving requests flagged for deletion in the system. This message typically arises when you are trying to execute a deletion job for archiving requests, but the system does not find any requests that meet the criteria for deletion.
  Cause:
  
  No Requests Flagged for Deletion: The most straightforward cause is that there are simply no archiving requests that have been marked for deletion in the system.
  Incorrect Selection Criteria: The selection criteria used in the deletion job may not match any existing archiving requests.
  Archiving Requests Already Processed: All archiving requests may have already been processed or deleted, leaving none available for the deletion job.
  
  Solution:
  
  Check Archiving Requests: Verify if there are any archiving requests in the system. You can do this by navigating to the relevant transaction (e.g., SARA) and checking the status of archiving requests.
  Flag Requests for Deletion: If there are archiving requests that you want to delete, ensure that they are properly flagged for deletion. This can typically be done in the archiving administration transaction (SARA) by selecting the requests and choosing the option to flag them for deletion.
  Review Selection Criteria: If you are using specific selection criteria for the deletion job, review them to ensure they are correct and that they should match existing requests.
  Run the Job Again: After ensuring that there are archiving requests flagged for deletion, rerun the deletion job.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA (Archive Administration) and SARI (Archive Information System) for managing archiving requests.
  Archiving Process: Understand the overall archiving process in SAP, including how to create, manage, and delete archiving requests.
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions related to this error message.
  Documentation: Review SAP documentation or help files related to archiving and deletion processes for more detailed guidance.
  
  If the issue persists after following these steps, consider reaching out to your SAP Basis or technical support team for further assistance.