How To Fix FDT_DSM003 - RFC connection &1 is not of type 'ABAP Connection'

SAP Error Message - Details

• Message type: E = Error

• Message class: FDT_DSM - BRFplus: Decision Service Manager

• Message number: 003

• Message text: RFC connection &1 is not of type 'ABAP Connection'

What causes this issue?

You have tried to set up a managed system with a reference to RFC
connection &v1&. However, the system has determined that this connection
is not of type 'ABAP connection' (type 3). In an ABAP system
environment, this is not permitted. If, however, the managed system
contains a partner module, choosing a different connection type is
possible, but requires additional steps as described below.

System Response

The managed system cannot be created.

How to fix this error?

If you have chosen the non-ABAP connection by accident, change it to
'ABAP connection'.
If you want to connect a partner module for extended programming
language support to the managed system, you may keep the connection type
as it is. However, be sure to click into the <LS>RFC Destination</>
entry field and choose <LS>Enter</>. The system then displays an
additional entry field, <LS>Partner Exit</>. Here, enter the name of the
ABAP OO class that you have used to implement the partner exit.

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 FDT_DSM003 - RFC connection &1 is not of type 'ABAP Connection' ?

  The SAP error message FDT_DSM003 indicates that there is an issue with the RFC (Remote Function Call) connection being used in your SAP system. Specifically, the error states that the RFC connection is not of type 'ABAP Connection', which is required for certain operations, particularly those involving the Function Module or Data Services.
  Cause:
  
  Incorrect RFC Connection Type: The RFC connection you are trying to use is not configured as an ABAP connection. This can happen if the connection is set up as a different type, such as a TCP/IP connection or a non-ABAP connection.
  Configuration Issues: There may be misconfigurations in the RFC destination settings in transaction SM59.
  System Compatibility: The system you are trying to connect to may not support ABAP connections, or there may be a version mismatch.
  Network Issues: There could be network-related issues preventing the proper establishment of the connection.
  
  Solution:
  
  
  Check RFC Destination:
  
  Go to transaction SM59 in your SAP system.
  Locate the RFC destination that is causing the issue.
  Ensure that the connection type is set to 'ABAP Connection'. If it is not, you will need to create a new RFC destination with the correct type.
  
  
  
  Create/Modify RFC Destination:
  
  If the existing connection is incorrect, you can either modify it or create a new one:
  
  Click on "Create" or "Change" in SM59.
  Set the connection type to 'ABAP Connection'.
  Fill in the necessary details such as target host, system number, client, user, password, etc.
  Test the connection to ensure it is working properly.
  
  
  
  
  
  Check Authorization:
  
  Ensure that the user credentials used in the RFC connection have the necessary authorizations to perform the required operations.
  
  
  
  Network Configuration:
  
  Verify that there are no network issues preventing the connection. Check firewalls, VPNs, or any other network configurations that might block the connection.
  
  
  
  Consult Documentation:
  
  If you are unsure about the settings, refer to SAP documentation or consult with your SAP Basis team for guidance on setting up RFC connections.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM59: To manage RFC destinations.
  ST22: To check for dumps that might provide more context on the error.
  SLG1: To check application logs for any related messages.
  
  
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  
  
  SAP Community: Consider searching or posting in the SAP Community forums for insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to resolve the FDT_DSM003 error and establish a proper ABAP connection.