SCMON Setup and Execution Guide
Purpose: The ABAP Call Monitor (SCMON) is a tool designed to monitor the execution and usage of ABAP code (function modules, method calls, etc.) in your productive SAP system. It helps identify which custom code is actively used and which business processes call specific ABAP objects. On average, 40-60% of custom code remains unused in productive landscapes, making SCMON essential for cleanup activities before migration projects like SAP S/4HANA transformations.
Key Capabilities
- Tracks usage frequency of ABAP objects
- Identifies calling business transactions and processes
- Provides data for custom code decommissioning decisions
- Supports long-term usage analysis when combined with transaction SUSG
Configuration Steps (Local Activation (Direct in ABAP System)
- Execute transaction SCMON or /SDF/SCMON (for NW < 7.4 SP13)
- Click the Activate button
- Configure activation settings:
- Scheduled Deactivation: Specify when monitoring will automatically stop
- Record Limit: Set maximum number of records (default: 200 million)
- Save the configuration
Configure Time Slices
- In transaction SCMON, navigate to ABAP Call Monitor > Configure Time Slices
- Set Maximum Number of days for data retention (default: 7 days, recommended: up to 365 for detailed analysis)
- Time slices enable analysis of monitoring progress over specific intervals
- SCMON automatically deletes data older than the configured retention period
Note - Please complete the required configuration steps in both corresponding systems so that the comparison for the usual analysis can be performed.
Extraction of Call Monitor Data Report –
- Click on button Display data
- Provide the required date range and other filter if needed.
- Download the result set into Excel format
Analysis of Objects Utilized in the Extract
- Extract the result from both comparison system.
- Identify unique objects from both extract result.
- Finally perform comparison it identifies which objects were not executed/tested
SUMMARY
| Sum of Count | Column Labels | ||
| Row Labels | Testing does not seem to performed | Testing Executed | Grand Total |
| Batch Job | 35 | 19 | 54 |
| CLAS | 2 | 33 | 35 |
| FUGR | 5 | 25 | 30 |
| PROG | 42 | 140 | 182 |
| Remote Function Call | 9 | 2 | 11 |
| Submit Report | 22 | 94 | 116 |
| Transaction | 50 | 157 | 207 |
| URL | 1 | 1 | 2 |
| Grand Total | 166 | 471 | 637 |
Note: - All the above activities are related to Excel operations. There are multiple possible approaches to perform this analysis no strict rule as such.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.