How To Fix RSDD059 - Cannot create aggregates for InfoCube &1 type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDD - Message class for data manager

• Message number: 059

• Message text: Cannot create aggregates for InfoCube &1 type &2

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 RSDD059 - Cannot create aggregates for InfoCube &1 type &2 ?

  The SAP error message RSDD059, which states "Cannot create aggregates for InfoCube &1 type &2," typically occurs in the context of SAP BW (Business Warehouse) when there is an issue with creating aggregates for a specific InfoCube. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  Data Model Issues: The InfoCube may have inconsistencies or issues in its data model, such as missing or incorrect characteristics, key figures, or dimensions.
  Data Volume: The volume of data in the InfoCube may be too large, leading to performance issues or timeouts during the aggregation process.
  Missing or Incorrect Aggregation Levels: The aggregation levels defined for the InfoCube may not be set up correctly, or there may be missing characteristics that are required for aggregation.
  Locking Issues: There may be locks on the InfoCube or related objects that prevent the aggregation process from completing.
  Technical Issues: There could be underlying technical issues, such as problems with the database or the BW system itself.
  
  Solutions:
  
  Check Data Model: Review the InfoCube's data model to ensure that all characteristics and key figures are correctly defined and that there are no inconsistencies.
  Review Aggregation Levels: Ensure that the aggregation levels are correctly defined and that all necessary characteristics are included.
  Data Volume Management: If the data volume is too large, consider partitioning the data or creating smaller aggregates to improve performance.
  Check Locks: Use transaction codes like SM12 to check for locks on the InfoCube and release any unnecessary locks.
  Rebuild Aggregates: If the aggregates are corrupted, you may need to delete and recreate them. This can be done through the InfoCube maintenance transaction.
  Monitor System Performance: Check the performance of the BW system and database to ensure that there are no underlying issues affecting the aggregation process.
  Consult Logs: Review the BW system logs for any additional error messages or warnings that may provide more context about the issue.
  
  Related Information:
  
  Transaction Codes: You may find it useful to use transaction codes such as RSA1 (Data Warehousing Workbench) to manage InfoCubes and aggregates.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Refer to SAP BW documentation for best practices on managing InfoCubes and aggregates, as well as performance tuning tips.
  
  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 and support.