# 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 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.

- Type: Report, Custom development, ALV report
- Module: BASIS
- Estimated effort: M (5–8 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/segregation-of-duties-sod-conflicts-by-user-report/


## 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.

### Closest standard alternatives

- SUIM: The critical combinations report finds conflicts; rules need technical maintenance and the role source and assignment validity are not on the same line.
- PFCG: Shows the content and users of one role; it does not analyze conflicts across users.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| USR02 | User type, user group, validity, lock status and last logon (driving table) | Read | - | ECC + S/4 |
| AGR_USERS | Role assignments valid on the key date and the composite role flag | Read | AGR_USERS-UNAME = USR02-BNAME | ECC + S/4 |
| AGR_1251 | S_TCODE values and critical object activities in the roles | Read | AGR_1251-AGR_NAME = AGR_USERS-AGR_NAME | ECC + S/4 |
| TSTC | Expansion of transaction code ranges and wildcards | Read | TSTC-TCODE BETWEEN AGR_1251-LOW AND AGR_1251-HIGH | ECC + S/4 |
| TSTCT | Description of the conflicting transactions | Read | TSTCT-TCODE = TSTC-TCODE AND TSTCT-SPRSL = SY-LANGU | ECC + S/4 |
| AGR_TEXTS | Role description | Read | AGR_TEXTS-AGR_NAME = AGR_USERS-AGR_NAME AND AGR_TEXTS-SPRAS = SY-LANGU AND AGR_TEXTS-LINE = 00000 | ECC + S/4 |
| USR21 | Person number of the user | Read | USR21-BNAME = USR02-BNAME | ECC + S/4 |
| ADRP | Full name of the user | Read | ADRP-PERSNUMBER = USR21-PERSNUMBER | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_UNAME | User | Range / multiple | USR02-BNAME | No |
| S_CLASS | User group | Range / multiple | USR02-CLASS | No |
| S_USTYP | User type (default: A dialog) | Range / multiple | USR02-USTYP | No |
| S_AGR | Role | Range / multiple | AGR_USERS-AGR_NAME | No |
| P_KEYDT | Key date (default: today) | Single value | - | Yes |
| P_RISK | Minimum risk level (High, Medium, Low) | Single value | - | No |
| P_OBJCHK | Object-level check (activity values) | Checkbox | - | No |
| P_LOCKD | Include locked users | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| User | USR02-BNAME |
| Full name | ADRP-NAME_TEXT |
| User group | USR02-CLASS |
| Rule | Calculated: Conflict description from the rule set |
| Risk | Calculated: Risk level of the rule; Low when the object check fails |
| Side A transaction | AGR_1251-LOW |
| Side A role | AGR_USERS-AGR_NAME |
| Side B transaction | AGR_1251-LOW |
| Side B role | AGR_USERS-AGR_NAME |
| Via composite role | AGR_USERS-COL_FLAG |
| Role valid to | AGR_USERS-TO_DAT |
| Last logon | USR02-TRDAT |

## How does the report work?

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. 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.

## Authorization objects

- S_USER_GRP: Display authorization for user data by user group
- S_USER_AGR: Display 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=basis-sod-conflicts-by-user
