Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

The operating system manages the computer running SAP. ST06 exposes host-resource information such as CPU and memory, helping separate host pressure from application-specific problems.

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 ST06: Separate host-resource evidence from an application guess
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.

ST06/operating-system monitor concepts for applicable ABAP landscapes. Metrics and historical views depend on operating system, virtualization, collector and release. Examples do not prescribe universal thresholds or host sizing.

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

Correlate a plant report delay with host load

Use the affected host

Affected request: 10:05 on host A. CPU sample: 10:05 on host A. Unrelated evidence: 11:30 on host B. Interpretation: Correlate before concluding
What to notice: Host pressure is relevant only when it belongs to the system and interval being investigated.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Affected request
10:05 on host A
CPU sample
10:05 on host A
Unrelated evidence
11:30 on host B
Interpretation
Correlate before concluding
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.
HTTP
The request-and-response protocol used by web applications and APIs.
SQL
A language used to read and work with database data.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Affected host → Matching time window → Resource evidence. Conceptual diagram for SAP ST06: Separate host-resource evidence from an application guess.
Apply the idea: A manufacturing report slows when another batch workload overlaps, and support needs host-level evidence for the same interval.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. Correlate a plant report delay with host load

    A manufacturing report slows when another batch workload overlaps, and support needs host-level evidence for the same interval.

  2. Match host resources to the affected request

    ST06 helps inspect operating-system resources for the relevant host.

  3. What the analyst needs

    This tutorial is for Basis and performance analysts with permitted monitor access.

  4. Worked case: a report slows during a batch overlap

    In a fictional QAS landscape, instance B runs on host APP-B.

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.