SymptomThereare a number of jobs that must periodically run in a live R/3installation, for example, to delete outdated jobs or spool objects.
As of Release 4.6C, you can easily schedule these jobs as follows:
Transaction sm36, choose 'Standard jobs'.
Unfortunately,there is no easy-to-use support for such jobs within Basis Customizingbefore Release 4.6C. Therefore, you must schedule the jobs explicitlyfor these release levels.
This note contains a list of the requiredprograms, their parameters, and the recommended repeat interval. Inaddition, names are suggested for the required jobs. Adhere to therecommendations, as the naming conventions enable us to check quicklyand easily whether these jobs have been activated in your system.
This note applies as of Releases 2.1G and 2.2A.
Exceptions:
Program RSXMILOGREORG is only available as of Release 4.6C.
In earlier releases, use ZRSXMILOGREORG
from Note 182963.
Program RSAL_BATCH_TOOL_DISPATCHING is only available as
of Release 4.6A.
Other termsREORGJOBS.
Reason and PrerequisitesNote: Application-specific reorganization programs are not included in this list.
SolutionJob 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 | no | 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
In any case, refer to Note 48400 regarding the spool and TemSe
consistency check.
For Business Information Warehouse (BW) only (also see the relevant comments below)Job name | Program | Variant | Repeat interval
SAP_ANALYZE_ALL_INFOCUBES | SAP_ANALYZE_ALL_INFOCUBES
| yes | weekly
Note:
- SAP_CCMS_MONI_BATCH_DPis not a reorganization job but is needed to start tools / methods inthe system monitoring area in the background -> transactionRZ20/RZ21.
- SAP_REORG_XMILOG reorganizes the tableTXMILOGRAW. This table contains log information on the XMI interface(-> Note 182963).
- As of Release 4.6A, the jobsteps are managed separately from the print parameters. This means thatreport RSBTCDEL no longer deletes any print parameters. Therefore youmust additionally schedule the report
RSBTCPRIDEL,
which 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_PERFORMANCE_MONITOR.
- The job SAP_COLLECTOR_FOR_NONE_R3_STAT is available as of SAP Web Application Server 6.20 only.
- On sapserv3, an improved version of RSPO0041 is available with RSPO1041 (Note 130978).
- In addition, you should regularly run a consistency check of the spooler and the TemSe (Note 48400).
- Batchinput reorganization may not run at the same time as normal batch inputactivity up to and including SAP Release 30C (see Note 18307). Theassociated job must be scheduled for a time when no other batch inputactivity is scheduled.
- ***** Caution: The standardjob SAP_REORG_UPDATERECORDS that was contained in some deliveredversions must no longer be executed (see Note 67014). In its newversion, the underlying ABAP Program RSM13002 is programmed so that itterminates when running in a job (that is, in the background).Therefore, the job SAP_REORG_UPDATERECORDS always terminates in thiscase. In any case, the job SAP_REORG_UPDATERECORDS should be deletedfrom the pool of standard jobs, if it is still there: sm36 ->'Standard jobs' -> 'Delete standard jobs'. In addition, releasedjobs that may exist and contain report RSM13002 should be deleted. Youcan find and delete these jobs using sm37.
- *****Caution: The job SAP_WP_CACHE_RELOAD_FULL is normally used to updatedata from the workplace component system to the workplace server.
Thisjob can only be run on a workplace server, otherwise it will terminate.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.
- Toeliminate ABAP dumps that are created due to runtime errors within anABAP program, use the program RSSNAPDL. To simplify the related jobscheduling, you also have the program RSNAPJOB. This program schedulesRSSNAPDL within a job. Implicit assumptions:
- Variant: DEFAULT (therefore it must exist)
- Start date : from the following day, 1:00 am
- Usingthe Support Packages specified in Note 666290, report RSTS0024 deletesjob logs that no longer belong to any job. Contact SAP if you need thereport in a release that is not specified in Note 666290.
Clients and authorizationsSomeof the jobs specified work with client-specific objects (for example,jobs). Whether a reorganization has any cross-client influence thennormally depends on particular authorizations. The following tablegives an overview.
Job name | Client-dependent
------------------------------------------------------------------------
SAP_REORG_JOBS | no
SAP_REORG_SPOOL | yes
SAP_REORG_BATCHINPUT | yes
SAP_REORG_ABAPDUMPS | no
SAP_REORG_JOBSTATISTIC | no
SAP_COLLECTOR_FOR_JOBSTATISTIC | no
SAP_COLLECTOR_FOR_PERFMONITOR | no
SAP_REORG_XMILOG | no
SAP_CCMS_MONI_BATCH_DP | no
SAP_COLLECTOR_FOR_NONE_R3_STAT | no
RSTS0024 | no
Jobsthat are not client-dependent perform a reorganization in all affectedclients. They require neither special authorizations nor a special username.
The job SAP_COLLECTOR_FOR_PERFMONITOR must always be scheduledin client 000 with user DDIC or with a user with the same authorization.
For some jobs, note the following correlations:
- Ifthe user that calls RSBTCDEL2 is the batch administrator (that is,authorization S_BTCH_ADM mit BTCADMIN= Y), reorganization is carriedout in all clients.
- If the user is not the batch administrator, reorganization is carried out in the current client only.
Two cases have to be distinguished here:
Ifthe user has authorization S_BTCH_JOB with JOBGROUP = * and JOBACTION =DELE, all jobs that meet the selection criteria are deleted in thecurrent client.
If the user does not have this authorization either,only his/her own jobs are deleted, that is, all jobs in the currentclient that meet the selection criteria and belong to that user.
- 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
- Job SAP_ANALYZE_ALL_INFOCUBES:
This job is only relevant if database system Oracle or DB6 is used.
See Note 129252 (Oracle) or
328106 (DB6).
In addition, after the introduction of BRConnect 6. 10 Patch Level 11 and
BW 3.0A, this job should no longer be used.
See Notes 421795 and 428212.
Note:
- The authorizations always relate to the user under whose ID the job is being processed.
- Ifthis user has the necessary authorizations to work in a cross-clientmanner, then it does not matter in which client the actual job isrunning.
Examples- User ADMIN has theAuthorization S_BTCH_ADM = 'Y'. If Job SAP_REORG_JOBS is now scheduledwith User ADMIN, the jobs are reorganized in all clients.
- UserREORG has the Authorization profile S_BDC_ALL. If JobSAP_REORG_BATCHINPUT is now scheduled with User REORG in Client 002,the batch input objects are reorganized in Client 002.
- If the job SAP_REORG_ABAPDUMPS is scheduled in any client, all ABAP short dumps are reorganized in all clients.
- UserSPOOLADM has the authorization S_ADMI_FCD-S_ADMI_FCD = 'SPAD'. If thejob SAP_REORG_SPOOL is now scheduled with user SPOOLADM and client 123is specified for the program parameters, then the spool objects inclient 123 are reorganized irrespective of the client in which theactual job is running. If you enter '*' as the client, all clients arereorganized.
NOTES: The job steps should beplanned using a language that is available in the system. Englishshould be available in every system. However, some of these jobs havesteps set by default in German. The following is valid until furthernotice: the jobs must be modified if necessary when, for example, aRussian code page is used.
No comments:
Post a Comment