# SAP ECC SM36 Standard Housekeeping Jobs Checklist

> Source: https://netray.co/tools/sap-ecc-sm36-standard-housekeeping-jobs-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Check that every standard SAP ECC housekeeping job is scheduled with the right program and frequency, plus the common interface and application jobs.

## Category

sap

## Erp

SAP ECC 6.0

## Audience

- SAP Basis administrator
- SAP batch scheduler
- SAP support analyst

## Tool

**Kind:** checklist

**Groups:**

#### Basis standard jobs (SM36 > Standard jobs)

**Items:**

**Text:** SAP_REORG_JOBS - RSBTCDEL2 - daily: deletes old job logs and job data

**Critical:** true

**Text:** SAP_REORG_SPOOL - RSPO0041 (or RSPO1041) - daily: deletes old spool requests

**Critical:** true

SAP_REORG_BATCHINPUT - RSBDCREO - daily: reorganises processed batch input sessions and logs

SAP_REORG_ABAPDUMPS - RSSNAPDL - daily: deletes old short dumps

SAP_REORG_JOBSTATISTIC - RSBPSTDE - monthly: deletes old job runtime statistics

SAP_COLLECTOR_FOR_JOBSTATISTIC - RSBPCOLL - daily: collects job runtime statistics

**Text:** SAP_COLLECTOR_FOR_PERFMONITOR - RSCOLL00 - hourly: collects performance data for ST03N and DB monitors

**Critical:** true

SAP_REORG_UPDATERECORDS - RSM13002 - daily: deletes processed update records

SAP_SPOOL_CONSISTENCY_CHECK - RSPO1043 - daily: checks spool and TemSe consistency

SAP_REORG_ORPHANED_JOBLOGS - RSTS0024 - weekly: deletes job logs without a job

SAP_REORG_PRIPARAMS - RSBTCPRIDEL - monthly: reorganises print parameters of jobs

SAP_REORG_XMILOG - RSXMILOGREORG - weekly: reorganises the XMI interface log

**Text:** SAP_CHECK_ACTIVE_JOBS - BTCAUX07 - hourly: corrects status of jobs shown active without a work process

**Critical:** true

SAP_DELETE_ORPHANED_IVARIS - BTC_DELETE_ORPHANED_IVARIS - weekly: deletes orphaned temporary variants

SAP_REORG_ORPHANED_TEMSE_FILES - RSTS0043 - weekly: removes orphaned TemSe files

SAP_SOAP_RUNTIME_MANAGEMENT - RSWSMANAGEMENT - hourly: web service runtime housekeeping

#### Interfaces (IDoc, ALE, tRFC)

**Items:**

RSEOUT00 - per interface schedule: sends outbound IDocs collected in status 30

**Text:** RBDAPP01 - per interface schedule: posts inbound IDocs in status 64 when processing is not immediate

**Critical:** true

RBDMANI2 - as agreed: reprocesses inbound IDocs in error status 51 after the cause is fixed

RBDMIDOC - per message type: creates IDocs from change pointers (same as BD21)

RBDCPCLR - weekly: deletes processed and obsolete change pointers (BD22)

RSARFCEX - as needed: retries failed tRFC calls shown in SM58

#### Application jobs

**Items:**

RMMRP000 - nightly: MRP planning run in background (MDBT)

**Text:** RMMMPERI - monthly: MM period close (MMPV) at month start, before goods movements need the new period

**Critical:** true

Credit, output and billing due list jobs as your SD design requires (document them in the same register)

#### Governance

**Items:**

Every job has a named business or Basis owner and a documented purpose

**Text:** Step users are system-type (B) users, not personal dialog users

**Critical:** true

Start conditions use events for dependencies instead of guessed times

Retention periods in the deletion variants match your audit and support needs

Canceled jobs raise an alert through CCMS (RZ20) or your enterprise scheduler

No duplicate standard jobs under other names running the same programs

**Scoring Note:** Critical items are the ones whose absence fills the database, hides performance data or leaves IDocs and jobs stuck.

## Content

**Intro:** This checklist lists the standard housekeeping background jobs that every SAP ECC 6.0 system should run, with job name, ABAP program and a sensible frequency, plus the interface and application jobs most plants add. Use it after a system copy, an upgrade or a support audit to confirm nothing is missing or duplicated.

**Sections:**

#### Where to schedule them

**Body:** In SM36, the Standard jobs button (in older releases under Goto > Standard jobs) lists the SAP default jobs and lets you schedule all of them with default variants in one step. SAP Note 16083 'Standard jobs, reorganization jobs' is the reference for job names, programs and recommended variants, and it is updated as programs change. Monitor the jobs in SM37 by selecting job name SAP* and status Canceled. After a system copy, schedule them again in the target system, because copied jobs may still point to the source system's servers or be released twice.

**Bullets:**

- SM36: define jobs and open the standard jobs list
- SM37: monitor, filter by SAP* and status
- SM62: define events for event-based chains

#### How to use the checklist

**Body:** Go through SM37 with job name SAP* and the last 7 days. For each item, tick it when the job exists, runs at the listed frequency and finishes. If the job exists under a different name, check that it runs the same program and remove duplicates. For the interface group, compare with your IDoc partner profiles: if an inbound partner profile is set to 'Trigger by background program', RBDAPP01 must be scheduled for it, and likewise RSEOUT00 for outbound profiles set to 'Collect IDocs'. Export the result to Excel as a job register.

#### Reading the results

**Body:** A missing SAP_COLLECTOR_FOR_PERFMONITOR shows up as empty ST03N data and gaps in DB monitoring. A missing SAP_REORG_JOBS or SAP_REORG_SPOOL shows up later as growing TBTCO, TBTCP and TemSe objects and slow SM37. Many jobs shown Active with no work process means SAP_CHECK_ACTIVE_JOBS is not running. Thousands of IDocs in status 64 or 30 point to missing RBDAPP01 or RSEOUT00 jobs. A missed MMPV period close stops goods movements on the first day of the month, which is why it is marked critical.

#### Common mistakes

**Body:** Running both RSPO0041 and RSPO1041 with conflicting retention. Scheduling RBDMANI2 every few minutes, which reprocesses errors that will fail again and floods the log. Leaving default deletion variants when audit rules require longer retention. Running standard jobs under a person's dialog user. Forgetting to reschedule standard jobs after a system copy or refresh.

**Cta:** If you want your team to ask ECC which jobs failed overnight and why, in plain English on your own servers, we can set that up.

**Faq:**

#### What is the transaction code for batch jobs in SAP?

**Answer:** SM36 creates and schedules background jobs, SM37 monitors them, SM62 manages events and SM50 or SM66 show running work processes. ST22 and SM21 are where you look when a job fails. RZ04 and SM63 control how many background work processes are available.

#### Which standard jobs should every SAP system run?

**Answer:** The SAP default list in SM36 Standard jobs, documented in SAP Note 16083: job, spool, batch input, dump and update record reorganisation, job and performance statistics collectors, spool consistency checks, orphaned job log and TemSe cleanup, and the active job check BTCAUX07. Check the note for your release.

#### How do I monitor SAP batch jobs?

**Answer:** In SM37 select by job name, user, status and date. Filter on Canceled daily, and on Active for jobs running much longer than usual. CCMS (RZ20) or an enterprise scheduler can alert on cancellations. Job runtime statistics from RSBPCOLL help you spot jobs that are slowly getting longer.

#### Do I need an external batch job scheduling tool?

**Answer:** Not for a single ECC system with simple dependencies: SM36 events and job chains are enough. External schedulers help when jobs span several SAP and non-SAP systems, when you need calendars and cross-system dependencies, or when an operations team monitors many systems from one console.

## Search terms

sap batch job monitoring, sap batch jobs, sap batch job list, sap batch job tcode, sap standard jobs sm36, sap housekeeping jobs, sap_reorg_jobs rsbtcdel2, sap batch job scheduling tools

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json