Do you have any question about this error?
Message type: E = Error
Message class: RSDD - Message class for data manager
Message number: 313
Message text: Hierarchy &1 of InfoObject &2 (aggregate &3) does not exist
This hierarchy may have been deleted in the meantime. When a hierarchy
is deleted, only the aggregate is deactivated and the definition
remains unchanged. Adjust the definition of the aggregate and then
resave.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
RSDD313
- Hierarchy &1 of InfoObject &2 (aggregate &3) does not exist ?The SAP error message RSDD313 indicates that a hierarchy for a specific InfoObject does not exist in the context of an aggregate. This error typically arises in the context of SAP BW (Business Warehouse) when working with aggregates and hierarchies.
Cause:
- Missing Hierarchy: The specified hierarchy for the InfoObject is not defined or has been deleted.
- Incorrect Aggregate Definition: The aggregate may reference a hierarchy that is not available or has not been activated.
- Transport Issues: If the InfoObject or hierarchy was transported from another system, it may not have been transported correctly.
- Data Model Changes: Changes in the data model, such as renaming or deleting InfoObjects or hierarchies, can lead to this error.
Solution:
Check Hierarchy Definition:
- Go to the InfoObject maintenance (transaction RSD1) and check if the hierarchy exists for the specified InfoObject.
- If it does not exist, you may need to create it.
Recreate or Activate Hierarchy:
- If the hierarchy exists but is inactive, activate it.
- If it has been deleted, you may need to recreate it based on your requirements.
Review Aggregate Settings:
- Check the aggregate definition (transaction RSD1) to ensure that it correctly references the existing hierarchy.
- If the aggregate is referencing a non-existent hierarchy, update the aggregate to point to the correct hierarchy.
Transport Check:
- If the hierarchy was supposed to be transported from another system, verify that the transport request was completed successfully and that all necessary objects were included.
Consistency Check:
- Run a consistency check on the InfoObject and aggregates to identify any inconsistencies that may need to be resolved.
Rebuild Aggregates:
- If necessary, you can rebuild the aggregates to ensure they are correctly aligned with the current state of the InfoObjects and hierarchies.
Related Information:
By following these steps, you should be able to resolve the RSDD313 error and ensure that your InfoObjects and hierarchies are correctly configured in SAP BW.
Get instant SAP help. Start your 7-day free trial now.
RSDD312
No SID for hierarchy '&3', InfoObject '&2' of aggregate '&1' (&4)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSDD311
No SID for fixed value '&3', InfoObject '&2' for aggregate '&1' (&4)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSDD314
Aggregation level "*" has been set for char. '&1' (aggregate '&3')
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSDD315
Hierarchy '&1' (characteristic &2; aggr. '&3') is not stored generically
What causes this issue? Hierarchy &V1& of characteristic &V2& in aggregate &V3& is not stored generically. The system therefo...
Click on this link to search all SAP messages.