|1. Housekeeping jobs for ABAP Systems|
|Job Name||Report||Repeat||Client Specific||PRD - Scheduled?|
This is something that I've compiled over the years to better track scheduled housekeeping tasks. These I've compiled from Notes 16083, 1411877, and 1440439.
Most of these jobs can be scheduled from within SM36 (standard jobs). I like to manually check these against the list above to make sure the jobs are running with the correct reports and in the correct clients. If a job isn't scheduled, I'll create a new job and assign the task to a dedicated SAP Basis background account (something like 'BATCH_BC' should work). Please don't assign your account to these jobs! Almost every site I've worked at has had jobs fail because the Basis admin used their own account and these all failed when their account was deleted or locked.
Even more amazing is the number of sites that don't run all of these. I run some of these jobs at older sites and found one that deleted over 6 years of stale temporary variants! Needless to say, it took less time to create new variants after this cleanup.
You should also remove the jobs below. These are defunct and only generate errors in the system.
|2. Defunct Jobs|
|SLCA_LCK_SYNCHOWNERS||SLCA_LCK_SYNCHOWNERS||Only schedule on livecache systems|
|SAP_WP_CACHE_RELOAD_FULL||Only schedule on workplace servers|
As a standard process, I'll add a check to standard system checks to ensure that these jobs are still scheduled (I'll check every month or so).
It is important to run these jobs so tables that hold transient data don't grow out of proportion to the rest of the data. Over time, you'll find the system starts to slow down as it reaches performance thresholds. As a Basis admin, you can return value to your client by ensuring that standard tasks are running and cleaning out those transient tables. Making sure these stay small, will make upgrades and migrations a bit easier.
Joseph P. Haynes
SAP Basis Consultant
Post a Comment