What to check
A slow workbook is not automatically a slow database query. Selection processing, analytic calculations, result transfer, and frontend rendering can all contribute. Use the same query, variables, and user context for comparisons, and distinguish a first execution from a repeat with warm caches.
Troubleshooting steps
- Record the query's technical name, variable values, drilldown, frontend, user, and measured runtime for the reported scenario.
- Compare a controlled backend execution in the query monitor with the frontend run. Review available statistics to locate the expensive phase.
- Collect a narrowly scoped approved trace if needed and test one targeted change, such as a justified restriction, corrected join, or calculation adjustment.
Confirm the result
Repeat comparable executions and verify totals and selection behavior. Report which phase improved and under which conditions instead of treating one fast cached run as proof of a permanent fix.
References
The SAP KBA link provides a public symptom preview; its full resolution requires SAP Support access. These diagnostic steps are independent guidance. Check the installed release before applying a correction.