How I analyse SAP issues fast
How I analyse SAP issues fast And why these 11 t-codes made me a better consultant. Most functional consultants rely only on business knowledge. But the ones who grow into architects? They know how to read the system before calling ABAP or Basis. Here are the 11 t-codes I use to do my first-level analysis on any project. ⸻ 1) ST22 — Dump Analysis Find why the program crashed. Saves hours of back-and-forth. 2) SM21 — System Log Great for spotting RFC failures, update errors, system events. 3) SM13 — Update Records If a user says “I saved, but nothing happened,” check here. 4) SM12 — Lock Entries Your first stop when an order or material refuses to open. 5) SM37 — Background Jobs For job delays, failures, or anything stuck in the night run. 6) SE93 — T-Code Lookup See the program behind a transaction. Helps identify custom vs. standard. 7) SE16N — Table Browser Validate master data, config, statuses—quick and clean. 8) ST05 — SQL Trace Not just technical. Lets you see which tables ...