Sapnote_0000016083 Sap Standard Jobs

5/26/2018 Sapnote_0000016083 Sap Standard Jobs

1/6

14.02.2013 Page 1 of 6

SAP Note 16083 - Standard jobs, reorganization jobs

Note Language: English Version: 75 Validity: Valid Since 12.01.2012

Summary

Symptom

There are a number of jobs that must periodically run in a live R/3

installation, 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

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.

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 terms

REORGJOBS.

Reason and Prerequisites

Note: Application-specific reorganization programs are not included in this

list.

Solution

Job name Program

Variant Repeat interval

SAP_REORG_JOBS RSBTCDEL2 yes d

daily

SAP_REORG_SPOOL RSPO0041/1041 y

yes daily

SAP_REORG_BATCHINPUT RSBDCREO yes d

daily

SAP_REORG_ABAPDUMPS RSSNAPDL yes d

daily

SAP_REORG_JOBSTATISTIC RSBPSTDE yes m

monthly

SAP_COLLECTOR_FOR_JOBSTATISTIC RSBPCOLL no d

daily

SAP_COLLECTOR_FOR_PERFMONITOR RSCOLL00 no h

hourly

SAP_COLLECTOR_FOR_NONE_R3_STAT RSN3_STAT_ n

no hourlyCOLLECTOR

SAP_REORG_PRIPARAMS RSBTCPRIDEL n


2/6

14.02.2013 Page 2 of 6


no monthly

SAP_REORG_XMILOG RSXMILOGREORG y

yes weekly

SAP_CCMS_MONI_BATCH_DP RSAL_BATCH_

no hourly

TOOL_DISPATCHING

SAP_SPOOL_CONSISTENCY_CHECK RSPO1043 yes d

daily

SAP_REORG_ORPHANED_JOBLOGS RSTS0024 yes w

weekly

SAP_CHECK_ACTIVE_JOBS BTCAUX07 yes h

hourly

SAP_DELETE_ORPHANED_IVARIS BTC_DELETE_ORPHANE

D_IVARIS ja weekly

SAP_REORG_ORPHANED_TEMSE_FILES RSTS0043 ja w

weekly

In any case, refer to Note 48400 regarding the spool and TemSe

consistency check.

Note:

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

o SAP_REORG_XMILOG reorganizes the table TXMILOGRAW. This table

contains log information on the XMI interface (-> Note 182963).

o As of Release 4.6A, the job steps are managed separately from the

print parameters. This means that report RSBTCDEL no longer deletesany print parameters. Therefore you must 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.

o The job SAP_COLLECTOR_FOR_PERFMONITOR was previously also called

COLLECTOR_FOR_PERFORMANCE_MONITOR.

o The job SAP_COLLECTOR_FOR_NONE_R3_STAT is available as of SAP Web

Application Server 6.20 only.

o On sapserv3, an improved version of RSPO0041 is available with

RSPO1041 (Note 130978).

o In addition, you should regularly run a consistency check of the

spooler and the TemSe (Note 48400).

o Batch input reorganization may not run at the same time as normal

batch input activity up to and including SAP Release 30C (see Note18307). The associated job must be scheduled for a time when no

other batch input activity is scheduled.


3/6

14.02.2013 Page 3 of 6


o ***** 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' -> 'Delete standard jobs'. In addition, released jobs that

may exist and contain report RSM13002 should be deleted. You can

find and delete these jobs using sm37.

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

o To eliminate ABAP dumps that are created due to runtime errors

within an ABAP program, use the program RSSNAPDL. To simplify the

related 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

o 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

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.

Job name:

SAP_REORG_BATCHINPUT

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:


4/6

14.02.2013 Page 4 of 6


o Job SAP_REORG_JOBS:

- See SAP Note 784969.

o 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

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

Note:

o The authorizations always relate to the user under whose ID the job

is being processed.

o If this user has the necessary authorizations to work in a

cross-client manner, then it does not matter in which client the

actual job is running.

Examples

o User ADMIN has the Authorization S_BTCH_ADM = 'Y'. If Job

SAP_REORG_JOBS is now scheduled with User ADMIN, the jobs are

reorganized in all clients.

o User REORG has the Authorization profile S_BDC_ALL. If Job

SAP_REORG_BATCHINPUT is now scheduled with User REORG in Client

002, the batch input objects are reorganized in Client 002.

o If the job SAP_REORG_ABAPDUMPS is scheduled in any client, all ABAP

short 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 and

client 123 is specified for the program parameters, then the spool

objects in client 123 are reorganized irrespective of the client in

which 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, some

of these jobs have steps set by default in German. The following is valid

until further notice: the jobs must be modified if necessary when, for

example, a Russian code page is used.


5/6

14.02.2013 Page 5 of 6


Header Data

Release Status: Released for Customer

Released on: 12.01.2012 13:23:51

Master Language: German

Priority: Recommendations/additional info

Category: Consulting

Primary Component: BC-CCM-BTC Background Processing

Secondary Components:

BC-CCM-MON Monitoring

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

1630506 DB6: History management of monitoring data

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

1021775 Orphaned temporary variants in the table VARI

800927 Standard jobs in the SCM/APO area

788797 Batch input: Session multiple selection for reorganization

728947 Job count cannot be created706478 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 Preparndose para una sesin de Early Watch GL

147354 Batch input: Reorg. and delete sessions and logs


6/6

14.02.2013 Page 6 of 6


Number Short Text

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

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

Documents

Sapnote_0000016083 Sap Standard Jobs