Background Jobs Running Under Personal Dialog Users Report
Short answer: 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.
- Estimated effort
- S · 3–4 working days
- System
- ECC and S/4HANA
- Tables
- 5
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
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.
Who uses it? BASIS administrators, authorization and user management teams, and IT managers closing audit findings.
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 |
|---|---|---|---|
| TBTCOBackground Job Status Overview | Job header: status, period, planned start, scheduling user (driving table) | — | ECC + S/4 |
| TBTCPBackground Job Step Overview | Job step: program, variant and step user | TBTCP-JOBNAME = TBTCO-JOBNAME AND TBTCP-JOBCOUNT = TBTCO-JOBCOUNT | ECC + S/4 |
| USR02User Logon Data | Type, lock, validity and last logon of the step user | USR02-BNAME = TBTCP-AUTHCKNAM | ECC + S/4 |
| USR21User Name to Address Key Assignment | Person number of the step user | USR21-BNAME = TBTCP-AUTHCKNAM | ECC + S/4 |
| ADRPPersons (Business Address Services) | Full name of the step user | ADRP-PERSNUMBER = USR21-PERSNUMBER | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_JOBNM | Job name | Range / multiple | TBTCO-JOBNAME | No | * |
| S_STAT | Job status | Range / multiple | TBTCO-STATUS | Yes | S, P, Z |
| S_AUTHU | Step user | Range / multiple | TBTCP-AUTHCKNAM | No | — |
| S_USTYP | Step user type | Range / multiple | USR02-USTYP | No | A |
| P_PERIO | Periodic jobs only | Checkbox | — | No | X |
| P_VALDY | Warn for user validity ending within (days) | Single value | — | No | 30 |
| P_ALL | Also show jobs without findings | Checkbox | — | No | — |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Job name | TBTCO-JOBNAME |
| 2 | Status | TBTCO-STATUS |
| 3 | Periodic | TBTCO-PERIODIC |
| 4 | Period | Calculated Text from PRDMINS/PRDHOURS/PRDDAYS/PRDWEEKS/PRDMONTHS or EVENTID |
| 5 | Planned start | TBTCO-SDLSTRTDT |
| 6 | Step | TBTCP-STEPCOUNT |
| 7 | Program | TBTCP-PROGNAME |
| 8 | Variant | TBTCP-VARIANT |
| 9 | Step user | TBTCP-AUTHCKNAM |
| 10 | Full name | ADRP-NAME_TEXT |
| 11 | User type | USR02-USTYP |
| 12 | Lock status | USR02-UFLAG |
| 13 | Valid to | USR02-GLTGB |
| 14 | Scheduled by | TBTCO-SDLUNAME |
| 15 | Finding | Calculated Dialog user / locked / validity ended / ends within N days / user missing |
Sample output
| Job name | Status | Periodic | Period | Planned start | Step | Program | Variant | Step user | Full name | User type | Lock status | Valid to | Scheduled by | Finding |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| FI_OTOMATIK_ODEME_GUNLUK | S | X | Daily | 11/18/2026 | 1 | SAPF110S | GUNLUK_1000 | MKAYA | Murat Kaya | A | 0 | 11/30/2026 | MKAYA | Dialog user; validity ends within 13 days |
| MM_MRP_GECE | S | X | Daily | 11/18/2026 | 1 | RMMRP000 | TESIS_1000 | EARSLAN | Elif Arslan | A | 64 | 12/31/9999 | EARSLAN | User locked by administrator; the job cancels on its next run |
| SD_FATURA_VADE_LISTESI | S | X | Every 4 hours | 11/17/2026 | 2 | SDBILLDL | TUM_ORG | OYILMAZ | Okan Yılmaz | A | 0 | 10/31/2026 | BATCH_SD | User validity ended on 31 Oct 2026 |
| QM_KALIBRASYON_PLANLAMA | S | X | Weekly | 11/23/2026 | 1 | RISTRA20 | HAFTALIK | SDEMIR | Selin Demir | A | 0 | 12/31/9999 | SDEMIR | Dialog user; should move to a technical user |
How does the report work?
- 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.
- The steps of each job, step program, variant and step user (AUTHCKNAM) are added from TBTCP.
- 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.
- 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.
- The period text is built from PRDMINS/PRDHOURS/PRDDAYS/PRDWEEKS/PRDMONTHS or the event ID (EVENTID).
- The result is sorted by finding priority; double-clicking the job opens SM37, double-clicking the user opens SU01.
Performance notes
Narrow TBTCO by status; finished (F) and cancelled (A) jobs are not needed for this report. Read user data once for the distinct step users. The report finishes in seconds; a weekly background run is enough.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the job opens SM37, double-clicking the user opens SU01.
- Export to Excel
- Runs as a background job
- Send the result by email Jobs of users whose validity ends soon are sent to the BASIS team weekly.
Authorization objects
- S_BTCH_ADMDisplay background jobs of all users
- S_USER_GRPDisplay 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.
Packages that include this solution
Basis Daily System Check Pack
A five-component pack that turns the Basis team's morning check into one list: cancelled and long-running background jobs, scheduled jobs running …
Related reports
Cancelled and Long-Running Background Jobs Report
A custom ALV report that lists background jobs that were cancelled, are still running or finished far above their usual runtime, with the step …
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 …
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.