Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

The system log records important SAP system events. SM21 is a classic tool for reviewing these records, helping operations teams connect a reported problem with events at the same time.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

SAP Basis work keeps relevant SAP systems running. Logs, background jobs and connection tools help explain what happened to a task at a particular time.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for SAP SM21 system log: Find the right server and incident time
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

AS ABAP system-log investigation for Basis and support analysts. ABAP Platform and post-7.02 central-log concepts are distinguished from older central-file documentation. Access, retention and remote collection depend on the installed landscape.

Documentation review on 14 November 2026 used the available official SAP indexed excerpts; several SAP Help pages returned no readable full text. The worked case and proposed checks are original illustrative teaching material, not execution evidence from a customer SAP system. Exact fields, permitted actions and behavior must be confirmed against the installed product, release and configuration.

A MANUFACTURING EXAMPLE

Locate the system event behind a factory failure

Match the incident window

Reported failure: 10:05. Application instance: Instance A. Log selection: 10:00–10:10 on A. Unrelated sample: 11:00 on instance B
What to notice: A nearby message is useful only when its system, instance and time actually match the incident.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Reported failure
10:05
Application instance
Instance A
Log selection
10:00–10:10 on A
Unrelated sample
11:00 on instance B
Words you’ll meet in this guide
Instance
A running SAP application-server environment.
Client
A logically separate data and configuration context in an ABAP system.
Log
A recorded sequence of events and messages.
ABAP
SAP’s programming language for business applications.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Incident time → Relevant instance log → Correlated event. Conceptual diagram for SAP SM21 system log: Find the right server and incident time.
Apply the idea: A manufacturing application fails on one server while an analyst reviews a quiet log from another instance.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Locate the system event behind a factory failure

    A manufacturing application fails on one server while an analyst reviews a quiet log from another instance.

  2. Find the event in the correct instance and time window

    SM21 displays SAP system-log messages.

  3. What you need before interpreting the list

    This tutorial is for Basis operators and application-support analysts with permitted log-display access.

  4. Worked case: a failure on instance B, a quiet log on A

    In our fictional system QAS, instances A and B serve dialog work.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.