How To Fix RSDD111 - Aggregate &1 is condensed to 0REQUID <= &2 and 0CNSID <= &3

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDD - Message class for data manager

• Message number: 111

• Message text: Aggregate &1 is condensed to 0REQUID <= &2 and 0CNSID <= &3

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 RSDD111 - Aggregate &1 is condensed to 0REQUID <= &2 and 0CNSID <= &3 ?

  The SAP error message RSDD111 indicates that an aggregate in the SAP BW (Business Warehouse) system has been condensed to a state where it no longer contains any data. This typically occurs when the aggregate is no longer relevant due to the data in the underlying InfoProvider or when the data has been deleted or filtered out.
  Cause:
  
  Data Deletion: The data that the aggregate was built upon has been deleted or filtered out, leading to an empty aggregate.
  Data Model Changes: Changes in the data model, such as changes in the InfoObjects or the underlying data sources, can lead to aggregates becoming irrelevant.
  Incorrect Aggregation Settings: If the aggregation settings are not correctly defined, it may lead to situations where the aggregate does not capture any data.
  Data Load Issues: If there were issues during the data load process, it could result in aggregates being created without any data.
  
  Solution:
  
  Check Data Availability: Verify that the underlying data in the InfoProvider is available and has not been deleted. You can do this by checking the relevant InfoProvider and ensuring that data exists for the specified time period.
  Rebuild the Aggregate: If the aggregate is indeed empty and no longer needed, you can delete it and recreate it. This can be done through the Aggregate Maintenance transaction (e.g., RSA1).
  Review Aggregation Settings: Ensure that the aggregation settings are correctly defined and that they align with the data model. Adjust the settings if necessary.
  Data Load Monitoring: Check the data load process to ensure that it is functioning correctly and that data is being loaded as expected. Look for any errors or warnings in the data load logs.
  Update Statistics: Sometimes, updating the statistics for the InfoProvider can help in resolving issues related to aggregates.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like RSA1 (Data Warehousing Workbench) to manage aggregates and InfoProviders.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to aggregates and data loading.
  Documentation: Refer to SAP BW documentation for best practices on managing aggregates and understanding their behavior in relation to data changes.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or BW team for further investigation.