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.
...
The first step is to download and import IT-Conduction Conductor function module in form of SAP Transport, this will enable batch job monitoring in your SAP system and it will display the ABAP SQL Statement that is currently being executed when the runtime threshold is reached.
...
Navigate to the IT-Conductor main menu → Support → Downloads and download and import the following IT-Conductor SAP Transport Module into the target SAP System (v6.76.72 1 IT-Conductor Function Modules MS1K90492Module MS1K900554)
...
After importing the Transport, you have to define the recovery activity for the job you want to monitor. In this case, let’s define a recovery activity for a background job.
Navigate to Target System → Background jobs, then click on the Runtime gear icon → Override
...