SAP BASIS Interview Questions (11 - 20)

11. What is transport request?

A transport request is a container used in SAP to manage and move changes between different SAP systems (like development, testing, and production). It ensures that modifications are consistently applied across environments. It contains changes (like programs/config). It is created automatically or manually via SE10.

12. What is the difference between a transport request and a transport task?

A transport request is a container for managing changes, while a transport task is a specific unit of work within a transport request. Transport tasks are created when you add objects to a transport request.

13. How do you check transport logs?

Use Use STMS → Import History or SE10 or SE09 to view transport logs and monitor the status of transport requests. Check return codes (0 = success, 4 = warning, 8 = error).

14. What is return code 8 in transport?

Return code 8 indicates an error occurred during the transport process. It means the transport failed and requires investigation and corrective action.

15. How do you monitor system performance?

System performance is monitored using standard transactions and tools:

  • ST03N → Workload analysis (user activity, response time).
  • ST06 → OS-level performance (CPU, memory, disk).
  • ST04 / DBACOCKPIT → Database performance monitoring.
  • SM50 / SM66 → Work process monitoring (active processes).
  • ST22 / SM21 → Dumps and system logs for issues.

16. What is ST22 used for?

ST22 is used to analyze ABAP dumps (runtime errors). It shows error details like error type, program, line number, and possible cause. For example: If a program crashes, you check ST22 to find the exact issue and fix it.

17. What is SM21?

SM21 is used to view system logs in SAP. It shows important events like errors, warnings, logins, and system issues. For example: If there is a system error or unexpected behavior, check SM21 logs to find the root cause.

18. How do you analyze long running jobs?

Long-running jobs are analyzed using:

  • SM37 → Check job status, duration, and logs.
  • ST22 / SM21 → Look for dumps or system errors.
  • ST05 / ST12 → Trace SQL or performance issues.
  • SM50 / SM66 → See what the job is doing at work process level.

For example: If a job runs too long, check SM37 logs + ST05 trace to find slow queries.

19. What is background job?

Background Job in SAP Basis is a program executed in the background without user interaction. It is mainly used for long-running tasks like data processing, batch jobs, or report execution.

For example: Scheduling a daily report run using SM36 and monitoring it in SM37.

20. What are job statuses in SAP?

Job statuses:

  • Scheduled → Job is defined but not yet released.
  • Released → Job is ready to run.
  • Ready → Waiting for a free background work process.
  • Active → Currently running.
  • Finished → Completed successfully.
  • Cancelled → Stopped due to error or manual cancellation.

For example: You check status in SM37 to see if a job is stuck in Ready or Active.