SAP

A Weekly SAP System Health Checklist

The ten checks I run every week on an SAP landscape to catch problems early — from background jobs to lock entries and dumps.

Abstract illustration of a system health dashboard

A healthy SAP system is rarely an accident. It is usually the result of someone checking the same things, the same way, every week.

The checklist

Area Transaction What to look for
Short dumps ST22 Repeated dumps from the same program
Background jobs SM37 Cancelled or long-running jobs
Lock entries SM12 Locks older than a day
Update errors SM13 Any failed updates
System log SM21 Errors and security warnings
Work processes SM50 / SM66 Processes stuck in one state
Spool SP01 Very large or failed spool requests
Database DB02 Tablespace growth and missing indexes
Users SU01 / SUIM Expired or unused privileged accounts
Transports STMS Failed imports in the queue

Turning it into a habit

Put the checklist in a shared document, record what you find each week, and review the trends monthly. Recurring issues become obvious, and the next engineer inherits context instead of surprises.

Keep Reading

Related articles

Let’s Talk

Let’s build something reliable together

Open to consulting, speaking and collaboration across SAP administration, cloud infrastructure and cybersecurity — questions are always welcome.