Scribd
Upload
14 views

SMON Job

The document provides guidance on configuring the Snapshot Monitoring tool (SMON) for performance monitoring in SAP systems, specifically for SAP NetWeaver 7.4 or higher. It details the necessary authorizations, steps to turn on and off daily monitoring, and notes on system performance impact. Additionally, it references relevant SAP Notes for installation and troubleshooting issues related to SMON.

Uploaded by

hopnhopstop
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
14 views

SMON Job

The document provides guidance on configuring the Snapshot Monitoring tool (SMON) for performance monitoring in SAP systems, specifically for SAP NetWeaver 7.4 or higher. It details the necessary authorizations, steps to turn on and off daily monitoring, and notes on system performance impact. Additionally, it references relevant SAP Notes for installation and troubleshooting issues related to SMON.

Uploaded by

hopnhopstop
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

SAP Knowledge Base Article

2651881 - How to configure SMON for performance monitoring and analysis


Component: SV-PERF (Service > Performance Problems), Version: 24, Released On: 31.03.2025

Symptom
The Snapshot Monitoring tool (/SDF/SMON) can be used for analysis of performance problems and general system
monitoring.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is
purely coincidental.

Environment
SAP NetWeaver 7.4 or higher

Cause
1. Authorizations required to run SMON

2. Turning on Daily Monitoring

3. Turning off Daily Monitoring

Resolution
SMON is delivered with the ST-PI Software Component (SAP Solution Tools Plug-In) and was first introduced in SP 0002.
If SMON does not yet exist in the system, see SAP Note 539977 for installing and updating ST-PI.
For errors/issues with SMON itself:
Ensure ST-PI is up to date per Note 539977.
If issues with SMON persist despite being up to date, an incident can be opened in SV-SMG-SDD for further assistance.

If the SAP NetWeaver release is lower than 7.4, /SDF/MON must be used instead (SAP Note 2383809).
To make use of SMON, it must be started before the desired analysis period or already running when the issue occurs.
If multiple ABAP systems are involved in the the problem scenario, SMON must be turned on in both systems.

Authorizations required to run SMON


The user which starts SMON requires the following authorizations.

Object Fields

S_TCODE TCD=/SDF/SMON,SM50,SM04

S_ADMI_FCD S_ADMI_FCD=PADM,ST0R

S_BTCH_JOB JOBGROUP=*
JOBACTION=RELE

S_BTCH_ADM BTCADMIN=Y
Turning on Daily Monitoring
1. To schedule SMON, open transaction /n/SDF/SMON in any client (data is collected per instance/system).
2. The Snapshot Collections screen (or the Start Snapshot Monitoring screen) will open.
3. Click the Schedule new monitoring (F6) button.

4. Click the Schedule Daily Monitoring (Ctrl+F2) button.

5. Configure the Settings to the following:

In some cases SAP will ask for additional content switches to be turned on. For daily monitoring purpose, all options
could be left as default.
6. Once configured as desired, click the Execute (F8) button and the SMON collectors will be started on each application
server.
If there were no snapshot collections before now, wait 1-2 minutes for the collectors to collect some snapshot samples,
then reopen /n/SDF/SMON to view the snapshot collection.
Turning off Daily Monitoring

SAP recommends keeping Daily Monitoring on 24/7 to aid in the analysis of past performance and resource problems.

To stop the current Daily Monitoring collector:

1. Open transaction /n/SDF/SMON in any client, select the active/running collection (the collection with the gear icon),
and click the Stop Analysis button.
2. The current collector should now be stopped.
To stop future Daily Monitoring collectors from being started:
1. On the same screen, click the Schedule new monitoring (F6) button.

2. Click the Stop Daily Monitoring (Ctrl+F3) button.

3. Daily Monitoring collectors will no longer be started automatically.

Overhead
Transaction SMON has negligible impact on overall system performance when the content switches remain as their defaults.
Every snapshot interval, an RFC call is made to each application server included in the monitoring in order to collect the
selected content. The calls typically last <1 second, however, if there is a (RFC) WP shortage, the snapshot content will be
delayed or fail to collect.

See Also
SAP Note 2689852 - /sdf/mon memory mapping
KBA 3006447 - Comparing slow transactions, users and reports between systems
KBA 3017593 - Documenting and capturing a General performance issue
SAP Note 539977 - Release strategy for add-on ST-PI

Keywords
SMON, Tracing, Resources, Collector, /SDF/MON

Attributes
Key Value

Other Components Service > SAP Solution Manager > Service Data Download (SV-SMG-SDD)

This document refers to


SAP Note/KBA Component Title

2383809 SV-PERF

2689852 SV-SMG-SDD /sdf/mon memory mapping

539977 BC-UPG-ADDON Release strategy for add-on ST-PI


This document is referenced by
SAP Note/KBA Component Title

3592935 Error: Transaction /SDF/SMON does not exist

2403798 BC-DWB-TOO-ATF Missing ATC and SCI check variants

3436673 SV-SMG-SDD SMON report does not display any WP details

3033103 SV-PERF Information required for initial analysis of Performance Issues in ABAP System

2388483 HAN-DB How-To: Data Management for Technical Tables

2770247 SV-PERF SV-PERF: Guidelines when opening a Customer Incident

2444034 SV-PERF General steps for analyzing high Processing Time

You might also like