How To Fix RSODSO_ROLLBACK021 - DSO &1 does not contain sufficiently old requests

SAP Error Message - Details

• Message type: E = Error

• Message class: RSODSO_ROLLBACK - DataStore Object: Messages for rollback

• Message number: 021

• Message text: DSO &1 does not contain sufficiently old requests

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 RSODSO_ROLLBACK021 - DSO &1 does not contain sufficiently old requests ?

  The SAP error message RSODSO_ROLLBACK021 indicates that a DataStore Object (DSO) does not contain sufficiently old requests for a rollback operation. This typically occurs when you are trying to roll back a request in a DSO, but the request you are trying to roll back is not available in the DSO's request history.
  Cause:
  
  Request Deletion: The request you are trying to roll back may have been deleted or purged from the DSO.
  Request Age: The request may not be old enough to be eligible for rollback. DSOs often have settings that limit the rollback capability to only certain requests based on their age.
  Data Management Settings: The DSO may have specific settings that restrict the rollback functionality, such as retention periods or data management policies.
  
  Solution:
  
  Check Request History: Verify the request history of the DSO to see if the request you are trying to roll back is still available. You can do this by navigating to the DSO in the SAP BW system and checking the request logs.
  Adjust Rollback Settings: If the DSO has specific settings that limit rollback capabilities, consider adjusting these settings if appropriate. This may involve changing retention periods or other data management configurations.
  Reprocess Data: If the request cannot be rolled back, you may need to reprocess the data manually. This could involve loading the data again or correcting any issues that led to the need for a rollback.
  Consult Documentation: Review the SAP documentation for your specific version of BW to understand the limitations and configurations related to rollback operations in DSOs.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like RSA1 (Data Warehousing Workbench) to manage and monitor your DSOs.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on managing DSOs and rollback operations.
  Data Management Best Practices: Familiarize yourself with best practices for data management in SAP BW, including how to handle requests, rollbacks, and data retention policies.
  
  If the issue persists after following these steps, consider reaching out to your SAP support team or consulting with an SAP BW expert for further assistance.