SAP ECC SM36 Standard Housekeeping Jobs Checklist
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.
0 of 31 items complete
7 critical items still open - these are the highest-risk gaps.
Basis standard jobs (SM36 > Standard jobs)
Interfaces (IDoc, ALE, tRFC)
Application jobs
Governance
Critical items are the ones whose absence fills the database, hides performance data or leaves IDocs and jobs stuck.
Get your job schedule reviewed
Export your SM37 job list and we will flag missing, duplicate and risky jobs.
Optional. The tool and every export work without this. No spam.
Where to schedule them
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.
- 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
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
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
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.
Frequently Asked Questions
What is the transaction code for batch jobs in SAP?
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?
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?
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?
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.
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.
Related Tools
SAP ECC Background Job Failure Troubleshooting Checklist (SM37, ST22, SM21)
Work through a failed, stuck or never-started SAP ECC background job in order: logs, scheduling errors, runtime failures, debugging and safe cancellation.
Developer ToolsSAP ECC IDoc Extension and Custom Segment Checklist (WE31, WE30, WE82)
Design, build, fill, configure and test a custom IDoc segment in SAP ECC: WE31, WE30, WE82, user exits, WE20 partner profiles and WE19.
SAPSAP IDoc Status Codes Reference
Look up any IDoc status code, see whether it is inbound or outbound, whether it is an error, and which transaction to use to fix it.
SAPSAP ECC Support Package Stack (SPS) Update Checklist
A checklist for applying a support package stack to SAP ECC 6.0: decide, prepare, apply with SUM or SPAM, adjust modifications and validate.
More SAP tools
See all- SAP ECC Private AI Layer Blueprint Generator
- SAP ECC AI Assistant Sizing and Value Calculator
- SAP ECC SD User Exit Forms Reference (MV45AFZZ, RV60AFZZ, MV50AFZ1)
- SAP ECC Customer Exits (SMOD Enhancements) by Module Reference
- SAP ECC Classic BAdI Definitions Reference (MIGO, ME21N, MIRO, Deliveries, PM Orders)
- SAP ECC Background Job Tables Reference (TBTCO, TBTCP, Job Status Codes)
- SAP ECC Output Determination Tables and Codes Reference (NAST, TNAPR, NACE)
- SAP ECC Movement Type Configuration Tables Reference (T156, T156T, T157D)
- SAP ECC Stock Type and Location Transfer Movement Type Matrix
Keep exploring
Free tools
- SAP ECC Job Log, Spool and TBTCO Growth Housekeeping CalculatorEnter jobs per day, steps, spool share, average sizes and retention days to see how many job and spool rows you keep and how much TemSe storage they use in the database or file system.
- SAP Background Job Scheduling TemplateA fill-in job request form that captures everything a Basis admin needs to schedule a background job in SM36 and monitor it in SM37.
- Shop Floor Housekeeping and Cleaning ChecklistA tickable housekeeping and cleaning checklist grouped by daily, weekly and monthly frequency, with critical safety items flagged and a score you can export.
ERP fixes and how-tos
- ERP Data Archiving Strategy: What to Archive and What to PurgeHow to decide what ERP data to archive or purge: find the big tables, set retention by record type, keep reports and audits working, and test restores first.
- How to add AI to SAP ECC 6.0 on-prem without moving data to a cloudReference architecture for a private on-prem AI assistant on SAP ECC 6.0: RFC and BAPI reads, SLT replica, retrieval index, local LLM, permission mirroring.
Integrations
- How to connect Power BI to SAP ECC 6.0Connect Power BI to SAP ECC 6.0: SAP ERP connector, BW and warehouse options, on-prem data gateway, key manufacturing dashboards, and adding natural-language Q&A.
- How to use ChatGPT with SAP ECC 6.0Using ChatGPT with SAP ECC 6.0: custom GPT actions, exports versus live access, an OData or MCP bridge, enterprise data controls, and when a private model is safer.