How To Fix RSDA385 - No archiving requests are flagged for deletion for DAP &1

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDA - BW Archiving: Messages

• Message number: 385

• Message text: No archiving requests are flagged for deletion for DAP &1

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 RSDA385 - No archiving requests are flagged for deletion for DAP &1 ?

  The SAP error message RSDA385 indicates that there are no archiving requests flagged for deletion for the specified Data Archiving Object (DAP) in the system. This message typically arises when you attempt to delete archiving requests that have not been marked for deletion.
  Cause:
  
  
  No Requests Flagged for Deletion: The primary cause of this error is that there are no archiving requests in the system that have been marked for deletion. This can happen if:
  
  The archiving process has not been executed properly.
  The requests were not flagged for deletion after archiving.
  The requests have already been deleted or processed.
  
  
  
  Incorrect Object Specification: The specified Data Archiving Object (DAP) might not have any associated archiving requests.
  
  
  Solution:
  To resolve this issue, you can follow these steps:
  
  
  Check Archiving Requests:
  
  Go to the transaction code SARA (Archive Administration).
  Select the relevant Data Archiving Object (DAP) and check the status of the archiving requests.
  Ensure that there are archiving requests available and that they are correctly flagged for deletion.
  
  
  
  Flag Requests for Deletion:
  
  If there are archiving requests that need to be deleted, you can manually flag them for deletion.
  In the SARA transaction, select the archiving requests and use the option to flag them for deletion.
  
  
  
  Run Archiving Process:
  
  If no archiving requests exist, you may need to run the archiving process again to create new requests.
  Ensure that the archiving process completes successfully and that requests are generated.
  
  
  
  Check Authorization:
  
  Ensure that you have the necessary authorizations to view and delete archiving requests.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to archiving for specific guidance on the Data Archiving Object you are working with.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SARA: Archive Administration
  SARI: Archive Information System
  SAD1: Archive Deletion
  
  
  SAP Notes: Check for any relevant SAP Notes that might address specific issues related to archiving for your version of SAP.
  Archiving Process: Familiarize yourself with the archiving process in SAP, including how to create, manage, and delete archiving requests.
  
  If the issue persists after following these steps, consider reaching out to your SAP Basis or technical support team for further assistance.