What are the Common Indicators of No RFC Authorization?

Updated May 18, 2018

Hello Experts,

What are the common indicators of no RFC authorization?

How can I resolve these RFC authorization issues?

Thanks in advance.

Comments

06 May 2016 2:15 pm Abhijeet Mudgal Helpful Answer
- For starting up web services, automatic configuration is used to set up a user of type 'Service'. The default role SAP_BC_WEBSERVICE_SERVICE_USER is then assigned to this user. The function group SYST is not taken into account by this role. The internal use of certain functions in RFC requires this authorization, after the RFC gets changed.
- After a system for Web services was configured using the function module SRT_TECHNICAL_SETUP, it is reported by the program SRT_ADMIN_CHECK which is used to check the configuration that the authorizations for the function group SYST is not possessed by the technical user of type 'Service'.
- Another indication is that the user doesn’t have authorizations for executing the function module "RFCPING".

06 May 2016 2:16 pm Rohit Mahajan Helpful Answer
RFC authorization errors can be resolved using the following steps:
- The function group SYST should be added to the RFC authorization.
- The function group “SYST” should be added to the default role SAP_BC_WEBSERVICE_SERVICE_USER in the authorizations for "Cross-application Authorization Objects" in the area "Authorization Check for RFC Access". The object "Name of RFC object to be protected" should be saved and this role needs to be activated.
- A user comparison for this role should then be executed.