SAP Daily Basis Health Check Checklist (Free PDF)

0%

0 of 33 items complete

10 critical items still open - these are the highest-risk gaps.

Download checklist:

System availability and processes

All application servers are up in SM51 and the central instance respondsCRITICALWork processes are not all busy or stuck; no long running dialog processes in SM50 or SM66CRITICALMessage server and gateway are reachable (SMMS, SMGW)ICM is running and HTTP(S) services respond (SMICM)No unusual number of users logged on compared with the normal pattern (SM04 or AL08)System log SM21 shows no new kernel, database or memory errors since yesterdayCRITICALOperating system load, memory and swap are within normal limits (ST06)

Errors, dumps and updates

ABAP dumps in ST22 reviewed; new or frequent dumps assigned to an ownerCRITICALNo terminated or stuck update requests in SM13CRITICALUpdate service is active (SM14)No unexpected long held lock entries in SM12Application logs for key interfaces reviewed (SLG1)Developer traces in ST11 checked if an error is suspected

Jobs, queues and interfaces

No cancelled or overrunning jobs in SM37 for critical schedules such as period end and interfacesCRITICALStandard housekeeping jobs ran (for example SAP_REORG_JOBS and spool and job log cleanup)tRFC calls have no errors in SM58CRITICALqRFC outbound and inbound queues are not blocked (SMQ1, SMQ2)Key RFC destinations connect successfully (SM59 test)Outbound email and SAPconnect queue is not backing up (SOST)Spool requests in error or growing unexpectedly are checked (SP01)IDoc and interface error queues reviewed according to your landscape

Database, backup and capacity

Last database backup completed successfully (DB12 or DBACOCKPIT)CRITICALLog backups or archiving are running, log area has free spaceCRITICALDatabase free space and growth are within thresholds (DB02 or DBACOCKPIT)File systems such as the transport directory and trace area have free space (AL11, OS level)Buffer quality and memory are acceptable (ST02)Response times for dialog and update tasks are in the normal range (ST03N)

Security and transport hygiene

Security Audit Log shows no unexpected use of SAP*, DDIC or emergency users (SM20)Failed logon attempts are within normal rangeNo unexpected imports in the production import queue (STMS)CRITICALSystem license and certificate expiry dates are not close (SLICENSE, STRUST)Monitoring alerts in RZ20 or your monitoring tool reviewed and acknowledgedFindings recorded in the shift log or ticketing system with owner and status

Mark each item once checked. Critical items should never be skipped; if one fails, raise an incident before continuing the routine.

Overnight SAP status summary

Optional: ask about a private assistant that summarises monitoring output for your Basis team.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Work through the groups in order each morning and tick items as you go. Export to PDF to print a shift sheet or to attach the completed list to a ticket. If a critical item fails, stop and handle it before continuing. The goal is a fifteen to thirty minute routine for one system; for a landscape, split by system and rotate the owner. Once the routine is stable, many of these checks can be automated in your monitoring tool.

Do the same checks at the same time each day
Record findings with an owner, even when they are minor
Review the checklist quarterly and remove checks you have automated

What each group is for

The first group answers 'is the system up and serving users'. The second finds application level failures: dumps, failed updates, locks. The third checks that data moves: background jobs, tRFC, qRFC and mail. The fourth protects against data loss and capacity problems, where a missed backup or full log area is the costliest failure. The last group adds security and change hygiene so unexpected imports or privileged logons are noticed early.

Common mistakes

Teams often check availability but not backups, or look at dumps without assigning owners so the same dumps stay open for months. Another mistake is relying on a single green traffic light in a monitor without checking what the monitor actually covers. Also avoid doing checks only on the central instance in a multi server system.

Check backups and log space every day
Assign every recurring dump to an owner
Include every application server in the routine

Frequently Asked Questions

How long should a daily SAP health check take?

For one system with a stable setup, fifteen to thirty minutes is typical. A larger landscape takes longer unless checks are automated through monitoring such as the CCMS alert monitor or a central tool.

Which checks should be automated first?

Backups, job failures, dumps above a threshold, file system space and failed RFC queues are the best candidates. They are objective, frequent and easy to alert on, leaving human time for judgement.

Is this checklist enough for a production system?

It is a daily baseline. Weekly and monthly tasks such as patching, capacity trending, access reviews and disaster recovery tests are separate and should have their own schedule.

Does the checklist apply to S/4HANA?

Mostly yes. Some database checks move to SAP HANA cockpit or DBACOCKPIT, and Fiori monitoring apps can replace some transactions, but the intent of each check stays the same.

If your Basis team spends the first hour of every day on these checks, we can help build a private assistant that summarises the overnight state of your SAP landscape.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

SAP Daily Basis Health Check Checklist