The ABAP Call Monitor allows you to monitor the execution of ABAP procedures (function modules, method calls, forms) and their leading requests (business processes) in the live ABAP system in parallel to productive use. Using this tool, you can focus on usages of a business process that is initiated by a request entry point – such as a specific transaction, RFC call, URL request, or ABAP report.
As a result of this monitoring, you get a list of executed request entry points along with all ABAP procedures that have been executed under the umbrella of these entry points.The ABAP Call Monitor not only indicates that the procedure was called in the first place, but also provides an execution counter for each procedure.
You can use the collected data, for example…
- To find all business processes that execute (depend on) a specific function module or method call. (For example: To identify the business processes affected by code change or deprecation)
- To find out which procedures are executed by a specific business process.
NOTE: In contrast to the SQL Monitor tool, which uses the same technique for SQL statements, the ABAP Call Monitor does not provide any performance data for ABAP procedures.
Requirements
- In order to use the functionality of this transaction, you need in the relevant system:
- The authorization profile for object S_ADMI_FCD with value SCMD for read 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.
Using ABAP Call Monitor – Administrative Tasks
All activities that result in changing the configuration or the data of transaction SCMON are executed by the system administrator.
These activities include:
- Viewing the Monitor Status Information
For all server instances of an ABAP system, you can view the status information, for example, whether or not ABAP Call Monitor is active.
Steps:
Launch the ABAP Call Monitor using transaction code SCMON. The initial screen displays the Activation status, along with other details that describe the operation of the call monitor.
- Changing the Monitor Status
For the entire system (all server instances), you can change the status by activating or deactivating the monitoring.
Steps:
To activate the system for monitoring…
- On the initial screen of transaction SCMON, click the Activate button or choose the corresponding menu item.
- Configure the activation. In the dialog that appears, change the default values – if necessary.
- The following configuration settings are specified:
- Scheduled Deactivation:
- Point of time when the monitoring will be deactivated automatically.
- Record Limit:
- You can limit the maximum number of records that are created during monitoring. The ABAP Call Monitor is then switched off automatically.
- Scheduled Deactivation:
- Confirm with Ok.
NOTE: To explicitly deactivate the monitoring of the system, click the Deactivate button or choose the corresponding menu item.
- Specifying the Time Slices
The time slices in the ABAP Call Monitor enable you to analyze the progress of monitoring results over time. You then have the option to focus on monitoring data for a specific time interval. For example, you might be interested in those ABAP procedures that call development objects that have been declared as deprecated since a specific point of time.
Steps:
- On the initial screen of transaction SCMON, choose the menu item ABAP Call Monitor > Configure Time Slices.
- Configure the values the time slices. In the dialog that appears, change the default value for Maximum Number of Daily Slices – if necessary.
- Maximum Number:
- With this number, you can limit the data records created during monitoring to a specific period of time. The ABAP Call Monitor automatically deletes the monitoring data that has been created before Maximum Number of days.
- Confirm with Ok.
- Collecting the Monitor Data Explicitly
Usually, the data collection takes automatically place once an hour by means of a periodically scheduled job ABAP CALL MONITOR: COLLECT – if the ABAP Call Monitor is active in the system. This job collects the monitoring data from shared memory and stores it in the central database of the system.
If you do not want to wait for this automatic data collection, you can trigger the data collection explicitly at any interim point of time.
Steps:
On the initial screen of transaction SCMON, click the Collect Data button or choose the corresponding menu item.
- Deleting the Monitor Data
Since you have finished your monitoring activities and no longer need the corresponding data, you have the option to explicitly delete the collected monitor data.
Steps:
On the initial screen, choose the menu item ABAP Call Monitor > Delete Data.
Using ABAP Call Monitor for Data Analysis
All activities that are involved in analyzing monitoring data records are executed by the ABAP developer.
These activities include:
- Displaying the Monitor Log
Occasionally, you will need an overview of all monitor activities within a certain period of time.
Steps:
On the initial screen of transaction SCMON, click the Display Log button or, alternatively, choose the corresponding menu item.
In the Log Browser screen that appears, you get a list of actions or events – such as activation or deactivation of the call monitor, deletion of records, and collection of data.
- Displaying and Analyzing the Monitor Data
The data browser of the ABAP Call Monitor allows you to analyze the use/dependency relationship between procedures, such as method calls and requests that represent specific (parts) of business processes.
Steps:
- On the initial screen of transaction SCMON, click the Display Data button or, alternatively, choose the corresponding menu item.
- In the Data Browser selection screen, specify the options for data selection.
Example 1: Get all URLs calling methods of the class CL_MY_CLASS during a specific period of time.
Specify the options for data analysis as follows:
Time Interval > Date: [Interested period of time]
Calling Request Entry Points > Type: U
Called Objects > Name: CL_MY_CLASS
Called Procedure > Type: METH
Example 2: Get all procedures that were used by a MY_TRANSACTION transaction today.
Specify the options for data analysis as follows:
Time Interval > Date: [today]
Calling Request Entry Points > Type: T
Calling Request Entry Points > Name: MY_TRANSACTION
- Choose Execute.
Based on the selection criteria, the ABAP Call Monitor generates a list of request entry points along with all ABAP procedures that have been executed within the selected time interval. Each entry in the list represents a monitoring data record, which you call drill down for viewing further details:
- Show Time Evolution – displays the daily time slices of monitoring data for the selected entry
- Show Calling Requests – displays the calling requests
- Show Called Requests – displays the called requests
- Displaying and Analyzing the Request Call Graph
The call graph option allows you to focus on the usage/dependency relationship between requests. For example, you want to know which programs call a specific transaction.
Steps:
- On the initial screen of transaction SCMON, click the Display Call Graph button or, alternatively, choose the corresponding menu item.
- In the Data Browser selection screen, specify the options for data selection.
Example: Get all requests calling the transaction MY_TRANSACTION during a period of time.
Specify the options for data analysis as follows:
Time Interval > Date: [interested period of time]
Called Request Entry Points > Type: T
Called Request Entry Points > NAME: MY_TRANSACTION
- Choose Execute.
