---
title: "Extracting SCMON Usage"
slug: "extracting-scmon-usage"
updated: 2026-08-12T11:01:50Z
published: 2026-08-12T11:01:50Z
canonical: "success.panaya.com/extracting-scmon-usage"
excludeFromExternalSearch: true
---
> ## Documentation Index
> Fetch the complete documentation index at: https://success.panaya.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Extracting SCMON Usage
This is a Beta feature.To be able to extract SCMON usage statistics, contact [Panaya Support](/v1/docs/check-out-panayas-support-portal)Caution!
- **Do not** run Usage Procedure Logging (UPL) and SCMON in parallel.
e.g., activating UPL via Solution Manager and then SCMON locally in the ABAP system.
- Avoid using SCMON (or UPL) for the systems already running in maximum load.
###
### Prerequisites
- ZZ_ARCHIVE_ETL (using tar) has been defined in the SM49 or SM69 transactions of the relevant system, per the steps [here](/v1/docs/compression-utility-definition-for-version-ecc60)
- ZZ_COMPRESS_ETL (using gzip) has been defined as described [here](/v1/docs/compression-utility-definition-for-version-ecc60)
- The SAP user running the extraction should be assigned with the SAP_ALL or a strong BASIS user authorization.[](/v1/docs/authorizations-required-for-extracting-your-custom-code)
[Click here for more details](/v1/docs/authorizations-required-for-extracting-your-custom-code)
- [Additional Required authorizations:](/v1/docs/authorizations-required-for-extracting-your-custom-code)
The authorization profile for object **S_ADMI_FCD** with value **SCMD** for reading access to ABAP Call Monitor data.
The authorization profile for object **S_ADMI_FCD** with value **SCMA** for administration activities in the ABAP Call Monitor.
- SUSG installation
If SUSG does not start in your production system, it must be installed first. To install SUSG, apply OSS note [2643357 – Installation of Transaction SUSG](https://launchpad.support.sap.com/#/notes/2643357). This is a TCI based OSS note (see [blogs](https://saptechnicalguru.com/snote/) below).
After the TCI note, also apply these 2 OSS notes:
- [2822357 – SUSG: Robustness of transaction SUSG](https://launchpad.support.sap.com/#/notes/2822357)
- [2830186 – SUSG: Runtime of SUSG_COLLECT_FROM_SCMON](https://launchpad.support.sap.com/#/notes/2830186)
**SAP Blogs**
- [SCMON](https://blogs.sap.com/2017/04/06/abap-call-monitor-scmon-analyze-usage-of-your-code/)
- [SUSG](https://blogs.sap.com/2019/02/27/aggregate-usage-data-in-your-production-system-with-susg-transaction/)
### Activate SCMON Data Collection, create a snapshot and upload to Panaya
####
1. Run transaction SCMON and activate data collection
2. Define the number of days for the SCMON to store the data by changing the ABAP Call Monitor > Configure Time Slices.
3. Run transaction **SUSG** and activate the data collection for the desired period and activate data aggregation.
The aggregation is a nightly job, and the 'Usage' data becomes available the next day.
4. Run the following commands in Command Prompt -
tar --help
If the command is unavailable, define the path in environment variables, or copy the tar files into the System32 folder.
You may be required to enter the full tar path, e.g.,/bin/tar, or use the 'which tar' command to determine its exact path.
5. Navigate to Panaya's Code Box to [download and install the newest extractor version](/v1/docs/how-to-extract-and-upload-your-custom-code).
6. Run SUSG, click on **Create** **Snapshot** and download the ZIP file.
7. Click on **Manage** **Snapshots**, select the newly created snapshot and download it to File:
8. Run a [new extraction](/v1/docs/how-to-extract-and-upload-your-custom-code) and select the downloaded File in the SUSG Upload section, and Upload it: 
9. Upload the automatically compressed (.tar) extraction file to [Panaya Code Box](/v1/docs/how-to-automatically-extract-and-upload-your-custom-code).