RFC problem in solman 7.0 ehp 1

[Former Member]

Dear

i am facing a problem when i crate trusted RFC trought SMSY.

error is " Error Creatinf RFC destination SM_SOMCLNT500_BACK" IN SYSTEM TEST.

BUT I HAVE GIVEN ALREADY "S_RFC & S_RFCACL" OBJECT IN BOTH SIDE SOURCE AND TARGET SYSTEM.

REGARDS

ANIL KUMAR

[Former Member]

hi

>

> error is " Error Creatinf RFC destination SM_SOMCLNT500_BACK" IN SYSTEM TEST.
> 
> ANIL KUMAR

since you are facing the problem in creation itself kindly check the deatil logs, and proceed it may be lot f reason,some case wrong host name also be the reason,

go to sm59, and check the connection test , based on te error you can proceed the suggestions provided here

jansi

[mateus_pedroso]

According with page 67 of Security Guide for Solman 7.0 EHP1

6.2.2 Authorization Object S_RFCACL

The trusting RFC destination has the Current User setting in transaction SM59. Authorization errors in the use of an RFC destination flagged as a Trusted System cause the following message to be sent: No Authorization to logon as Trusted System (Trusted RC = #).

=> Prerequisites

To apply the authorization object, you need full access to transaction PFCG, in the SAP Solution Manager system and the managed systems.

=> Features

To create the trusted RFC connection you need to have the authorization object S_RFCACL in the Solution Manager and in the managed system for this user. The role SAP_S_RFCACL contains the authorization object S_RFCACL, which consists of a number of authorization fields, which allow a trusting trusted relationship between SAP Solution Manager and any managed system. Due to the high potential risk of such an RFC connection, the authorization object S_RFCACL is not in authorization profile SAP_ALL.

You said that you already gave S_RFC and S_RFCACL, but you customized a new role ? or are you using SAP_S_RFCACL ?

[Miguel_Ariño]

Hi there,

Sorry to state the obvious... have you checked that there is a user with the same ID in the target system? Have you made sure that the RFC connection is to the right client? Sometimes these things can be missed.

Best regards,

Miguel Ariñ

[Former Member]

thanks dear

issue has been solved.

[Diggeshhjoshi]

Anil,

Check SM21 log for details why it is not creating RFC in back system.

Other recommendations, Go to SM59 and see if the RFC is created or not. If created check hostname.

Some times you get this error but still RFC is created and it is not able to talk to other system because of hostname resolution or Authorization issue.

If RFC is not created, please create manual RFC in SM59 and see if you are able to connect to other host and no authorization issue.

Regards,

Digesh