CHECK LIST PROVIDED: 1. ST07: Application server monitoring a. Number of work process, b. Number of Users configured c.

We can confirm it is optimally configured or not. 2. ST06: Operating system level monitoring a. CPU utilization, b. Memory, Swap, c. File system Monitoring. 3. ST04: Database hit ratio (should be more than 94%). 4. ST03: Workload analysis a. Response time, b. User profile, work load, c. Top 10 programs/users/transactions. 5. ST02: R/3 Buffer hit ratio (>98%), swaps free directories and free spaces 6. DB02: Database size, critical objects and missing indexes. 7. DB12: last successful backup and redo log backup. 8. DB14: Database statics (check whether they ran successfully) 9. SM50: work process overview per instance 10.SM51: Number of active instances (server monitoring). 11.SM66: Global work process overview for all instances. 12.SM04: logged in users locally (the total number of users and sessions are given at the bottom of the list) 13.AL08: logged in users globally 14.SM35: Batch inputs (Incorrect, IN-processing, IN-background) 15.SM36: used to define background jobs(You can define the background job in two ways the job overview and job scheduling wizard) 16.SM37: Background job monitoring (check for active and called jobs). 17. SM20: System audit logs 18.SM21: System logs (the SAP system logs all the system erros, warnings, user locks due to failed logon attempts from known users and process messages in the system logs there are two

different types of logs created by the system 1. Local logs and 2. Central logs ) 19.SM12: System locks (The sap system consist of lock mechanism the purpose of the local mechanism is to prevent two transactions from changing the data on the data base simultaneously. Locks are defined generally as lock objects in the data dictionary lock entries are usually set and deleted automatically when the user programs access a data object and release it again. The SAP lock mechanism is closely related to update mechanism) 20. SM13: Monitoring the update records (In the SAP system a business process is mapped my means of an SAP transaction, which can include several screen changes. The changes to the data caused by this business process should be written to the database in full or not at all. If the operation is cancelled while the transaction is being executed or if an error occurs, the truncation should not make any changes to the database. These activities are handled by the SAP update system, which is described below. The update system also enhances the reliability and performance and makes easier to restore the data when the changes are made to database). 21. SM14: Check that update is activated or deactivated (Ensure that it is activated) (its lets u configure the update servers and update groups and display and modify update parameters). 22.AL11: SAP directories. 23. ST11: Error log files/developer traces 24. SP01: Monitoring the spool requests 25. SCOT: Check that the SMTP is enabling or not 26. WE05: IDOC Monitoring 27. RZ04: Check whether operation modes or configured or not 28. SM58: Transactional RFC. 29. SMQ1: Outbound Queues 30. SMQ2: Inbound Queues 31. ST22: ABAP dumps 32. SMGW: Gateway Monitoring

33.