In SAP a few jobs are scheduled to run periodically, which helps the system to run stable in terms of performance.
Following is the list of standard SAP jobs:
| Background Job Name & Description | Program | Schedule |
| SAP_COLLECTOR_FOR_PERFMONITOR | RSCOLL00 | Hourly |
| SAP_REORG_JOBS_<client no.> | RSBTCDEL | Daily |
| SAP_REORG_SPOOL_<client no.> | RSPO0041 | Daily |
| SAP_REORG_BATCHINPUT_<client no.> | RSBDCREO | Daily |
| SAP_REORG_ABAPDUMPS | RSSNAPDL | Daily |
| SAP_COLLECTOR_FOR_JOBSTATISTIC | RSBPCOLL | Daily |
| DBA:CHECKOPT…* | RSDBAJOB | Weekly |
| DBA:ANALYZETAB…* | RSDBAJOB | Weekly |
| SAP_REORG_TEMSE_CHECK_<client no.> | RSTS0020 | Weekly |
| SAP_REORG_JOBSTATISTIC | RSBPSTDE | Monthly |
| SAP_REORG_IDOC_<client no.> | RBDCPCLR | Monthly |
RSCOLL00:
Runs periodically in the central SAP System and looks in the table TCOLL to see what programs should be started on the various hosts to get the statistics data.
The statistics data will be sent from the local host to the central host, therefore CCMS data is refreshed as often as RSCOLL00 runs. It has components RSSTAT80 that reads local statistic data from shared memory and stores it in the performance table MONI, and RSSTAT60 that creates statistic data for day, week, month, year and reorganizes the table MONI. It also updates the following other tables:
- RSHOSTDB - data for host system monitor,
- RSHOSTPH - protocol changes on host parameters
- RSORATDB - analyzes the space of the database
- RSORAPAR - protocol changes on database parameters
This job was previously also called COLLECTOR_FOR_PERFORMANCE_MONITOR.
Read here: How to overcome the problem of Spool full or Spool overflow?
RSBTCDEL:
Deletes old job logs. At the OS level, under /sapmnt/<SID>/global you can find different file systems (Eg: <#>JOBLG, where # is the client number) where SAP stores the job logs. It is recommended to clear the old jobs logs periodically. The RSBTCDEL program can be used to delete the old logs.
RSPO0041:
Deletes old spool requests.
RSBDCREO:
RSBDCREO program is to reorganize the batch input log file. Running this program reduces the size of the log file.
RSSNAPDL:
Delete old dumps produced by ABAP abnormal terminations. All the ABAP dumps will be stored in the SNAP table. As every dump requires more storage space, it is recommended to clear old dumps from the system to make room for the new dumps.
RSBPCOLL:
Generates runtime statistics for background jobs. RSBPCOLL collects the statistical data to analyze the average run time of the periodically executed jobs in the system.
RSDBAJOB:
Checks the connectivity to the database instance using brconnect.exe program.
Read here: SPOOL PROCESSING - An Overview
RSTS0020:
TemSe consistency check. You can use the spool consistency check to check whether tables that contain spool requests, output requests, and output data are inconsistent.
Along with deleting old spool requests, the spool consistency check is one of the most important functions for maintaining the SAP spool database.
The spool consistency check will be done on the following tables:
- Header entry in table TST01 (TemSe objects)
- Object associated with the header entry; it can be stored in the file system or in the database table TST03 (TemSe data of the object)
- Entry in table TSP01 (spool requests)
- Entry in table TSP02, if output requests exist
Read here: SPOOL MONITORING using SP01 and SP02
RSBPSTDE:
Delete Statistics Data from the Job Run-time Statistics.
RBDCPCLR:
Reorganization of change pointer table (BDCP) to delete all records transferred to IDoc.
Read more here SAP Background Jobs Tutorials