Mass Background Job Scheduling from Excel
Short answer: A custom program that schedules dozens of background jobs in one go from an Excel file after a go-live, a system copy or the opening of a new company code, with program, variant, step user, start time and period. Rows with the same job name are created as a multi-step job; program, variant and user are checked in advance, and no job is created in test mode.
- Estimated effort
- S · 3–5 working days
- System
- ECC and S/4HANA
- Tables
- 5
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
SM36 defines jobs one by one, step by step on the screen; setting up hundreds of periodic jobs from a list takes hours and is prone to typos. After a system copy, BTCTRNS1/BTCTRNS2 only suspend and release existing jobs; they do not load a new job plan. This program loads the approved job plan list directly and keeps the result of each row in a log.
Who uses it? BASIS administrators, and project and support teams rebuilding the job schedule after a go-live or system copy.
Closest standard alternatives
Tables used
The tables the program reads and updates. ECC and S/4HANA differences are marked separately.
| Table | Role | Access | System |
|---|---|---|---|
| TBTCOBackground Job Status Overview | Job header; created through JOB_OPEN and JOB_CLOSE | Write | ECC + S/4 |
| TBTCPBackground Job Step Overview | Job steps; added through JOB_SUBMIT | Write | ECC + S/4 |
| TRDIRABAP Program Directory | Check of program existence and type | Read | ECC + S/4 |
| VARIDVariant Directory | Existence check for the variant | Read | ECC + S/4 |
| USR02User Logon Data | Type and lock status of the step user | Read | ECC + S/4 |
BAPIs and functions used
- JOB_OPENOpen Background Job. Opens a new background job and returns the job count
- JOB_SUBMITAdd Step to Background Job. Adds a step with program, variant and step user to the job
- JOB_CLOSEClose and Release Background Job. Sets start time, period and target server, closes and releases the job
- BP_JOB_READRead Background Job Data. Reads existing jobs with the same name
- BP_JOB_DELETEDelete Background Job. Deletes the old scheduled job when the replace option is on
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| P_FILE | Job plan file (XLSX or CSV) | Single value | — | Yes | C:\temp\is_plani.xlsx |
| P_TEST | Test mode (check without creating jobs) | Checkbox | — | No | X |
| P_RELEA | Release jobs immediately | Checkbox | — | No | X |
| P_REPL | Replace scheduled jobs with the same name | Checkbox | — | No | — |
| S_USTYP | Allowed step user types | Range / multiple | USR02-USTYP | No | B, S |
Input file columns
The columns of the upload template and the SAP fields they are written to. Columns with an asterisk are mandatory.
| # | Column | Target field | Required |
|---|---|---|---|
| 1 | Job name | TBTCO-JOBNAME | Yes |
| 2 | Job class | TBTCO-JOBCLASS | No |
| 3 | Program | TBTCP-PROGNAME | Yes |
| 4 | Variant | TBTCP-VARIANT | No |
| 5 | Step user | TBTCP-AUTHCKNAM | Yes |
| 6 | Start date | TBTCO-SDLSTRTDT | Yes |
| 7 | Start time | TBTCO-SDLSTRTTM | Yes |
| 8 | Period (days) | TBTCO-PRDDAYS | No |
| 9 | Period (hours) | TBTCO-PRDHOURS | No |
| 10 | Period (months) | TBTCO-PRDMONTHS | No |
| 11 | Target server | TBTCO-EXECSERVER | No |
Sample upload file
| 1 | Job name * | Job class | Program * | Variant | Step user * | Start date * | Start time * | Period (days) | Period (hours) | Period (months) | Target server |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | BASIS_IS_GECMISI_TEMIZLIK | C | RSBTCDEL2 | 30_GUN | BATCH_BASIS | 11/18/2026 | 01:00:00 | 1 | 0 | 0 | |
| 3 | BASIS_SPOOL_TEMIZLIK | C | RSPO1041 | 14_GUN | BATCH_BASIS | 11/18/2026 | 01:30:00 | 1 | 0 | 0 | |
| 4 | SD_FATURA_VADE_LISTESI | B | SDBILLDL | TUM_ORG | BATCH_SD | 11/18/2026 | 03:15:00 | 0 | 4 | 0 | sapapp02 |
Result list columns
| # | Column | Source |
|---|---|---|
| 1 | Row | Calculated Row number in the file |
| 2 | Job name | TBTCO-JOBNAME |
| 3 | Job count | TBTCO-JOBCOUNT |
| 4 | Program | TBTCP-PROGNAME |
| 5 | Variant | TBTCP-VARIANT |
| 6 | Step user | TBTCP-AUTHCKNAM |
| 7 | Planned start | TBTCO-SDLSTRTDT |
| 8 | Job status | TBTCO-STATUS |
| 9 | Result | Calculated Created / Replaced / Test / Skipped / Error |
| 10 | Message | Calculated Check or job function message |
Sample result list
| Row | Job name | Job count | Program | Variant | Step user | Planned start | Job status | Result | Message |
|---|---|---|---|---|---|---|---|---|---|
| 1 | BASIS_IS_GECMISI_TEMIZLIK | 01001500 | RSBTCDEL2 | 30_GUN | BATCH_BASIS | 11/18/2026 | S | Created | Daily job released |
| 2 | BASIS_SPOOL_TEMIZLIK | 01001501 | RSPO1041 | 14_GUN | BATCH_BASIS | 11/18/2026 | S | Replaced | Old job with the same name deleted, new one created |
| 3 | SD_FATURA_VADE_LISTESI | SDBILLDL | TUM_ORG | BATCH_SD | 11/18/2026 | Error | Variant TUM_ORG not found for the program |
How does the program work?
- The file is read; consecutive rows with the same job name are grouped as steps of one job.
- Checks: the program exists in TRDIR and is executable (SUBC = 1); the variant exists in VARID; the step user exists in USR02, is not locked and has an allowed type (default: system or service user); the start time is not in the past.
- Depending on the selection, scheduled (P) or released (S) jobs with the same name are found with BP_JOB_READ and deleted with BP_JOB_DELETE if the replace option is on; otherwise the row is skipped.
- In test mode only the check results are listed. In a real run the job is opened with JOB_OPEN and each step is added with JOB_SUBMIT with program, variant and step user.
- JOB_CLOSE sets the start date/time, the period (minutes, hours, days, weeks, months) and the target server; depending on the selection the job is released immediately or left as scheduled.
- The result is shown per row in ALV: job count, status and message; double-clicking the job name opens SM37.
Performance notes
Job creation is fast; a few hundred jobs are set up in under a minute. Read the checks once for the distinct programs, variants and users in the file. On a production system, always use test mode and an approved job plan before the real run.
Features
- Test mode (check without posting) Test mode runs program, variant, user and time checks without creating jobs.
- ALV list (sort, filter, subtotals)
- Line-by-line result and error log
- Download failed lines as a separate file Failed rows can be downloaded in the same template, corrected and uploaded again.
- Double-click drill-down to the document Double-clicking the job name opens SM37.
Authorization objects
- S_BTCH_JOBCreate and release jobs in the job group (RELE)
- S_BTCH_NAMRun a step under another user name
- S_BTCH_ADMDelete and change jobs of other users
Frequently asked questions
Can I export the current job plan and load it into another system?
Yes, an export option in the same template can be added: released periodic jobs in the source system are written to a file, edited and loaded in the target system. This takes about one extra day.
Can event-triggered jobs be scheduled as well?
The basic template covers time-based starts. By adding event ID and parameter columns to the file, event-triggered jobs can also be scheduled with JOB_CLOSE; predecessor job chains can be added the same way.
Can spool recipients or print parameters be provided?
Yes. Columns for printer, print immediately and spool list recipient per step can be added; JOB_SUBMIT supports these print parameters.
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
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 …
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 …
Let us build this program for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.