SAP System monitoring guide

SAP BASIS
SYSTEM MONITORING GUIDE
For Freshers

Mastering SAP Basis in a week

Author : Suresh Krishnaiah

Email : [email protected]

Internal Use 1
 SAP System monitoring guide

CONTENTS PAGE
CONTENTS PAGE ................................................................................................................................................................... 2
SECTION 1 ................................................................................................................................................................................ 5
1.0 OVERVIEW ............................................................................................................................................................... 6
SECTION 2 ................................................................................................................................................................................ 7
2.0 DAILY CHECKLISTS ............................................................................................................................................... 8
2.0.1 CRITICAL SYSTEM TASKS ................................................................................................................................. 8
SECTION 3 ................................................................................................................................................................................ 9
3.0 VERIFY THAT SAP IS RUNNING ......................................................................................................................... 10
3.0.1 WHAT? .............................................................................................................................................................. 10
3.0.2 WHY? ................................................................................................................................................................. 10
3.0.3 HOW? ................................................................................................................................................................ 10
3.1 VERIFY THAT BACKUPS RUN SUCCESSFULLY.............................................................................................. 11
3.1.1 WHAT? .............................................................................................................................................................. 11
3.1.2 WHY? ................................................................................................................................................................. 11
3.1.3 WHEN? .............................................................................................................................................................. 11
SECTION 4 .............................................................................................................................................................................. 12
4.0 R/3 TASKS - CHECK ALL APPLICATION SERVERS ARE UP (SM51).............................................................. 13
4.0.1 WHAT? .............................................................................................................................................................. 13
4.0.2 WHY? ................................................................................................................................................................. 13
4.0.3 HOW? ................................................................................................................................................................ 13
4.0.4 SCREEN SHOT 1 – SAP SERVERS (OVERVIEW)............................................................................................ 14
4.1 WORK PROCESSES MONITOR (SM50) ............................................................................................................... 14
4.1.1 WHAT? .............................................................................................................................................................. 14
4.1.2 WHY? ................................................................................................................................................................. 14
4.1.3 HOW? ................................................................................................................................................................ 14
4.1.4 SYSTEMS WITH APPLICATION SERVERS. .................................................................................................... 14
4.1.5 SCREEN SHOT 2 – SAP SERVERS ................................................................................................................... 15
4.1.6 SYSTEMS WITHOUT APPLICATION SERVERS. ............................................................................................ 15
4.1.7 WHAT TO LOOK FOR! ..................................................................................................................................... 15
4.1.8 SCREEN SHOT 3 – PROCESS OVERVIEW ..................................................................................................... 15
4.1.9 COLUMN DEFINITIONS: - .............................................................................................................................. 16
4.2 LOAD BALANCING (SMLG) ................................................................................................................................. 16
4.2.1 WHAT? .............................................................................................................................................................. 16
4.2.2 WHY? ................................................................................................................................................................. 16
4.2.3 HOW? ................................................................................................................................................................ 17
4.3 GLOBAL WORK PROCESS OVERVIEW (SM66) ................................................................................................. 17
4.3.1 WHAT? .............................................................................................................................................................. 18
4.3.2 WHY? ................................................................................................................................................................. 18
4.3.3 HOW? ................................................................................................................................................................ 18
4.3.4 SCREEN SHOT 5 – GLOBAL WORK PROCESS OVERVIEW ......................................................................... 18
4.4 MAINTAIN PRODUCTION OPERATION MODE (RZ04) ................................................................18

Internal Use 2
 SAP System monitoring guide

4.5 FAILED UPDATES (SM13) .................................................................................................................................... 19

4.5.1 WHAT? .............................................................................................................................................................. 19
4.5.2 WHY? ................................................................................................................................................................. 19
4.5.2.1 ANALOGUE ...................................................................................................................................................... 19
4.5.3 HOW? ................................................................................................................................................................ 20
4.5.4 SCREEN SHOT 7 – UPDATE RECORDS ......................................................................................................... 21
4.5.4 MANAGING UPDATE TERMINATIONS .......................................................................................................... 22
4.5.5 HOW? ................................................................................................................................................................ 22
4.5.6 SCREEN SHOT 8 – UPDATE MODULES ........................................................................................................ 22
4.5.7 SCREEN SHOT 9 – UPDATE STATUS ............................................................................................................. 23
4.6 SYSTEM LOG (SM21)............................................................................................................................................. 24
4.6.1 WHAT? .............................................................................................................................................................. 24
4.6.2 WHY? ................................................................................................................................................................. 24
4.6.3 HOW? ................................................................................................................................................................ 24
4.6.4 UNUSUAL ENTRIES ......................................................................................................................................... 25
4.6.5 SCREEN SHOT 10 – SYSTEM LOG: ANALYSIS FOR ALL REMOTE INSTANCES ........................................ 25
4.7 BACKGROUND JOBS (SM37) ............................................................................................................................... 26
4.7.1 WHAT? .............................................................................................................................................................. 26
4.7.2 WHEN? .............................................................................................................................................................. 26
4.7.3 HOW? ................................................................................................................................................................ 26
4.7.4 SCREEN SHOT 11 - SIMPLE JOB SELECTION .............................................................................................. 27
4.7.5 SCREEN SHOT 12 – JOB OVERVIEW ............................................................................................................. 28
4.8 GRAPHICAL MONITOR (RZ01) ............................................................................................................................ 28
4.8.1 WHAT? .............................................................................................................................................................. 28
4.8.2 WHY? ................................................................................................................................................................. 28
4.8.3 HOW? ................................................................................................................................................................ 29
4.8.4 SCREEN SHOT 13 - COMPUTING CENTRE MANAGEMENT SYSTEM (CCMS) .........................................29
4.9 LOCKS (SM12) ........................................................................................................................................................ 29
4.9.1 WHAT? .............................................................................................................................................................. 29
4.9.2 WHY? ................................................................................................................................................................. 29
4.9.3 HOW? ................................................................................................................................................................ 30
4.9.4 SCREEN SHOT 14 – LOCK ENTRY LIST ......................................................................................................... 31
4.10 ACTIVE USERS (AL08/SM04) ................................................................................................................................ 31
4.10.1 WHAT? .............................................................................................................................................................. 31
4.10.2 WHY? ................................................................................................................................................................. 31
4.10.3 HOW? ................................................................................................................................................................ 32
4.10.4 SCREEN SHOT 14 – OVERVIEW OF USERS .................................................................................................. 33
4.10.4 MULTI-INSTANCE SYSTEM (AL08) ................................................................................................................ 33
4.10.4.1 WHAT? ............................................................................................................................................................ 33
4.10.4.2 WHY? .............................................................................................................................................................. 33
4.10.4.3 HOW? .............................................................................................................................................................. 33
4.10.4.4 SCREEN SHOT 15 – CURRENT ACTIVE USERS.......................................................................................... 34
4.11 CHECK SPOOL LIST (SP01) ................................................................................................................................... 35
4.11.1 WHAT? .............................................................................................................................................................. 35
4.11.2 WHY? ................................................................................................................................................................. 35
4.11.3 HOW? ................................................................................................................................................................ 35
4.11.4 SCREEN SHOT 16 – OUTPUT CONTROLLER: LIST OF SPOOL REQUESTS.............................................. 36
4.12 BATCH INPUT JOBS, IN ERROR OR TO BE PROCESSED (SM35) .................................................................... 36
4.12.1 WHAT? .............................................................................................................................................................. 36
4.12.2 WHY? ................................................................................................................................................................. 37
4.12.3 HOW? ................................................................................................................................................................ 37
4.12.4 SCREEN SHOT 17 – BATCH INPUT SESSION OVERVIEW ........................................................................... 38

Internal Use 3
 SAP System monitoring guide

4.14 ABAP DUMP ANALYSIS (ST22) ............................................................................................................................ 38

4.14.1 WHAT? .............................................................................................................................................................. 38
4.14.2 WHY? ................................................................................................................................................................. 39
4.14.3 HOW? ................................................................................................................................................................ 39
4.14.4 SCREEN SHOT 18 – ABAP DUMP ANALYSIS ................................................................................................ 39
4.14.5 SCREEN SHOT 19 – ABAP DUMP ANALYSIS (OVERVIEW) ......................................................................... 40
4.14.6 SCREEN SHOT 20 – ABAP RUNTIME ERRORS ............................................................................................. 40
4.15 WORKLOAD ANALYSIS OF THE SYSTEM (ST03).......................................................................................................... 41
4.15.1 WHAT? .............................................................................................................................................................. 41
4.15.2 SCREEN SHOT 21 – WORKLOAD ANALYSIS OF SAP SYSTEM .................................................................... 41
4.16 BUFFERS (ST02) ..................................................................................................................................................... 43
4.16.1 WHAT? .................................................................................................................................................................. 43
4.16.2 WHY? ..................................................................................................................................................................... 43
4.16.3 HOW? ................................................................................................................................................................ 43
4.16.4 SCREEN SHOT 22 – TUNE SUMMARY .......................................................................................................... 43
4.17 DATABASE TASKS (DB02).................................................................................................................................... 44
4.17.1 WHY? ................................................................................................................................................................. 44
4.17.3 HOW? ................................................................................................................................................................ 44
4.17.4 SCREEN SHOT 23 – DATABASE PERFORMANCE TABLES ......................................................................... 44
4.18 DATABASE ERROR LOG (ST04) .......................................................................................................................... 45
4.18.1 WHAT? .............................................................................................................................................................. 45
4.18.2 WHY? ................................................................................................................................................................. 45
4.18.3 HOW? ................................................................................................................................................................ 45
4.18.4 SCREEN SHOT 24 - DATABASE PERFORMANCE ANALYSIS: OVERVIEW ................................................ 45
4.19 OPERATING SYSTEM TASKS (ST06/OS06)............................................................................................................. 46
4.19.1 WHAT? .............................................................................................................................................................. 46
4.19.2 WHY? ................................................................................................................................................................. 46
4.19.3 HOW? ................................................................................................................................................................ 46
4.19.4 SCREEN SHOT 25 - LOCAL/OPERATING SYSTEM MONTIOR:(ST06/OS06).............................................. 46
4.20 USER TRAINING ..................................................................................................................................................... 47

Internal Use 4
 SAP System monitoring guide

SECTION 1

Internal Use 5
 SAP System monitoring guide

1.0 OVERVIEW
These procedures have been compiled following specific guidelines.

A Healthy SAP system requires

• A properly configure SAP System

• A continuously Tuned Database

• A proper application of workload on the system

Periodic system administration tasks help in ensuring satisfactory health of the SAP system
within your business. There are sets of transactions, which must be completed by the system
administrator on a daily basis.

The checklist is required to ensure the health of the system and perform the checks on shift basis.

The checklist can be modified to meet the specifications of the business whick will provide you
with the following: -

• Critical Tasks

• SAP System

• Database

• Operating System

These activities can be performed daily, at least once for each of the SAP systems. The
observation and the action taken are recorded within the checklist, which is included and has
been recommended by the ASAP methodology. Once the checklist has been completed, an alert
table can be prepared which will include all Basis components in Colour code (RED, YELLOW,
& GREEN), each of these colour codes indicate their status. The Objective of the process is to
strive to have the Green status for all Basis components.

Internal Use 6
 SAP System monitoring guide

SECTION 2

Internal Use 7
 SAP System monitoring guide

2.0 DAILY CHECKLISTS

2.0.1 CRITICAL SYSTEM TASKS

Monitoring the system will involve some critical tasks to be completed as soon as the
administrator arrives into the office each day. These tasks will answer the following questions.

• Is the SAP System running?

• Did the backups execute and complete successfully?

• If the answer to either question is “no”, then the situation must be resolved quickly,
because of the following: -

• IF THE SYSTEM IS DOWN AT ANY TIME, NO WORK CAN BE DONE.

• IF THE BACKUPS FAILED, AND A DIASTER OCCURS, THERE COULD BE A LOSS OF DATA SINCE
THE MOST RECENT BACKUP.

Internal Use 8
 SAP System monitoring guide

SECTION 3

Internal Use 9
 SAP System monitoring guide

3.0 VERIFY THAT SAP IS RUNNING

3.0.1 WHAT?

When the system administrator arrives in the morning, the first task to be completed is to check
that the SAP system is running. This task is a high level check to see if the SAP system is up
and functioning correctly, and whether or not you can connect to the system.

3.0.2 WHY?

If the system is not running, the END-USERS will contact the HELPDESK enquiring as to why
the system is not operational, and when the system will be back up and running.
As a basic level check, if one can connect to the SAP system, the following questions can be
answered:

1 Is the SAP system working?

2 Is the network between you and the SAP system working?

3.0.3 HOW?

Log onto the system using SAPGUI.

If you can log on, the test is successful.

Internal Use 10
 SAP System monitoring guide

3.1 VERIFY THAT BACKUPS RUN SUCCESSFULLY.

3.1.1 WHAT?

Ensure that the backups, which were scheduled to run everyday and completed successfully.

Backups of the SAP database and related non-database operating system level files are
essential to recover the SAP system.

Types of non-database files include

Database log dumps
Data files for a third party application.
Transport files
Inbound and outbound interface files

3.1.2 WHY?

If there is a problem with any of the backups, the problem needs to be quickly resolved. If a
failure occurs within the database, which requires a restore to be carried out, from the last
backup, and the last backup, failed. The system administrator will have to recover the system
by using the most recent successful backup that is available. At the operating system level,
some of these files may need to be in sync with the R/3 database.

3.1.3 WHEN?

These critical tasks need to complete first thing in the morning. Any failed backups must be
immediately investigated and resolved.

Internal Use 11
 SAP System monitoring guide

SECTION 4

Internal Use 12
 SAP System monitoring guide

4.0 SAP TASKS - CHECK ALL APPLICATION SERVERS ARE UP (SM51)

4.0.1 WHAT?

SM51 allows you to look at all the serves set up within the system, you do not have to log into
each individual server.

4.0.2 WHY?

• If one of your dialog application servers are not up, the users who normally log onto the
server in question will have difficulty logging onto the system. This is due to a server not
being available.

• If the batch application server is down, batch jobs that have been schedule to run on the
server would have been not been completed.

4.0.3 HOW?

Within the command field, enter the transaction code SM51, and press ENTER.

Or

TOOLS > ADMINSTRATION > MONITOR > SYSTEM MONITORING > SERVERS.

Review the list of instances under the server name.

Verify that all the instances are listed; if it is listed it is up and running successfully.

Internal Use 13
 SAP System monitoring guide

4.0.4 SCREEN SHOT 1 – SAP SERVERS (OVERVIEW)

4.1 WORK PROCESSES MONITOR (SM50)

4.1.1 WHAT?

The process overview transaction allows users to view the status of the work processes and
monitor for any potential problems. Transaction SM51 is a central transaction from which you
can select the instance you wish to monitor. SM51 starts transaction SM50 for each of the
application servers, transaction SM50 is used for a system without any application servers.

4.1.2 WHY?

SM50 is one place to look for jobs or programs that may have “hung”, which would be
indicated by the long run times. If batch jobs are not running, transaction SM50 may provide a
hint to the problem, if the entire batch processes are in use.

4.1.3 HOW?

4.1.4 SYSTEMS WITH APPLICATION SERVERS.

• Enter SM51 within the command field, then ENTER, or.

• TOOLS > ADMINSTRATION > MONITOR > SYSTEM MONITORING > SERVERS.
• Select the instance you wish to view.
• Choose the process, this will take you through to SM50.

Internal Use 14
 SAP System monitoring guide

4.1.5 SCREEN SHOT 2 – SAP SERVERS

4.1.6 SYSTEMS WITHOUT APPLICATION SERVERS.

• Enter SM50 within the command field, then ENTER, or

• TOOLS > ADMINSTRATION > MONITOR > SYSTEM MONITORING > PROCESS OVERVIEW.

4.1.7 WHAT TO LOOK FOR!

Dialog work processes (DIA) that have long run time values

These values could indicate a problem, or a long running step in batch programs, which
sometimes start dialog work processes.

Work processes, with a stopped status, these can sometimes be a problem because a process
may have stalled or failed.

4.1.8 SCREEN SHOT 3 – PROCESS OVERVIEW

Internal Use 15
 SAP System monitoring guide

4.1.9 COLUMN DEFINITIONS: -

No COLUMN DEFINITION

1 No Work process number

2 Type Type of work process
3 PID OS PID (Process ID) number
4 STATUS Current status of the work process
5 ERR Number of detected errors in the work process
6 CPU Cumulative CPU time that the current process is taking
7 TIME Cumulative “wall” time that the current process is taking
8 Report Name of the ABAP Program
9 CLIENT CLIENT NUMBER
10 USER User ID that is using the work process
11 TABLE Table that the action is being performed on

4.2 LOAD BALANCING (SMLG)

4.2.1 WHAT?

Within SAP R/3 you want to have all the application servers within the SAP environment to
work equally hard. The load balancing process is not extremely sophisticated, since it is based
on the average response time for a specific application server and the number of users currently
working on the server in question.

The load distribution monitor will enable you to monitor the user load on each application
server within the SAP environment.

4.2.2 WHY?

Internal Use 16
 SAP System monitoring guide

The load distribution monitor will enable you to monitor the user load on each application
server within the SAP environment. The average weight within the load balancing should be
roughly 5 – 1 within the application servers the ratio can be changed within the relevant ABAP
code.

4.2.3 HOW?

The load distribution monitor can be monitored using the transaction code SMLG or menu
path
TOOLS > CCMS > CONFIGURATION > LOGON GROUPS (Select the logon group you wish to
review) > GOTO > LOAD DISTRIBUTION>

4.2.4 SCREEN SHOT 4 – CCMS: MAINTAIN LOGON GROUPS

4.3 GLOBAL WORK PROCESS OVERVIEW (SM66)

Internal Use 17
 SAP System monitoring guide

4.3.1 WHAT?

The Global work process overview enables the system administrator to view all the work
processes and monitor them for any potential problems. SM66 transaction is roughly the same
as SM50, but t is an overall view of all the work processes within the system.

4.3.2 WHY?

SM66 is one place to look for jobs or programs that may have “hung”, which would be
indicated by the long run times. If batch jobs are not running, transaction SM66 may provide a
hint to the problem, if the entire batch processes are in use.

4.3.3 HOW?

To view Global Work Process Overview (SM66), enter transaction code SM66 within the
command field, and then enter. This should give you a list of all the Global Work Processes.

4.3.4 SCREEN SHOT 5 – GLOBAL WORK PROCESS OVERVIEW

4.4 MAINTAIN PRODUCTIVE OPERATION MODES (RZ04)

Internal Use 18
 SAP System monitoring guide

4.5 FAILED UPDATES (SM13)

4.5.1 WHAT?

A failed update or an update termination is an update to the database that failed. The failed
updates occur when a user entry or transaction is not entered or updated within the database.
The following analogue should help to clarify this concept.

4.5.2 WHY?

The alert monitors will detect any update failures immediately and report the failure to the
system log and the alert monitor. All update failures should be address, as quickly as possible,
if you follow the analogue which follows it will give you a brief explanation as to how updates
fail.

4.5.2.1 ANALOGUE

1 A secretary gives a files clerk a folder (similar to a save or execute).

2 The file clerk gives the secretary a receipt (similar to the R/3 document number).
3 On the way to file cabinet, the clerk falls and gets hurt.
4 The folder never makes it to the cabinet (this is a failed update)
5 The end result is the folder is not held within the cabinet, even thought the secretary
has a
receipt.

For performance reasons the database update is done in asynchronous mode. Within this
mode, the user continues to work while the system takes over the update process and waits
for the database to update itself and complete.

In synchronous mode, users would have to wait until the database has successfully updated
before they can continue to work effectively.

The users probably received a document a number, so they assume that the entry is within the
system, however, if a failed update has occurred, it is not. If this were a customer order,
unless the order is re-entered, the customers would not get their order and no trace of it
would be found within the system.

The system should be checked for any failed updates several times a day.

Internal Use 19
 SAP System monitoring guide

During a dayshift, the system checks can be distributed.

• First thing in the morning

• Late morning

• Early afternoon

• Late afternoon

The longer one waits after the update termination has occurred, the more difficult it will be for
users to remember what they did when the update terminates. If one waits too long, the user
will not remember.

4.5.3 HOW?

1 Enter SM13 within the command field, or choose, TOOLS > ADMINSTRATION>
MONITOR > UPDATE.

2 Enter * within the CLIENT FIELD.

3 Enter * within the USER ID FIELD.

4 Under Status, select ALL.

5 Change the date to a year ago, within from date.

6 Select ENTER.

7 Look for entries with an Err within the Status column.

These entries are failed updates, or update terminations. One may also see other entries
listed without the Err status.

If there are no failed updates, one may stop here. Otherwise the terminated updates are to be
managed.

Internal Use 20
 SAP System monitoring guide

4.5.4 SCREEN SHOT 7 – UPDATE RECORDS

STATUS DEFINITIONS

No COLUMN DEFINITION

1 OK Update request was executed without errors

2 V1 V1 modules of the update request were executed without errors
3 DEL Update request was deleted
4 RUN Update request is currently being executed
5 AUTO Due to an error (for example, stopping the update server), the update
request has not yet been executed. It will now be automatically updated.
6 INIT Update request has not yet been requested
7 ERROR An error occurred during the execution of the update request

A background job can be scheduled within the Background to clear all those updates, which
ended in ERROR. This job has been scheduled to run on a daily basis, throughout the night.
Internal Use 21
 SAP System monitoring guide

However any updates that end in ERR, will still show within SM13, therefore they will need to
be manually deleted from the system, by the system administrator during their daily tasks.
Before the updates are deleted from SM13, a thorough investigation must be undertaken.

4.5.4 MANAGING UPDATE TERMINATIONS

4.5.5 HOW?

If there are failed updates, the following steps need to be proceeded by the system
administrator: -

1 Double click on an entry with an Error status within the above screen shot, this will show
the module name and where in the process that the update terminated.

4.5.6 SCREEN SHOT 8 – UPDATE MODULES

2 Double click on the entry with an Error Status.

Internal Use 22
 SAP System monitoring guide

4.5.7 SCREEN SHOT 9 – UPDATE STATUS

4 If a short dump appears for the ERROR, it will appear.

5 This screen shows an ABAP dump for the terminated updates

Some problems that can occur with an update termination are:-

• No Short dump
(In this case, the only clues you have are the)
• User ID
• Date
• Time
• Transaction
• Difficulty reading the short dump

The ability to read a short dump comes with experience and practice; some of the short
dumps content is only useful to the developer.

Not being able identifies the batch job, which was the source of update terminations is a
known issue.

Internal Use 23
 SAP System monitoring guide

6 The users affected need to be contacted, they should check for the missing entries and
reprocess the missing transactions.

Do not attempt to reapply the failed update; there are conditions under which this can
lead to corruption of the database.

The users should always be advised to re-enter the transaction.

4.6 SYSTEM LOG (SM21)

4.6.1 WHAT?

The system log is the log of events, errors, problems and other system messages that have
occurred within the R/3 System.

4.6.2 WHY?

The system log is important, because unexpected and unknown warnings and errors could
indicate a serious problem that has occurred.

4.6.3 HOW?

The ability to properly monitor the system log will improve with experience. Over time you
will become familiar with what log entries “normally” appear within your system log, and pick
out the unusual instances that may require further investigation.

Within the command field enter /nSM21, press enter

Or

TOOLS > ADMINSTRATION > MONITORING > SYSTEM LOG

Enter the dates and time, can be extremely useful if you wish to review a specific time scale in
a certain day.

Internal Use 24
 SAP System monitoring guide

To make reviewing the system log easier, within Problem classes select one of the following: -

Problems only
Problems and warnings
All messages

These options allow you to view the system log in the following priority layers

Problems
Problems and warnings
All messages
What to look for: -

4.6.4 UNUSUAL ENTRIES

Before you can recognise the unusual entries, you will need to become familiar with which
entries are in the log under normal conditions.

Column Priority highlights the errors that error.

The errors that have occurred within the system, have been highlighted in RED, and the entries
that have ended in a warning status will be highlighted in YELLOW within column C

4.6.5 SCREEN SHOT 10 – SYSTEM LOG: ANALYSIS FOR ALL REMOTE INSTANCES

All those entries, which have marked as RED, should be monitored

Internal Use 25
 SAP System monitoring guide

4.7 BACKGROUND JOBS (SM37)

4.7.1 WHAT?

Background jobs are batch jobs, which have been scheduled to run at specific times during the
day, or evening.

4.7.2 WHEN?

If you are running critical jobs, which fail, you need to know if the job failed because of other
processes, activities, or tasks that are dependent on these jobs.

4.7.3 HOW?

You should have a list of critical jobs, which have been schedule to run on a daily basis, these
dates will not change from one month to the next unless a change to the date and time has
been requested. For each of the critical jobs, you should have the following check list which
shows: -

• When the jobs have been scheduled to run.

• The expected run time of each job.
• Emergency contact (names and phone numbers) if the job fails or suffers any problems.
• Restart the problem procedure for the job in question.

1 Enter transaction SM37

OR

SYSTEM > SERVICE > JOBS> JOB OVERVIEW

2 Enter * within the JOB NAME field, this will enable you to see all the jobs.
3 Enter *, or a specific user ID that the batch job runs under (to limit the display to those
scheduled under a specific user ID or user name).
4 Enter a start date in form.
5 Enter an end date.
6 Under only jobs with status, select: -
• Active
• Finished
• Cancelled
7 Choose ENTER.

Internal Use 26
 SAP System monitoring guide

4.7.4 SCREEN SHOT 11 - SIMPLE JOB SELECTION

8 Check for any failed or cancelled jobs. Analyse why the jobs have failed or why they were
cancelled and make the necessary corrections.
9 Check for any critical jobs.
You will need to know the job name that they are run under to do this.

To check a job log, you must carry out the following:-

10 Select a job
11 The choose job log.

Check the job performance and record the run times. A deviation from the usual run time on a
job may indicate a problem and should be investigated.

Internal Use 27
 SAP System monitoring guide

4.7.5 SCREEN SHOT 12 – JOB OVERVIEW

4.8 GRAPHICAL MONITOR (RZ01)

4.8.1 WHAT?

The graphical monitor is useful when co-ordinating many background jobs, because it allows
you to see individual job statistics. Also easy way to check the job class assigned for the
servers.

4.8.2 WHY?

The graphical job monitor is a more visually format in which the status of a job is indicated by
colour,

Aborted Jobs (RED)

Active Jobs (BLUE)

If a job has ran past its expected run time, and other jobs have been scheduled to start, the
graphical job monitor will enable you to see the conflicts that have occurred.

Internal Use 28
 SAP System monitoring guide

4.8.3 HOW?

1 Within the command field, enter RZ01 then ENTER

2 Choose Time unit Hour to get a more usable time scale.
3 Choose Legend to get a popup legend of the colours and patterns used.

4.8.4 SCREEN SHOT 13 - COMPUTING CENTRE MANAGEMENT SYSTEM (CCMS)

4.9 LOCKS (SM12)

4.9.1 WHAT?

Lock objects are used within SAP to ensure the integrity of the data stored, using locks will
prevent multiple users updating the same data simultaneously. Therefore if you are updating
data within the system, and another user tries to update the same data. They will be locked out
from updating the information.

4.9.2 WHY?

There may be “old” locks still in place from transactions that did not release, or from when the
user was cut off from the network. Unless these locks are cleared, these locks will prevent
access to change the record until the system cycles have been cleared. The easiest way in which
to clear them is to look for any locks from previous days. Locks can be used as a form of
troubleshooting issues, since lock the

system programs normally delete entries automatically. The lock monitoring transaction
enables the locks to be removed manually

No locks should be manually deleted, without a THROUGH investigation into the cause of the
problem.

Internal Use 29
 SAP System monitoring guide

4.9.3 HOW?

To effectively monitor the Locks within your SAP system, you will need to follow the bullet
points listed:-

• TOOLS > ADMINSTRATION > MONITOR > LOCK ENTRIES

• OR, Enter transaction SM12
• Enter * within the Client
• Clear the user name field
• Press ENTER
• Look for any Locks from the previous days within the Time column
• The presence of a lock from a previous day could mean that the user was disconnected
from the network and from the SAP system.

IMPORTANT

The parameter defines an automatic logout of the user, if there is no activity for the set
number of minutes. Setting the auto-logout parameter is recommended for security
purposed. The parameter auto-logout is a global setting that applies to all users on the
instance. One cannot have different logout times for different groups of users, on the same
instance

In order to clear any locks from the system, you will need to follow a number of steps: -

1 Check that the user is not logged on to any of the servers, using SM04 (no application
servers), or AL08 (with application servers).
2 If the user is not on the system, but transaction SM04 shows them on the system the
session must be deleted.
3 Before the user is deleted from the system, a check must be completed to ensure that
there are no processes running under the user ID. Using transaction SM50 or SM51 can
complete this.
4 Check that there are no batch jobs running under the user ID using transaction SM37
5 Check that there are no updates in process for that user ID using transaction SM13
6 Once you aware satisfied that there is no activity using the users ID, select the lock entry
for deletion.
7 Choose LOCK ENTRIES > DELETE

IMPORTANT

Only one entry can be locked at any one time.

The mass delete option should never be used, if you use the mass delete option all the locks
within the system will be deleted not just the ones for the user you have selected.

Internal Use 30
 SAP System monitoring guide

4.9.4 SCREEN SHOT 14 – LOCK ENTRY LIST

4.10 ACTIVE USERS (AL08/SM04)

4.10.1 WHAT?

The transaction AL08, SM04 and SMLG will display all the users, who are logged onto the
system

4.10.2 WHY?

AL08 - Will show you where each user is logged on, along with the user distribution
over all the application servers.

SM04 - Displays the list of users that are currently using a specific application server, from
this transaction you will be able to see different user sessions for each of the users and it also
enables you to terminate a session once you have selected to correct session.

Using these transactions will enable the administrator to recognise the user ID’s logged onto
“unfamiliar” terminals, this may indicate that someone, other that the designated user is using
the same user ID.

Internal Use 31
 SAP System monitoring guide

If a user is logged on to more that one terminal, this may indicate the following: -

• Someone else is using the user ID.

• The user ID is being shared/used by a group of people.

Sometimes, a group user is created for specific jobs, which have been scheduled within SAP, or
if jobs have been scheduled using another platform, which feeds information into SAP.

DISADVANTAGES

Transaction SM04 may show the user as active, when in fact the user has actually logged off.
Because the user session was not properly closed, the system “thinks” that the user is still
logged on.

The following (among others) can cause this condition to occur.

• A network failure, which cuts off the user.

• The user turning off their computer without logging off from the R/3 system.

4.10.3 HOW?

• Within the command field enter SM04, then ENTER, or choose TOOLS > ADMINSTRATION >
• MONITOR > SYSTEM MONTORING > USER OVERVIEW.
• Select the user ID to view the sessions the user has open.

Internal Use 32
 SAP System monitoring guide

4.10.4 SCREEN SHOT 14 – OVERVIEW OF USERS

4.10.4 MULTI-INSTANCE SYSTEM (AL08)

4.10.4.1 WHAT?

Multi instance system (Transaction AL08) enables the system administrator to view the overall
list of the users that are using the system

4.10.4.2 WHY?

If your business is operating several instances within your system, by using transaction AL08 is
will be an easier method, to show all the users within all instances on the system at once.

4.10.4.3 HOW?

To view the data held within the Multi Instance System, you will need to follow the information
provided below/

Internal Use 33
 SAP System monitoring guide

• Enter AL08, then ENTER, or.

• TOOLS > CCMS > CONTROL MONITORING > ALL WORK PROCESSES > GOTO > GLOBAL USER
OVERVIEW.
• The current active user screen shows all the instances within your system.

For each instance there is a list of users logged onto that instance/application server.

4.10.4.4 SCREEN SHOT 15 – CURRENT ACTIVE USERS

Internal Use 34
 SAP System monitoring guide

4.11 CHECK SPOOL LIST (SP01)

4.11.1 WHAT?

The SAP Spool system main responsibility is to administer and process of any print requests
from SAP, along with the administration of any of the output devices. All data generated for
printing within the SAP system, is then sent to the operating system to print.

4.11.2 WHY?

There may be problems with the printer at the operation system level. These problems need to
be resolved immediately, for time critical print jobs or there may be an operational impact.

You should check the active spool jobs that have been running for over an hour. These long
running jobs could indicate a problem with the operating system spool or the printer.

4.11.3 HOW?

• Enter SP01 within the command field, or.

• SYSTEM > SERVICES > OUTPUT CONTROLLER.
• Clear the user name
• Set the form date to one week ago
• Clear the Client
• Press ENTER

This will enable you to look for any jobs with an ERROR status, within the OUTPUT STATUS COLUMN.

Internal Use 35
 SAP System monitoring guide

4.11.4 SCREEN SHOT 16 – OUTPUT CONTROLLER: LIST OF SPOOL REQUESTS

4.12 BATCH INPUT JOBS, IN ERROR OR TO BE PROCESSED (SM35)

4.12.1 WHAT?

This transaction will show the jobs that need to be processed or started, along with the jobs with
errors that need to be resolved.

4.12.2 WHY?

SM35 is important because it will alert you to batch input job which: -

• Needs to be processed
• These are jobs that are waiting to be processed, if not processed the data will not post to
the system.
• Are in ERROR

Internal Use 36
 SAP System monitoring guide

These are jobs that have failed due an error. The danger is that only a portion of the job may
have posted to the system, this will increase the potential for data corruption, as only part of the
data is saved within the system.

4.12.3 HOW?

• Enter SM35 within the command field, then ENTER, or

• SYSTEM > SERVICES > BATCH INPUT > EDIT
• Enter a start date of at least one week previous within the creation date (is does not need
to one week previous, it can have a wider variable).
• Under session status, select both
• To be processed
• Incorrect
• These selections will display only the batch jobs that need to be processed, along with
those errors that need to be resolved.
• Select Enter, then contact the person responsible for the job and notify them in order to
determine if jobs are: -
• Sessions are still to be processed.
• Errors within the session.

Internal Use 37
 SAP System monitoring guide

4.12.4 SCREEN SHOT 17 – BATCH INPUT SESSION OVERVIEW

4.14 ABAP DUMP ANALYSIS (ST22)

4.14.1 WHAT?

An ABAP dump (which is also known as a short dump) is generated when a report or
transaction terminates as a result of a serious error. The system will record the error within the
system log (transaction SM21), and writes a snapshot (dump) of the program termination to a
special table.

This transaction can also be called from the system log (Transaction SM21)

Internal Use 38
 SAP System monitoring guide

4.14.2 WHY?

The ABAP dump is used to analyse and determine why an error has occurred in order to take
corrective action.

4.14.3 HOW?

• Enter ST22 within the command field, then ENTER, or

• TOOLS > ADMINSTRATION > MONITOR > DUMP ANALYSIS
• There are two selection methods to display the list of dumps
• For simple selection, today or yesterday (go to step 2)
• For free selection (go to step 5)
• Under No. of short dumps, if you see a value other than zero (0) in today or yesterday,
dumps have occurred that will need to be examined.
• Select today.
• Choose Display list to obtain a list of short dumps for the day.
• Go to step 8
• Choose selection
• Enter your selection criteria within the ABAP Dump analysis screen.
• Choose Execute
• Double click on the dump you wish to analyse

This screen will show the “short dump”

You must be warned; some Abap dumps can exceed 75 pages in length. It is recommended to
save the dump file on the PC and print out the section, which is required. If the SAP hotline
asks for a copy of the short dump, it is easier to e-mail or upload the file.

4.14.4 SCREEN SHOT 18 – ABAP DUMP ANALYSIS

Internal Use 39
 SAP System monitoring guide

4.14.5 SCREEN SHOT 19 – ABAP DUMP ANALYSIS (OVERVIEW)

4.14.6 SCREEN SHOT 20 – ABAP RUNTIME ERRORS

Internal Use 40
 SAP System monitoring guide

4.15 WORKLOAD ANALYSIS OF THE SYSTEM (ST03)

4.15.1 WHAT?

The workload analysis is used to determine the performance of the system.

You should check statistics and record trends in order to obtain an overall feel for the systems
behaviour and performance. Understanding the system when it is running well will help you to
determine what changes may need to be made when it is not.

• Enter ST03N within the command field, then ENTER, or

4.15.2 SCREEN SHOT 21 – WORKLOAD MONITOR

• Choose database server or this application server.

• Select a time period to analyse.
Options include
• Single stat. Records
• Today’s workload
• Performance database
• Last minute load
• Local alert monitor

Internal Use 41
 SAP System monitoring guide

For this example, choose last minute load.

Enter how many minutes back you wish to analyse, or choose other selection to specify a date
and time period in which to analyse.

Enter how many minutes back to analyse, or choose OTHER SELECTION to specify a date and
time period to analyse.

If the value entered is less than 1000ms (1second), the response time will meet the target
response time.

Judgement should be applied when reviewing statistical values. If you have just started the SAP
system, the buffers will be empty and many of the statistics will be unfavourable. Once the
buffers are loaded, you can properly evaluate the values.

o Choose Transaction Profile

o Click on any cell in the Response time avg column
o Choose Sort

From this screen, you can review transactions in order of overage response time.

See the following table for known long running transactions.

A few standard functional transactions will exceed the one second guidelines, these include:-

No Type of transaction Time (ms)

1 Create Sales Order – VA01 1,500

2 Changing Sales Orders – VA02 1,500

3 Display Sales Order – VA03 1,000

4 Create Billing Document – VF01 1,500

5 Create Delivery – VL01 2,000

6 Maintain Master HR Data – PA30 1,000

Internal Use 42
 SAP System monitoring guide

4.16 BUFFERS (ST02)

4.16.1 WHAT?

The buffer tune summary transaction, will display the R/3 buffer performance, each of
the buffers listed within ST02 will have a history associated with it. To display the history
of each buffer, you will need to drill down by clicking on each of the buffers. This will
determine if you need to add more memory to the buffer or remove some memory.

4.16.2 WHY?

The aim behind this is to avoid swapping and to have a good buffer quality; however
allocating too much memory to a buffer is a waster. Those buffers with too much
memory allocated to them, should have the excess memory reduced.

4.16.3 HOW?

In order to view the buffers within your SAP system, you will need to execute the
following points:-

• Enter transaction code ST02 within the command field, then click ENTER, or
• TOOLS > ADMINSTRATION > MONITOR > PERFORMANCE > BUFFERS

4.16.4 SCREEN SHOT 22 – TUNE SUMMARY

Internal Use 43
 SAP System monitoring guide

4.17 DATABASE TASKS (DB02)

4.17.1 WHY?

Database tasks, are performed in order to ensure that the database is running correctly, and to its
full potential.

4.17.3 HOW?

To review the database check job, you must use the following transaction code or menu path.

• Enter transaction code DB02 within the command field, or

• TOOLS > ADMINSTRATION > MONITOR > PERFORMANCE > DATABASE >
TABLES/INDEXES.

4.17.4 SCREEN SHOT 23 – DATABASE PERFORMANCE TABLES

A review of the table space percentage utilisation must be completed every day.

Identification of any “action points” where you will increase a table space by adding another data
file, as per the procedure followed in client place.

Schedule a cron job to montor the tablespace and monitor the database.

Internal Use 44
 SAP System monitoring guide

4.18 DATABASE ERROR LOG (ST04)

4.18.1 WHAT?

The Database log is a record of all errors at the database level.

4.18.2 WHY?

Database errors may indicate a database problem, which has not been reported from
other locations.

4.18.3 HOW?

To obtain the necessary information, you will need the following points.

• Within the command field, enter transaction code ST04, then CLICK ENTER, or
• TOOLS > CCMS >CONTROL/MONITOR > PERFORMANCE MENU > DATABASE >
ACTIVITY.

4.18.4 SCREEN SHOT 24 - DATABASE PERFORMANCE ANALYSIS: OVERVIEW

Internal Use 45
 SAP System monitoring guide

4.19 OPERATING SYSTEM TASKS (ST06/OS06)

4.19.1 WHAT?

The system logs are the operating system, and some applications write even logs.

4.19.2 WHY?

There may be indications of a problem developing, or reasons for the current problem in
hand.

4.19.3 HOW?

To obtain the operating system log, you will need to perform the following tasks.

• Within the command field, enter transaction code OS06, then CLICK ENTER, or
• TOOLS > CCMS > CONTROL/MONITORING > PERFORMANCE MENU > OPERATING
SYSTEM > LOCAL > ACTIVITY.
• Select the detailed analysis menu
• Select Operating system log

4.19.4 SCREEN SHOT 25 - LOCAL/OPERATING SYSTEM MONTIOR: (ST06/OS06)

Internal Use 46
 SAP System monitoring guide

4.20 USER TRAINING

When a user receives a popup message, it usually signals a problem. The message reads “You have
received express mail in you inbox”. The user should immediately stop and get assistance to determine
what has happened within the SAP system. SAP Abap system uses “express mail” to notify the user of
any failed updates. It is during this short period immediately after the error has occurred that the user
has the best chance of correcting the error.

Internal Use 47