SAP Batch Jobs Monitoring
Background
SAP Batch Job is a scheduled program that runs without user intervention. It is frequently used to automate tasks that need to be performed on a regular basis. This process runs in background to process a huge quantity of data in batches rather than separate transactions.
Batch jobs are less visible to the end-users because they run in background. Activating alerts will allow the users to regularly check if the batch jobs have run successfully or in case of any failure be able to identify the root cause of any error in the failed stages.
On This Page
IT-Conductor Job Alert Subscription
IT-Conductor allows users and/or teams to subscribe to automated alerts. These alerts can be modified through the system and can be set to specific jobs via filters. IT-Conductor offers very flexible criteria to define when managing the alerts.
Below are simple subscriptions to CCMS job failure alerts:
In the IT-Conductor dashboard, navigate to the SAP Systems > SAP System Name > CCMS Alerts > Failed Batch Jobs. This will show the chart where the failed jobs are detected. By clicking on the graph, it will show the details of the failed jobs.
IT-Conductor can create thresholds based on the number of failed jobs per interval, that can raise IT-Conductor alerts when too many jobs failed within an interval.
With the ability to track job failures from CCMS alerts, IT-Conductor can also track specific failed jobs by any of the fields in the job details, such as name, user, server, or combinations.
Batch server performance for job processing is also monitored, by default, Batch queue utilization %.
IT-Conductor also supports multi-steps jobs via our own scheduler to be executed in SAP, which of course will allow us to monitor the job run time and job logs. Job performance like runtime, delays, and more can be set up by us for specific jobs or groups of jobs. These are called SLA.
For long-term reports on Job processing logs, we don't currently have a ready-made report, but it is simple to define a report and run them on a periodic scheduled to be stored in IT-Conductor and also be distributed to defined users via email HTML reports. We use SAP XBP (External Batch Processing) interface to monitor and manage jobs. Most objects in IT-Conductor can have a retention period set via template so they can be retained at the detail level if required, otherwise, the leaf nodes are expired but their reports of # counts will still be available for months/years just not in drill-down details unless we mark them with longer retention.
Related articles
Do you have a question about the content on this page? E-mail us at support@itconductor.com.