How To Fix RSDTM108 - No external hierarchy found for source system "&2", InfoSource "&1"

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDTM - Data Mining Connection Messages

• Message number: 108

• Message text: No external hierarchy found for source system "&2", InfoSource "&1"

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 RSDTM108 - No external hierarchy found for source system "&2", InfoSource "&1" ?

  The SAP error message RSDTM108 indicates that there is no external hierarchy found for a specified source system and InfoSource. This error typically occurs in the context of SAP BW (Business Warehouse) when trying to load or process data that relies on external hierarchies.
  Cause:
  
  Missing Hierarchy: The most common cause of this error is that the external hierarchy for the specified InfoSource does not exist in the system.
  Incorrect Configuration: The InfoSource may not be properly configured to reference the external hierarchy.
  Source System Issues: There may be issues with the source system connection or configuration that prevent the retrieval of the hierarchy.
  Transport Issues: If the InfoSource or hierarchy was recently transported from another system, it may not have been transported correctly.
  
  Solution:
  
  
  Check Hierarchy Configuration:
  
  Go to the hierarchy maintenance transaction (e.g., RSH1) and verify that the external hierarchy for the specified InfoSource exists.
  If it does not exist, you may need to create it or ensure that it is properly defined.
  
  
  
  Verify InfoSource Settings:
  
  Check the settings of the InfoSource in the Data Warehousing Workbench (transaction RSA1) to ensure that it is correctly configured to use the external hierarchy.
  Ensure that the InfoSource is linked to the correct source system.
  
  
  
  Check Source System Connection:
  
  Verify that the connection to the source system is active and functioning correctly. You can do this by checking the RFC connections in transaction SM59.
  Test the connection to ensure that it can retrieve data from the source system.
  
  
  
  Transport Issues:
  
  If the InfoSource or hierarchy was recently transported, check the transport logs to ensure that there were no errors during the transport process.
  If necessary, re-transport the hierarchy or InfoSource.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific InfoSource and external hierarchy to ensure that all prerequisites and configurations are met.
  
  
  
  Check Authorizations:
  
  Ensure that the user executing the data load has the necessary authorizations to access the external hierarchy.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  RSA1: Data Warehousing Workbench
  RSH1: Hierarchy Maintenance
  SM59: RFC Destinations
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address specific issues related to this error message.
  SAP Community: Consider checking the SAP Community forums for discussions related to this error, as other users may have encountered and resolved similar issues.
  
  By following these steps, you should be able to identify the cause of the RSDTM108 error and implement a solution to resolve it.