NO_AUTHORIZATION
mediumAuthorization Check Failed — Missing Object or Field Value
Module: ABAP / Authorization
What this means
NO_AUTHORIZATION is raised when a program executes AUTHORITY-CHECK and the result is not SY-SUBRC = 0 — meaning the user lacks a required authorization object, activity, or field value. The dump occurs when the program does not handle the failed check gracefully (i.e., no IF SY-SUBRC <> 0 branch). This is common in custom programs that call AUTHORITY-CHECK without proper error handling, or in standard programs where the authorization concept has gaps. Note: the user sees a dump rather than a clean "not authorised" message because the developer did not handle the failure path.
Run SU53 immediately after the failed action — it shows the last failed authorization check including the exact object, field, and value that was missing. Use SU24 to check which authorization objects are assigned to the transaction. Add the missing object/value combination to the user's role in PFCG and regenerate the profile. Never grant SAP_ALL to resolve authorization issues — diagnose and grant only what is needed.
Quick Info