SAP systems are powerful but complex. Issues like performance bottlenecks, authorization errors, and integration failures are common, and troubleshooting them can be daunting. That’s where SAP Tracing becomes invaluable. It allows administrators to pinpoint issues by examining backend logs and processes in real-time. In this article, we’ll explore the most important types of SAP traces and how to use them effectively.

1. ABAP Trace (ST05 / ST12)

Purpose: Identify ABAP performance issues and logic flaws, especially in custom programs or transactions.

Steps:

• ST05: Choose trace type, apply user filter, activate trace, reproduce issue, deactivate trace, and analyze output.
• ST12: Enter user name, add a comment, execute the trace, and analyze performance stats.

2. Authorization Trace (ST01 / SU53)

Purpose: Resolve authorization failures by identifying missing permissions.

Steps:

• ST01: Enable “Authorization Check”, filter by user, activate trace, reproduce the error, stop trace, and analyze.
• SU53: Run immediately after an authorization failure for a quick diagnostic snapshot.

3. OData Gateway Trace (/IWFND/TRACES, /IWFND/ERROR_LOG)

Purpose: Diagnose issues in SAP Fiori and OData services.

Steps:

• /IWFND/TRACES: Add user or URI prefix, enable performance/payload trace, reproduce issue, and analyze logs.
• /IWFND/ERROR_LOG: View service or user-specific error logs.

4. SAP Gateway Trace (SMGW, GWMON)

Purpose: Debug external RFC communication issues and gateway problems.

Steps:

• Go to SMGW → Goto → Trace → Gateway → Increase level, reproduce issue, then reduce trace level.
• Use GWMON or dev_rd logs for deeper analysis, especially in integrated gateway scenarios.

5. HTTP and ICM Trace (SMICM / SICF)

Purpose: Analyze HTTP-related issues like timeouts, routing, or SSL problems.

Steps:

• SMICM: Set Trace Level to 3 → Reproduce issue → View logs via Trace File option.
• SICF: Go to Edit → Trace → Activate Trace, define service, reproduce issue, and review output.

6. Work Process / Developer Trace (SM50 / ST11)

Purpose: Monitor work process activity and trace runtime failures.

Steps:

• SM50: Choose process → Administration → Trace → Active Components → Set Level (1–3).
• ST11: View logs like dev_w*, dev_disp for troubleshooting.

7. System Monitoring Trace (/SDF/SMON)

Purpose: Continuously monitor ABAP workload to identify resource-heavy users or jobs.

Steps:

• Use /SDF/SMON → Schedule New Monitoring → Define filters (user, program).
• Review captured sessions with /SDF/MON.

8. Enqueue Trace (SM12 / ST05)

Purpose: Investigate lock table overflow, deadlocks, and enqueue-related issues.

Steps:

• ST05: Select Enqueue Trace → Filter by user or process → Activate → Reproduce → Analyze.
• SM12: Go to Server Admin → Diagnosis → System Trace → Activate trace and review lock statistics.

9. HANA SQL Trace (HANA Studio / HANA Cockpit)

Purpose: Analyze expensive SQL queries and database bottlenecks in SAP HANA.

Steps:

• In HANA Studio: Go to Administration → Trace Configuration → SQL Trace → Set filter → Start/Stop trace.
• Use sqlTraceAnalyzer.py script to process and review trace output.

Best Practices for SAP Tracing

• Use filters: Always trace specific users or processes to reduce overhead.
• Deactivate after use: Active traces consume system resources—disable them promptly.
• Combine traces: For deeper issues, correlate multiple traces (e.g., ST05 + ST12 + /IWFND/TRACES).
• Cleanup: Periodically delete obsolete trace files to free up system space.