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

RSDME790 - Overview

• 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