TBTCS table — Time-Based Background Jobs Waiting to Start
TBTCS contains one entry for each time-based background job that has a date-and-time start condition and has not started yet. The background-processing time scheduler periodically scans this table and starts due jobs. TBTCS is not the job-status text table; TBTCO is the main job header table and TBTCP stores the individual job steps.
Verified practitioner reference for Time-Based Background Jobs Waiting to Start. It explains the table's real business role, safe keys and joins, proof path, S/4HANA behavior, common misinterpretations, ownership, and related SAP objects.
Published 20 Sept 2026· 601 words
Purpose
TBTCS is a runtime scheduling table for classic SAP background processing. SAP documentation describes it as the list of time-based jobs that have not started yet. Each qualifying job has a scheduling entry so the time scheduler can find jobs whose planned start time has been reached. The durable job definition/status remains in TBTCO and the job steps remain in TBTCP.
Key fields
The exact DDIC field set is release dependent, so investigation should start from the job identity and scheduled-start context rather than invented status-text fields.
- Job name and job count identify the scheduled background job together.
- Scheduled date/time and start-condition fields determine when the time scheduler can pick the job up.
- Client/user or scheduler context helps distinguish identical job names across scopes.
- TBTCO is the authoritative companion for the job header and current processing status.
- TBTCP contains the ABAP program, variant, external command, or other step definitions.
How it joins the data model
Join or reconcile TBTCS to TBTCO using the background job identity (job name and job count) in the same client. Use TBTCP for step details. Event-based jobs that are still waiting use separate background-processing runtime structures rather than being the same TBTCS population.
How to read it safely
Use TBTCS only to answer whether a time-based job is still waiting in the scheduler queue and what start condition it is waiting for. Do not use it as a historical status report. Once the scheduler starts the job, its TBTCS waiting entry is no longer the right source; SM37/TBTCO and the job log/spool become the evidence for execution and outcome.
How to prove it in the data
For a job that should have started but did not, identify the exact job name/count in SM37 or TBTCO, then check whether a corresponding TBTCS entry still exists and whether its scheduled start time is already in the past. If it is still waiting, continue with scheduler/runtime checks; if it has left TBTCS, inspect TBTCO status, work-process history, and job log before assuming the scheduler missed it.
ECC vs S/4HANA
TBTCS remains part of the classic ABAP background-processing runtime in S/4HANA. Newer job-management capabilities can schedule or monitor jobs through higher-level frameworks, but classic SM36/SM37 jobs still rely on the traditional background-processing tables. The important semantic point is unchanged: TBTCS is a waiting time-schedule table, not a table of human-readable job statuses.
Common pitfalls
- Treating TBTCS as a status-text lookup and trying to translate TBTCO status codes from it.
- Using a job name without job count and accidentally mixing multiple scheduled instances.
- Expecting completed or active jobs to remain represented as waiting TBTCS entries.
- Deleting scheduler rows manually instead of correcting the job definition/start condition through standard background-job administration.
- Diagnosing a scheduler issue without checking whether the job was event-based rather than time-based.
Whose problem this is
Primary ownership is Basis/background-processing administration. Application teams own the program and variant logic inside the job; Basis owns scheduler availability, work-process capacity, server groups, and runtime administration. ABAP joins only when the job starts but the program itself fails or hangs.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tables/tbtcsERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.