How To Fix RSDMDD_DELETE036 - Unused SID entries are deleted (see detail - max. 25000)

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDMDD_DELETE - Messages for Deleting Master Data

• Message number: 036

• Message text: Unused SID entries are deleted (see detail - max. 25000)

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_DELETE036 - Unused SID entries are deleted (see detail - max. 25000) ?

  The SAP error message RSDMDD_DELETE036 indicates that the system has detected unused SID (Surrogate ID) entries in the data warehouse and is in the process of deleting them. This is a part of the data management process in SAP BW (Business Warehouse) to maintain the integrity and performance of the data model.
  Cause:
  
  Unused SID Entries: The error message typically arises when there are SID entries that are no longer associated with any data records in the InfoObjects. This can happen due to data model changes, data deletions, or when data is archived.
  Data Model Changes: Changes in the data model, such as the deletion of InfoObjects or changes in the data flow, can lead to orphaned SID entries.
  Data Deletion: If data is deleted from the InfoProviders, the corresponding SID entries may remain in the SID tables, leading to an accumulation of unused entries.
  
  Solution:
  
  Automatic Deletion: The system is designed to automatically delete these unused SID entries. You may not need to take any action if the system is handling it correctly.
  Monitor the Process: Check the system logs or the process chain logs to ensure that the deletion process is completing successfully without errors.
  Manual Cleanup: If the automatic deletion does not resolve the issue or if you encounter performance issues, you may need to manually trigger a cleanup process. This can be done using transaction codes like:
  
  RSD1: To check the InfoObjects and their SID tables.
  RSD2: To analyze the SID tables.
  RSD3: To perform a manual cleanup of the SID tables.
  
  
  Data Consistency Check: Run consistency checks on your data model to ensure that all InfoObjects and their associated SID entries are correctly aligned.
  Adjust Data Load Processes: Review your data load processes to ensure that they are not leaving behind unused SID entries. This may involve adjusting your ETL (Extract, Transform, Load) processes.
  
  Related Information:
  
  SID Tables: SID tables are used in SAP BW to map the key figures and characteristics to their corresponding values. They help in optimizing the storage and retrieval of data.
  Performance Impact: Accumulation of unused SID entries can lead to performance degradation in reporting and data retrieval processes.
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or patches related to SID management and cleanup processes.
  Documentation: Refer to SAP BW documentation for best practices on data modeling and SID management.
  
  If the issue persists or if you encounter further complications, consider reaching out to SAP support for more tailored assistance.