SAPFree calculatorPDF, Excel, Word exportSAP ECC 6.0All SAP ECC 6.0 tools

SAP Batch Job Log and Spool Table Growth Calculator (TBTCO, TBTCP, TSP01, TST03)

This calculator estimates how much background job and spool data an SAP ECC 6.0 system keeps at steady state, from jobs per day and the retention you set in the standard reorganisation jobs. It shows row counts in TBTCO, TBTCP and TSP01 and the TemSe storage in TST03 or the file system.

Your numbers

Jobs per day

jobs

Average steps per job

steps

Jobs that create spool output

40 %

Average job log size

Average spool request size

Job retention (RSBTCDEL2 / SAP_REORG_JOBS)

14 days

Spool retention (RSPO1041 / SAP_REORG_SPOOL)

14 days

Spool data storage (rspo/store_location)

Your results

Database growth in TST03

1,093.75

MB. Zero when spool data is stored in files.

Total retained TemSe

1,531.25

MB, job logs plus spool data.

TBTCO job header rows retained

56,000

TBTCP job step rows retained

84,000

TSP01 spool request rows retained

22,400

Job log TemSe (file system)

437.5

MB. Job logs are TemSe objects stored as files.

Spool TemSe data

1,093.75

MB.

Steady-state estimate assuming the reorganisation jobs run daily. Measure real averages in SP12 (TemSe administration) and SM37 before sizing.

Save results:

Retained spool and TemSe MB vs spool retention days

Sweeps Spool retention (RSPO1041 / SAP_REORG_SPOOL) from 1 to 90, holding your other inputs fixed.

Want a housekeeping check of your ECC system?

Send us TBTCO and TSP01 counts and your SP12 TemSe figures and we will review retention variants and the standard job schedule.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

Which tables hold batch jobs and spool

Each background job has a header row in TBTCO with name, count, status, scheduler and start and end times, and one row per step in TBTCP with the program or command, variant and print parameters. Spool requests are listed in TSP01, and their content is a TemSe object, catalogued in TST01. Where spool data physically sits depends on the profile parameter rspo/store_location: db stores it in table TST03 in the database, G stores it as files in the global directory. Job logs are also TemSe objects but are kept as files, so they consume file system space, not TST03. SM37 reads TBTCO and TBTCP; SP01 reads TSP01; SP12 shows TemSe usage and runs consistency checks.

TBTCO: job header and status, TBTCP: job steps
TSP01: spool requests, TST01: TemSe objects
TST03: TemSe data when rspo/store_location = db
SM37, SP01, SP12 for monitoring

How the estimate is calculated

At steady state the reorganisation job deletes what is older than the retention, so retained rows equal daily volume x retention. TBTCO rows = jobs per day x job retention. TBTCP rows = jobs x average steps x job retention. TSP01 rows = jobs x spool share x spool retention, assuming one spool request per spooling job. Job log MB = jobs x log KB x job retention / 1024. Spool MB = spooling jobs x spool KB x spool retention / 1024. TST03 growth equals spool MB when spool data is stored in the database and zero when it is in files. Use real averages: SP12 TemSe data storage shows sizes by object type, and a count of TBTCO by end date shows your actual jobs per day.

Worked example

4,000 jobs a day, 1.5 steps each, 40% with spool output, 8 KB per job log, 50 KB per spool request, 14 days retention for both, spool in the database. TBTCO keeps 56,000 rows and TBTCP 84,000. TSP01 holds 22,400 requests. Job logs take about 438 MB of file system space and spool about 1,094 MB of TST03. Raising spool retention to 60 days pushes TST03 to roughly 4.7 GB. The chart sweeps spool retention from 1 to 90 days. If audit needs long retention for specific outputs, archive those to an optical archive or document management system rather than keeping all spool in TST03.

The standard housekeeping jobs

SAP delivers standard jobs you schedule in SM36 (Standard Jobs): SAP_REORG_JOBS runs RSBTCDEL2 to delete old jobs and their logs; SAP_REORG_SPOOL runs RSPO0041, or the newer RSPO1041, to delete old spool requests; SAP_REORG_ORPHANED_JOBLOGS runs RSTS0024 for job logs whose job no longer exists; and SAP_SPOOL_CONSISTENCY_CHECK runs RSPO1043 to remove inconsistent spool objects. Run them daily with variants per retention class, for example shorter retention for frequent technical jobs. Missing housekeeping is a common cause of slow SM37 and SP01 and of a large TST03.

Frequently Asked Questions

What is the SAP batch job log table?

Job logs are not stored in a normal table row. They are TemSe objects kept as files in the global directory, displayed from SM37. The job header with status is in TBTCO and the steps in TBTCP. Deleting old jobs with RSBTCDEL2 also removes their logs; RSTS0024 cleans orphaned logs.

Which table stores the spool of an SAP batch job?

TBTCP holds the step and its print parameters, TSP01 lists spool requests with the creating user and date, and the spool content is a TemSe object catalogued in TST01. Content sits in TST03 when rspo/store_location is db, or in files when it is G. SP01 shows spool requests by job or user.

What are the main SAP batch job tables?

TBTCO (job header and status), TBTCP (job steps), TBTCS (time-scheduled jobs for the batch scheduler) and BTCEVTJOB (jobs waiting for events). For spool, TSP01 lists requests, TST01 catalogs TemSe objects and TST03 stores TemSe data in the database.

How do I monitor SAP batch jobs?

Use SM37 to list jobs by name, user, status and date, and open the log for failures. SM36 schedules jobs and the standard housekeeping jobs. For volume, count TBTCO rows by status and end date. Many teams also send cancelled job alerts through CCMS or Solution Manager.

If your operations team wants to ask which jobs failed overnight and why in plain English against ECC on your own servers, we can set up a private, read-only AI layer over TBTCO and the job logs.

Talk to an Expert Explore More Free Tools