How To Fix RSDD813 - Aggregate &1: Characteristic/navigation attr. &2 no longer in InfoCube

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDD - Message class for data manager

• Message number: 813

• Message text: Aggregate &1: Characteristic/navigation attr. &2 no longer in InfoCube

What causes this issue?

Problems with activation, transport and content transfer may mean that
characteristics and navigation attributes appear in the modified version
of an aggregate definition (M version) that should not be there. For
example, characteristics from the units and package dimension
(RequestID, ChangeID, ...) and navigation attributes with aggregation
status "%" - these are not automatically included until the aggregate is
activated. They ought to then appear in the A version of the aggregate
(that is, the active version). In aggregate maintenance (transaction
RSDDV), only the M version for an aggregate is displayed.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSDD813 - Aggregate &1: Characteristic/navigation attr. &2 no longer in InfoCube ?

  The SAP error message RSDD813 indicates that there is an issue with an aggregate in the SAP BW (Business Warehouse) system. Specifically, it means that a characteristic or navigation attribute that is part of the aggregate is no longer present in the associated InfoCube. This can happen for several reasons, such as changes in the InfoCube structure, deletion of characteristics, or modifications in the data model.
  Cause:
  
  Deletion of Characteristics: The characteristic or navigation attribute referenced in the error message has been deleted from the InfoCube.
  Changes in InfoCube Structure: The structure of the InfoCube has been modified, and the characteristic is no longer part of it.
  Inconsistent Metadata: There may be inconsistencies in the metadata between the aggregate and the InfoCube.
  Transport Issues: If changes were transported from one system to another, there might be inconsistencies due to incomplete transports.
  
  Solution:
  To resolve the RSDD813 error, you can follow these steps:
  
  
  Check the InfoCube Structure:
  
  Go to the InfoCube in the Data Warehousing Workbench (transaction RSA1).
  Verify if the characteristic or navigation attribute mentioned in the error message is still part of the InfoCube.
  
  
  
  Adjust the Aggregate:
  
  If the characteristic has been deleted or is no longer needed, you may need to adjust the aggregate.
  You can do this by going to the aggregate in the Data Warehousing Workbench and removing the characteristic or navigation attribute that is causing the issue.
  
  
  
  Rebuild the Aggregate:
  
  If necessary, you can delete the aggregate and recreate it. This will ensure that it is aligned with the current structure of the InfoCube.
  
  
  
  Check for Transport Issues:
  
  If the issue arose after a transport, ensure that all related objects were transported correctly and that there are no inconsistencies.
  
  
  
  Activate the InfoCube and Aggregate:
  
  After making changes, make sure to activate the InfoCube and the aggregate to ensure that the changes take effect.
  
  
  
  Check for Dependencies:
  
  Review any queries or reports that may depend on the aggregate to ensure they are still valid after the changes.
  
  
  
  Related Information:
  
  Transaction Codes: Use transaction RSA1 for the Data Warehousing Workbench, and transaction RSD1 for InfoCubes.
  Documentation: Refer to SAP Help documentation for more details on aggregates and InfoCubes.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to aggregates and InfoCubes.
  
  By following these steps, you should be able to resolve the RSDD813 error and ensure that your aggregates are functioning correctly with the InfoCubes in your SAP BW system.