APPLIES TO:

DAILY CHECK LIST

SUMMARY
This article explains Daily Check List

AUTHOR:
K.VENKATA RAMU.

COMPANY:
WILLSYS INFOSYSTEMS Pvt. Ltd.,

CREATED ON:
3rd October 2015.
 DAILY CHECK LIST

1. SAP Active Servers (SM51)

Active Servers (SM51)

Execute tcode SM51 at sap command line. It shows the active servers available for the
Central Instance if there.

2. User Overview: SM04

Transaction code SM04 shows the list of the users which are logged on to the instance in
which are currently logged in. The total number of users and sessions are given at the bottom of
the list.
 Client:
SAP Client.
 User:
User logged on to server (SAP user name).
 Terminal:
Terminal at which the user is working. (If it is a UNIX front end, the terminal
name corresponds to the display variable of the front end process; if it is a Windows or
OS/2 front end, the terminal name corresponds to the host name on which the front end
was started.)
 Transaction:
Last executed SAP transaction code.
 Time:
Time at which the user last initiated a dialog step by entering data.
 Sessions:
Number of external sessions (session) opened by the user (up to 6). You can
 display detailed information on a session by selecting a user and choosing the Sessions
button.
 Type:
Connection type (GUI, RFC or Plugin (HTTP or SMTP request).
 Megabyte:
Size of the memory allocated to the user in megabytes.

From the above figure you can see, total 9 users have logged in into different clients like
000, 001
Check the detail of each line.

 Take the example of user SAPUSER, this user has logged into client 000, from system
WILLSYS-PC, executing tcode SM36 time of login, 2 sessions.
 DDIC user has logged into another client no. 001 and also 1 session there.
 Two know more about session, select the user or line and double click on it.

 Now if you want to delete one session, select /click on the specific line and click on “End
Session”.
 Click button to come out from the window.
 Click on button to get most up to date data.
3. Active Users: Al08

AL08 shows the list of all the users who are logged on to the system globally or for all the
instances in the systems which are active. It shows all the active instances and number of active
users in the system. It contains the following columns.

1) Instance - It shows the Instance into which the user logged in

2) Client - It displays the SAP client into which the user is Logged in

3) User Names - SAP user name

4) Terminal - Terminal at which the user is working

5) T-code - Last executed transaction code

6) Time - Time at which the user last initiated a dialog step by entering data

7) External Sessions - Number of External sessions the user has opened

8) Internal Sessions - Number of Internal sessions the user has opened

4. SM21: System Logs
To know /to investigate the problems in SAP system, Basis Admin checks the system
logs to check the possible errors and the cause of the error. Any system related task are recorded
into system logs and can be viewed and analyzed later to trouble shoot the problem.

We check log for the previous day with the following selection/option:

 Enter Date and time.

 Select Radio Button Problems and Warnings
 Press Reread System Log.
5. ST22: ABAP runtime error/ ABAP dumps
When users are working they face some kind of time out problem and any kind of
problem for which their work got terminated. That termination is reported in an area called
ABAP dumps. Using ST22, Basis can analyze the error and cause of the error.
ST22 show the today and yesterday all the time. To get more dumps from previous days,
you can select the date range.
6. SM12: Lock Entries

SAP provides a locking mechanism to prevent other users from changing the record that
you are working on. In some situations, locks are not released. This could happen if the users are
cut off i.e. due to network problem before they are able to release the lock.
These old locks need to be cleared or it could prevent access or changes to the records.
We can use lock statistics to monitor the locks that are set in the system. We record only
those lock entries which are having date time stamp of previous day.

SAP lock entries for current transactions can be seen here. Whenever any DDL/ DML
operations start, SAP put a lock into those transactions in order to keep it safe from overwritten.
Locks are released when ever user exits or user finishes his/her operation/transaction.
If for some more reason, locks cannot be released by SAP, it is displayed here with the
date it was locked.
Note: The locks which are more than 24 hours old should be deleting from the system to allow
other users to work efficiently.
7. SM13: Update Management

With update management (transaction SM13) you can perform the following tasks:
 Display update requests
 Analyze problems relating to the update
 Test and clean up canceled update requests
 Display and reset the status of update requests
 Delete update requests
 Display statistics on the update
The update management initial screen (Transaction SM13) looks like:
8. SM14: UPDATE ADMINISTRATOR

SM14 is used to administrate the update system.

It lets you configure the update servers and update groups, and display and modify update
parameters.

9. ST06: Operating System Monitor

In operating system monitor we check what is CPU utilization and who is using that much
resources as shown in fig below
Check Top CPU Utilization:

Now Click on Detail Analysis Menu click Top CPU

10. DB02: Monitor the growth of the database
Analyze tables and indexes
1. Current sizes % used space ,should not more than 90 %
2. Free space statistics check free space –Maximum/kb and Max next extent /kb, critical
objects.
3. Space critical objects
4. Missing indexes
11. ST02: Tune Summary

SAP transaction ST02 can be used to view SAP Buffer and memory configuration for a
SAP instance and review SAP memory quotas for individual user job or process as well as
current SAP Buffer status, SAP memory utilization at SAP instance or user/transaction level.

 Display statistics relating to SAP buffer performance,

 Help with the fine-tuning of buffer parameters,
 SAP database parameters,
 Operating system parameters.
In above pic we check how much swap is occurring and what is the hitratio?
Hit ratio should be >90 % all the time
There should not be much swap during System running.
In the below pic we see how much memory is used in same tcode ST02

 Max. Use (in KB) should be less than In memory (in KB).
 The lower part of the Setups / Tune Buffers monitor displays data on:
 Extended memory size and usage
 Usage and configuration of the roll mechanism
 Bottlenecks may be indicated if:
 For extended memory: Max use. = In memory
  For roll area: Max use. > In memory
 For a detailed analysis of R/3 memory management, see unit R/3 Memory
Management.

12. DB12 - Backup Logs Overview

This transaction is useful to check the details of

 last successful backup

 overview of database backups ( Success / failure of backup with log details)
 Archiving directory status (Free space of oraarch )
 Overview of redolog files ( Number of redologs that are not yet backed up)
 overview of redolog backups (Success / failure of backup with log details)
13. DB13: DBA planning calendar

This transaction will be useful to schedule various database backups & clean up jobs like
( whole database backup offline/online, Full backup online/offline, incremental backup
offline/online, redolog backup, update statistics, check db, cleanup logs, compress database,
verify database, initialize tape and validate structure jobs).

In this transaction, you can also check the status of every job that was scheduled and can
reschedule in case of failures.

14. DB14:

SAP provides an excellent DBA tools (for Oracle DB) which is called
BRTOOLS. BRTOOLS is a compilation tools range from BRBACKUP (tools to maintain
backup database), BRARCHIVE (tools to maintain archive files backup), BRCONNECT (tools
to maintain checking database, updating database statistics, etc), BRRESTORE (tools to
maintain database restoration), and some specific and useful tool.

When SAP Basis running one or more tools from BRTOOLS, it will create a job log to provide
SAP Basis some information about BRTOOLS activities whether it succeed, succeed with
warning, or failed. We can access those logs from SAP R/3 through SAPGUI.

SAP provides DB14 tcode for SAP Basis to access those database logs.
14. SM51

Transaction code SM51 is to display list of active application servers that

have registered in the SAP message server. Further, you can manage & display
the status, users, and work process in all application servers belonging to the SAP System.
• Processes: Display & control work process. [SM50]
• User: Display & manage user sessions. [SM04]
• SNC Status: Display SNC status.
• Release Notes: Display detailed release information for an application server.
• Remote Logon: Log on by any server in the system; you can see the server where you are
logged on in the status bar in the second entry from the left.
• System Log: System logs. [SM21]

15. SM50: Monitoring Work Processes for Individual Instances

Displays all running, waiting, stopped and PRIV processes related to a particular
instance. Under this step we check all the processes; the process status should always be waiting
or running. If any process is having status other than waiting or running we need to check that
particular process and report accordingly.

This transaction displays lot of information like:

1. Status of Work process (whether its occupied or not)

2. If the work process is running, you may be able to see the action taken by it in Action
column.
3. You can which table is being worked upon

Some of typical problems:

 User take long time to log on/not able to logon/online transaction very slow. This could
be the result of the DIA work processes are fully utilized. There could be also the result of
long running jobs (red indicator under the Time column). If necessary you can cancel the
session by selecting the jobs then go to Process>Cancel Without core. This will cancel the job
and release the work process for other user/process
 Some users may have PRIV status under Reason column. This could be that the user
transaction is so big that it requires more memory. When this happen the DIA work process
will be 'owned' by the user and will not let other users to use. If this happens, check with the
user and if possible run the job as a background job.
 If there is a long print job on SPO work process, investigate the problem. It could be a
problem related to the print server or printer.
16. SM66: Monitoring System wide Work Processes

This transaction code will be useful to view the processes that are running across all
instances/application servers of a SAP system. Similar to SM50 checks can be done in this
transaction as well.

By checking the work process load using the global work process overview, we can quickly
investigate the potential cause of a system performance problem.

Monitor the work process load on all active instances across the system

Using the Global Work Process Overview screen, we can see at a glance:

 The status of each application server

 The reason why it is not running
 Whether it has been restarted
 The CPU and request run time
 The user who has logged on and the client that they logged on to
 The report that is running
17. SM20: Monitoring the audit log

Viewing the Audit Analysis Report:-

 Log on to any client in the appropriate SAP system.

 Go to transaction SM20.
 In the Selection, Audit classes, and Events to select sections of the Security Audit Log:
Local Analysis screen, provide your information to filter the audit information. If you
need to trace the activities of a specific user, be sure to include that user’s ID. Click the
Re-read audit log button.
 The resulting list is displayed. This list can be printed using the usual methods.
18. SM35: BATCH INPUT LOG

Batch input is one of the primary ways in which data can be transferred into the R/3
System. Batch input is used for bulk data transfers and not for near real-time data transfers.
Typical uses of batch input include the one-time import of data from a legacy system into a
newly installed R/3 System. Another typical use is for periodic (hourly, daily...) transfers of data
from external systems or legacy systems that are still in use into R/3, where all enterprise data is
consolidated.
For the system administrator, batch input usually requires minimal attention, only a
periodic check to make sure all batch input sessions have been processed successfully. In the
event of an error in a session, then the responsibility for triggering the error analysis and
correction of the problem usually lies with the system administrator. Detailed analysis of the
problem will require the help of the department or specialist responsible for the data to be
entered. Incorrect entries in an R/3 financial transaction in a session, for example, have to be
evaluated and corrected by the book-keeping department.
The process description here explains the typical workflow in batch-input operation from
the point of view of the system administrator.
19. SM37: Monitor the background

This transaction will be useful to have an overview of jobs with different statuses.
As part of daily monitoring, SAP basis administrator should use this transaction to find out0
canceled jobs and active jobs (for eg: long running - more than 24hrs etc).

In case of canceled jobs, root cause for the failure to be figured out from the logs of the
respective job and to be auctioned by rescheduling etc.
In case of long running jobs, we need to figure out the reason for long running and action them
accordingly.

In SM37, using extended job selection option, we can even select the jobs based on start
condition, steps (like abap program, external command or external program), period etc
.

Press
Note

• Scheduled - Job already been defined, but the start condition has not yet been defined.
• Released - The job has been fully defined, including a start condition.
• Ready - The start condition of a released job has been met. A job scheduler has put the job in
line to wait for an available background work process.
• Active - The job is currently running. Active jobs can no longer be modified or deleted.
• Finished - All steps that make up this job have completed successfully.
• Canceled - The job has terminated.
20. SP01

SP01 is useful to find out the status of spool request and output request. In SP01 transaction,
you can list the spool requests or output requests between a given intervals.

In the list generated, you can check out the status of spool requests and find out any errors by
drilling down further.

For eg: if so many spools are in waiting status, find out whether output device is available or not.

If many spool are in error status, figure out if there is any network issue and take necessary actions.
.

Press icon
21. WE05:
View the IDocs and their statuses
IDOC stands for “Intermediate Document"
IDOC is simply a data container used to exchange information between any two
processes that can understand the syntax and semantics of the data.
In other words, an IDOC is like a data file with a specified format which is exchanged
between 2 systems which know how to interpret that data.
In the SAP System, IDOCs are stored in database. Every IDOC has a unique
number (within a client)
22. ST03N:

The ST03 Workload Monitor is the central access point for analyzing performance problems
in the SAP system. ST03N is a revised version of transaction ST03. In current SAP Releases
transaction ST03N replaces transaction ST03 and is automatically started when you enter
transaction code ST03.
Here you can compare the performance values for all instances, and compare the
performance of particular instances over a period of time. Due to the number of possible analysis
views for the data determined in transaction ST03, you can quickly determine the cause of
performance problems.
You can use the workload monitor to display the following, among other things:

 Number of instances configured for your system

 Number of users working on the different instances
 Response time distribution
 Distribution of workload by transaction steps, transactions, packages, subapplications,
and applications
 Transactions with the largest response times and database time
 Memory usage for each transaction or each user per dialog step
 Workload caused by RFC, broken down by transactions, function modules, and
destinations
 Number and volume of spool requests
 Statistics about response time distribution, with or without the GUI time
 Optional: table accesses
 Workload and transactions used by users, broken down by users, accounting numbers,
and clients
 Workload generated by requests from external systems
23. ST04 - DB Performance Analysis

Transaction code ST04 is used to shows detail of the database behave & usage, both history
and current time.
 Data buffer cache size & quality must be above 94% [meaningless physical
read from disk]
 User/Recursive Call > 2 [Recursive call will get more over time]
 Read/User Call < 30 [> 30 means expensive SQL statements]
 Time/User Call < 15ms
 Busy time & CPU time ratio 60:40 ratio. Higher ratio means tuning required
 Sort sections. It should be less than 0.1% of total sorts.
 Shared pool statistics. DD (data dictionary) cache quality should be more than 99%,
similarly the SQL area get ratio.
 Instance performance. Soft parse ratio max value is 1 which is not possible because at
least once the SQL is hard parsed and then soft parsed in its next executions. But this
must be as close as possible to 1 for a healthy system. Similarly there is another fact
which is in-memory sort ratio; this is for a healthy system should have higher values. In
fact the less the disk sorts the better.
24. SMQ1:
qRFC Monitor for the outbound queue you use this transaction to monitor the status of
the LUWs in the outbound queue and restart any hanging queues manually.
25. SMQ2:
qRFC Monitor for the inbound queue. You use this transaction to monitor the status of
the LUWs in the outbound queue.
26. SM58:
Transaction code SM58 is used to check the transactional rfc job logs for whichever
chain that are running in the system. The transaction code needs to be run in the source system
from where it is bringing the data for your target system. If the transactional fails, the data
transfer will be incomplete.
27. RZ04:

Transaction code RZ04 is used to maintain operation modes and instances. The operation
mode is divided into two modes, Night and Normal. Night modes will be during out of office
hours (23.00 pm – 06.00 am) and Normal mode will be during office hours (06.00 am – 23.00
pm). You can manually set the time frame of operation modes via transaction code SM63.

Operation Mode not configured

Related Content:

www.help.sap.com
www.sdn.sap.com/irj/sdn/index.

Disclaimer and Liability Notice:

WILLSYS will not be held liable for any damages caused by using or misusing the information,
code or methods suggested in this document, and anyone using these methods does so at his/her
own risk. WILLSYS offers no guarantees and assumes no responsibility or liability of any type
with respect to the content of this technical article or code sample, including any liability
resulting from incompatibility between the content within this document and the materials and
services offered by WILLSYS. You agree that you will not hold, or see