How To Fix RSDD737 - Aggregate is structured by fragment

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDD - Message class for data manager

• Message number: 737

• Message text: Aggregate is structured by fragment

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 RSDD737 - Aggregate is structured by fragment ?

  The SAP error message RSDD737, which states "Aggregate is structured by fragment," typically occurs in the context of SAP BW (Business Warehouse) when there is an issue with the structure of an aggregate. This error indicates that the aggregate is not properly defined or is fragmented, which can lead to performance issues or incorrect data retrieval.
  Cause:
  
  Fragmented Aggregates: The aggregate may be defined in a way that it is split into multiple fragments, which can happen if the underlying data model has changed or if there are inconsistencies in the definitions.
  Inconsistent InfoObjects: If the InfoObjects used in the aggregate have been modified or are inconsistent with the aggregate definition, it can lead to this error.
  Data Model Changes: Changes in the underlying data model, such as the addition or removal of characteristics or key figures, can cause aggregates to become fragmented.
  Incorrect Aggregation Levels: If the aggregation levels are not properly aligned with the data model, it can lead to structural issues.
  
  Solution:
  
  Check Aggregate Definition: Review the definition of the aggregate in the SAP BW system. Ensure that it is correctly defined and that all necessary InfoObjects are included.
  Rebuild the Aggregate: If the aggregate is fragmented, consider rebuilding it. This can be done by deleting the existing aggregate and creating a new one based on the current data model.
  Consistency Check: Perform a consistency check on the InfoObjects and the aggregate. This can help identify any inconsistencies that need to be resolved.
  Adjust Aggregation Levels: Ensure that the aggregation levels are correctly defined and aligned with the data model. Adjust them if necessary.
  Transport Requests: If the issue arose after a transport, check if the transport request included all necessary objects and that they are in sync with the target system.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like RSA1 (Data Warehousing Workbench) to manage aggregates and InfoObjects.
  SAP Notes: Check for relevant SAP Notes that may address specific issues related to aggregates and fragmentation.
  Performance Monitoring: Monitor the performance of aggregates and consider using the BW Statistics to identify any performance bottlenecks related to aggregates.
  Documentation: Refer to SAP documentation for best practices on managing aggregates and InfoObjects in BW.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with SAP support or a BW expert for further assistance.