SAP Daily Basis Health Check Checklist
A short, consistent morning routine catches most SAP problems before the business does. This checklist organizes the usual Basis checks by theme and flags the ones you should never skip.
0 of 33 items complete
10 critical items still open - these are the highest-risk gaps.
System availability and processes
Errors, dumps and updates
Jobs, queues and interfaces
Database, backup and capacity
Security and transport hygiene
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.
Related Tools
SAP Basis Transaction Codes Cheat Sheet
A searchable reference of the SAP Basis, security and system administration transaction codes you use every week, grouped by area.
SAPSAP Security Profile Parameters Reference
A searchable reference of the profile parameters that control SAP logon, passwords, authorization checks, RFC, gateway and audit logging.
SAPSAP Basis Security Hardening Assessment
Answer ten questions about your SAP system security basics and get a score with the gaps to close first.
SAPSAP Inactive Users ABAP Report Generator
Fill in the inactivity threshold and user type to get a ready to paste ABAP report that lists dormant users from USR02.
More SAP tools
See all- SAP SD Rebate Agreement Request Form Template
- SAP SD Sales Order Item ABAP SELECT Generator
- SAP Cost Element Categories Reference
- SAP Period End Closing Checklist
- SAP Standard Cost Variance Calculator
- SAP Activity Type Rate Calculator
- SAP Document Types Reference
- SAP Posting Keys Reference
- SAP Cost Center Hierarchy Upload Worksheet
Keep exploring
Free tools
- SAP Basis Security Hardening AssessmentAnswer ten questions about your SAP system security basics and get a score with the gaps to close first.
- SAP Go-Live Security Readiness ChecklistA checklist of security and Basis items to confirm before an SAP system or release goes live, with critical items flagged.
- SAP Basis Transaction Codes Cheat SheetA searchable reference of the SAP Basis, security and system administration transaction codes you use every week, grouped by area.
ERP fixes and how-tos
- SAP S/4HANA upgrade steps: a runbook for manufacturersStep-by-step SAP S/4HANA upgrade and conversion runbook: readiness check, Maintenance Planner, custom code, SUM, testing and cutover for manufacturers.
- SAP: 'This Function Is Not Possible' - Causes and How to DiagnoseSAP shows 'This function is not possible' when status, authorization, posting rules or the object state block an action. Learn how to find the real cause.
- Printer Not Working in SAP: Troubleshooting Spool Requests with SP01 and SPADFix a printer not working in SAP: read the spool request in SP01, check the output device and access method in SPAD, spool work processes and user defaults.
AI on your ERP
- Building GDPR-Compliant AI on Top of Your ERPDesign AI on ERP data that satisfies GDPR: lawful basis, DPIA, data minimisation, and an on-prem architecture that avoids the Schrems II transfer problem.
- Get AI Value From SAP ECC Now, and Use It to De-Risk the Move to S/4HANASAP ECC 6.0 mainstream maintenance ends in 2027. Add AI value on ECC now, using its existing BAPIs and IDocs, and use it to de-risk the S/4HANA migration.