GUIDE · SAP BASIS MONITORING

SAP Basis monitoring checklist: what to check every day

Most SAP outages give warning signs hours or days in advance. A consistent daily routine catches them early. This checklist covers what an SAP Basis team should look at every day, and how to automate it across many systems.

7 min readUpdated 13 November 2026By the Farrenio SAP Basis team

Daily checks for every SAP system

  • System availability: all application server instances up and the message server reachable.
  • Work processes: free dialog and background work processes, and long-running processes that block others.
  • Background jobs: cancelled or long-running jobs, especially business-critical and housekeeping jobs.
  • Runtime errors: new ABAP dumps, grouped by type and program, with sudden increases flagged.
  • System log: errors and warnings since the last check.
  • Lock entries: old locks that block users or jobs.
  • Update requests: failed or stuck update records.
  • Spool: print requests in error and spool database growth.

Database and SAP HANA

  • Data and log volume fill, and growth trend in days of headroom.
  • Memory usage against the allocation limit, and the largest memory consumers.
  • Expensive statements and blocked transactions.
  • Backups: last successful data and log backup, and backup catalog size.
  • System replication status, where high availability is configured.

Interfaces and connectivity

  • RFC destinations reachable, and queues (inbound and outbound) not stuck.
  • Integration jobs and IDocs in error.
  • Certificates: expiry dates for SSL, SNC and client certificates.

Operating system and host

  • CPU, memory and paging on every host.
  • File system usage, especially for logs, traces and transport directories.
  • Time synchronisation and host availability.

Weekly and monthly checks

  • Workload and response time trends, to spot slow degradation.
  • Transport and change logs.
  • User and authorization changes.
  • SAP Security Notes and kernel or HANA patch levels.

From checklist to monitoring

Doing these checks by hand works for one system. For a landscape of several systems, it takes hours and depends on who is on duty. A monitoring platform collects the same data continuously, raises alerts on thresholds and keeps the history to show trends. Farrenio Cloud Control was built for this: one web console across all SAP systems and SAP HANA databases, with alert routing and an audit trail.

Frequently asked questions

What should SAP Basis check every day?

System availability, work processes, background jobs, runtime errors, system log, locks, update requests, database and HANA health, backups, interfaces and certificates.

Can SAP Basis monitoring be automated?

Yes. Tools such as SAP Solution Manager, SAP Cloud ALM and Farrenio Cloud Control collect these metrics continuously and alert on thresholds, so engineers act on exceptions instead of checking every system by hand.

How do you monitor SAP HANA?

Track data and log volume fill, memory against its limit, expensive statements, backups and replication status, for the system database and every tenant.

Written by the SAP Basis team at Farrenio. Dates and rules reflect publicly available information on 2026-11-13; check SAP's and ANAF's current terms before making decisions.

Talk to an SAP Basis consultant

Tell us about your landscape. We come back with a first assessment and the cost and time savings we see.

Contact us