Segregation of Duties (SoD) Conflict Report by User
Short answer: A custom ALV report that lists users who can run conflicting activities together (for example changing vendor master data and running the payment program) and shows which role grants each side. The rule set follows the company's own control matrix, so risky users are visible in a single run before an audit.
- Estimated effort
- M · 5–8 working days
- System
- ECC and S/4HANA
- Tables
- 8
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
The critical authorization combinations report in SUIM can find conflicts, but it expects the rules to be maintained technically in SUIM's own maintenance screens; the result does not show on one line which role grants each side of the conflict, whether the assignment comes from a composite role and when the role assignment expires. Auditors therefore merge PFCG and SUIM output in Excel. The custom report uses a rule set written in business terms, gives the role source per line and can distribute the result by email.
Who uses it? SAP authorization administrators, internal audit and internal control teams, IT security officers.
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| USR02User Logon Data | User type, user group, validity, lock status and last logon (driving table) | — | ECC + S/4 |
| AGR_USERSAssignment of Roles to Users | Role assignments valid on the key date and the composite role flag | AGR_USERS-UNAME = USR02-BNAME | ECC + S/4 |
| AGR_1251Authorization Data for Roles | S_TCODE values and critical object activities in the roles | AGR_1251-AGR_NAME = AGR_USERS-AGR_NAME | ECC + S/4 |
| TSTCSAP Transaction Codes | Expansion of transaction code ranges and wildcards | TSTC-TCODE BETWEEN AGR_1251-LOW AND AGR_1251-HIGH | ECC + S/4 |
| TSTCTTransaction Code Texts | Description of the conflicting transactions | TSTCT-TCODE = TSTC-TCODE AND TSTCT-SPRSL = SY-LANGU | ECC + S/4 |
| AGR_TEXTSRole Texts | Role description | AGR_TEXTS-AGR_NAME = AGR_USERS-AGR_NAME AND AGR_TEXTS-SPRAS = SY-LANGU AND AGR_TEXTS-LINE = 00000 | ECC + S/4 |
| USR21User Name to Address Key Assignment | Person number of the user | USR21-BNAME = USR02-BNAME | ECC + S/4 |
| ADRPPersons (Business Address Services) | Full name of the user | ADRP-PERSNUMBER = USR21-PERSNUMBER | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_UNAME | User | Range / multiple | USR02-BNAME | No | AYILMAZ |
| S_CLASS | User group | Range / multiple | USR02-CLASS | No | FIN |
| S_USTYP | User type (default: A dialog) | Range / multiple | USR02-USTYP | No | A |
| S_AGR | Role | Range / multiple | AGR_USERS-AGR_NAME | No | FI_AP_* |
| P_KEYDT | Key date (default: today) | Single value | — | Yes | 17.11.2026 |
| P_RISK | Minimum risk level (High, Medium, Low) | Single value | — | No | Orta |
| P_OBJCHK | Object-level check (activity values) | Checkbox | — | No | X |
| P_LOCKD | Include locked users | Checkbox | — | No | — |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | User | USR02-BNAME |
| 2 | Full name | ADRP-NAME_TEXT |
| 3 | User group | USR02-CLASS |
| 4 | Rule | Calculated Conflict description from the rule set |
| 5 | Risk | Calculated Risk level of the rule; Low when the object check fails |
| 6 | Side A transaction | AGR_1251-LOW |
| 7 | Side A role | AGR_USERS-AGR_NAME |
| 8 | Side B transaction | AGR_1251-LOW |
| 9 | Side B role | AGR_USERS-AGR_NAME |
| 10 | Via composite role | AGR_USERS-COL_FLAG |
| 11 | Role valid to | AGR_USERS-TO_DAT |
| 12 | Last logon | USR02-TRDAT |
Sample output
| User | Full name | User group | Rule | Risk | Side A transaction | Side A role | Side B transaction | Side B role | Via composite role | Role valid to | Last logon |
|---|---|---|---|---|---|---|---|---|---|---|---|
| AYILMAZ | Ayşe Yılmaz | FIN | Vendor master + payment run | High | XK02 | FI_AP_MASTERDATA | F110 | FI_AP_PAYMENT | 12/31/2026 | 11/16/2026 | |
| MDEMIR | Mehmet Demir | PUR | Create purchase order + goods receipt | Medium | ME21N | MM_PUR_BUYER | MIGO | MM_WH_CLERK | X | 12/31/9999 | 11/17/2026 |
| KAYAZ | Zeynep Kaya | SAL | Customer credit limit + billing cancellation | High | FD32 | FI_AR_CREDIT | VF11 | SD_BILLING | 03/31/2027 | 11/12/2026 | |
| BCELIK | Burak Çelik | FIN | Post vendor invoice + payment run | Low | MIRO | MM_IV_CLERK | F110 | FI_AP_DISPLAY_ALL | X | 12/31/9999 | 11/03/2026 |
How does the report work?
- The rule set is read: each rule consists of two function groups (A and B), each group is a list of transaction codes and the rule carries a risk level. Rules are kept in a small maintenance table delivered with the report; common P2P, O2C and R2R conflicts are pre-filled at installation.
- Users in the selection are read from USR02; by default only dialog users (USTYP = A) that are not locked (UFLAG = 0) and valid on the key date (GLTGV ≤ date ≤ GLTGB, or GLTGB empty) are included.
- Role assignments valid on the key date are read from AGR_USERS (FROM_DAT ≤ date ≤ TO_DAT). Single roles that come through a composite role are flagged with COL_FLAG and shown separately.
- For each role, the TCD field of object S_TCODE (DELETED blank) is read from AGR_1251; LOW–HIGH ranges and values containing * are expanded against the transaction codes in TSTC.
- Each user’s effective transaction set is compared with the rules: if the user has at least one transaction from group A and at least one from group B, a conflict is written; the first granting role and transaction is kept for each side.
- With “Object-level check” selected, the critical object and activity values defined in the rule (for example ACTVT 01/02) are also checked in AGR_1251; lines with the transaction but without the activity are downgraded to low risk.
- The full name is added from USR21 and ADRP, and the role description from AGR_TEXTS. The result is shown in ALV with subtotals per user and rule.
Performance notes
Read AGR_1251 only for the roles of the selected users and with the filter OBJECT = 'S_TCODE'. Expand wildcard values against TSTC once and keep them in memory. On systems with thousands of users, run the report as a nightly background job.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the role name displays the role in PFCG.
- Export to Excel
- Runs as a background job
- Send the result by email A summary can be sent to internal audit at each quarter end.
Authorization objects
- S_USER_GRPDisplay authorization for user data by user group
- S_USER_AGRDisplay authorization for roles and their content
Frequently asked questions
Who defines the rule set, and how?
Rules come from the internal control matrix and are kept in business terms in the maintenance screen delivered with the report: each rule has a name, A and B transaction lists and a risk level. Common purchasing, sales and finance conflicts are pre-filled at installation and the company adjusts them to its own matrix.
How do users with the SAP_ALL profile appear?
Users who carry SAP_ALL directly through UST04 produce a conflict for every rule. The report flags them separately at the top so they can be handled as one finding instead of hundreds of lines.
Are Fiori apps also checked on S/4HANA?
The report works on transaction codes and authorization object values, which also apply to the authorization checks behind Fiori apps. Catalog and group assignments can be added to the rule set through their transaction equivalents.
Packages that include this solution
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, …
Related reports
Automatic Lock of Inactive Users Program
A custom background program that first warns dialog users who have not logged on for a given period by email, locks them with an administrator lock …
User License Type and Last Logon Report (Inactive Users)
A custom ALV report that shows each user's license type, last logon date, number of valid roles and department in one list. Users who have not logged …
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.