How To Fix RSM028 - Cannot find entries to be deleted from RSSDLINIT with these selections

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM -

• Message number: 028

• Message text: Cannot find entries to be deleted from RSSDLINIT with these selections

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 RSM028 - Cannot find entries to be deleted from RSSDLINIT with these selections ?

  The SAP error message RSM028, which states "Cannot find entries to be deleted from RSSDLINIT with these selections," typically occurs in the context of data archiving or deletion processes in SAP systems, particularly when dealing with the Data Archiving Workbench or similar functionalities.
  Cause:
  
  No Matching Entries: The primary cause of this error is that the system cannot find any entries in the RSSDLINIT table that match the selection criteria specified in the deletion or archiving request.
  Incorrect Selection Criteria: The selection criteria used for the deletion process may be too restrictive or incorrect, leading to no entries being found.
  Data Already Deleted: The entries you are trying to delete may have already been deleted or archived in a previous run.
  Authorization Issues: There may be authorization issues preventing the system from accessing the necessary data.
  Configuration Issues: There could be configuration issues in the archiving object or the related settings.
  
  Solution:
  
  Check Selection Criteria: Review the selection criteria you are using for the deletion process. Ensure that they are correct and not overly restrictive.
  Verify Data Existence: Use transaction codes like SARA (Archive Administration) to check if there are indeed entries in the RSSDLINIT table that match your criteria. You can also check the relevant application tables to see if the data exists.
  Review Previous Runs: Check if the data has already been archived or deleted in previous runs. You can do this by reviewing the logs of previous archiving jobs.
  Authorization Check: Ensure that you have the necessary authorizations to perform the deletion. You may need to consult with your SAP security team.
  Consult Documentation: Review the documentation for the specific archiving object you are working with to ensure that all configurations are correct.
  SAP Notes: Check for any relevant SAP Notes that might address this issue. Sometimes, specific bugs or issues are documented by SAP, along with recommended solutions or patches.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA (for archiving), SARI (for restoring), and SLG1 (for viewing application logs).
  SAP Help Portal: Utilize the SAP Help Portal for detailed documentation on archiving and deletion processes.
  Community Forums: Consider checking SAP Community forums or other user groups for similar issues and solutions shared by other users.
  System Logs: Review system logs for any additional error messages or warnings that might provide more context about the issue.
  
  If the problem persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.