SAP BASIS Real time (Scenario based) Interview Questions (21 - 30)

21. Urgent fix needed in production—what is your approach?

  • Follow emergency transport process (create hotfix in DEV → transport directly to PROD).
  • Take approvals and ensure proper testing (quick QA or controlled validation).
  • Import transport via STMS and monitor logs carefully.

22. How do you analyze a job running longer than usual?

  • Check SM37 → job logs, duration, and step details.
  • Analyze SM50/SM66 to see what the job is doing (long WP or waiting).
  • Use ST05/ST12 to identify slow SQL or performance issues.

23. Job cancelled with error—what logs to check?

  • Check SM37 → job logs for error messages and cancellation details.
  • Analyze ST22 → dumps if the job crashed or caused a short dump.
  • Review SM21 → system log for any related errors or warnings.

24. Job not triggered at scheduled time — how to check the root cause?

  • First, I check SM37 to see job status (Scheduled/Released/Ready) and start time.
  • Then I verify SM36 start condition (time, event, periodic settings) and ensure job is released.
  • Next, I check SM50/SM66 for available background work processes and SM21 for system issues.
  • Finally, I review SM37 logs for any scheduling errors or conflicts.

25. How do you reschedule failed jobs?

  • First, I check SM37 → job logs to identify failure reason.
  • Then I fix the issue (like dump, lock, or missing data).
  • Finally, I reschedule or release the job again from SM36/SM37.

26. Multiple jobs conflicting — how to manage?

  • Check SM37 to identify overlapping jobs and their schedules.
  • Analyze SM12 for lock conflicts and SM50/SM66 for resource usage.
  • Reschedule jobs or define job dependencies/events to avoid overlap.

27. Spool request not printing—how to troubleshoot?
Printer not responding—what checks will you do?

  • Check SP01 → spool status and error messages.
  • Verify printer configuration in SPAD and ensure printer is active.
  • Check spool work process in SM50 and system logs (SM21) for issues.

28. Spool overflow issue—how to fix?

  • Check SP01 → identify large/old spool requests.
  • Delete unnecessary spools and schedule cleanup job (RSPO1041).
  • Monitor spool space and increase limits if required.

29. RFC connection failing—how to debug?

  • First, I check SM59 and run Connection Test / Authorization Test to see the exact error.
  • Then I verify target host, system number, client, user/password, and whether the remote system is up.
  • I also check SM21, ST22, and gateway logs (SMGW) if the issue is related to network, login, or gateway.

30. IDoc stuck due to RFC issue—what steps?

  • Check IDoc status in WE02/WE05 and identify error (usually status 03/12/30).
  • Verify RFC in SM59 (connection/authorization test) and fix any issues.
  • Reprocess IDoc using BD87 after resolving RFC problem.