How To Fix RSDD704 - __Aggregate &1 is better/smaller than the previous "best"

RSDD704 - Overview

• Message type: E = Error

• Message class: RSDD - Message class for data manager

• Message number: 704

• Message text: __Aggregate &1 is better/smaller than the previous "best"

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 RSDD704 - __Aggregate &1 is better/smaller than the previous "best" ?

  The SAP error message RSDD704 indicates that there is an issue with the aggregation level in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence). This message typically arises during the process of data aggregation or when working with InfoProviders, particularly when the system is trying to determine the best aggregation level for a query or data model.
  
  Cause:
  The error message "Aggregate &1 is better/smaller than the previous 'best'" suggests that the system has encountered an aggregation level that is more efficient or smaller than the previously determined best aggregation level. This can happen due to various reasons, including:
  
  Changes in Data Model: Modifications in the underlying data model or InfoObjects that affect the aggregation levels.
  Inconsistent Aggregation Levels: Different aggregation levels being defined for the same InfoProvider or query.
  Performance Optimization: The system is trying to optimize performance by selecting the most efficient aggregation level, but it encounters conflicting definitions.
  
  
  Solution:
  To