# Background Jobs Running Under Personal Dialog Users Report

> A custom ALV report that lists periodic or scheduled background jobs with a step running under a personal dialog user, showing whether that user is locked, when its validity ends and the last logon date. It catches in advance night jobs that will cancel when an employee leaves or the user is locked, and gives the list of jobs to move to a technical user.

- Type: Report, Custom development, ALV report
- Module: BASIS
- Estimated effort: S (3–4 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/background-jobs-running-under-personal-users-report/


## Why is the standard not enough?

SM37 shows jobs and the step user, but not the type of the step user (dialog, system, service), its lock status or validity end. To see which periodic job depends on a personal user, every job has to be opened one by one. SU01 does not show in which jobs a user is the step user either. The custom report combines both and warns in advance about users whose validity ends soon.

### Closest standard alternatives

- SM37: Shows jobs and the step user; no user type, lock or validity end.
- SU01: Shows the lock and validity of a user; it does not show in which jobs the user is the step user.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| TBTCO | Job header: status, period, planned start, scheduling user (driving table) | Read | - | ECC + S/4 |
| TBTCP | Job step: program, variant and step user | Read | TBTCP-JOBNAME = TBTCO-JOBNAME AND TBTCP-JOBCOUNT = TBTCO-JOBCOUNT | ECC + S/4 |
| USR02 | Type, lock, validity and last logon of the step user | Read | USR02-BNAME = TBTCP-AUTHCKNAM | ECC + S/4 |
| USR21 | Person number of the step user | Read | USR21-BNAME = TBTCP-AUTHCKNAM | ECC + S/4 |
| ADRP | Full name of the step user | Read | ADRP-PERSNUMBER = USR21-PERSNUMBER | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_JOBNM | Job name | Range / multiple | TBTCO-JOBNAME | No |
| S_STAT | Job status | Range / multiple | TBTCO-STATUS | Yes |
| S_AUTHU | Step user | Range / multiple | TBTCP-AUTHCKNAM | No |
| S_USTYP | Step user type | Range / multiple | USR02-USTYP | No |
| P_PERIO | Periodic jobs only | Checkbox | - | No |
| P_VALDY | Warn for user validity ending within (days) | Single value | - | No |
| P_ALL | Also show jobs without findings | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Job name | TBTCO-JOBNAME |
| Status | TBTCO-STATUS |
| Periodic | TBTCO-PERIODIC |
| Period | Calculated: Text from PRDMINS/PRDHOURS/PRDDAYS/PRDWEEKS/PRDMONTHS or EVENTID |
| Planned start | TBTCO-SDLSTRTDT |
| Step | TBTCP-STEPCOUNT |
| Program | TBTCP-PROGNAME |
| Variant | TBTCP-VARIANT |
| Step user | TBTCP-AUTHCKNAM |
| Full name | ADRP-NAME_TEXT |
| User type | USR02-USTYP |
| Lock status | USR02-UFLAG |
| Valid to | USR02-GLTGB |
| Scheduled by | TBTCO-SDLUNAME |
| Finding | Calculated: Dialog user / locked / validity ended / ends within N days / user missing |

## How does the report work?

1. Jobs in the selected statuses (default: S released, P scheduled, Z put active) are read from TBTCO; depending on the selection only periodic jobs (PERIODIC = X) are taken.
2. The steps of each job, step program, variant and step user (AUTHCKNAM) are added from TBTCP.
3. The USR02 record of the step user is read: user type (USTYP), lock (UFLAG), validity end (GLTGB) and last logon (TRDAT). The full name is added from USR21/ADRP.
4. Findings are set: the step user is a dialog user (A); the user is locked; validity has ended; validity ends within N days; the user does not exist.
5. The period text is built from PRDMINS/PRDHOURS/PRDDAYS/PRDWEEKS/PRDMONTHS or the event ID (EVENTID).
6. The result is sorted by finding priority; double-clicking the job opens SM37, double-clicking the user opens SU01.

## Authorization objects

- S_BTCH_ADM: Display background jobs of all users
- S_USER_GRP: Display master data of step users (ACTVT 03)

## Frequently asked questions

### Can the report also move the job to another user?

The basic version only lists. If needed, an action button can be added that replaces the step user of selected rows with a given technical user; this needs the S_BTCH_NAM authorization and takes about two extra days.

### Why are jobs under personal users risky?

The job runs with the authorizations of the step user. If the user is locked, its validity ends or its roles change, the job cancels or produces a different result. Audits also report automated processing under personal users as a finding.

### Does the report work on S/4HANA?

Yes. TBTCO, TBTCP and the user tables are the same in S/4HANA. Jobs scheduled through Fiori Application Jobs are stored in the same tables, so they are included.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=basis-background-jobs-personal-users
