Monitoring exists to catch problems before they affect the business โ ideally at the point of early warning rather than failure.
The daily checklist
| Code | What it shows | A problem means |
|---|---|---|
| SM51 | Instances | A server is down |
| SM50 / SM66 | Work processes | Long runners or process exhaustion |
| SM21 | System log | System-level errors |
| ST22 | Short dumps | Programs terminating |
| SM37 | Job results | Batch failures |
| SM13 | Update errors | Documents users believe were saved |
| SM12 | Lock entries | Stale locks blocking work |
| SP01 | Spool requests | Print failures or spool overflow |
| DB02 | Database space | Tablespace running out |
| SM58 | Failed tRFC | Interface failures |
Work processes
| State | Meaning | Concern |
|---|---|---|
| Waiting | Idle; normal | โ |
| Running | Processing | Investigate if it persists |
| Stopped | Waiting on something | Check the reason |
| PRIV | Holding private memory | Unavailable to other users |
Locks
Logs and dumps
| Step | Check |
|---|---|
| 1 | Is the same dump repeating? |
| 2 | Is it concentrated on one user or program? |
| 3 | Did anything change at that time โ a transport, a patch? |
| 4 | For timeouts or memory errors, check system resources |
| 5 | Search SAP Notes for a known issue |
Automating monitoring
| Tool | Content |
|---|---|
| CCMS (RZ20) | Alert monitor with thresholds |
| SAP Solution Manager | Monitoring across systems |
| SAP Focused Run | Large landscape monitoring |
| External tools | Integration with Zabbix, Nagios and similar |