Daily System Monitoring T-Codes

SAP systems must be monitored daily in order to check if there is a problem in

the system and correct in advance or at the time the system has a trouble.
In that cases, if connection to SAP is available, some critical points on SAP level,
database level and OS level especially should be checked via the transaction
codes.
SAP LEVEL

SM50 : Process Overview

All of the running, working, stopped and PRIV mode workprocesses can be
displayed using the t-code sm50.
Running mode means that work process is busy processing user request.
Waiting mode means that work process is ready to accept user request.
PRIV mode means that the used transaction is so large so that work process is
running with heap memory. In this case, the work process should be analyzed in
detail and cancel if required.
Status must be in Running and Waiting mode in order to have a properly worked
SAP system.
If there are no idle work processes ( i.e. all work processes are running ) then
the oncoming request have to be wait for a workprocess to be free, so the
waiting times get increased and caused the system to work slower.
If there is any PRIV mode work process, means that this workprocess is owned
by the user and will not get free.
In such cases, work processes can be required to be stopped explicitly by the
sap admin.

How to cancel a workprocess?

To cancel a work process, choose the process you want to cancel and go
with Process -> Cancel with core or Cancel without core.
The option Cancel with core cancels the workprocess with the processes
related to this process. So, prefer to cancel without core option if possible.

Click on Yes to proceed the termination process.

SM51 : SAP Server Overview

The transaction code sm51 lists all of the active servers. For a proper work in an
SAP system, all application servers belonging to the SAP,message server should
be in Active status.
Also, here you can see all the workprocesses ( i.e. SM50 screen ) belonging to
an instance by double-clicking to a particular instance.

SM66 : Global Workprocess Overview

All running workprocesses on all active instances across the system can be
monitored using the transaction code sm66.

Helpful Tip

The difference between the t-codes sm50 and sm66 is that the workprocesses
of a particular server can be monitored using sm50 while the workprocesses of
all active instances can be seen using sm66.

ST22 : ABAP Dump Analysis

ABAP dump analysis is used to display ABAP dumps and runtime errors.

It is possible here to see the dumps and runtime errors happened

specifically Today or Yesterday using the buttons as shown in the above figure.
Also you can have a detailed review with a double-click on an error.

SM21 : System Log Analysis

Every important process done in an SAP sytem is kept and updated in system
logs. System logs can be monitored as executing the t-code sm21. Click on
Reread system log pushbutton to see the logs. System log analysis plays an
important role to investigate the errors in the system in case of a trouble.

Logs can be seen in the following figure. To see the details double-click on a
particular log entry. In case of a trouble, the logs must be investigated via sm21
to find and resolve the problem.

SM12 : Lock Concept

In an SAP system, there is a lock mechanism such that if any user is working on
a table it is not allowed to work on the same record by another user to keep the
data consistency. Executing the t-code sm12, lock entries in a system is
monitored and can be deleted if required. Usually, the lock entries hold by a
user or process for more than 2 days should be analysed and deleted.
To see the lock entries in a system, execute sm12 and click on List after you
fill in the required blanks as shown in the following figure.

Lock entries are listed as shown below.

To delete a lock entry, select a particular lock or push on the button Select All in
order to delete all lock entries and then useDelete button. After deleting the lock
entry, user session which locks the deleted entry should be ended using the tcode sm04 as explained at the SM04 : User List part of this post.

SM13 : Update Requests Overview

T-code sm13 is used to display update requests. To monitor the update requests
in a system execute the t-code sm13 and click on Execute button after selecting
client, user, time interval, status etc. as shown below.

The update records are listed. Records can be deleted here as selecting the
wanted entry and then using the Delete button but before deleting an update
request, required analysis have to be done.

SM04 : User List

T-code sm04 lists all of the active users working on the particular instance in
which you are logged in.

DATABASE LEVEL

DB02 : Database Administration

Transaction db02 is to monitor all database statistics in an SAP system. Details

of db performance, space ( e.g. tablespaces, containers, indexes ), Backup,
Configuration, Alerts etc. can all be displayed via the database administration
screen as shown in the below figure. Here you can see used and free sizes of
tablespaces or monthly/weekly/daily changes of spaces in detail. In case of that
a tablespace is used more than 95% growth of tablespaces should be anaylsed
here in order to decide size of the data file which must be added to resolve the
problem.
Note that db02 screen might have a different image than the image shown
below depending on OS-DB type of the system but the same analysis can be
performed at all combinations.

DB12 : Backup Logs Overview

Backup history is shown using this transaction. All database backups can be
seen with the details such as Backup Timestamp, Runtime, Status, Backup Type
etc. via the db12 transaction screen. Backups always should be checked in
order to be sure that last backup comleted successfully. It is also possible to see
this screen using the t-code db02 explained above and choosing Backup and
Recovery tab from the left side bar.

ST04 : DB Performance Analysis

ST04 is a transaction for SAP performance tuning. In the st04 screen, you can
find lots of statistics and do lots of analysis. One of the most critical points here
is Buffer Pool statistics. For a properly worked SAP system, Overall Buffer
Quality must be higher than 95%.

System Administration Assistant [1]

In order to make the system monitoring work easier and for a full checklist
including transactions seperated as daily/weekly/montly, System Administration
Assistant for SAP Basis which is an extremely useful transaction can be used. To
start system administration assistant, run the t-code : ssaa and get the screen
shown below.
As expanding Basis >> SID : Checklist for Operating the Production System >>
SID:Daily Tasks, transaction codes for a daily monitoring can be seen. It is also
possible to view each screen as using the Execute buttons which are standing at
the left side of each check entry. After checking the related transaction, it can be
marked both as green meaning OK or leaved as red meaning that there is a
problem.