SAP BASIS Real time (Scenario based) Interview Questions (1 - 10)

What is SAP BASIS?

SAP BASIS is the technical foundation of SAP systems that manages system operations, configuration, and performance. It handles tasks like user administration, system monitoring, database management, and troubleshooting to keep SAP applications running smoothly. In simple terms, SAP BASIS acts like the “engine room” that ensures all SAP modules (like MM, SD, PP) work properly without issues.

Why real-time/scenario questions are important in interviews?

Real-time or scenario-based questions are important because they test how well you can handle actual problems in a live system, not just theory. In areas like SAP BASIS, companies want to see your troubleshooting skills, decision-making, and practical experience in situations like system slowdowns or job failures. They help interviewers understand whether you can work confidently in real production environments.

What the reader will learn?

In this guide, you’ll learn real-time SAP BASIS interview questions along with clear, beginner-friendly answers that are commonly asked in interviews. You’ll also see actual production issues and how they are handled step-by-step, including important TCodes and troubleshooting approaches. By the end, you’ll be confident in handling both interview questions and real-world SAP BASIS scenarios.

1. System is very slow—how do you identify the root cause?

When system is very slow, we usually check step by step like below:

  • Check ST03N to see response time and which users/programs are heavy.
  • Then go to ST06 to check CPU, memory, or OS bottlenecks.
  • Next check SM50/SM66 to see if any work process is stuck or running long.
  • Verify ST22/SM21 for dumps or system errors.
  • Finally, use ST05/ST12 to identify slow SQL queries.

2. What steps will you take if users complain SAP is hanging?

  • First I check SM50/SM66 to see if any work process is stuck or in long-running status.
  • Then I check ST06 for CPU/memory issues and ST03N for workload spikes.
  • I verify SM12 for lock issues and SM21/ST22 for errors or dumps.
  • If needed, I trace using ST05/ST12 or restart affected work process.

3. Work processes are full—how do you analyze and fix it?

  • First, I check SM50/SM66 to identify long-running or stuck processes (CPU/PRIV/WAIT status).
  • Then I verify SM12 (locks) and SM37 (background jobs) to see if anything is blocking.
  • I analyze SQL using ST05/ST12 if DB queries are slow.
  • If needed, I cancel the problematic job/process or increase work processes temporarily.

4. System is down—what logs do you check first?

  • SM21 → System log (first check for errors).
  • ST22 → Dumps to see if crash happened due to ABAP error.
  • Dev traces (dev_disp, dev_w)* → Work process level issues.
  • DB logs / DBACOCKPIT → Database availability issues.
  • OS logs (ST06 / OS level) → CPU, memory, or disk problems.

5. Short dumps are increasing—how do you handle it?

  • First, I check ST22 to identify dump type, program, and root cause.
  • Then I correlate with SM21 (system log) and recent transports/changes.
  • If it’s code issue → inform ABAP team; if it’s memory/DB → check ST02/ST06/DBACOCKPIT.
  • Apply fix (code correction, SAP Note via SNOTE, or parameter tuning).

6. Background jobs are failing randomly—how do you troubleshoot?

  • First, I check SM37 → job logs, spool, and error messages.
  • Then I verify ST22 (dumps) and SM21 (system log) for failures.
  • I check SM12 (locks) and DBACOCKPIT/ST05 for DB or performance issues.
  • Also review recent transports or changes affecting the job.
  • Finally, I apply fixes (code, parameters) or reschedule the job as needed.

7. Update requests are stuck—what will you do?

  • First, I check SM13 to see status and error messages of update records.
  • Then I verify SM50 to ensure update work processes are running and not stuck.
  • I check SM12 for locks and ST22/SM21 for dumps or system issues.
  • If needed, I fix root cause and reprocess updates from SM13.

8. Database is growing rapidly—how do you control it?

  • First, I check DBACOCKPIT to identify which tables/logs are consuming space.
  • Then I clean up old data using archiving (SARA), delete old logs, and manage spool (SP01).
  • I also review table growth (DB02) and remove unnecessary data/indexes.
  • Finally, I ensure regular housekeeping jobs are scheduled.

9. CPU usage is high on app server—how do you analyze?

  • First, I check ST06 to confirm CPU spike at OS level.
  • Then I go to SM50/SM66 to find which work processes/users are consuming high CPU.
  • I verify workload in ST03N and trace heavy queries using ST05/ST12.
  • If needed, I stop long-running jobs or optimize queries.

10. Memory bottleneck in SAP—what transactions and steps?

  • Analyze → Check ST02 (buffer swaps) and ST06 (OS memory usage).
  • Identify → Use SM50/SM66 to find high memory/PRIV processes and check ST22 dumps.
  • Fix → Tune memory parameters or restart affected processes/instance.