SAP Standard Jobs, Reorganization Jobs
DAS
-----------------------------------------------------------------------
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
RSPO1043 | RSPO1043 | yes | daily
RSTS0024 | RSTS0024 | yes | daily
In any case, refer to Note 48400 regarding the spool and TemSe
consistency check.
For Business Information Warehouse (BW) only (also see the relevant
notes below):
Job name | Program | Variant | Repeat int.
-----------------------------------------------------------------------
SAP_ANALYZE_ALL_INFOCUBES | SAP_ANALYZE_ALL_INFOCUBES
| yes | weekly
Comments:
SAP_CCMS_MONI_BATCH_DP is not a reorganization job but is needed to
start tools / methods in the area System Monitoring in the background
-> Transaction RZ20/RZ21.
SAP_REORG_XMILOG reorganizes the Table TXMILOGRAW. This table contains
log information on the XMI interface (-> Note 182963).
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. Thereforeyoumust additionally schedule Report
RSBTCPRIDEL
Itreorganizes print parameters on a cross-client basis.
Since the number of print parameters increases more slowly than the
number of batch steps, it suffices to execute this report after longer
periods of time (> 1 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.
Job SAP_COLLECTOR_FOR_NONE_R3_STAT is available as of SAP Web
ApplicationServer 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).
Batch input reorganization may not run at the same time as normal batch
input activity. The associated job must be scheduled for a time when no
other batch input activity is scheduled.
***** Caution: Standard job SAP_REORG_UPDATERECORDS which 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 (i.e. in the batch). Thus
Job SAP_REORG_UPDATERECORDS always terminates in this case. In any
case, Job SAP_REORG_UPDATERECORDS should be deleted from the pool of
standard jobs, if it is still there: SM36 -> button 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.
***** Caution: Job SAP_WP_CACHE_RELOAD_FULL is normally used to update
datafrom 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
standardjob.
Ifthis job has been scheduled for your system, but you do not need it,
delete the scheduled job in Transaction SM37.
To eliminate ABAP/4 dumps that are created due to runtime errors within
ABAP/4 programs, use RSSNAPDL. To simplify job scheduling, there is an
additional program: RSNAPJOB. This program schedules RSSNAPDL within a
job. Implicit assumptions:
Job name: RSSNAPDL
Variant: DEFAULT (therefore it must exist)
Start time: following day, 1:00 am
Repeat interval: daily
Only with the Support Packages specified in Note 666290, Report
RSTS0024 deletes job logs that no longer belong to any job. Please
contact SAP, if you need a report in a release that is not mentioned in
Note 666290.
Clients and authorizations
Some of the jobs specified work with client-specific objects (e.g.
jobs). Whether a reorganization then has any client-independent
influence normally depends on particular authorizations. The following
table gives 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
Jobs that are not client-dependent perform a reorganization in all
affected clients. They require neither special authorizations nor a
special user name.
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:
If the user that calls RSBTCDEL2 is batch administrator (i.e.
S_BTCH_ADM mit BTCADMIN= Y), reorganization is carried out in all
clients.
If the userisnot batch administrator, reorganization is carried out in
the currentclient only.
Two cases have to be distinguished here:
If the user has Authorization S_BTCH_JOB with JOBGROUP = * and
JOBACTION = DELE, all jobs which meetthe selection criteria are deleted
in the current client.
If the user does not have this authorization either, his/her own jobs
are deleted only, i.e. all jobs in the current client that meet the
selection criteria and belong to that user.
Job SAP_REORG_SPOOL:
AuthorizationS_ADMI_FCD-S_ADMI_FCD = 'SPAD'
Reorganization runs in chosen client (Client = '*': runs in all
clients)
AuthorizationS_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_ALL
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.
Comments:
The authorizations always relate to the user under whose ID the job is
being processed.
If this user has the necessary authorizations to work client
independently, then it does not matter in which client the actual job
is running.
Examples
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.
User REORG has the Authorization profile S_BDC_ALL. If Job
SAP_REORG_BATCHINPUTis now scheduled with User REORG in Client 002, the
batch input objects are reorganized in Client 002.
If Job SAP_REORG_ABAPDUMPS is scheduled in any client, all ABAP short
dumps are reorganized in all clients.
User SPOOLADM has the Authorization S_ADMI_FCD-S_ADMI_FCD = 'SPAD'. If
Job SAP_REORG_SPOOL is now scheduled with User SPOOLADM and Client 123
program parameters are specified, 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.
Note: The job steps should be planned using a language that is
available in the sysyem. 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.
Kali Prasad pani
I need to change the background job retention period (History), lets say 10days to 30 days .
All the job history should show me from past 30 day.
Can you help to provide the simple steps .
Which reorg job need the changes. What is the risk. Which table will be growing.
Thanks
Kali Prasad
On Monday, 2 October 2006 19:31:56 UTC+5:30, RABINDRA DAS wrote:re
Kali Prasad Pani
--
---
You received this message because you are subscribed to the Google Groups "MYSAPBASIS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mysapbasis+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.