How to run background maintenance jobs

This procedure will detail seven reorganization programs that SAP suggests are run on an SAP
system. These reports provide system maintenance for any SAP system. These programs, which
should be scheduled in the background, delete/reorganize information that has become outdated
or is no longer in use.
SAP Note 16083

PROCEDURE
The six programs that should be run in the background for SAP Maintenance are as follows:
RSBTCDEL
RSPO0041
RSBDCREO
RSSNAPDL
RSBPCOLL
RSBPSTDE
RSCOLL00
RSBTCDEL
This program is responsible for cleaning up background jobs. This program is used to remove
all background job records from the queue which have run successfully and are at least x days
old. The program parameters can be defined to delete scheduled, released, finished, or canceled
jobs. The default is set for finished and canceled jobs. A variant must be defined for this job.
The recommended frequency for this job is daily during off-peak hours.
RSPO0041
This program is responsible for removing spooling objects. Every print request produces a spool
object and is archived in case of system failure. These spool objects, printed or not, can then be
removed depending on the input criteria of the variant. The recommended frequency is at least
once per day depending on system load and the number of spool object printouts.
RSBDCREO -
This program is responsible for cleaning up the batch input session log. If the batch input
functionality of the R/3 system is utilized, log entries are produced. The recommended
frequency is once per day.
RSSNAPDL
This program is used to delete old short dumps from the SNAP table. It deletes any short dumps
that are more than one week old and not flagged as protected. It is also possible to select short
dumps you want to keep longer than this in Transaction ST22. To avoid table overflow, the
program also deletes more recent short dumps, if there are large numbers of dumps. For this
reason, you should flag any short dumps you want to protect as soon as possible. The values
specified in the variant refer to number of table entries, not the number of short dumps (a short
dump can generate many table entries). The recommended usage of the report is daily.
RSBPCOLL
This program is responsible for calculating the runtime statistics information. A variant is not
needed to run this report. This job only takes the periodic jobs which have terminated normally
and calculates an average runtime statistic for each job. This data is stored in the transparent
database table BTCJSTAT. This table needs periodic reorganization to get rid of any old
runtime statistics. This report should be run daily depending on system load.
RSBPSTDE
This program is responsible for cleaning the job runtime statistics information. This job deletes
the statistics which have not been updated either since the specified date or the number of days in
the variant. The recommended frequency to run this report is once a month.
RSCOLL00
This program is responsible for collecting performance data across all applicable R/3 servers. No
variant is needed. The recommended frequency is once an hour.
Below is a summary of the seven jobs detailed above. The chart gives a suggested job name, the
actual program name that is running, whether it needs a variant or not, whether it is client-
dependent, and how often it should be run.







Please refer to the document titled Procedures for Scheduling Reports (11000.doc). This will
detail the procedures for scheduling the jobs listed above.
Jobs that are not client-dependent perform in all existing clients.
The job SAP_COLLECTOR_FOR_PERFMONITOR is always scheduled in client 000 with user
DDIC.
It is good practice to schedule these jobs in all SAP systems and all client-dependent jobs, in all
clients within that system.