How To Fix RSDA150 - Not all requests have been rolled up to subsequent aggregates

RSDA150 - Overview

• Message type: E = Error

• Message class: RSDA - BW Archiving: Messages

• Message number: 150

• Message text: Not all requests have been rolled up to subsequent aggregates

What causes this issue?

The InfoCube &v1&contains &v2& data records in the selections for the
current archiving request that have not been rolled up to subsequent
aggregates. &v3& request(s) are affected. If you want uncompressed time
slice archiving, you first need to roll up all the data, to be archived,
to all subsequent aggregates.

System Response

The archiving session is terminated.

How to fix this error?

First roll up all the requests up to the request with the SID &v4& to
all subsequent aggregates and then start the archiving session again.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSDA150 - Not all requests have been rolled up to subsequent aggregates ?

  The SAP error message RSDA150 indicates that not all requests have been rolled up to subsequent aggregates in the context of data warehousing, specifically within the SAP BW (Business Warehouse) environment. This error typically occurs during the process of data aggregation, where data from lower-level InfoProviders (like DataStore Objects or InfoCubes) is being summarized into higher-level aggregates.
  
  Cause:
  The error can be caused by several factors, including:
  
  
  Incomplete Data Load: Some data requests may not have been successfully loaded into the InfoProvider, leading to missing data that cannot be aggregated.
  
  
  Data Consistency Issues: There may be inconsistencies in the data, such as missing keys or incorrect data formats, which prevent the successful aggregation of requests.
  
  
  Aggregation Settings: The settings for the aggregates may not be correctly configured, leading to issues when trying to roll up data.
  
  
  Request Status: The status of the data requests may not be in a state that allows for aggregation (e.g., requests