How To Fix RSDD815 - Check of aggregate &1 in mode '&2' started

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDD - Message class for data manager

• Message number: 815

• Message text: Check of aggregate &1 in mode '&2' started

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 RSDD815 - Check of aggregate &1 in mode '&2' started ?

  The SAP error message RSDD815 typically relates to issues with aggregates in the SAP BW (Business Warehouse) environment. This message indicates that there is a problem with the check of an aggregate, which can occur during various operations such as loading data, querying, or during the maintenance of aggregates.
  Cause:
  The error message RSDD815 can be triggered by several factors, including:
  
  Corrupted Aggregate: The aggregate may be corrupted or not properly defined.
  Inconsistent Data: There may be inconsistencies in the data that the aggregate is supposed to summarize.
  Missing Data: Required data for the aggregate may be missing or not loaded correctly.
  Configuration Issues: There may be configuration issues in the InfoCube or the aggregate itself.
  Performance Issues: If the system is under heavy load, it may not be able to process the aggregate check properly.
  
  Solution:
  To resolve the RSDD815 error, you can follow these steps:
  
  
  Check Aggregate Status: Use transaction code RSA1 to check the status of the aggregate. Look for any inconsistencies or errors in the aggregate definition.
  
  
  Rebuild the Aggregate: If the aggregate is corrupted, you may need to rebuild it. You can do this by:
  
  Deleting the existing aggregate.
  Recreating it using the appropriate settings.
  
  
  
  Check Data Consistency: Ensure that the data in the InfoCube is consistent. You can use the RSA1 transaction to check for data inconsistencies and perform data repairs if necessary.
  
  
  Load Missing Data: If there is missing data, ensure that all necessary data loads are completed successfully.
  
  
  Check for Locks: Sometimes, locks on the InfoCube or aggregates can cause issues. Check for any locks and resolve them.
  
  
  Monitor System Performance: If the system is under heavy load, consider scheduling the aggregate check during off-peak hours.
  
  
  Review Logs: Check the system logs for any additional error messages or warnings that may provide more context about the issue.
  
  
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench), RSD1 (InfoObject Maintenance), and RSD3 (Aggregate Maintenance).
  SAP BW Documentation: Review SAP BW documentation for best practices on managing aggregates and troubleshooting common issues.
  SAP Community: Engage with the SAP Community forums for insights and solutions shared by other users who may have encountered similar issues.
  
  If the problem persists after following these steps, consider reaching out to SAP support for further assistance.