How To Fix RSDD113 - Aggregate &1(&2) is rolled up to &3

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDD - Message class for data manager

• Message number: 113

• Message text: Aggregate &1(&2) is rolled up to &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 RSDD113 - Aggregate &1(&2) is rolled up to &3 ?

  The SAP error message RSDD113 indicates that an aggregate (a pre-calculated summary of data) has been rolled up to a higher-level aggregate. This typically occurs in the context of SAP BW (Business Warehouse) when dealing with data aggregation and reporting.
  Cause:
  The error message RSDD113 is triggered when:
  
  An attempt is made to access or process data from an aggregate that has been rolled up to a higher-level aggregate.
  The data in the lower-level aggregate is no longer available because it has been consolidated into a higher-level aggregate.
  
  Solution:
  To resolve this issue, you can consider the following steps:
  
  
  Check Aggregate Status: Verify the status of the aggregates involved. You can do this by using transaction codes like RSA1 (Data Warehousing Workbench) to check the aggregates and their roll-up status.
  
  
  Rebuild Aggregates: If necessary, you may need to rebuild the aggregates. This can be done by:
  
  Going to the InfoCube or DataStore Object (DSO) in question.
  Selecting the aggregate and choosing the option to rebuild it.
  
  
  
  Adjust Queries: If you are running a query that is trying to access the rolled-up aggregate, consider adjusting the query to point to the higher-level aggregate instead.
  
  
  Data Load: Ensure that the data load process is completed successfully. Sometimes, aggregates may not be updated due to issues in the data loading process.
  
  
  Check for Locks: Ensure that there are no locks on the aggregates that might prevent access or updates.
  
  
  Consult Documentation: Refer to SAP documentation or support notes for any specific instructions related to your version of SAP BW.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 for data modeling and RSD1 for InfoObjects.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Performance Considerations: Understand that aggregates are used to improve query performance, and managing them effectively is crucial for optimal system performance.
  
  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.