When a remote call of a function module is made, an automatic authorization check is performed, provided that the profile parameter auth/rfc_authority_check is set to 1. The authorization check uses the authorization object S_RFC to check whether the user defined in the destination has RFC authorization for the function group of the called function module.
In addition to the function groups belonging to the application function modules, authorization object S_RFC must also contain any RFC function groups in order to perform technical processes during communication:
● For tRFC and qRFC calls between two SAP systems: Function groups ERFC and ARFC
● For all RFC calls in external (non-SAP) systems: function group SYST
If there is any Missing authorization for a user doing Remote Call to SAP system, SAP throws an exception with ABAP Dump RFC_NO_AUTHORITY.
The automatic authorization check is made by implicitly calling function module AUTHORITY_CHECK_RFC. If it detects an authorization issue, this function module triggers one of the exceptions defined in its interface, namely USER_DONT_EXIST or RFC_NO_AUTHORITY, thus triggering a runtime error.
Eg : If the user logged into portal and accessing the information or data which needs to be fetched from SAP Backend, and that particular User id is not maintained in the Backend or have insufficient authorization, than the RFC_NO_AUTHORITY dump will be generated.
In addition to the function groups belonging to the application function modules, authorization object S_RFC must also contain any RFC function groups in order to perform technical processes during communication:
● For tRFC and qRFC calls between two SAP systems: Function groups ERFC and ARFC
● For all RFC calls in external (non-SAP) systems: function group SYST
If there is any Missing authorization for a user doing Remote Call to SAP system, SAP throws an exception with ABAP Dump RFC_NO_AUTHORITY.
The automatic authorization check is made by implicitly calling function module AUTHORITY_CHECK_RFC. If it detects an authorization issue, this function module triggers one of the exceptions defined in its interface, namely USER_DONT_EXIST or RFC_NO_AUTHORITY, thus triggering a runtime error.
Eg : If the user logged into portal and accessing the information or data which needs to be fetched from SAP Backend, and that particular User id is not maintained in the Backend or have insufficient authorization, than the RFC_NO_AUTHORITY dump will be generated.