sapnote_0000016083

21.05.2011 of 7

SAP Note 16083 - Standard jobs, reorganization jobs

Note Language: English Version: 71 Validity: Valid Since 29.10.2010

Summary

SymptomThere are 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 BasisCustomizing before Release 4.6C. Therefore, you must schedule the jobsexplicitly for these release levels.This note contains a list of the required programs, their parameters, andthe recommended repeat interval. In addition, names are suggested for therequired jobs. Adhere to the recommendations, as the naming conventionsenable us to check quickly and easily whether these jobs have beenactivated 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 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 thislist.

Solution

Job name ProgramVariant Repeat interval

SAP_REORG_JOBS RSBTCDEL2 yes ddailySAP_REORG_SPOOL RSPO0041/1041 yyes dailySAP_REORG_BATCHINPUT RSBDCREO yes ddailySAP_REORG_ABAPDUMPS RSSNAPDL yes ddailySAP_REORG_JOBSTATISTIC RSBPSTDE yes mmonthlySAP_COLLECTOR_FOR_JOBSTATISTIC RSBPCOLL no ddailySAP_COLLECTOR_FOR_PERFMONITOR RSCOLL00 no hhourlySAP_COLLECTOR_FOR_NONE_R3_STAT RSN3_STAT_ nno hourly

COLLECTORSAP_REORG_PRIPARAMS RSBTCPRIDEL n

21.05.2011 of 7


no monthlySAP_REORG_XMILOG RSXMILOGREORG yyes weeklySAP_CCMS_MONI_BATCH_DP RSAL_BATCH_ no hourly

TOOL_DISPATCHINGSAP_SPOOL_CONSISTENCY_CHECK RSPO1043 yes ddailySAP_REORG_ORPHANED_JOBLOGS RSTS0024 yes wweeklySAP_CHECK_ACTIVE_JOBS BTCAUX07 yes hhourlySAP_DELETE_ORPHANED_IVARIS BTC_DELETE_ORPHANED_IVARIS ja weeklySAP_REORG_ORPHANED_TEMSE_FILES RSTS0043 ja wweekly

In any case, refer to Note 48400 regarding the spool and TemSeconsistency check.

For Business Information Warehouse (BW) only

(also see the relevant comments below)

Job name ProgramVariant Repeat interval

SAP_ANALYZE_ALL_INFOCUBES SAP_ANALYZE_ALL_INFOCUBES

yes weekly

Note:

o SAP_CCMS_MONI_BATCH_DP is not a reorganization job but is needed tostart tools / methods in the system monitoring area in thebackground -> transaction RZ20/RZ21.

o SAP_REORG_XMILOG reorganizes the table TXMILOGRAW. This tablecontains log information on the XMI interface (-> Note 182963).

o As of Release 4.6A, the job steps are managed separately from theprint parameters. This means that report RSBTCDEL no longer deletesany print parameters. Therefore you must additionally schedule thereport

RSBTCPRIDEL,

which reorganizes print parameters in a cross-client manner. Sincethe number of print parameters increases more slowly than thenumber of background processing steps, you can execute this reportafter longer periods of time ( longer than one month).You must refer to Note 307970 in connection with RSBTCPRIDEL.

o The job SAP_COLLECTOR_FOR_PERFMONITOR was previously also calledCOLLECTOR_FOR_PERFORMANCE_MONITOR.

21.05.2011 of 7


o The job SAP_COLLECTOR_FOR_NONE_R3_STAT is available as of SAP WebApplication Server 6.20 only.

o On sapserv3, an improved version of RSPO0041 is available withRSPO1041 (Note 130978).

o In addition, you should regularly run a consistency check of thespooler and the TemSe (Note 48400).

o Batch input reorganization may not run at the same time as normalbatch input activity up to and including SAP Release 30C (see Note18307). The associated job must be scheduled for a time when noother batch input activity is scheduled.

o ***** Caution: The standard job SAP_REORG_UPDATERECORDS that wascontained in some delivered versions must no longer be executed(see Note 67014). In its new version, the underlying ABAP ProgramRSM13002 is programmed so that it terminates when running in a job(that is, in the background). Therefore, the jobSAP_REORG_UPDATERECORDS always terminates in this case. In anycase, the job SAP_REORG_UPDATERECORDS should be deleted from thepool of standard jobs, if it is still there: sm36 -> 'Standardjobs' -> 'Delete standard jobs'. In addition, released jobs thatmay exist and contain report RSM13002 should be deleted. You canfind and delete these jobs using sm37.

o ***** Caution: The job SAP_WP_CACHE_RELOAD_FULL is normally used toupdate data from the workplace component system to the workplaceserver.This job can only be run on a workplace server, otherwise it willterminate. In the future, this job will no longer be delivered as astandard job.If this job has been scheduled for your system, but you do not needit, delete the scheduled job in transaction sm37.

o To eliminate ABAP dumps that are created due to runtime errorswithin an ABAP program, use the program RSSNAPDL. To simplify therelated job scheduling, you also have the program RSNAPJOB. Thisprogram 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

o Using the Support Packages specified in Note 666290, reportRSTS0024 deletes job logs that no longer belong to any job. ContactSAP if you need the report in a release that is not specified inNote 666290.

Clients and authorizationsSome of 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 table displays

21.05.2011 of 7


all of the client-dependent jobs. All of the other jobs are notclient-dependent.

Job name:SAP_REORG_BATCHINPUT

Jobs that 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 scheduled in client000 with user DDIC or with a user with the same authorization.

For some jobs, note the following correlations:

o Job SAP_REORG_JOBS:

- If the user that calls RSBTCDEL2 is the batch administrator(that is, authorization S_BTCH_ADM with BTCADMIN= Y),reorganization is carried out in all clients.

- If the user is not the batch administrator, reorganization iscarried out in the current client only.Two cases have to be distinguished here:If the user has authorization S_BTCH_JOB with JOBGROUP = * andJOBACTION = DELE, all jobs that meet the selection criteria aredeleted in the current client.If the user does not have this authorization either, onlyhis/her own jobs are deleted, that is, all jobs in the currentclient that meet the selection criteria and belong to thatuser.

o Job SAP_REORG_SPOOL:

- Authorization S_ADMI_FCD-S_ADMI_FCD = 'SPAD'Reorganization runs in chosen client (Client = '*', then runsin all clients)

- Authorization S_ADMI_FCD-S_ADMI_FCD = 'SPAR'Reorganization only in the client in which the actual job isrunning

o 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

o 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).

21.05.2011 of 7


In addition, after the introduction of BRConnect 6.10 Patch Level11 and

BW 3.0A, this job should no longer be used.See Notes 421795 and 428212.

Note:

o The authorizations always relate to the user under whose ID the jobis being processed.

o If this user has the necessary authorizations to work in across-client manner, then it does not matter in which client theactual job is running.

Examples

o User ADMIN has the Authorization S_BTCH_ADM = 'Y'. If JobSAP_REORG_JOBS is now scheduled with User ADMIN, the jobs arereorganized in all clients.

o User REORG has the Authorization profile S_BDC_ALL. If JobSAP_REORG_BATCHINPUT is now scheduled with User REORG in Client002, the batch input objects are reorganized in Client 002.

o If the job SAP_REORG_ABAPDUMPS is scheduled in any client, all ABAPshort dumps are reorganized in all clients.

o User SPOOLADM has the authorization S_ADMI_FCD-S_ADMI_FCD = 'SPAD'.If the job SAP_REORG_SPOOL is now scheduled with user SPOOLADM andclient 123 is specified for the program parameters, then the spoolobjects in client 123 are reorganized irrespective of the client inwhich the actual job is running. If you enter '*' as the client,all clients are reorganized.

NOTES: The job steps should be planned using a language that is availablein the system. English should be available in every system. However, someof these jobs have steps set by default in German. The following is validuntil further notice: the jobs must be modified if necessary when, forexample, a Russian code page is used.

Header Data

Release Status: Released for CustomerReleased on: 29.10.2010 14:15:51Master Language: GermanPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: BC-CCM-BTC Background Processing

Secondary Components:BC-CCM-MON Monitoring

21.05.2011 of 7


BC-CCM-PRN Print and Output Management

BC-ABA-LA Syntax, Compiler, Runtime

BC-ABA-LI List Processing

BC-ABA-SC UI services, screen, batch input

The Note is release-independent

Related Notes

Number Short Text

1411877 New standard jobs

1407635 Unnecessary database accesses in RSBTCPRIDEL

1260586 Runtime error in SQL Server Performance History

1255188 Missing standard variants for reorg reports

1083786 RZ20: Job monitoring data collector terminates

800927 Standard jobs in the SCM/APO area

788797 Batch input: Session multiple selection for reorganization

728947 Job count cannot be created

706478 Preventing Basis tables from increasing considerably

568690 Incorrect system variant for RSBTCDEL

553621 DB6: No history data in the application monitor (ST07)

534468 Not all parts of a job log are deleted

509454 Batch input log overview: Delayed display

500950 iSeries: R/3 EBCDIC --> ASCII Codepage Conversion Doc.

498668 Deadlocks on the TSP01 table (deleting spool requests)

307970 Wrong print specifications, wrong printer in background

168439 Preparándose para una sesión de Early Watch ó GL

147354 Batch input: Reorg. and delete sessions and logs

144864 SAP Remote Services: Technical preparation - ST03

130978 RSPO1041 - Replacement for RSPO0041

129252 Oracle DB Statistics for BW Tables

98065 Spool consistency check with RSPO1043 as of 4.0A

48400 Reorganization of TemSe and Spool

41547 How does report RSPO0041 work?

19706 Tuning the Spooler

18319 Difficulties with the batch input log file

18307 Batch input logs and reorganization

16513 File system is full - what do I do?

12103 Contents of the TCOLL table

11070 Space requirements of TemSe and spooler

21.05.2011 of 7


Number Short Text

7224 Deleting old corrections and transport requests

6604 Deleting job logs at operating system level

Attributes

Attribute Value

Transaction codes HIER

Transaction codes SM36

Transaction codes SPAD

Transaction codes SPAR

sapnote_0000016083

Documents