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.
All that is needed to get started tracking expensive and long SAP SQL Statements is to define the recovery activity in 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.
First, go Navigate to the IT-Conductor main menu → Support → Downloads and download and import the following IT-Conductor SAP Transport (v6.72 IT-Conductor Function Modules MS1K90492)
...
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
Navigate to the background utilization option on the targeted system’s menu and click on the “Background Utilization” icon → Overrides
...
You may choose to create an override from zero or create an override from a template
...
If you select “create override from template”, you’ll get a list of prepared templates to create a recovery activity.
Select “AppServer Background Utilization”
...
...
Go to XXX → Overrides
...
All that is needed to get started tracking expensive and long SAP SQL Statements is to define the recovery activity in the background job monitoring threshold override.
How to create threshold overrides?
https://docs.itconductor.com/users-guide/notifications/creating-threshold-overrides