Trusted RFC connection with SAP Router string

[Former Member]

Hello!

We have defined a RFC connection with SAP router string between 2 SAP EHP4 systems.

Unfortunately the remote login function from these RFC connection does not work.

The user within RFC connection has the required authoritations (SAP_ALL, S_RFC, S_RFCACL).

Can some one help to solve this problem?

kind regards

[jrg_engel]

Hello,

if you have to use SAProuters for trusted system connections you have to read Note 128447 "Trusted/trusting systems" and maybe take care of the parameter rdisp/use_rfc_dest_lookup =ON from Note 555162 "Asynchronous RFCs with a dialog using a SAP router". Years ago this was the solution for us.

Kind regards

Joerg

[Former Member]

With regard to the Trusted Connection, also please ensure that the /etc/services file of the Trusting System (dependant on OS) is appropriately updated with the below entry for the Trusted System if not already done:

sapmsSID 36XX/tcp # SAP System Messaging Service Port

Ensure SID and port above are correct per your system configuration. This has been a culprit for several of our trusted connections in the past.

[frdric_morand]

Just change the saprouter route permission table ( saprouttab )

saprouttab

=> Authorization "P" and not "S" for the SAP Server Host

____________________________________________________________________________________

Standard entries in a route permission table appear as follows:

P/S/D <source host> <dest host> <dest serv> <password>

<source-host> and <dest-host> could be SAProuters.

Handling the Connection: P/S/D

P (ermit) causes SAProuter to set up the connection. P(ermit) entries can contain a

password. SAProuter checks whether this password corresponds to that sent by the

client.

Directly after the P you can also specify the maximum number of SAProuters allowed

on this route before and after this SAProuter so that the connection is permitted: Pv,n

- v stands for the maximum number of SAProuters before this one, and n stands for the

maximum number of SAProuters after this one allowed on this route.

S (ecure) only allows connections with the SAP Protocol; connections with

other protocols (such as TCP) are not allowed.

With Sv,n you can determime the number of preceding and

succeeding SAProuters on the route, the same as you can with P.

D (eny) prevents the connection from being set up.

You can also add comment lines, which must begin with u2018#u2019

[Former Member]

Please follow this link,

Make sure that you have created trusted RFC in SM59, and maintained that connection details in SMT1.

http://help.sap.com/saphelp_nw04/helpdata/en/22/042671488911d189490000e829fbbd/content.htm

If you still have issues then go to sm59 > RFC>display trace, you will find dev_rfc* paste the log file details.

Regards

JUDE.

[JPReyes]

Check connection via SMT1/SMT2 and please post the errors.

Regards

Juan

[Former Member]

Hi,

Check the user type of the login defined within the RFC connection. If it is System or communication then remote login from RFC will not work. You have to make the user type as Dialog for it to work.

Regards,

Sharath

[Former Member]

Hello!

My user defined in the RFC connection is a Dialog user...