SAP BASIS Real time (Scenario based) Interview Questions (41 - 50)

41. How do you correlate dump with user activity?

  • Check ST22 → note user, time, transaction, and program causing dump.
  • Cross-check SM21 → system log at same timestamp for related errors.
  • Use ST03N or SM20 (audit log) to see what user action triggered it.

42. How to monitor system health proactively?

  • Use ST03N, ST06, ST02 to monitor workload, CPU, and memory regularly.
  • Check SM21, ST22, SM37 for logs, dumps, and job issues.
  • Set up alerts in Solution Manager / CCMS (RZ20) for early warnings.

43. Unauthorized access detected—what actions?

  • Immediately lock the user in SU01 and reset password.
  • Check logs in SM20 (Security Audit Log) and SM21 to identify source and activity.
  • Analyze roles in PFCG and remove unnecessary authorizations.

44. Audit log shows suspicious activity—how to handle?

  • Check details in SM20 → user, time, IP, and actions performed.
  • Immediately lock user (SU01) and reset password if required.
  • Analyze roles in PFCG and inform security/audit team.

45. How do you enforce password/security policies?

  • Maintain password rules in RZ10 (parameters like length, complexity, expiry).
  • Enable and monitor logs using SM20 (Security Audit Log).
  • Control access via proper roles in PFCG and regular user audits.

46. Kernel upgrade failed—how to recover?

  • Check dev_disp / dev_w logs (AL11)* to identify the error.
  • Roll back to previous kernel backup and restart SAP.
  • Fix issue (missing files, permission, incompatibility) and retry upgrade.

47. After patching, system behaving abnormally—what steps?

  • Check SM21 / ST22 → identify errors or dumps after patch.
  • Verify recent changes (patch logs, transports) and isolate the issue.
  • If needed, rollback patch or apply SAP Note fix.

48. System stops accepting new logins during peak hours—what could be the reason and how do you fix it?

Usually this happens when all dialog work processes are busy or parameters like rdisp/wp_no_dia are exhausted. I check SM50/SM66 to see process status and also look at RZ11/RZ10 parameters. If needed, I free stuck processes or increase work processes after analysis.

49. One application server is slow but others are fine—how do you isolate and resolve the issue?

I compare workload using ST03N and check server-specific load in SM51 → select server → SM50. Then I analyze OS resources using ST06 to see CPU/memory issues. If required, I restart that instance or balance load using logon groups (SMLG).

50. Users report data inconsistency after transport—how do you troubleshoot this?

First, I check transport logs in STMS to ensure objects moved successfully. Then I verify if dependent transports were missed or sequence was wrong. If needed, I re-import transports or coordinate with functional team.