# SAP Daily Basis Health Check Checklist

> Source: https://netray.co/tools/sap-daily-basis-health-check-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A daily checklist of the transactions and checks a Basis admin runs each morning to confirm an SAP system is healthy.

## Category

sap

## Erp

SAP ECC and S/4HANA

## Audience

- SAP Basis admin
- SAP support analyst
- IT operations

## Tool

**Kind:** checklist

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

**Groups:**

#### System availability and processes

**Items:**

**Text:** All application servers are up in SM51 and the central instance responds

**Critical:** true

**Text:** Work processes are not all busy or stuck; no long running dialog processes in SM50 or SM66

**Critical:** true

Message 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)

**Text:** System log SM21 shows no new kernel, database or memory errors since yesterday

**Critical:** true

Operating system load, memory and swap are within normal limits (ST06)

#### Errors, dumps and updates

**Items:**

**Text:** ABAP dumps in ST22 reviewed; new or frequent dumps assigned to an owner

**Critical:** true

**Text:** No terminated or stuck update requests in SM13

**Critical:** true

Update service is active (SM14)

No unexpected long held lock entries in SM12

Application logs for key interfaces reviewed (SLG1)

Developer traces in ST11 checked if an error is suspected

#### Jobs, queues and interfaces

**Items:**

**Text:** No cancelled or overrunning jobs in SM37 for critical schedules such as period end and interfaces

**Critical:** true

Standard housekeeping jobs ran (for example SAP_REORG_JOBS and spool and job log cleanup)

**Text:** tRFC calls have no errors in SM58

**Critical:** true

qRFC 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

**Items:**

**Text:** Last database backup completed successfully (DB12 or DBACOCKPIT)

**Critical:** true

**Text:** Log backups or archiving are running, log area has free space

**Critical:** true

Database 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

**Items:**

Security Audit Log shows no unexpected use of SAP*, DDIC or emergency users (SM20)

Failed logon attempts are within normal range

**Text:** No unexpected imports in the production import queue (STMS)

**Critical:** true

System license and certificate expiry dates are not close (SLICENSE, STRUST)

Monitoring alerts in RZ20 or your monitoring tool reviewed and acknowledged

Findings recorded in the shift log or ticketing system with owner and status

## Content

**Intro:** 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.

**Sections:**

#### How to use the checklist

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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.

**Bullets:**

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

**Cta:** 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.

**Faq:**

#### How long should a daily SAP health check take?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

sap daily health check, sap basis daily checklist, sap system monitoring checklist, sap morning checks, sap basis daily tasks, sap health check sm50 sm21 st22, sap operations checklist, sap basis monitoring template

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json