How To Fix RSDMDD_DELETE058 - Number of records selected for usage check : &1.

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDMDD_DELETE - Messages for Deleting Master Data

• Message number: 058

• Message text: Number of records selected for usage check : &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 RSDMDD_DELETE058 - Number of records selected for usage check : &1. ?

  The SAP error message RSDMDD_DELETE058 typically occurs in the context of data management in SAP BW (Business Warehouse) when you are trying to delete or manage data in InfoProviders, such as InfoCubes or DataStore Objects (DSOs). The message indicates that a certain number of records have been selected for a usage check, which may be related to the deletion of data or the management of data models.
  Cause:
  The error message RSDMDD_DELETE058 is generally triggered when:
  
  Data Usage Check: The system is performing a check to see how many records are being used in other objects (like queries, reports, or other InfoProviders) before allowing deletion.
  Data Dependencies: There are dependencies or references to the records you are trying to delete, which prevents the operation from completing successfully.
  Configuration Issues: There may be configuration issues in the InfoProvider or the data model that are causing the system to misinterpret the usage of the records.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Dependencies: Investigate the dependencies of the records you are trying to delete. Use transaction codes like RSA1 (Data Warehousing Workbench) to analyze the InfoProvider and see where the data is being used.
  
  
  Usage Analysis: Use the "Usage Analysis" feature in the Data Warehousing Workbench to identify which queries or reports are using the records. This can help you understand why the deletion is being blocked.
  
  
  Data Cleanup: If the records are indeed being used, you may need to clean up or modify the dependent objects before attempting to delete the records again.
  
  
  Adjust Settings: If you believe the records should be deletable, check the settings of the InfoProvider and ensure that there are no restrictions or locks preventing the deletion.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific InfoProvider or the error message for additional guidance.
  
  
  Contact SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench), RSD1 (InfoObject Maintenance), and RSD5 (DataSource Maintenance).
  SAP Notes: Check for any SAP Notes related to RSDMDD_DELETE058 for specific patches or updates that may address the issue.
  Data Model Documentation: Review the documentation for your specific data model to understand how data is structured and managed within your BW environment.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.