--- description: Monitor a SAP System using tcodes SM51,SM50,SM66,AL08,SM04,SM13, SM12,SM21,ST02,ST06,ST22,SP01,SM37,SM58,SMQ1,SMQ2,DB02,DB12 title: SAP Basis Monitoring Tcodes & Health Checks image: https://www.guru99.com/images/system-monitoring-performance-checks-1.png --- [Skip to content](#main) **⚑ Smart Summary** SAP System Monitoring is a daily Basis routine that keeps servers, work processes, locks, updates, and database health under control. Core T-codes such as SM51, SM50, SM66, SM21, ST22, ST02, ST06, DB02, and DB12 give administrators a complete proactive checklist. - πŸ–₯️ **Verify servers and work processes:** SM51 lists application servers, while SM50 and SM66 expose instance-level and system-wide work-process status. - πŸ”’ **Clear stale locks and updates:** SM12 flags old lock entries; SM13 catches deactivated updates and stuck queues. - πŸ“œ **Audit the system log and dumps:** SM21 surfaces errors and warnings; ST22 collects ABAP short dumps for the day. - βš™οΈ **Tune buffers and CPU:** ST02 reveals buffer swaps; ST06 confirms CPU idle stays around 60–65% during steady load. - πŸ€– **Use AI for anomaly detection:** AI assistants summarise SM21 and ST22 patterns, flag DB02 growth trends, and recommend the next investigative T-code. Read More ![SAP Monitoring \& Performance Checks](https://www.guru99.com/images/system-monitoring-performance-checks-1.png) ## What is SAP System Monitoring? **SAP System Monitoring** is the daily Basis routine that keeps an SAP landscape healthy by checking servers, work processes, locks, updates, system logs, and database health at regular intervals. The goal is proactive β€” to spot problems before users notice them. A typical daily checklist includes: - Checking application servers. - Monitoring system-wide work processes. - Monitoring work processes for individual instances. - Monitoring lock entries. - CPU utilisation. - Available space in the database. - Monitoring update processes. - Monitoring the system log. - Buffer statistics. - Monitoring batch jobs. - Spool request monitoring and print-request counts. - ABAP dump analysis. - Database performance and consistency checks. - Monitoring application users. | | #1 BEST OVERALL [![GoFrugal]()](https://guru99.live/mmus9e) 9.8/10 β˜…β˜…β˜…β˜…β˜… [Start Free Trial](https://guru99.live/mmus9e) | [![Xero]()](https://guru99.live/7sgags) 9.5/10 β˜…β˜…β˜…β˜…β˜… [Visit Xero](https://guru99.live/7sgags) | [![Paychex]()](https://guru99.live/291q7y) 9.3/10 β˜…β˜…β˜…β˜…β˜… [Visit Paychex](https://guru99.live/291q7y) | | --- | --- | --- | --- | | Best For | Retail & Distribution ERP | Online Accounting | Payroll & HR | | Key Feature | *βœ“*POS, inventory & accounting in one | *βœ“*Invoicing & bank reconciliation | *βœ“*Payroll processing & tax filing | | Also Includes | *βœ“*Cloud & mobile apps | *βœ“*1,000+ app integrations | *βœ“*Benefits administration | | Free Trial | 30-Day Free Trial | 30-Day Free Trial | Get a Free Quote | | | [Start Free Trial](https://guru99.live/mmus9e) | [Visit Xero](https://guru99.live/7sgags) | [Visit Paychex](https://guru99.live/291q7y) | #1 BEST OVERALL 1 [![GoFrugal]()](https://guru99.live/mmus9e) 9.8/10 β˜…β˜…β˜…β˜…β˜… Best For Retail & Distribution ERP Key Feature *βœ“*POS, inventory & accounting in one Also Includes *βœ“*Cloud & mobile apps Free Trial 30-Day Free Trial [Start Free Trial](https://guru99.live/mmus9e) 2 [![Xero]()](https://guru99.live/7sgags) 9.5/10 β˜…β˜…β˜…β˜…β˜… Best For Online Accounting Key Feature *βœ“*Invoicing & bank reconciliation Also Includes *βœ“*1,000+ app integrations Free Trial 30-Day Free Trial [Visit Xero](https://guru99.live/7sgags) 3 [![Paychex]()](https://guru99.live/291q7y) 9.3/10 β˜…β˜…β˜…β˜…β˜… Best For Payroll & HR Key Feature *βœ“*Payroll processing & tax filing Also Includes *βœ“*Benefits administration Free Trial Get a Free Quote [Visit Paychex](https://guru99.live/291q7y) ## Why Daily Basis Checks and System Monitoring? Daily checks catch small issues β€” a stuck work process, an old lock, a tablespace nearing 95% β€” before they cascade into outages. They give the Basis team a reliable baseline so anomalies stand out, and they feed historical data into capacity-planning decisions. [![Daily Basis checks / System Monitoring]()](https://www.guru99.com/images/sap/2013/05/050913_0552_1.png) ## How Do We Monitor a SAP System? Monitoring is organised around T-codes, each owning a specific layer β€” servers, work processes, locks, updates, logs, buffers, CPU, dumps, spool, batch jobs, RFC, and the database. The sections below walk through every check in order. ## Checking Application Servers (SM51) SM51 lists every active application server in the landscape, along with the services and work processes configured on each instance. [![Checking Application Servers SM51]()](https://www.guru99.com/images/sap/2013/05/050913_0552_2.png) ## Monitoring Work Processes for Individual Instances (SM50) SM50 displays every running, waiting, stopped, and PRIV process on the current instance. Every process should be in *Running* or *Waiting* status; anything else needs investigation. [![Monitoring Work Processes for Individual Instances SM50]()](https://www.guru99.com/images/sap/2013/05/050913_0552_3.png) The screen surfaces several useful columns: 1. The status of each work process (occupied or free). 2. The action being taken by an occupied process, shown in the Action column. 3. The database table being worked on. Typical problems and remedies: - **Users can’t log on or the GUI is slow:** dialog (DIA) work processes are exhausted. Look for long-running jobs (red indicator under *Time*). Cancel them via *Process > Cancel without core* to free the slot. - **PRIV under the Reason column:** a transaction is consuming so much memory that the DIA work process is β€œowned” by one user. Speak to the user and, if possible, rerun the job in the background. - **Long-running SPO work process:** investigate the print server or printer; a stuck spool can monopolise a process. ## Monitoring System-wide Work Processes (SM66) SM66 is the Global Work Process Overview. It rolls SM50 data across every active instance into one screen, which makes it the quickest way to spot a system-wide performance issue. [![Monitoring System-wide Work Processes SM66]()](https://www.guru99.com/images/sap/2013/05/050913_0552_4.png) At a glance you see: - The status of every application server. - Why a process is not running. - Whether the process has been restarted. - CPU usage and request runtime. - The logged-on user and client. - The report currently executing. ## Monitor Application Users (AL08 and SM04) AL08 lists users across every active instance, while SM04 shows users on the current instance. Both surface terminal IDs and clients, which help confirm that only expected user IDs are logged on. [![Monitor Application User AL08 and SM04]()](https://www.guru99.com/images/sap/2013/05/050913_0552_5.png) ## Monitoring Update Processes (SM13) Run SM13, place `*` in the *User* field, and execute. If there are no pending updates the queue is empty. [![Monitoring Update Processes SM13]()](https://www.guru99.com/images/sap/2013/05/050913_0552_7.png) [![Empty SM13 queue]()](https://www.guru99.com/images/sap/2013/05/050913_0552_8.png) If updates are not active, answer the following questions: - Is the update process active? If not, was it deactivated by the system or by a user? - Has any update been cancelled? - Is there a long queue of pending updates older than 10 minutes? **Don't Miss:** - [How to Download & Install SAP GUI](https://www.guru99.com/guide-to-install-sap-gui-aka-frontend.html) - [login/fails\_to\_session\_end – SAP RZ11](https://www.guru99.com/how-to-limit-logon-attempts.html "login/fails_to_session_end – SAP RZ11") - [SAP RSBTCDEL2: How to Delete a Background Job](https://www.guru99.com/how-to-delete-a-background-job.html) - [STMS Configuration in SAP](https://www.guru99.com/how-to-configure-tms.html) ## Monitoring Lock Entries (SM12) Run SM12 and enter `*` in the *User Name* field. [![Monitoring Lock Entries SM12]()](https://www.guru99.com/images/sap/2013/05/050913_0552_11.png) [SAP](https://www.guru99.com/what-is-sap.html) uses a locking mechanism to prevent two users from changing the same record at the same time. Sometimes a network drop or session crash leaves a lock behind. Old locks must be cleared, or they block access to records. Capture lock entries whose timestamp is from the previous day or earlier β€” those are the candidates for cleanup. ## Monitoring the System Log (SM21) SM21 surfaces system errors, warnings, and security messages. Use it to pinpoint and rectify issues in the system and its environment. Check the previous day’s log with: - Enter the date and time range. - Select the *Problems and Warnings* radio button. - Click *Reread System Log*. [![Monitoring System Log SM21]()](https://www.guru99.com/images/sap/2013/05/050913_0552_12.png) ## Tune Summary (ST02) ST02 shows the buffer tune summary. Use the steps below to act on swap problems. **Step 1)** Open ST02 to view the tune summary. **Step 2)** Double-click any red value under *SWAPS*. [![Tune Summary ST02]()](https://www.guru99.com/images/sap/2013/05/050913_0552_13.png) **Step 3)** Click the *Current Parameters* tab. [![ST02 Current Parameters]()](https://www.guru99.com/images/sap/2013/05/050913_0552_14.png) **Step 4)** Note the values and the profile parameters. [![ST02 profile values]()](https://www.guru99.com/images/sap/2013/05/050913_0552_15.png) **Step 5)** Open RZ10 to change profile-parameter values. **Step 6)** Save the changes. **Step 7)** Restart the server so the new values take effect. ## CPU Utilization (ST06) ST06 shows operating-system level performance. Idle CPU utilisation should sit around 60–65%; sustained higher load means the system is under pressure. [![CPU Utilization ST06]()](https://www.guru99.com/images/sap/2013/05/050913_0552_16.png) When CPU is high, follow this short triage path: - Run OS-level commands (such as `top`) to find which processes are using the most CPU. - Open SM50 or SM66 and look for long-running jobs or update queries. - Open SM12 and check for old lock entries. - Open SM13 to check update status. - Open SM21 to look for system errors. ## ABAP Dumps (ST22) ST22 captures ABAP runtime errors (short dumps). Review the previous day’s dumps each morning to spot unusual patterns or repeat offenders. [![ABAP Dumps ST22]()](https://www.guru99.com/images/sap/2013/05/050913_0552_17.png) ## Spool Request Monitoring (SP01) Run SP01 to monitor spool requests: - Enter `*` in the *Created By* field. - Click *Execute*. [![Spool Request Monitoring SP01]()](https://www.guru99.com/images/sap/2013/05/050913_0552_19.png) Record only requests terminated with problems. [![Spool requests terminated]()](https://www.guru99.com/images/sap/2013/05/050913_0552_20.png) ## Monitoring Batch Jobs (SM37) Run SM37 to monitor background jobs: - Enter `*` in the *User Name* and *Job name* fields. - Under *Job status* select Scheduled, Cancelled, Released, and Finished. [![Monitoring Batch Jobs SM37]()](https://www.guru99.com/images/sap/2013/05/050913_0552_21.png) ## Transactional RFC Administration (SM58) Transactional RFC (tRFC), originally known as asynchronous [RFC](https://www.guru99.com/rfc-remote-function-call.html), executes the called function module on the RFC server exactly once. [![Transactional RFC SM58]()](https://www.guru99.com/images/sap/2013/05/050913_0552_22.png) Select the display period you want to review, enter `*` in the user field, and execute. The list shows any calls that have not run successfully or are still waiting in the queue. ## QRFC Administration (Outbound Queue β€” SMQ1) SMQ1 monitors outbound qRFC queues. Specify the client and look for queues in *Waiting* or *Error* state. [![QRFC Outbound SMQ1]()](https://www.guru99.com/images/sap/2013/05/050913_0552_23.png) ## QRFC Administration (Inbound Queue β€” SMQ2) SMQ2 mirrors SMQ1 for inbound qRFC queues. Specify the client and look for incoming queues in *Waiting* or *Error* state. [![QRFC Inbound SMQ2]()](https://www.guru99.com/images/sap/2013/05/050913_0552_24.png) ## Database Administration (DB02) DB02 is the central database administration cockpit. The first screen lets you drill into tablespaces, missing indexes, and growth history. [![Database Administration DB02 entry]()](https://www.guru99.com/images/sap/2013/05/050913_0552_25.png) Select *Current Sizes* to see the status of every tablespace. [![DB02 Current Sizes]()](https://www.guru99.com/images/sap/2013/05/050913_0552_26.png) If any tablespace is more than 95% full and auto-extend is off, add a new datafile so the database does not run out of space. You can also review the history of a tablespace by month, week, or day to spot growth trends. [![DB02 history selection]()](https://www.guru99.com/images/sap/2013/05/050913_0552_27.png) [![DB02 history chart]()](https://www.guru99.com/images/sap/2013/05/050913_0552_28.png) [![DB02 detail view]()](https://www.guru99.com/images/sap/2013/05/050913_0552_29.png) ## Database Backup Logs (DB12) DB12 confirms when the last successful backup ran. Review the previous day’s database and redo-log backups to make sure they finished cleanly. [![Database Backup logs DB12]()](https://www.guru99.com/images/sap/2013/05/050913_0552_30.png) ## Quick Review: Daily Monitoring Checklist The tables below summarise the critical daily checks for Basis administrators. ### Critical Tasks | # | Task | Transaction | Procedure / Remark | | --- | --- | --- | --- | | 1 | Confirm the R/3 system is up. | β€” | Log on to the R/3 system. | | 2 | Confirm the daily backup ran without errors. | DB12 | Check the database backup log. | ### SAP System Checks | # | Task | Transaction | Procedure / Remark | | --- | --- | --- | --- | | 1 | Confirm every application server is up. | SM51 | All servers up. | | 2 | Check work processes. | SM50 | All work processes in Running or Waiting status. | | 3 | Global work-process overview. | SM66 | No work process running more than 1800 seconds. | | 4 | Look for failed or terminated updates. | SM13 | Set date to one day ago, enter `*` in User ID, set to β€œAll” updates. Look for lines with `Err.` | | 5 | Check the system log. | SM21 | Set the date and time to before the last review. Look for errors, warnings, security messages, and database problems. | | 6 | Review cancelled jobs. | SM37 | Enter `*` in User ID. Confirm every critical job finished successfully. | | 7 | Check for old locks. | SM12 | Enter `*` in User ID. | | 8 | Check for users on the system. | SM04 / AL08 | Look for unexpected user IDs or terminals; review several times per day. | | 9 | Check for spool problems. | SP01 | Enter `*` in Created By. Look for spool jobs stuck β€œIn process” for over an hour. | | 10 | Check the job log. | SM37 | Look for new or incorrect jobs. | | 11 | Review and resolve dumps. | ST22 | Look for excessive or unusual dumps. | | 12 | Review buffer statistics. | ST02 | Look for swaps. | ### Database Checks | # | Task | Transaction | Procedure / Remark | | --- | --- | --- | --- | | 1 | Review the database error log. | ST04 | Investigate any new errors. | | 2 | Database growth and missing indexes. | DB02 | If a tablespace is > 90% used add a new datafile; rebuild missing indexes. | | 3 | Database statistics log. | DB13 | Confirm scheduled statistics jobs completed. | ## FAQs ⚑ Which T-codes form the core SAP daily monitoring checklist? The core T-codes are SM51, SM50, SM66, SM12, SM13, SM21, SM37, SP01, ST22, ST02, ST06, DB02, and DB12. Together they cover servers, work processes, locks, updates, logs, dumps, buffers, CPU, and database health. πŸš€ What is the difference between SM50 and SM66? SM50 shows work processes for the current application server only. SM66 aggregates work-process data across every active instance, giving a system-wide view that is ideal for cross-instance performance triage. πŸ’‘ When should I delete a lock entry in SM12? Delete a lock only after confirming the owning session has ended. Locks older than the previous day that are no longer tied to an active session are usually safe to remove after consulting the user or owning team. πŸ”’ What does PRIV status mean in SM50? PRIV means a dialog work process is operating in private (extended) memory mode because a single user transaction grew too large. Other users cannot use that work process until the owning transaction ends. πŸ“ What is a healthy CPU utilisation target in ST06? Idle CPU around 60–65% is a healthy steady-state target. Sustained idle below 30% signals capacity pressure and warrants a review of SM50, SM66, SM12, SM13, and SM21 to find the root cause. ⏱️ How often should Basis administrators run these checks? Most checks run once per day, ideally early morning. Critical ones such as SM04/AL08 (active users), SM21 (system log), and ST06 (CPU) are reviewed several times a day, especially during peak business hours. πŸ€– How can AI improve SAP system monitoring? AI tools cluster SM21 messages, summarise ST22 dump trends, predict tablespace exhaustion from DB02 history, and recommend the next investigative T-code. This reduces noise and speeds up incident response. ✍️ Can AI generate a daily SAP Basis report automatically? Yes. AI assistants ingest screenshots and exports from the daily T-codes, then produce a structured report that flags anomalies, links each issue to the next T-code, and proposes remediation steps for the Basis team. #### Summarize this post with: ChatGPTPerplexityGrokGoogle AI **Stay Updated on AI** **Get Weekly AI Skills, Trends, Actionable Advice.** ##### Sign up for the newsletter Subscribe for Free You have successfully subscribed. Please check your inbox. ![AI-Newsletter]() Chosen by over **350,000+** professionals [Scroll to top](#wrapper) Γ— Search for: ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://www.guru99.com/#organization","name":"Guru99","sameAs":["https://www.facebook.com/Guru99Official","https://twitter.com/guru99com"],"logo":{"@type":"ImageObject","@id":"https://www.guru99.com/#logo","url":"https://www.guru99.com/images/guru99-logo-v1-150x59.png","contentUrl":"https://www.guru99.com/images/guru99-logo-v1-150x59.png","caption":"Guru99","inLanguage":"en-US"}},{"@type":"WebSite","@id":"https://www.guru99.com/#website","url":"https://www.guru99.com","name":"Guru99","publisher":{"@id":"https://www.guru99.com/#organization"},"inLanguage":"en-US"},{"@type":"ImageObject","@id":"https://www.guru99.com/images/system-monitoring-performance-checks-1.png","url":"https://www.guru99.com/images/system-monitoring-performance-checks-1.png","width":"650","height":"250","inLanguage":"en-US"},{"@type":"BreadcrumbList","@id":"https://www.guru99.com/system-monitoring-performance-checks.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":"1","item":{"@id":"https://www.guru99.com","name":"Home"}},{"@type":"ListItem","position":"2","item":{"@id":"https://www.guru99.com/sap-basis","name":"SAP - Basis"}},{"@type":"ListItem","position":"3","item":{"@id":"https://www.guru99.com/system-monitoring-performance-checks.html","name":"SAP Basis Monitoring Tcodes & Health Checks"}}]},{"@type":"WebPage","@id":"https://www.guru99.com/system-monitoring-performance-checks.html#webpage","url":"https://www.guru99.com/system-monitoring-performance-checks.html","name":"SAP Basis Monitoring Tcodes & Health Checks","dateModified":"2026-10-09T12:14:01+05:30","isPartOf":{"@id":"https://www.guru99.com/#website"},"primaryImageOfPage":{"@id":"https://www.guru99.com/images/system-monitoring-performance-checks-1.png"},"inLanguage":"en-US","breadcrumb":{"@id":"https://www.guru99.com/system-monitoring-performance-checks.html#breadcrumb"}},{"@type":"Person","@id":"https://www.guru99.com/author/editorial","name":"Editorial Team","url":"https://www.guru99.com/author/editorial","image":{"@type":"ImageObject","@id":"https://www.guru99.com/images/favicon-new-logo.png","url":"https://www.guru99.com/images/favicon-new-logo.png","caption":"Editorial Team","inLanguage":"en-US"},"sameAs":["https://www.guru99.com/editorial-team"],"worksFor":{"@id":"https://www.guru99.com/#organization"}},{"articleSection":"SAP - Basis","headline":"SAP Basis Monitoring Tcodes & Health Checks","description":"Monitor a SAP System using tcodes SM51,SM50,SM66,AL08,SM04,SM13, SM12,SM21,ST02,ST06,ST22,SP01,SM37,SM58,SMQ1,SMQ2,DB02,DB12","keywords":"sap-basis, sap","speakable":{"@type":"SpeakableSpecification","cssSelector":[".entry-title",".summary"]},"@type":"Article","author":{"@id":"https://www.guru99.com/author/editorial","name":"Editorial Team"},"dateModified":"2026-10-09T12:14:01+05:30","image":{"@id":"https://www.guru99.com/images/system-monitoring-performance-checks-1.png"},"copyrightYear":"2026","name":"SAP Basis Monitoring Tcodes & Health Checks","subjectOf":[{"@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Which T-codes form the core SAP daily monitoring checklist?","acceptedAnswer":{"@type":"Answer","text":"The core T-codes are SM51, SM50, SM66, SM12, SM13, SM21, SM37, SP01, ST22, ST02, ST06, DB02, and DB12. Together they cover servers, work processes, locks, updates, logs, dumps, buffers, CPU, and database health."}},{"@type":"Question","name":"What is the difference between SM50 and SM66?","acceptedAnswer":{"@type":"Answer","text":"SM50 shows work processes for the current application server only. SM66 aggregates work-process data across every active instance, giving a system-wide view that is ideal for cross-instance performance triage."}},{"@type":"Question","name":"When should I delete a lock entry in SM12?","acceptedAnswer":{"@type":"Answer","text":"Delete a lock only after confirming the owning session has ended. Locks older than the previous day that are no longer tied to an active session are usually safe to remove after consulting the user or owning team."}},{"@type":"Question","name":"What does PRIV status mean in SM50?","acceptedAnswer":{"@type":"Answer","text":"PRIV means a dialog work process is operating in private (extended) memory mode because a single user transaction grew too large. Other users cannot use that work process until the owning transaction ends."}},{"@type":"Question","name":"What is a healthy CPU utilisation target in ST06?","acceptedAnswer":{"@type":"Answer","text":"Idle CPU around 60-65% is a healthy steady-state target. Sustained idle below 30% signals capacity pressure and warrants a review of SM50, SM66, SM12, SM13, and SM21 to find the root cause."}},{"@type":"Question","name":"How often should Basis administrators run these checks?","acceptedAnswer":{"@type":"Answer","text":"Most checks run once per day, ideally early morning. Critical ones such as SM04/AL08 (active users), SM21 (system log), and ST06 (CPU) are reviewed several times a day, especially during peak business hours."}},{"@type":"Question","name":"How can AI improve SAP system monitoring?","acceptedAnswer":{"@type":"Answer","text":"AI tools cluster SM21 messages, summarise ST22 dump trends, predict tablespace exhaustion from DB02 history, and recommend the next investigative T-code. This reduces noise and speeds up incident response."}},{"@type":"Question","name":"Can AI generate a daily SAP Basis report automatically?","acceptedAnswer":{"@type":"Answer","text":"Yes. AI assistants ingest screenshots and exports from the daily T-codes, then produce a structured report that flags anomalies, links each issue to the next T-code, and proposes remediation steps for the Basis team."}}]}],"@id":"https://www.guru99.com/system-monitoring-performance-checks.html#schema-1111618","isPartOf":{"@id":"https://www.guru99.com/system-monitoring-performance-checks.html#webpage"},"publisher":{"@id":"https://www.guru99.com/#organization"},"inLanguage":"en-US","mainEntityOfPage":{"@id":"https://www.guru99.com/system-monitoring-performance-checks.html#webpage"}}]} ```