SM37
Quick answer
SM37 monitors background jobs, showing their status (scheduled, released, active, finished, cancelled), logs and spool, the go-to for batch-job operations.
Key takeaways
- Selection: job name, user, date range, status.
- Job list with status and timings.
- Job log and spool (output) per job.
- Watch out: Using the wrong variant (create vs change vs display).
Purpose
It monitors background jobs, showing their status (scheduled, released, active, finished, cancelled), logs and spool, the go-to for batch-job operations.
Key fields and screen
- Selection: job name, user, date range, status.
- Job list with status and timings.
- Job log and spool (output) per job.
- Actions: release, cancel, repeat.
Tips
- Investigate cancelled jobs via the job log (and ST22 for dumps).
- Filter by status to find failures quickly.
- Use SM36 to define/schedule jobs.
Common errors
- Cancelled jobs (check the log for the cause).
- Jobs delayed by too few background work processes.
- Missing authorization to view other users’ jobs.
Common pitfalls
- Using the wrong variant (create vs change vs display).
- Missing prerequisite master data or authorization.
- Not checking the resulting document/log.
Want to learn this properly?
Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.
Check your understanding
Which statement is true of SM37?
- A. SAP Event Mesh (part of Integration Suite/BTP) enables event-driven integration, systems publish and…
- B. Actions: release, cancel, repeat.
- C. Master data is the long-lived, relatively static reference data that business transactions depend on…
Show answer
B. Actions: release, cancel, repeat.
Covered in the “Key fields and screen” section of this lesson.
Which part of the Learn SAP curriculum covers SM37?
- A. SAP interview questions
- B. SAP downloads
- C. SAP TCodes
Show answer
C. SAP TCodes
This lesson sits in the SAP TCodes section of the Learn SAP course.
Frequently asked questions
What does SM37 stand for in SAP?
SM37 is the SAP transaction code for Job Monitoring (Simple Job Selection) (Basis). It monitors background jobs, showing their status (scheduled, released, active, finished, cancelled), logs and spool, the go-to for batch-job operations.
What is worth checking when troubleshooting SM37?
Investigate cancelled jobs via the job log (and ST22 for dumps). Filter by status to find failures quickly. Use SM36 to define/schedule jobs.
What is worth remembering about SM37 in practice?
Selection: job name, user, date range, status. Job list with status and timings. Job log and spool (output) per job.
What tends to go wrong with SM37?
Using the wrong variant (create vs change vs display). Missing prerequisite master data or authorization. Not checking the resulting document/log.