How To Fix RSDME790 - Source &2 of Model &1 is detached from BW DataSource &3.

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDME -

• Message number: 790

• Message text: Source &2 of Model &1 is detached from BW DataSource &3.

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 RSDME790 - Source &2 of Model &1 is detached from BW DataSource &3. ?

  The SAP error message RSDME790 indicates that a source of a model in SAP BW (Business Warehouse) is detached from the associated DataSource. This typically occurs when there is a disconnection between the InfoProvider (like a CompositeProvider or a Query) and the underlying DataSource that feeds it with data.
  Cause:
  
  DataSource Deletion or Modification: The DataSource that the model is linked to may have been deleted or modified in a way that it is no longer compatible with the model.
  Transport Issues: If the DataSource was transported from one system to another (e.g., from development to production), it may not have been properly activated or may not exist in the target system.
  Model Configuration Changes: Changes in the model configuration or structure that do not align with the DataSource can lead to this error.
  Authorization Issues: Sometimes, authorization issues can prevent the model from accessing the DataSource.
  
  Solution:
  
  Check DataSource Status: Verify that the DataSource (in this case, &3) exists and is active in the system. You can do this by navigating to the DataSource in the Data Warehousing Workbench (transaction RSA1).
  Reattach the DataSource: If the DataSource is available but detached, you may need to reattach it to the model. This can usually be done in the model configuration settings.
  Review Transport Logs: If the issue arose after a transport, check the transport logs to ensure that the DataSource was transported correctly and is active in the target system.
  Check Model Configuration: Review the model configuration to ensure that it is correctly set up to use the DataSource. Make any necessary adjustments.
  Authorization Check: Ensure that the user has the necessary authorizations to access the DataSource and the model.
  Recreate the Model: If the above steps do not resolve the issue, consider recreating the model and linking it to the DataSource again.
  
  Related Information:
  
  Transaction Codes: Use transaction codes like RSA1 (Data Warehousing Workbench) to manage DataSources and models.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Refer to SAP BW documentation for detailed information on managing DataSources and models.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.