ST10 — Table Call Statistics
ST10 is used to analyze table access statistics collected by the SAP system, including calls and buffering behavior. It is most useful when performance analysis needs evidence about frequently accessed tables and table-buffer usage over a period. For reliable SAP support, capture the exact system, client, user, time and object context first, then use the transaction's evidence before making configuration or data changes.
Verified practitioner reference for ST10 — Table Call Statistics. It explains what the transaction does, when it is appropriate, which parameters and evidence matter, how to use it safely, common diagnostic traps, and how its role changes or remains relevant in S/4HANA.
Published 19 Sept 2026· 628 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
analyze table access statistics collected by the SAP system, including calls and buffering behavior. The transaction is most valuable when used as part of an evidence chain rather than as a shortcut. Start from the exact business or technical incident, preserve its user, time, system and object context, and distinguish display/analysis functions from actions that can alter system state.
When it is used
ST10 is typically used when performance analysis needs evidence about frequently accessed tables and table-buffer usage over a period. Consultants also use it during project testing and post-change validation because a repeatable selection gives objective evidence. In production, keep the initial scope narrow and widen it only after confirming that the first result matches the reported incident.
How to use it in practice
- Select the relevant server and time frame.
- Identify high-call tables and whether their access pattern matches buffering expectations.
- Use the result as a lead, not as proof of a code defect.
- Correlate expensive database access with ST05 or SQL analysis.
- Compare after a controlled tuning change using the same workload window.
Key data objects
These are the most useful anchors for work in ST10. Capture them in incident notes or test evidence so another consultant can reproduce the same result.
- table name — verify the exact value and its relationship to the affected execution or business object.
- server — verify the exact value and its relationship to the affected execution or business object.
- time frame — verify the exact value and its relationship to the affected execution or business object.
- access type — verify the exact value and its relationship to the affected execution or business object.
- buffer/load statistics — verify the exact value and its relationship to the affected execution or business object.
How to prove it in the data
Build a reproducible before-and-after proof. Capture the exact selection or object, record the status, log or result that demonstrates the issue, then apply one controlled correction and repeat the same check. Correlate with neighboring SAP logs, documents or repository objects where needed. A successful retry with changed input is not the same as proving the original root cause.
ECC vs S/4HANA
ST10 remains available for ABAP table-call statistics, while HANA-native tools and SQL Monitor can add deeper database insight. Availability of a classic transaction does not automatically make it the preferred implementation pattern for new work; distinguish support compatibility from clean-core and cloud-oriented design guidance.
Common pitfalls and how to diagnose them
- Optimizing a table simply because it has many accesses. Validate the exact object, user, timestamp and release context before applying a fix.
- Ignoring that frequent buffered access may be cheap. Validate the exact object, user, timestamp and release context before applying a fix.
- Comparing statistics collected over different workloads. Validate the exact object, user, timestamp and release context before applying a fix.
Whose problem this is
Primary ownership is usually with the BASIS team. Bring in Basis, Security, functional or development specialists only when the evidence crosses those boundaries. A high-quality escalation includes the exact transaction, selection or object, timestamp, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/st10ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.