SAP Basis Performance Tuning

You are a SAP Basis administrator responsible for system performance analysis and tuning. The user wants to identify bottlenecks using ST02, ST03, and ST22 transactions and apply targeted tuning measures.

What to check first

• Run transaction ST02 (Tune Summary) to verify buffer pool status and memory allocation
• Check transaction ST03 (SAP Statistics) to confirm statistical data collection is enabled (STAT parameter)
• Access transaction ST22 (Dump Analysis) to review runtime error logs and frequency patterns
• Verify you have the PFCG role SAP_ALL or SAP_BASIS_ADMIN for full access

Steps

1. Open transaction ST02 and navigate to the "Buffer" tab—examine hit ratios for DB buffer, program buffer, and CUA buffer (target: >99% for DB, >95% for program)
2. Identify critical misses in ST02's "Detail Analysis" section; note buffer types with <90% hit ratio requiring expansion via parameter db_tabsize, db_ctry_size, or rsdb_max_filters
3. Execute transaction ST03 and select "Workload Analysis" for the current day—sort by "Total Time" to isolate expensive transactions consuming >10% of system time
4. In ST03, drill into top transactions (typically SAPMSSS0, SAPMSSS1, or module-specific transactions) and check "Database Time", "CPU Time", and "Roll Wait Time" columns
5. Switch to transaction ST22 and filter dumps by "Exception Type"—focus on DBIF_REPO_NOT_FOUND, STATEMENT_NOT_EXECUTED, or SYSTEM_FAILURE patterns indicating SQL, buffer, or memory issues
6. In ST22, select frequent runtime errors and click "Extended Information" to extract root causes; cross-reference with ST03 transaction times during error windows
7. Adjust SAP profile parameters based on findings: increase em/initial_size_mb if ST02 shows extended memory pressure, or modify ztta/roll_area if ST03 shows high rollout rates
8. Monitor ST02 "Memory Configuration" post-change to validate buffer behavior; re-run ST03 analysis after 24–48 hours to quantify improvement in transaction response times

Code

REPORT zperf_tune_analysis.

DATA: lt_buffer_stats TYPE TABLE OF statistic_record,
      lt_transaction_data TYPE TABLE OF sapstat_transaction,
      ls_buffer LIKE LINE OF lt_buffer_stats,
      lv_hit_ratio DECIMAL,
      lv_db_time INT4,
      lv_cpu_time INT4,
      lv_buffer_name STRING.

" ST02 Buffer Analysis via RFC/API
CALL FUNCTION 'STUN_GET_BUFFER_STATISTICS'
  EXPORTING
    buffer_name = 'DB'
  IMPORTING
    statistics = lt_buffer_stats
  EXCEPTIONS
    buffer

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change