1. How do you verify SAP system health after a restart?
Ans:
Check application-server availability, work processes, database connectivity, system logs, background jobs, interfaces, and relevant monitoring alerts. Confirm that critical SAP services are functioning before considering the system operational.
2. What is the purpose of transaction SM21?
Ans:
SM21 is used to review the SAP system log. BASIS administrators can examine system events, warnings, errors, timestamps, and application-server information while investigating technical problems.
3. How would you troubleshoot an SAP application server that is unavailable?
Ans:
Check the instance status, operating-system processes, dispatcher and work processes, message-server communication, database connectivity, system logs, and recent changes. The available evidence helps determine the appropriate troubleshooting path.
4. What is SAP work-process configuration?
Ans:
Work-process configuration determines the number and types of processes available for activities such as dialog, background, update, spool, and enqueue processing. Configuration should match workload requirements and be changed through approved procedures.
5. How do you analyse a high CPU utilisation issue in SAP?
Ans:
Review operating-system CPU usage, SAP workload, active work processes, long-running transactions, background jobs, and database activity. Correlating these indicators can help identify the component contributing to the resource consumption.
6. What is transaction SM66 used for?
Ans:
SM66 provides a global overview of work processes across SAP application servers. It can help administrators identify long-running processes, workload patterns, and processing conditions across the SAP landscape.
7. How can you check SAP application-server configuration?
Ans:
Review relevant instance and profile parameters, server status, work-process configuration, and operating-system information. Configuration checks should be performed according to the SAP version and organisational administration standards.
8. What is SAP system monitoring?
Ans:
SAP system monitoring involves observing application servers, databases, work processes, jobs, interfaces, system resources, logs, and alerts. Regular monitoring helps technical teams identify abnormal conditions and respond to incidents.
9. How do you investigate repeated SAP job failures?
Ans:
Review job logs, execution history, programs, variants, user authorisations, dependencies, system logs, and related dumps. Comparing multiple failed executions can help identify recurring technical or application-related conditions.
10. What information should be recorded after resolving a BASIS incident?
Ans:
Document the incident symptoms, affected system, investigation steps, evidence collected, root cause, corrective action, validation results, and any preventive measures. Proper records support future troubleshooting and operational knowledge sharing.