RFC_NO_AUTHORITY
mediumRFC Authorization Check Failed for Function Module
Module: RFC / Authorization
What this means
RFC_NO_AUTHORITY occurs when an RFC call reaches the target system successfully, but the RFC user does not have authorization to execute the specific function module. RFC function module access is controlled by authorization object S_RFC (with field RFC_NAME for function group name and ACTVT = 16 for execute). This error commonly appears in: interface users whose role was not updated when new function modules were added to a function group; system-to-system calls where the technical RFC user has a minimal authorization profile; or Basis hardening efforts that restrict S_RFC access without a full impact analysis.
Run SU53 on the RFC user in the target system immediately after the failure. The result shows the exact function group (not individual function module — S_RFC works at function group level) that was rejected. Add the missing S_RFC entry to the RFC user's role in PFCG. For interface users, maintain a specific S_RFC role rather than granting blanket access.
Quick Info