How To Fix RSODSO_ROLLBACK274 - Flag "Delete Successfully Updated Requests Only" not set for pattern &1

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 274

• Message text: Flag "Delete Successfully Updated Requests Only" not set for pattern &1

What causes this issue?

During object transfer, a process variant of type "Deletion of Requests
from Write-Optimized DSO (classic)" was transferred to a process variant
of type "Deletion of Requests from DSO (advanced)". In the old variant,
removal of requests that had not yet been successfully updated was
possible if the "Delete Successfully Updated Requests Only" flag was not
checked. In the new variant, this is no longer possible, because the
restriction that requests can only be removed if they are
delta-transferred to all further data targets cannot be overruled for
DataStore objects (advanced).

System Response

The process variant transfer has been performed, but in the new variant
requests will only be removed if they are delta-transferred to all
further data targets. This also applies if the "Delete Successfully
Updated Requests Only" was not checked in the old variant.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSODSO_ROLLBACK274 - Flag "Delete Successfully Updated Requests Only" not set for pattern &1 ?

  The SAP error message RSODSO_ROLLBACK274 indicates that the flag "Delete Successfully Updated Requests Only" is not set for a specific data transfer process (DTP) pattern. This error typically occurs in the context of data extraction and loading processes in SAP BW (Business Warehouse) or SAP BW/4HANA.
  Cause:
  The error arises when you attempt to delete data requests from a DataStore Object (DSO) or InfoProvider, but the DTP is configured in such a way that it does not allow for the deletion of requests that have been successfully updated. The specific pattern mentioned in the error message refers to the DTP that is being used for the data transfer.
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check DTP Settings:
  
  Go to the Data Transfer Process (DTP) in the SAP BW system.
  Check the settings for the DTP related to the DSO or InfoProvider in question.
  Look for the option "Delete Successfully Updated Requests Only" and ensure that it is set according to your requirements.
  
  
  
  Modify DTP Configuration:
  
  If you want to allow the deletion of requests that have been successfully updated, you may need to enable the flag "Delete Successfully Updated Requests Only".
  If you do not want to delete successfully updated requests, you may need to adjust your process to handle the requests differently.
  
  
  
  Re-run the Process:
  
  After making the necessary changes to the DTP configuration, re-run the data loading or deletion process to see if the error persists.
  
  
  
  Check for Dependencies:
  
  Ensure that there are no dependencies or other processes that might be affecting the DTP or the requests you are trying to delete.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for more detailed information on DTP configurations and error handling.
  
  
  
  Related Information:
  
  Data Transfer Process (DTP): A DTP is a process in SAP BW that is used to transfer data from a source (like an InfoSource or another DSO) to a target (like a DSO or InfoCube).
  DataStore Object (DSO): A DSO is a type of data storage in SAP BW that allows for the storage of detailed transactional data.
  Error Handling: Understanding how to handle errors in SAP BW processes is crucial for maintaining data integrity and ensuring smooth data flows.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or BW team for further investigation, as there may be additional configurations or system-specific issues at play.