1 Best-Practice Document: Housekeeping

You can delete some types of data from your system very soon after it has been created. You should carry out deletion
at regular intervals for the data discussed in this section. See SAP Note 16083 (release- independent). When
performing our recommendations, use the recommended job names within the single chapters, as they can be used to
check if the jobs have already been active in your system.
Where applicable, we have included a section on the deletion of data under the table-specific sections of this document.
See also SAP Notes:

 2388483 - How-To: Data Management for Technical Tables

 16083 (release-independent): Standard Jobs, Reorg Jobs

 48400 (SAP_BASIS 610 – 710): Reorganization of TemSe and Spool

 800927 (SAP_APO 713 – 310, SCM 700 – SCM713): Standard jobs in the SCM/APO area

 1034532 (SAP_BASIS 640 – 720): Changes for standard jobs

 1411877 (SAP_BASIS 640 - 730): New standard jobs

 1829728 (SAP_BW 730 – 740): BW Housekeeping Task List
 2581518 - SAP_BASIS (SAP_BASIS 750 – 753) Jobs in the Technical Job Repository
(SJOBREPO)Housekeeping for Background Jobs

 2718597 - Collection solutions for some big growth tables relevant to HANA DB

1.1 Administration Data for Background Jobs

 Program: RSBTCDEL2

 Reorganized tables: BTC*

 Job scheduling: Daily (with variants)

 Recommended job name: SAP_REORG_JOBS
This report deletes old background jobs.
See also SAP Notes:

 784969 (SAP_BASIS 640): Program RSBTCDEL2

 852351 (SAP_BASIS 640 – 711): Program RSBTCDEL2: Enhancement (2)

 1893670 (SAP_BASIS 700 – 740): Problems with RSBTCCNS (SM65)

Important recommendation: Please ensure that report RSBTCDEL2 is replacing the former report
RSBTCDEL. Also, make sure that you reschedule your jobs with the new report name.

1.2 Print Parameters for Background Jobs

 Program: RSBTCPRIDEL

 Reorganized tables: TPRI_PAR

 Job scheduling: monthly (with variants)

  Recommended job name: SAP_REORG_PRIPARAMS
See also SAP Notes:

 759682 (SAP_BASIS 620 - 640): Performance problems when scheduling batch jobs

 1407635 (SAP_BASIS 700 – 720): Unnecessary database accesses in RSBTCPRIDEL

 2581518 - SAP_BASIS (SAP_BASIS 750 – 753) Jobs in the Technical Job Repository
(SJOBREPO)Housekeeping for Background Jobs

1.3 Runtime Statistics for Background Jobs

 Program: RSBPSTDE
 Reorganized tables: BTCJSTAT*

 Job scheduling: monthly (with variants)

 Recommended job name: SAP_REORG_JOBSTATISTIC

This report deletes old data from the job runtime statistics.

Please see SAP Note 16083 - Standard jobs, reorganization jobs.

In SAP S/4HANA, please see SAP Note 2190119 - Background information about S/4HANA technical job repository.

1.4 Consistency Check for Administration Tables of Background Jobs

 Program: RSBTCCNS

 Reorganized tables: TBTC*

 Job scheduling: daily (with variants)

 Recommended job name: SAP_BTC_TABLE_CONSISTENCY_CHECK
This report checks the consistency of job definitions and repairs erroneous entries. See
also SAP Notes:
 1549293 (SAP_BASIS 700 - 740): SM65: Improvements in consistency check

 1893670 (SAP_BASIS 700 – 740): Problems with RSBTCCNS (SM65)

 2581518 - SAP_BASIS Jobs in the Technical Job Repository (SJOBREPO)

1.5 Orphaned Temporary Variants in Table VARI

 Program: BTC_DELETE_ORPHANED_IVARIS
 Reorganized tables: VARI

 Job scheduling: weekly (with variants)

 Recommended job name: SAP_DELETE_ORPHANED_IVARIS

If you schedule a report as a background job, the system generates a variant called &0000000000xxx for the report.
However, if an error occurs during scheduling, the generated variant is not deleted.
See also SAP Notes:
  1021775 (SAP_BASIS 640 – 711): Orphaned temporary variants in the table VARI
 2581518 - SAP_BASIS Jobs in the Technical Job Repository (SJOBREPO)
1.6 Housekeeping for Spool Data

1.7 Spool Data and Administration Data for Spool Jobs

 Program: RSPO1041
 Reorganized tables: TSP*

 Job scheduling: Daily (with variants)

 Recommended job name: SAP_REORG_SPOOL

This report deletes old spool data.

See also SAP Notes:

 130978 (SAP_BASIS 610 - 710): RSPO1041 - Replacement for RSPO0041
 852141 - Large spool request cannot be deleted
Important recommendation: Please ensure that report RSPO1041 is replacing the former report
RSPO0041. Also, make sure that you reschedule your jobs with the new report name.

1.8 Spool Data Consistency Check

 Program: RSPO1043
 Reorganized tables: TSP*, TST01, TST03

 Job scheduling: Daily (with variants)

 Recommended job name: SAP_SPOOL_CONSISTENCY_CHECK

Report RSPO1043 enables the continuous monitoring of inconsistent spool objects (example: no entries in TST01 but
entries in TST03 for a selected spool are available). Just as in RSPO0043, the write locks are analyzed and, if
necessary, deleted. In contrast to report RSPO0043, report RSPO1043 can run in parallel to the other activities in the
background. To do this, the report must run daily.
See also SAP Notes:

 98065 (SAP_APPL 610 - 700): Spool consistency check with RSPO1043 as of 4.0A
 1748033 (SAP_BASIS 620 – 740): RSPO1043 does not delete all inconsistencies

Important recommendation: Please ensure that report RSPO1043 is replacing the former report
RSPO0043. Also, make sure that you reschedule your jobs with the new report name.

1.9 Orphaned ADS Spool Files

 Program: RSPO1042
 Job scheduling: Daily (with variants)

 Recommended job name: SAP_ADS_SPOOL_CONSISTENCY_CHECK

The DIR_GLOBAL directory or in the client-specific ADSP subdirectories contain files starting with SPOOL. Some of
them may be very old. Usually, these files are removed by deleting the relevant spool request.
However, under certain circumstances, these files may remain in the system as "orphaned" files. To reorganize these
files, you can use report RSPO1042.
See also SAP Notes:

 1440439 (SAP_BASIS 700 – 740): New Standard Jobs (2)

 1493058 (SAP_BASIS 700 – 740): Orphaned ADS files

1.10 Orphaned Job Logs

 Program: RSTS0024

 Reorganized tables: TST01

 Job scheduling: Weekly (with variants)

 Recommended job name: SAP_REORG_ORPHANED_JOBLOGS

The TST01 table can contain job log headers or files that are older than the jobs in the TBTCO table. To delete such
“orphaned” job logs, you can use report RSTS0024.

See also SAP Notes:

 666290 (SAP_BASIS 610 – 710): Deleting “orphaned” job logs

 1293277 (SAP_BASIS 620 – 720): Report RSTS0024 runs for a very long time

 1436325 (SAP_BASIS 700 – 720): TemSe objects JOBLGX_ZOMBIE

 1605708 (SAP_BASIS 710 – 802): RSTS0024 terminates with COMPUTE_INT_TIMES_OVERFLOW

1.11 TemSe: File System Against TST01
 Program: RSTS0043

 Job scheduling: Weekly (with variants)

 Recommended job name: SAP_REORG_ORPHANED_TEMSE_FILES

Files (for example, spool requests, job logs, batch input logs) are stored on the file system but the relevant entries are
missing in table TST01.

See also SAP Notes:

 936049 (SAP_BASIS710 - 711): TemSe: Consistency check, file system against TST01

 1246731 (SAP_BASIS 640 – 731): RSTS0043: Some of the job logs are not recognized
 1272528 (SAP_BASIS 620 – 711): RSTS0043: All orphaned logs are not deleted

 1676870 (SAP_BASIS 700 – 731): RSTS0043 incorrectly deletes files

1.12 Administration Data for Batch Input
 Program: RSBDCREO or RSBDC_REORG (different selection screen)

 Reorganized tables: BDC* and APQ*

 Job scheduling: daily (with variants)

  Recommended job name: SAP_REORG_BATCHINPUT
This report deletes old batch input sessions.

See also SAP Notes:

 147354 (release-independent): Batch input: Reorg. and delete sessions and logs
1.13 ABAP Short Dumps
 Program: RSSNAPDL
RSNAPJOB (program to schedule report RSSNAPDL as a job)

 Reorganized tables: SNAP

 Job scheduling: daily (with variants)

 Recommended job name: SAP_REORG_ABAPDUMPS

This report deletes old ABAP short dumps.

See also SAP Notes:

 11838 (release-independent): Deleting short dumps from the SNAP table

 1091769 (SAP_BASIS 700 – 710): RSSNAPDL deletes too many short dumps
1.14 External Job Scheduling Tools
 Program: RSXMILOGREORG
 Reorganized tables: TXMILOGRAW

 Job scheduling: weekly (recommended)

 Recommended job name: SAP_REORG_XMILOG

If you use external job scheduling programs, XMI log entries are written to table TXMILOGRAW. As a result, this
table can grow quite large and should be reorganized periodically.
Program RSXMILOGREORG is available to delete XMI logs.

A weekly reorganization of your tables should delete any entries that are older than seven days. If the table is already
large, we recommend that you use the reorganization method TRUNCATE at database level. This can be done without
any negative consequences because the table does not have any dependencies to other tables. For more information, see
SAP Note 182963.
SAP Note 852933 (SAP NetWeaver AS 6.40 – 7.00) provides information about how to speed up the deletion process
when you are using reorganization program RSXMILOGREORG.

See also SAP Notes:

 852933 (SAP_BASIS 620 – 700): XMILOG-Reorg: Performance optimization

 1715863 (SAP_BASIS 700 – 731): Entries too frequent in XMI log

1.15 Checking Database Indexes
If your system has very slow response times, check whether your database indexes are fragmented in
any way. If your system is showing signs of fragmentation, regenerate your indexes or defragment
them. If changes are made to tables on a regular basis, we recommend that you regenerate your indexes
or defragment them on a regular basis, such as once a week.
Important recommendation: Indexes should be regenerated regularly in retail if your database does not
do so automatically (for example, Oracle databases cannot perform this function)

1.16 Housekeeping for SAP CRM

1.17 CRM Middleware Tables

 Program: SMO6_REORG2
In SAP Customer Relationship Management (SAP CRM) and SAP Supplier Relationship Management
(SAP SRM), it is common to see strong growth of BDoc and trace tables in CRM Middleware. This
could have a negative impact on performance during the processing of BDocs.
See SAP Note:

 2086931 - Middleware Reorganization Reports (BBPCRM 712 -714)

 1138051 (BBPCRM 400 – 600) Deactivation of BDoc to Object links

 1876287 (BBPCRM 5.0 – 7.13): Performance Optimization Of SMO6_REORG

 2388483 - How-To: Data Management for Technical Tables
1.18 Housekeeping for SAP Solution Manager (BW Housekeeping for Diagnostics)
 Program: E2E_HK_CONTROLLER
 Job scheduling: daily

 Recommended job name: E2E BI HOUSEKEEPING

A central housekeeping process (report E2E_HK_CONTROLLER) runs on a daily basis on SAP
Solution Manager ABAP. Please make sure that the following SAP Notes are implemented in your
system:

See SAP Note:

 1480588 (Solution Manager ST 400 – 710): ST: E2E Diagnostics – BI Housekeeping – Information
 894279 (Solution Manager ST 400 – 720) Background processing in SAP Solution Manager
1.19 Housekeeping for SAP BW Systems
For performing a regular housekeeping on your SAP BW system, please take care of SAP Note
1829728, which provides detailed information about regular tasks and tools.

See SAP Note:

 1829728 (SAP_BW 700 - 740): BW Housekeeping Task List

 1734333 - BW Pre and Post Upgrade and Migration Tasks