BASIS Report Custom development ALV report

Users with Critical Authorizations Report (SAP_ALL, Debug, Table Maintenance)

Short answer: A custom ALV report that lists users holding authorizations that are critical on their own, such as the SAP_ALL and SAP_NEW profiles, debugging with value change, table maintenance, user and role maintenance or changing RFC destinations, showing which role or profile grants the access, the value and the validity end of the assignment. The rule list is kept in a settings table that can be maintained per customer; before an audit, one list shows who has what.

Estimated effort
M · 5–7 working days
System
ECC and S/4HANA
Tables
7
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

"Users by complex selection criteria" in SUIM (RSUSR002) searches one authorization object and value combination at a time; it does not evaluate dozens of critical rules in one run, and it does not show in the same row which role grants the access and when the assignment ends. SAP_ALL profile assignments and role-based authorizations are searched separately. The segregation of duties (SoD) report checks pairs of authorizations; this report scans authorizations that are critical on their own against a rule list.

Who uses it? BASIS and authorization administrators, information security teams, internal audit and IT management working with external auditors.

Closest standard alternatives

  • SUIM User Information System. Finds users with one combination of authorization values; there is no multi-rule run with role source and assignment end in one list.
  • PFCG Role Maintenance. Shows the authorizations and users of a role one role at a time; it does not scan critical access across users.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
USR02User Logon DataUser type, group, lock status, validity and last logon (driving table)—ECC + S/4
AGR_USERSAssignment of Roles to UsersUser-to-role assignment and validity datesAGR_USERS-UNAME = USR02-BNAMEECC + S/4
AGR_1251Authorization Data for RolesAuthorization object, field and values in the roleAGR_1251-AGR_NAME = AGR_USERS-AGR_NAMEECC + S/4
UST04User Profile AssignmentsDirectly assigned profiles (SAP_ALL, SAP_NEW)UST04-BNAME = USR02-BNAMEECC + S/4
AGR_TEXTSRole TextsRole descriptionAGR_TEXTS-AGR_NAME = AGR_USERS-AGR_NAME AND AGR_TEXTS-SPRAS = SY-LANGU AND AGR_TEXTS-LINE = 0ECC + S/4
USR21User Name to Address Key AssignmentPerson number of the userUSR21-BNAME = USR02-BNAMEECC + S/4
ADRPPersons (Business Address Services)Full name of the userADRP-PERSNUMBER = USR21-PERSNUMBERECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_UNAMEUserRange / multipleUSR02-BNAMENo* hariç FIREFIGHTER*
S_USTYPUser typeRange / multipleUSR02-USTYPNoA, B, S
S_CLASSUser groupRange / multipleUSR02-CLASSNo—
S_AGRRoleRange / multipleAGR_USERS-AGR_NAMENoROL_*
S_OBJCTAuthorization object (narrows the rule list)Range / multipleAGR_1251-OBJECTNoS_DEVELOP, S_TABU_DIS
P_KEYDTKey dateSingle value—Yes17.11.2026
P_PROFCheck directly assigned critical profilesCheckbox—NoX
P_LOCKAlso show locked usersCheckbox—No—

Output columns

#ColumnSource
1UserUSR02-BNAME
2Full nameADRP-NAME_TEXT
3User typeUSR02-USTYP
4User groupUSR02-CLASS
5Last logonUSR02-TRDAT
6Critical ruleCalculated Description of the matching rule in the settings table
7RoleAGR_USERS-AGR_NAME
8Role descriptionAGR_TEXTS-TEXT
9ProfileUST04-PROFILE
10Authorization objectAGR_1251-OBJECT
11FieldAGR_1251-FIELD
12ValueAGR_1251-LOW
13Assignment valid toAGR_USERS-TO_DAT
14Risk levelCalculated Risk level of the rule; SAP_ALL and debug change are always Critical

Sample output

UserFull nameUser typeUser groupLast logonCritical ruleRoleRole descriptionProfileAuthorization objectFieldValueAssignment valid toRisk level
MKAYAMurat KayaAFINANS11/16/2026Table maintenance (change)ROL_FI_ANAHTAR_KULLANICIFI key userS_TABU_DISACTVT0212/31/9999High
ADEMIRAyşe DemirABT_DESTEK11/17/2026Debugging with value changeROL_BT_DESTEKIT application supportS_DEVELOPOBJTYPEDEBUG12/31/2026Critical
RFC_ENTEGRASYONIntegration technical userBTEKNIK11/17/2026Full authorization profileSAP_ALLCritical
OYILMAZOkan YılmazASATIS09/02/2026User maintenance transactionROL_SD_SUPERVIZORSales supervisorS_TCODETCDSU0103/31/2027High
A view built with fictional sample data; not real system data.

How does the report work?

  1. The rule list is read from the settings table: rule code, risk level, authorization object, field and value (e.g. S_TCODE-TCD = SU01, PFCG, SE38, SM59, SCC4; S_DEVELOP OBJTYPE = DEBUG and ACTVT = 02; S_TABU_DIS ACTVT = 02; S_USER_GRP ACTVT = 01/02; S_BTCH_ADM BTCADMIN = Y).
  2. Authorization values that are not deleted (DELETED blank) are read from AGR_1251 and matched against the rules; ‘*’ wildcards and LOW–HIGH ranges count as a match when they cover the rule value.
  3. Matching roles are expanded to users through AGR_USERS assignments valid on the key date; single roles of composite roles are stored separately in AGR_USERS and are found directly. The role description is added from AGR_TEXTS.
  4. Users with SAP_ALL, SAP_NEW or other critical profiles from the rule list assigned directly are read from UST04.
  5. User type, group, lock status (UFLAG), validity and last logon are added from USR02, the full name from USR21/ADRP. Locked users are excluded depending on the selection.
  6. The result is listed by user and rule in ALV; double-clicking the user opens SU01, double-clicking the role opens PFCG.

Performance notes

Narrow AGR_1251 by the authorization objects in the rule list first and compare the values in ABAP. Read user and name data once with FOR ALL ENTRIES. On systems with thousands of roles the report can take a few minutes; run it in the background for the monthly audit list.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants
  • Double-click drill-down to the document Double-clicking the user opens SU01, double-clicking the role opens PFCG.
  • Export to Excel
  • Runs as a background job
  • Send the result by email The monthly list can be emailed to the information security team.

Authorization objects

  • S_USER_GRPDisplay user data by user group (ACTVT 03)
  • S_USER_AGRDisplay roles and role authorizations
  • S_USER_PRODisplay profiles

Frequently asked questions

Who defines the critical rule list?

During installation, a starter list of common critical authorizations is prepared with the information security and audit team. The list is kept in a settings table; adding a rule needs no program change.

Does the report read user password data?

No. The report reads only metadata such as roles, profiles, user type, validity and last logon. Fields holding password hashes or security keys are never selected.

How are emergency (firefighter) users separated?

Emergency users can be excluded from the selection by user group or name pattern, or listed alone with a separate variant. Approved exceptions are then tracked apart from the main findings.

Packages that include this solution

BASIS Package Custom

SAP Access and Payment Risk Audit Pack

A six-component pack that brings together the controls asked most often in the yearly IT and finance audit: users with critical authorizations, …

6 components · v1.0

Related reports

BASIS Report Custom ALV report

Expiring and Expired Role Assignments Report

A custom ALV report that lists role assignments whose validity ends within the next N days or that have ended but are still on the user, with the …

AGR_USERS · AGR_TEXTS · AGR_DEFINE · AGR_1016

BASIS Report Custom ALV report

Segregation of Duties (SoD) Conflict Report by User

A custom ALV report that lists users who can run conflicting activities together (for example changing vendor master data and running the payment …

USR02 · AGR_USERS · AGR_1251 · TSTC

Let us build this report for your system

Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.

Related report: Users with Critical Authorizations Report (SAP_ALL, Debug, Table Maintenance)