Symptom :
There are a number of jobs that must periodically run in a live SAP installation, for example, to delete outdated jobs or spool objects.
As of Release 4.6C, you can easily schedule these jobs as follows:
TCode
SM36 -> '
Standard jobs' button.
Unfortunately, there is no easy-to-use support for such jobs within Basis Customizing before Release 4.6C. Therefore, you must schedule the jobs explicitly for these release levels.
This note contains a list of the required programs, their parameters, and the recommended repeat interval. In addition, names are suggested for the required jobs. Adhere to the recommendations, as the naming conventions enable us to check quickly and easily whether these jobs have been activated in your system.
This note applies as of Releases 2.1G and 2.2A.
Solution :
Job name: Program Variant Repeat interval
SAP_REORG_JOBS
RSBTCDEL2
Yes
Daily
SAP_REORG_SPOOL
RSPO0041/1041
Yes
Daily
SAP_REORG_BATCHINPUT
RSBDCREO
Yes
Daily
SAP_REORG_ABAPDUMPS
RSSNAPDL
Yes
Daily
SAP_REORG_JOBSTATISTIC
RSBPSTDE
Yes Monthly
SAP_COLLECTOR_FOR_JOBSTATISTIC
RSBPCOLL
No
Daily
SAP_COLLECTOR_FOR_PERFMONITOR RSCOLL00
No
Hourly
SAP_COLLECTOR_FOR_NONE_R3_STAT RSN3_STAT_
No
Hourly
COLLECTOR
SAP_REORG_PRIPARAMS
RSBTCPRIDEL,
Yes*
Monthly
SAP_REORG_XMILOG
RSXMILOGREORG
Yes
Weekly
SAP_CCMS_MONI_BATCH_DP
RSAL_BATCH_
No
Hourly
TOOL_DISPATCHING
SAP_SPOOL_CONSISTENCY_CHECK
RSPO1043
Yes
Daily
SAP_REORG_ORPHANED_JOBLOGS
RSTS0024
Yes
Weekly
SAP_CHECK_ACTIVE_JOBS
BTCAUX07
Yes
Hourly
SAP_DELETE_ORPHANED_IVARIS
BTC_DELETE_ORPHANED_IVARIS
Yes
Weekly
SAP_REORG_ORPHANED_TEMSE_FILES RSTS0043
Yes
Weekly
Note:
SAP_CCMS_MONI_BATCH_DP is not a reorganization job but is needed to start tools/methods in the system monitoring area in the background ->
transaction RZ20/RZ21.
SAP_REORG_XMILOG reorganizes the table
TXMILOGRAW. This table contains log information on the XMI interface.
As of Release 4.6A, the job steps are managed separately from the print parameters. This means that report
RSBTCDEL no longer deletes any print parameters. You must, therefore, schedule the following report, too:
RSBTCPRIDEL
It reorganizes print parameters in a cross-client manner. Since the number of print parameters increases more slowly than the number of background processing steps, you can execute this report after longer periods of time ( longer than one month).
You must refer to Note 307970 in connection with
RSBTCPRIDEL.
The job
SAP_COLLECTOR_FOR_PERFMONITOR was previously also called
COLLECTOR_FOR_PERFORMANCEMONITOR.
The job
SAP_COLLECTOR_FOR_NONE_R3_STAT is available as of SAP Web Application Server 6.20 only.
In addition, you should regularly run a consistency check of the spooler and the TemSe (Note 48400).
***** Caution: The standard job
SAP_REORG_UPDATERECORDS that was contained in some delivered versions must no longer be executed (see Note 67014). In its new version, the underlying ABAP Program RSM13002 is programmed so that it terminates when running in a job (that is, in the background). Therefore, the job
SAP_REORG_UPDATERECORDS always terminates in this case. In any case, the job
SAP_REORG_UPDATERECORDS should be deleted from the pool of standard jobs, if it is still there:
SM36 -> '
Standard jobs' button -> 'Delete standard jobs' button. In addition, released jobs that may exist and contain report
RSM13002 should be deleted. You can find and delete these jobs using sm37.
***** Caution: The job
SAP_WP_CACHE_RELOAD_FULL is normally used to update data from the workplace component system to the workplace server.
This job is allowed to be run on a workplace server only; otherwise, it terminates. In the future, this job will no longer be delivered as a standard job.
If this job has been scheduled for your system, but you do not need it, delete the scheduled job in transaction
SM37.
To eliminate
ABAP dumps that are created due to runtime errors within an ABAP program, use the program
RSSNAPDL. To simplify the associated job scheduling, you also have the program
RSNAPJOB. This program schedules RSSNAPDL within a job. Implicit assumptions:
Job name:
RSSNAPDL
Variant:
DEFAULT (therefore it must exist)
Start date: From the following day, 1:00 am
Repeat interval: Daily
Using the Support Packages specified in Note 666290, report RSTS0024 deletes job logs that no longer belong to any job. Contact SAP if you need the report in a release that is not specified in SAP Note 666290.
Clients and authorizations
Some of the jobs specified work with client-specific objects (for example, jobs). Whether a reorganization has any cross-client influence then normally depends on particular authorizations. The following table displays all of the client-dependent jobs. All of the other jobs are not client-dependent.
Jobs that are not client-dependent perform a reorganization in all affected clients. They require neither special authorizations nor a special user name.
The job SAP_COLLECTOR_FOR_PERFMONITOR must always be scheduled in client 000 with user DDIC or with a user with the same authorization.
For some jobs, note the following correlations:
Job
SAP_REORG_JOBS:
An authorization for the object
S_BTCH_ADM = 'Y' is required in order to be able to delete jobs of other users and in other clients.
Job
SAP_REORG_SPOOL:
Authorization
S_ADMI_FCD-S_ADMI_FCD = 'SPAD'
Reorganization runs in chosen client (Client = '*', then runs in all clients)
Authorization
S_ADMI_FCD-S_ADMI_FCD = 'SPAR'
Reorganization only in the client in which the actual job is running
Job
SAP_REORG_BATCHINPUT:
Authorization profile
S_BDC_MONI - BDCAKTI = 'REOG'
S_BDC_MONI - BDCGROUPID = '*'
Reorganization only in the client in which the job is running (as of SAP Note 2177694 and Release 7.00, cross-client).
More details Refer the Snote:
16083
