SAP BASIS Real time (Scenario based) Interview Questions (31 - 40)

31. After system refresh, users cannot login—why?
What are the steps to troubleshoot a user login issue?

  • Users may be locked or passwords reset during refresh (check SU01).
  • Profile parameters / login settings might have changed (check RZ10).
  • License issue or RFC/SNC config mismatch can also block login.

32. Logical system errors after refresh—how to fix?

  • Update logical system name using BDLS to convert old system to new one.
  • Check and correct settings in SALE / WE20 / WE21 (IDoc, partner profiles).
  • Verify RFC destinations in SM59 and adjust target systems.

33. Client copy failed—how do you troubleshoot?

  • Check logs in SCC3 to identify error (tables, locks, or space issues).
  • Verify ST22/SM21 for dumps and system errors during copy.
  • Check DB space, locks (SM12), and background jobs (SM37).

34. Post-refresh activities checklist—what do you perform?

  • Run BDLS → update logical system names.
  • Check RFC (SM59), ALE/IDoc settings (SALE/WE20) and fix connections.
  • Unlock users, reset passwords (SU01), and update licenses (SLICENSE).
  • Clean up jobs, spool, and schedule background jobs (SM37/SP01).
  • Verify transports, system settings, and test key business transactions.

35. Table access is slow—how do you analyze?

  • Use ST05 (SQL Trace) to identify slow queries on the table.
  • Check DBACOCKPIT / ST04 for expensive SQL, missing indexes, or DB load.
  • Verify table buffering (SE11) and check table size/indexes (DB02).

36. Expensive SQL statements—how to find and fix?

ST05 for detailed trace, SQLM/SQLMD for top expensive statements, HANA Expensive Statements Trace for DB-level costly SQL, then optimize and retest.

37. Buffer issues in SAP—how to identify?

  • Check ST02 → look for high swaps, low hit ratio, or buffer overflow.
  • Verify ST06 → OS memory pressure impacting buffers.
  • Check ST22 → dumps related to buffer/memory issues.

38. How do you tune SAP system for better performance?

  • Monitor performance using ST03N, ST06, ST02 to identify bottlenecks (CPU, memory, buffers).
  • Optimize DB using ST05/DBACOCKPIT (indexes, expensive SQL).
  • Tune parameters (RZ10), clean up jobs/spool, and balance workload.

39. How do you analyze a short dump step by step?

  • Go to ST22 and check the dump type, program name, date/time, and user.
  • Read the error details and “What happened / What can you do” section to understand the root cause.
  • Cross-check SM21 for related system errors and, if needed, involve ABAP team / DB team based on whether it is code, memory, or database issue.

40. System log showing repeated errors—how to act?

  • Check SM21 → identify error pattern, time, and affected component.
  • Correlate with ST22/SM50/ST06 to find root cause (dump, WP, resource issue).
  • Fix underlying issue (code, memory, DB, or config) and monitor again.