How to Configure & Test RFC Connection in SAP - SM59. Details Last Updated: 08 January 2019. This tutorial is divided into 4 sections. Step 1: Setup an RFC connection. The RFC users must have the required authorizations in the trusting system (authorization object S_RFCACL). I'm debugging a solution where a program in one SAP system (A) calls a remote-enabled function module in a different SAP system (B) via RFC connection. Is there a way to 'test-run' the RFC from A. Stack Overflow. SAP: How to test an RFC from a remote system. Ask Question 5.
-->Lists high-level tasks to complete on the SAP system to create an RFC. Each task may involve very detailed procedures. As a result, we recommend contacting your SAP administrator to complete these tasks, or refer to the SAP guidance.
Create an RFC
Start the SAP GUI.
Go to Transaction SE37 (Function Builder), enter the RFC name, and click Create.
Enter an existing function group under which the RFC will be created, a short description for the RFC, and click Save.
In the Attributes tab, select the Remote-Enabled Module radio button.
In the Import tab, enter the import parameters. These parameters are used for passing the external data to the function module.
In the Export tab, enter the export parameters.
In the Changing tab, enter the changing parameters.
In the Tables tab, enter the table names.
In the Exceptions tab, enter the exceptions to handle errors.
In the Source Code tab, enter the source code (logic) for the RFC.
Click the Activate icon on the toolbar to activate the function module.
Create an RFC destination
Start the SAP GUI.
Go to Transaction SM59 (Display and Maintain RFC Destinations).
From the menu bar, click Create.
Enter the RFC destination, connection type, description, and then press Enter.
Select the Registered Server Program radio-button, enter the program ID, gateway host, and gateway service.
Save the RFC destination.
Send an RFC from an SAP system
Start the SAP GUI.
Create a logical system using BD54 transaction.
Create an RFC destination in TCP/IP connections using SM59 transaction.
Create a port using WE21 transaction and attach it to the RFC destination created in the last step.
Trigger an RFC by using SE37. This RFC must contain the logic to make an RFC call to an external application and then receive a response from that application.
See Also
As a SAP Administrator I often get questions on trusted RFC connections. I also noticed on the SCN forums that there are often questions regarding the setup.
All in all it’s not that hard but it’s like that with a lot of configurations and setups, you just have to know how to do it properly and it will cause less issues.
After you have set up a trust connection from AA1 to BB1 for example, you can access BB1 through AA1 without having to login again, given your username exists on both sides and you have sufficient authorizations.
In transaction SM59 you need to define a RFC connection towards the target system you want to enable as trusted in your source system.
For example:
On your source SAP system AA1 you want to setup a trusted RFC towards target system BB1. When it is done it would mean that when you are logged onto AA1 and your user has enough authorization in BB1, you can use the RFC connection and logon to BB1 without having to re-enter user and password .
In transaction SM59 on AA1 define an R3 type RFC connection(connection type 3) towards BB1.
Maintain the technical settings tab
Next go to the logon & security tab
Fill in details for logon
Choose the right option in MDMP & Unicode (is your target Unicode yes or no). We assume BB1 is Unicode in this example as it will be like that for most SAP system with a recent release level.
Now you can first test this RFC connection to see if it works, if you run into problems you need to fix them before continuing.
This can be done using Utilities -> Connection Test, Authorization Test and Unicode Test
Now the R3 RFC connection is made, we can continue to the next step. Go to transaction SMT1 and click the create button.
Fill in the previously created RFC connection name
Click yes
Now click the Maintain Destination button
This will take you back into SM59 destination BB1CLNT100
Change the Trusted System option to yes in the logon & security tab.
Yes
Remove the user from the logon and select “Current User”.
Result in SM59 destination BB1CLNT100
Setting the trusted system to yes and so on can be done directly when creating the RFC connection in SM59 but maintaining the destination when creating the entry in SMT1 avoids more issues in my opinion (you already know up front the connection itself works when you enter SMT1).
Sap Rfc Connection Test
Save the RFC connection
Now you have a trusted RFC connection. The current user flag checked means that the RFC connection will use the user-id of the person who is logged on and wants to use the RFC connection. This is for security reasons, you should not fill in a user/pass in a trusted RFC connection as it can be abused by other users that way.
Sap Check Rfc Connection
The necessary authorization to actually use this RFC connection has to be set in the target SAP system BB1 and of course in the client where the RFC is pointing to (client 100 in this example). Object S_RFCACL is the authorization object which needs to be maintained in BB1 client 100 for the user-ids that have to be able to use the trusted RFC connection from AA1 to BB1 client 100.
Sap Rfc Connection Security
The specifics for S_RFCACL depend on the SAP release version. For this a SAP note exists which has details on what should be set:
Note 128447 – Trusted/trusting systems
Sap Rfc Connection Transaction
Once you have created your trusted RFC you should also see BB1 in transaction SMT1 on SAP system AA1 and AA1 in transaction SMT2 (trusting SAP systems) on SAP system BB1. You can repeat the steps (switch AA1 and BB1) to configure a trusted RFC connection from BB1 to AA1 if wanted.