How To Fix RSOBI_MF168 - No RFC connection stored; see long text

SAP Error Message - Details

• Message type: E = Error

• Message class: RSOBI_MF - Messages for SOBI Model Factory

• Message number: 168

• Message text: No RFC connection stored; see long text

What causes this issue?

During the generation, a connection to a J2EE Engine is created. To do
this, a RFC connection must be set up. The name of the RFC connection is
stored in the global settings of the Data Warehousing Workbench.

System Response

A model generation cannot be executed.

How to fix this error?

Set up an RFC connection to a J2EE Engine. Store the name of the RFC
connection in the global settings of the Data Warehousing Workbench.

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSOBI_MF168 - No RFC connection stored; see long text ?

  The SAP error message RSOBI_MF168 "No RFC connection stored; see long text" typically occurs in the context of using the SAP Business Warehouse (BW) or when trying to execute certain functions that require a Remote Function Call (RFC) connection. This error indicates that the system is unable to find a valid RFC connection to the target system or service that it needs to communicate with.
  Cause:
  
  Missing RFC Connection: The most common cause is that the required RFC connection has not been created or is not properly configured in the SAP system.
  Incorrect Configuration: The RFC connection may exist but could be incorrectly configured (e.g., wrong target system, incorrect credentials).
  Authorization Issues: The user may not have the necessary authorizations to access the RFC connection.
  Network Issues: There could be network connectivity issues preventing the SAP system from reaching the target system.
  
  Solution:
  
  
  Create or Check RFC Connection:
  
  Go to transaction code SM59 in the SAP GUI.
  Check if the required RFC connection exists. If it does not, create a new RFC connection.
  If it exists, verify that the connection parameters (such as target host, system number, client, user, and password) are correct.
  
  
  
  Test the RFC Connection:
  
  In transaction SM59, select the RFC connection and use the "Test Connection" button to ensure that the connection is working properly.
  If the test fails, check the error message for more details and troubleshoot accordingly.
  
  
  
  Check Authorizations:
  
  Ensure that the user executing the transaction has the necessary authorizations to use the RFC connection.
  
  
  
  Review Network Configuration:
  
  If the RFC connection is configured correctly but still fails, check for any network issues that might be preventing communication between the systems.
  
  
  
  Consult Long Text:
  
  The error message suggests checking the long text for more details. You can do this by clicking on the message or using transaction SE91 to look up the message and its long text for additional context.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM59: To manage and test RFC connections.
  SE91: To view and manage message classes and messages.
  
  
  
  Documentation: Refer to SAP Help documentation for more details on RFC connections and troubleshooting.
  
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address specific issues related to this error message.
  
  
  By following these steps, you should be able to resolve the RSOBI_MF168 error and establish the necessary RFC connection for your SAP processes.