Monitoring Long-Running Transactions (Draft)

In SAP systems, long-running transactions refer to business processes or activities that take a significant amount of time to complete. These transactions can have an impact on system performance and overall efficiency. If your SAP system is experiencing performance degradation, it may be due to the long-running job execution time that is caused by an expensive SQL statement. Other causes and side effects of long-running transactions can also show up in areas like waits, blocking, locks, memory bottlenecks, high process, and CPU utilization, and timeouts.

Create Override Threshold for long-running Background Activity

Getting started with monitoring expensive and long SAP SQL Statements is as simple as defining the recovery activity within the background job monitoring threshold override.

The first step is to download the functionality from IT-Conductor, this will enable batch job monitoring to display the ABAP SQL Statement that is currently being executed when the runtime threshold is reached.

1. Navigate to the IT-Conductor main menu → Support → Downloads and download and import the following IT-Conductor SAP Transport into the target SAP System (v6.72 IT-Conductor Function Modules MS1K90492)

2. After importing the role, you have to define the recovery activity that you want to monitor. In this case, let’s define a recovery activity for a background job

3. Navigate to Target System → Background jobs, then click on the Background jobs icon → Override

4. You may choose to create an override from zero or create an override from a template

5. Give the alert a descriptive name

6. On the object criteria, indicate the following

   1. Elapsed Time

   2. Target System (SID)

   3. Job Name you wish to track

   4. User who created the job

7. Set the threshold values and the alert message that will be displayed whenever the job elapsed time goes over the threshold. The message will display the objects selected on the object criteria section

8. Click on the Save icon

When an alert notification for a long-running job is generated, a recovery action activity is also triggered

Tracking In-Flight Time

You may track the time in which a background activity had gone over the previously established elapsed time as well.

1. Navigate to Target System → Background jobs → In-Flight Time