How To Fix RSDRD122 - Selective Deletion on ADSO '&1' started in mode '&2'

RSDRD122 - Overview

• Message type: E = Error

• Message class: RSDRD - Messages for Delete Module

• Message number: 122

• Message text: Selective Deletion on ADSO '&1' started in mode '&2'

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 RSDRD122 - Selective Deletion on ADSO '&1' started in mode '&2' ?

  The SAP error message RSDRD122 indicates that a selective deletion process on an Advanced DataStore Object (ADSO) has been initiated, but it is currently running in a specific mode (indicated by '&2'). This message typically arises in the context of data management and data warehousing within SAP BW/4HANA or SAP BW on HANA environments.
  
  Cause:
  
  Ongoing Deletion Process: The error usually occurs when a selective deletion process is already in progress for the specified ADSO. This means that another deletion operation is currently being executed, and the system does not allow overlapping deletion processes to ensure data integrity.
  Locking Mechanism: SAP uses a locking mechanism to prevent multiple processes from modifying the same data simultaneously. If a deletion is already in progress, any new request for deletion will be blocked until the first one completes.
  
  
  Solution:
  
  Check Current Processes: Use transaction codes like SM37 (Job Monitoring) or SM21 (System Log) to check if there is