BASIS Report Custom development ALV report

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

  • SM37 Job Selection Overview. Shows jobs and the step user; no user type, lock or validity end.
  • SU01 User Maintenance. Shows the lock and validity of a user; it does not show in which jobs the user is the step user.

Tables used

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

TableRoleJoinSystem
TBTCOBackground Job Status OverviewJob header: status, period, planned start, scheduling user (driving table)—ECC + S/4
TBTCPBackground Job Step OverviewJob step: program, variant and step userTBTCP-JOBNAME = TBTCO-JOBNAME AND TBTCP-JOBCOUNT = TBTCO-JOBCOUNTECC + S/4
USR02User Logon DataType, lock, validity and last logon of the step userUSR02-BNAME = TBTCP-AUTHCKNAMECC + S/4
USR21User Name to Address Key AssignmentPerson number of the step userUSR21-BNAME = TBTCP-AUTHCKNAMECC + S/4
ADRPPersons (Business Address Services)Full name of the step userADRP-PERSNUMBER = USR21-PERSNUMBERECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_JOBNMJob nameRange / multipleTBTCO-JOBNAMENo*
S_STATJob statusRange / multipleTBTCO-STATUSYesS, P, Z
S_AUTHUStep userRange / multipleTBTCP-AUTHCKNAMNo—
S_USTYPStep user typeRange / multipleUSR02-USTYPNoA
P_PERIOPeriodic jobs onlyCheckbox—NoX
P_VALDYWarn for user validity ending within (days)Single value—No30
P_ALLAlso show jobs without findingsCheckbox—No—

Output columns

#ColumnSource
1Job nameTBTCO-JOBNAME
2StatusTBTCO-STATUS
3PeriodicTBTCO-PERIODIC
4PeriodCalculated Text from PRDMINS/PRDHOURS/PRDDAYS/PRDWEEKS/PRDMONTHS or EVENTID
5Planned startTBTCO-SDLSTRTDT
6StepTBTCP-STEPCOUNT
7ProgramTBTCP-PROGNAME
8VariantTBTCP-VARIANT
9Step userTBTCP-AUTHCKNAM
10Full nameADRP-NAME_TEXT
11User typeUSR02-USTYP
12Lock statusUSR02-UFLAG
13Valid toUSR02-GLTGB
14Scheduled byTBTCO-SDLUNAME
15FindingCalculated Dialog user / locked / validity ended / ends within N days / user missing

Sample output

Job nameStatusPeriodicPeriodPlanned startStepProgramVariantStep userFull nameUser typeLock statusValid toScheduled byFinding
FI_OTOMATIK_ODEME_GUNLUKSXDaily11/18/20261SAPF110SGUNLUK_1000MKAYAMurat KayaA011/30/2026MKAYADialog user; validity ends within 13 days
MM_MRP_GECESXDaily11/18/20261RMMRP000TESIS_1000EARSLANElif ArslanA6412/31/9999EARSLANUser locked by administrator; the job cancels on its next run
SD_FATURA_VADE_LISTESISXEvery 4 hours11/17/20262SDBILLDLTUM_ORGOYILMAZOkan YılmazA010/31/2026BATCH_SDUser validity ended on 31 Oct 2026
QM_KALIBRASYON_PLANLAMASXWeekly11/23/20261RISTRA20HAFTALIKSDEMIRSelin DemirA012/31/9999SDEMIRDialog user; should move to a technical user
A view built with fictional sample data; not real system data.

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.

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 Package Custom

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 …

5 components · v1.0

Related reports

BASIS Report Custom ALV report

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 …

TBTCO · TBTCP · TRDIRT

BASIS Program Custom Background program

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 …

USR02 · USR21 · ADR6 · AGR_USERS

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: Background Jobs Running Under Personal Dialog Users Report