Contact Us
×
How you can contact us:

Job & Automation Monitoring

Scope & Content

Scope

The purpose of Job & Automation Monitoring, which is available as of SAP Focused Run 3.0 FP02, is to provide transparency about the status of automation processes regarding Execution Status, Application Status, Start Delay and Run Time with the aim to offer these 4 core operations aspects for all kinds of (scheduled) automation processes (for simplification called “jobs” in the later text), that run on different platforms with a unified user experience using a common look-and-feel and handling pattern.

Job & Automation Monitoring replaces the Job Monitoring application that supports the monitoring of ABAP jobs only. See a high-level feature comparison with Job Monitoring here.

The basic concept is to collect individual job execution data into the central monitoring application, to correlate it with its job definition and evaluate every execution using historical data. The rating of the last (or latest) execution(s) is propagated to the job level and finally to the service level so that you can easily understand the current state of many jobs that are executed in the different systems. In case of issues with job executions, context-based navigation is offered from the job to the individual execution and finally a direct navigation to the corresponding job execution in the executing system (or service). This is for providing quick access for a more detailed analysis, for example to stop a not ending execution or to restart a failed execution.  

Job & Automation Monitoring shall help to understand the current state of the automation processes across all involved cloud services and systems. The aggregated historical data shall help to detect deteriorations to avoid downtimes. On top, in case of a SAP ABAP system it shall help you to efficiently monitor so called Standard Jobs, which are those jobs that are scheduled by the SAP S/4HANA Technical Job Repository (see SAP Note 2190119) or in lower releases by the SM36 Standard Job framework. 

 

Concept

Jobs and workflows are executed in the managed cloud services and on-premise systems. The individual executions are captured (start, end times, and status) by the local execution infrastructures this “normalized” run data is sent to SAP Focused Run, where the individual execution data is assembled and correlated with definition data. 

Content

Job & Automation Monitoring in SAP Focused Run collects data for these job types: 

  • SAP ABAP Jobs
  • SAP BW Process Chains
  • SAP Application Jobs
  • SAP Intelligent Robotic Process Automation Jobs

Supported Products

  • SAP NetWeaver Application Server for ABAP (higher than 7.40)
  • SAP S/4HANA and SAP Business Suite
  • SAP S/4HANA Cloud
  • SAP Intelligent Robotic Process Automation
  • SAP Marketing Cloud
  • SAP Integrated Business Planning for Supply Chain
  • SAP SuccessFactors Employee Central Payroll
  • SAP BTP, ABAP Environment

Features

Home Page

The Status Overview provides a summary regarding job execution for the systems in scope. It shows the number of systems and the number of automations ("jobs"). The jobs are rated based on the rating of the latest execution:

  • The Execution Status is rated green, if a job finished successfully and red, if the job execution did not finish, i.e., aborted. It is rated yellow, if a job finished with warnings or errors without aborting.
  • The Application Status is rated green, if a job successfully processed the application data. It is rated red, if e.g., an ABAP job execution writes errors into the application log and yellow, if there are warnings, but no errors.
  • The Start Delay rating is rated green, if the technical delay of a job (e.g., in case of an ABAP job the time passed until a job gets a work process assigned) did not exceed the threshold defined.
  • The Run Time is rated green, if the runtime of a job did not exceed the threshold defined.  

The Application Overview provides a card-based overview, with more details:

  • Latest Rating - All Jobs: Information on the number of jobs, where the last execution had an issue in the different aspects.
  • Latest Rating - Standard Jobs: Information on the number of standard jobs, where the last execution had an issue in the different aspects.
  • Jobs with open alerts - All Jobs: Information on the alert numbers per alert type.
  • Jobs with open alerts - Standard Jobs: Information on the alert numbers per alert type for standard jobs.
  • Missing execution of mandatory job: Information on the alert numbers in case of missing execution of a mandatory job.

In the Alert Ticker you see the most recent Job & Automation Monitoring alerts for the selected scope.

Please note that alerts, which are currently rated green are not shown in the alert ticker, whereas Job & Automation Monitoring considers all alerts that are not yet confirmed. Consequently, the alert number in the Status Overview section is typically higher than in the Alert Ticker.

Monitoring

The jobs are listed and rated regarding Execution Status, Application Status, Start Delay and Run Time. The rating reflects the rating of the respective aspect for the latest execution of the job.

  • The list of jobs is default sorted by Execution Status rating in a descending order. You can change the sort and filter the list of jobs.
  • The Column Open Alerts shows the number of not yet confirmed alert situations. By clicking on a number, you are navigated to the alert details.

To drill-down to a failed execution of a job in the remote system:

  • Click on a name, you view the list of executions for the selected job sorted by planned start time.
  • Click on the arrow at the end of the line, to view the run details regarding the executed actions (e.g., reports and variants).

  • Clicking on the information icon next to each execution, to view further details and navigate directly to the job in the managed system by clicking on the Run ID value.

Alerting

Alerts are raised for every distinct job definition name. You can get alerted, if a job execution has a red Executions Status, a red or yellow Application Status, a Start Delay or Run Time that exceeds the threshold that you have set.

The alert Additional Key contains the NameType and Context/Client of the job. If the alert has been defined for a group of jobs, the alert Additional Information contains the name of the job group. In the METRICS table you see the alerted executions of the job and have a direct link to the managed system like from the monitoring application.

Exceptions

In view Exceptions detailed information on exceptions is offered.

Exceptions Overview

The exceptions overview offers you for ABAP systems the exception categories offered are “ABAP Application Log” and “ABAP Aborted Jobs”. You can drill down into the details, i.e. to the single exception.

Exception Details Integrated with Job Executions

To get exception detail information from an ABAP managed system without specifying the SLG1 object and with a link to the corresponding job execution the prerequisite is ST-PI 7.40 SP20 (or higher). To get the collected exceptions transferred to the SAP Focused Run system you need to activate in Integration Monitoring configuration the monitoring of the category in the monitoring client (see more details in chapter Configuration).

With above points fulfilled, the collected exceptions get a correlator value so that from Job & Automation Monitoring navigation from a job execution to the related exceptions is possible. 

If there are exception details linked to a job execution, then this is indicated with a slightly changed icon as displayed below and on click on the icon you drill down to the exception messages and see their details. In case of ABAP jobs, the exceptions related to the Execution Status are those of category ABAP Aborted Jobs.

In case of ABAP jobs, the exceptions related to the Application Status are those of category ABAP Application Log.

Analysis and Trend Reporting

Analytical information is offered for the jobs regarding number of executions, failed executions and run time. The table is default sorted by Total Run Time. You can change the sorting and apply filters.

On clicking on the graph icon at the end of every line you are navigated to view Trend Graphs, where you can see the values over time.

The data presented is based on hourly aggregates. For a large time frame the hourly aggregates are summed up to daily values automatically for better readability. Via custom time frame you can restrict to a certain period in the past and via the resolution option in the top right corner you can switch between Hourly and Daily.

Prerequisites

  • In managed ABAP system ST-PI 700 SP31 (or higher) or 
  • In managed ABAP system ST-PI 740 SP16 (or higher) + SAP note 3102288 is implemented
  • SDA version is at least 1.59 (for download see here)
  • In SAP Focused Run System, the following SAP notes are applied (and manual actions executed):
    • 3276434 - FRUN 4.0 FP00 Job & Automation Monitoring back-end correction
    • 3276373 - FRUN 4.0 FP00 Job & Automation Monitoring front-end corrections

Setup

Activation of Job & Automation Monitoring Use Case

Flag and save the use case setting.

On activating Job Monitoring in SSI for an ABAP system job data collection is not automatically activated, but needs to be done manually for every system in the Job & Automation Monitoring application via configuration. If you want to automate this, please check for details in Configuration Guide 4.0 SP00 with Use Cases.

Collect Job Execution Information via Agent for Technical Systems

SAP ABAP Job and SAP BW Process Chain executions can be collected via the Simple Diagnostic Agent, by switching on data collection for the technical system. In the picture below for the top 4 systems data collection is activated. For the first 2 systems there are issues.

If you switch to "On" as default for job type SAP ABAP Job the job execution data is collected from all clients, but in the detail view you can restrict the ABAP job collection for specific clients and collect data for further job types. Currently SAP ABAP Job and SAP BW Process Chain are offered for Application Server ABAP.

Collect Job Execution Information via SAP Cloud ALM Push Proxy for Services

SAP Application Jobs from S/4HANA CE and SAP Intelligent Robotic Process Automation Jobs can be pushed to SAP Focused Run from the respective cloud services via the so-called SAP Cloud ALM Push Proxy.

Configuration

For a detailed description of use cases, please see see the corresponding chapter of the Configuration Guide 4.0 SP00 with Use Cases.

Configuration of Alerts

To configure alerting in case of job failures, expand the configuration pane and then access the Technical System or the Job Group for which you want to configure the alerts.

Job & Automation Monitoring alerts are raised for every distinct job name and job type as those are written into the “Additional Alert Keys” field. Consequently, if you do not maintain filter values in alert configuration all jobs of the system or job group are considered and an individual alert for every failing job is raised. 

If you adjust the alert configuration (for example restrict the jobs using the filter options), we recommend adjusting the Alert Name to describe, what is being monitored. Please avoid overlapping the filter conditions for same alert types to avoid redundant alerts.

Job & Automation Monitoring Alerting is integrated with SAP Focused Run downtime management, i.e., an alert for a job is not raised if the executing system is currently in a planned downtime.

 

Alert Types

The following Alert Types are offered:

  • Critical Execution Status: An alert is raised, if the Executions Status of a job is rated red, which is the case if an execution aborts or cancels. The option to get alerted only, if a job fails several times in a row is not enabled yet.
  • Critical Application Status: An alert is raised, if the Application Status of a job is rated red, which is the case if an execution produces an application error (for an ABAP job error in SLG1 log). You have the option to get alerted also for warnings, in this case the Application Status of a job is rated yellow.
  • Critical Delay: An alert is raised if the start-delay of a job execution exceeds the threshold set by you. The alert is not raised if the planned start time of the job falls into a planned down time.
  • Critical Runtime: An alert is raised if the run time of a job execution exceeds the threshold set by you.
  • Missing Execution of Mandatory Job: An alert is raised if the execution of a mandatory job is more than 15 minutes after the expected start time. A job can be set "mandatory" in section "Job Definitions", in the table that contains the recurring jobs.

Alert Filters

An alert is applied to all Jobs / Automations of the system for which the alert is activated unless you make use of the filter option to restrict the Jobs / Automations for example to those that an alert notification recipient is responsible for. For the filter values you can use the conditions "Is", "Is not" or "Contains".

  • Job / Automation Name: To restrict the alert to jobs or automations with specific names as displayed in the monitoring application.
  • Job / Automation Execution User: To restrict the alert to jobs or automations, where the executable is executed by a specific user. Take the value from field “Executed by” of the job from the monitoring application.
  • Job / Automation Executable Name: To restrict the alert to jobs or automation, based on what is being executed. Take the value from field “Executable” of the job from the monitoring application (in case of ABAP systems the field contains “<report>|<variant>”).
  • ABAP Client: To restrict the alert to jobs or automations that are running in a specific client.
  • Standard Job: To restrict to “Standard Jobs”. Jobs that are scheduled by the ABAP Job Repository or SM36 -> Standard Jobs get the attribute “Standard Job” with value “Yes”. In the future it is planned to offer this attribute for other products as well.
  • Mandatory Job: To restrict to “Mandatory Jobs”. Jobs that are flagged as mandatory in table Job Definitions get the attribute “Mandatory Job” with value “Yes” (if the filter option is not displayed, please run report REPT_AJM_ADD_DATA_CONT_TABLE)
  • Job type: To restrict the alert to jobs or automations of a specific job type.

Note: For the alert type Missing Execution of Mandatory Job and for those alerts that you create for a Job Group the filter option is different as in this case a defined set of jobs is considered. Therefore, instead of the above-mentioned filter options you can filter from that set of jobs. If you do not maintain filter values, the complete set of jobs is considered for the alert. 

Alert Settings

You can maintain the typical SAP Focused Run alert and notification settings:

  • Alert Severity: Set to a high value, if you want to get in the alert inbox a high priority assigned to the alert. Please note, that the current rating of the alert influences its priority, for example
    • if Alert Severity is set to 0 - Low, and Current Rating for instance is Red then - Alert Priority is set to Medium.
    • if Severity is 0 - Low, and Current rating is Green then- Alert Priority is set to Low.
  • Raise Alert: If “Grouped” is set then no new notification is sent out on consecutive occurrences of the alert situation (Example: job cancels 5 times in a row, then only for the first failure a notification is sent).
  • Automatic Alert Confirmation: If the flag is set, an alert gets confirmed automatically, if a succeeding execution of the same job did not raise the alert.
  • Notification Variant: Enter the variant that shall be used when triggering a notification. If no value is entered, the global variant will be used, if that is maintained.
  • Outbound Variant: Enter the variant that shall be used when triggering an external incident system via outbound connector BADI. If no value is entered, the global variant will be used, if that is maintained.

Alert Resolution

The alert resolution text is copied over to the alert instance. A default text is offered, that you should adjust, to describe the actions that you want the alert processor to do before turning to an expert.

Option to flag Jobs as Mandatory

Prerequisite to get alerted if a scheduled job does not run any more is to flag such a job as mandatory and make sure, that it has a recurrence value.

If you expect a job to run in a system unchanged (with the defined executables and with the defined periodicity) after you have scheduled it, please flag it as mandatory in Configuration in view Job Definitions, which lists all recurring jobs. 

Once you have flagged a job as mandatory, it stays in table Job Definitions also if it has been changed or deleted in the managed system. With alert type Missing Execution of Mandatory Job you can get alerted, if the execution of the job is overdue.

For example, you need to make sure that 2 jobs are running unchanged after system setup. As part of system configuration activities, you have

  1. changed the variant of a standard job A and adjusted its periodicity.
  2. scheduled a job B.

Both jobs are scheduled, and you want to get alerted if these jobs are not running as expected. For this you flag job A and job B in table Job Definitions as mandatory and create an alert of type “Missing Execution of Mandatory Job” and filter for job A and job B.

An alert will be created if the execution of the jobs is overdue. This will be the case, if

  1. the job is changed (for example the name of the variant changes) as the data collector will create a new hash ID for the job and not send job data for the former ID anymore.
  2. the job is deleted
  3. the job is scheduled to run less frequently (as the job will be recognized as overdue).

Option to Create Job Groups

Job & Automation Monitoring collects by default all ABAP job executions from the managed systems. Also, for BW Process Chains all chain executions are collected. This is done to give you a holistic overview on the current situation and on trends. If you are responsible for a subset of jobs, you can create Job Groups and launch the application for one or more Job Groups and also configure alerting for the jobs of a group. 

You can create job groups in Configuration, add jobs to the group and define alerts for the jobs.

Option to Set Run Time and Delay Threshold in Monitoring

Once job data is loaded from the managed system, you see that Execution Status, Application Status, Start Delay and Run Time are rated. The rating is set according to Rating Rules, for which you can adjust the thresholds for Start Delay and Run Time. Such a change is applied only to the user session, it is not (yet) possible to save the setting.

Option to Set Name of Job with Changing Name

In case of the ABAP job scheduler there is no job definition with a unique ID. When scheduling a job the user defines what shall be executed, gives a job name and on save this entity gets a run ID. The job name does not need to be unique as together with the run ID it is unique for the ABAP system. At execution of the job the next occurrence is determined, and the job data is copied to the next due date and gets a new run id value.

To be able to group the executions of a job for Job & Automation Monitoring a stable ID is formed by the data collector as a hash value:

 ID

 Hash of

 JobId

 jobname + client + number of steps + job metadata[(step no + program + variant)]

 

If a job constantly changes its name (e.g. job name contains a time stamp), the formed JobId hash value is not stable, which does allow to group executions under one JobID. To enable the grouping for such a case, the JobId hash value is formed without the job name and on the monitoring UI, such a situation is indicated as follows:

In such a case, please give the job a name that represents all related executions (by pressing the pencil icon).

Note: Several ABAP jobs that have changing names and that execute the same (i.e. client + number of steps + job metadata[(step no + program + variant)] are identical), cannot be distinguished by the monitoring application. 

Option to Get Application Status Rated for ABAP Jobs

For SAP ABAP jobs in many cases the rating of the Application Status is grey. This is normal, if the job does not write any application log messages. To ensure that application log messages that are written during batch execution of a program are linked to the job execution you need to do following configuration:

  1. call transaction CRIT
  2. add "Auto-linking Applog-Handles for jobs"
  3. activate the profile

Please note, that with "Option" [=] the value * will be interpreted as *. For patterns make sure to use "Option" [x].

Option to Collect Exception Messages from ABAP Application Log and Job Log

Any Job Log abort or ABAP Application Log warning or error that is raised by the job execution is collected on the managed system (from all clients) by job monitoring data provider using function /SDF/E2EEM_FEED_LOGS_OF_JOB (prerequisite ST-PI 740 SP20 and higher). To get the message details transferred to the SAP Focused Run system, it is necessary to activate the corresponding agent. This can be done in Integration Monitoring configuration, by configuring category ABAP Aborted Job for collection and category ABAP Application Log for collection for the client in which the job monitoring data collection runs (which is the default client)

Note, that for category ABAP Application Log the system expects you to fill a value for the Object filter, still all Application log exceptions raised at job execution will be collected.

To determine the default client for an ABAP system, check in Simple System Integration (SSI). In below example, for system FT4ADM the default client is 200.

Use Cases

  • Have an overview on the current status
    • of all jobs executed in one or more systems
    • of a list of jobs across several systems (via job groups)
  • Get alerted and notified
    • if any job aborts in a system (using alert type Critical Execution Status)
    • if a standard job fails (using alert filter Standard Job)
    • if a "mandatory" job fails (using alert filter Mandatory Job)
    • if a job from a list of jobs fails or runs too long (using alert filter Job Name or by creating alerts for a Job Group)
    • if an ABAP job writes critical application log messages (using alert type Critical Application Status)
    • if a job does not run any more (using alert type Missing Execution of Mandatory Job)
    • if jobs that execute a specific report fail (using alert filter Job Executable)
  • Analyze
    • which are the long running jobs and check if they deteriorate
    • for a job, if there are times with high run time or high failure rate

For a detailed description of use cases, please see see the corresponding chapter of the Configuration Guide 4.0 SP00 with Use Cases.

Housekeeping

In SAP Focused Run Job & Automation Monitoring data reorganization is as follows:

  • the data of individual executions are kept for monitoring depending on job frequency and deleted with a default rule that you cannot change. The rule is, that for every job at least the last 14 executions are kept, all from the last 24 hours and on top all failed executions for 3 days. 
  • jobs that are deleted in the managed service (that are not scheduled any more) are removed from the database after 2 weeks together with the related executions and schedules.
  • the data of individual executions are aggregated for analysis and deleted by default after 52 weeks. For changing the default to a value between 4 and 150 weeks navigate to Configuration -> Global Settings.

Note: Please ensure to confirm alerts as alerted job executions are not removed from the data base.

Troubleshooting

You have switched on data collection for a technical system of Type Application Server ABAP, but the status of data collection stays "in progress" for more than 15 minutes or switches to "failed”. 

Background: By switching on data collection for a managed system you have implicitly created a filter for job type SAP ABAP Job and will collect job data from all clients. You might have explicitly created filters, for example to collect ABAP jobs only from a certain client or collect BW process chains. The following artifacts need to work for the collection to happen

  1. Job SAP_FRN_JAM_DATA_COLLECTION is running 
  2. In remote ABAP system needed ST-PI + notes (see prerequisites) are applied.
  3. Agent version needs to be >= 1.59
  4. In Agent Administration for the technical system (see in Configuration Information)
    • the following files are received from SAP Focused Run for creation or deletion of threads based on activation or deactivation of filters in monitoring configuration
      • com.sap.solman.agent.jobmon.housekeeping
      • com.sap.solman.agent.jobmon.metadata
      • com.sap.solman.agent.jobmon.runtime
    • the following threads have been created (see in Agent Internals in tab Collector Framework)
      • in case of ABAP job monitoring
        • jobmonhousekeeping [<<FRUN SID>>.JOB_ABAP_HOUSEKEEP_OP_<<host>>_<<LMDB ID of managed system>>] Period [86400 S]
        • jobruntime [<<FRUN SID>>.JOB_ABAP_RUNTIME_OP_<<host>>_<<configuration ID of filter>>] Period [300 S]
        • metadata [<<FRUN SID>>.JOB_ABAP_METADATA_OP_<<host>>_<<LMDB ID of managed system>>] Period [300 S]
      • in case of BW Process Chain monitoring
        • jobmonhousekeeping [<<FRUN SID>>.JOB_BW_HOUSEKEEP_OP_<<host>>_<<LMDB ID of managed system>>] Period [86400 S]
        • jobruntime [<<FRUN SID>>.JOB_BW_RUNTIME_OP_<<host>>_<<configuration ID of filter>>] Period [300 S]
        • metadata [<<FRUN SID>>.JOB_BW_METADATA_OP_<<host>>_<<LMDB ID of managed system>>] Period [300 S]

If there are exception like “Empty CSRF token” in the threads the reason could be that the properties file is outdated (job monitoring had to update the custom properties). In order to make the agent use the new properties you need to manually reconfigure and restart the agent using the Agent Administration and selecting the technical system or Host.

  1. Re-configure the SDA (to push the updated Properties files to the system)
    • Via the Mass Action drop down 
      • select Configure Agent
      • Press Go button
  2. Re-start the SDA (once the Agent configuration has completed):
    • via the Agent Action drop down
      • select Restart Agent
      • press Go button

Issue: In the Additional Alert Key we see job name FRN_ARP_0000001242. However, this job does not exist. The actual job names, that we see in SM37 are:

  1. FRN_GP_C2022111514563629923_001
  2. FRN_GP_C2022111514563629923_002
  3. ...
  4. FRN_GP_C2022111514563629923_012
  5. ...

Answer: As explained in the Configuration section under Option to Set Name of Job with Changing Name: In case of the ABAP job scheduler there is no job definition with a unique ID. To be able to group the executions of a job for Job & Automation Monitoring a stable ID is formed by the data collector as a hash value that contains the job name. If a job constantly changes its name (e.g. job name contains a time stamp), the formed JobId hash value is not stable, which does allow to group executions under one JobId. To enable the grouping for such a case, the JobId hash value is formed without the job name and on the monitoring UI you have the option to give to such a job a name that represents the group of jobs. It is this name, that will be used at alert creation.

Still forward navigation from the alert details via URL to the job in the managed ABAP system is supported.

In SM37 all jobs are displayed, whereas in the monitoring application jobs that execute report RSPROCESS are not displayed. The reason is, that those jobs are elements of BW Process Chains. They are displayed as executables of the related BW Process Chain (job type SAP BW Process Chain).

With note 3102288 (version 31) parent PPF jobs are collected, but not the child jobs that execute reports RBANK_PROC_START or RBANK_PROC_END. Those child jobs are consequently invisible in the monitoring application. The reason for not collecting their execution data is, that the parent job runs until all child jobs have finished and if any of the child jobs fails, the parent job has a message in its job log. If the collector (as of ST-PI 7.4 SP20) finds such messages, it rates the parent job yellow.

There are ABAP jobs, that write messages of type E (Error) or W (Warning) into the job log, without actually aborting. To indicate such a situation the job monitoring application rates such job executions with yellow Execution Status rating.

If you can see jobs being collected, but not those that run more frequently than every hour probably there is a one-hour difference between system time and the time in the system time zone. 

Please check this and make sure to set the system time zone (via transaction /nstzac), so that it matches the system time.

Release Notes

  1. Initial Version

Detail information available in Configuration Guide 3.0 FP02 with Use Cases.

  1. Pattern support for alert filters Job Name, Execution User and Executable Name
  2. New Alert Type Missing Execution of Mandatory Job
  3. New view Analysis offering summarized information on
    • number of executions
    • number of failed executions
    • total and average run times 
  4. New view Trend Reporting offering trend information (based on hourly aggregates) for individual jobs regarding
    • number of executions
    • number of failed executions
    • total and average run times
  5. Option to monitor via SAP Cloud ALM Proxy cloud jobs like
    • SAP Application Jobs in SAP S/4HANA Cloud
    • SAP Intelligent RPA Jobs    

Detail information available in Configuration Guide 3.0 FP03 with Use Cases.

  1. Alert filter option Mandatory Job
  2. Optimized usage of the application for a group of jobs
    • you can create groups and assign jobs from different systems
    • you can efficiently configure cross system alerts, by defining them for a group of jobs
    • you can access the monitoring application for one or more groups (for better focus and performance)
  3. Report REPT_MIGRATE_JOBMON_TO_JAM for migrating monitoring rules of Job Monitoring to Job & Automation Monitoring
  4. Report REPT_ADD_JOB_TO_MANDT_JOBS for condition based update of mandatory jobs
  5. Report REPT_ADD_JOB_TO_GROUP for condition based adding of jobs to a job group
  6. Detail information on exceptions at job execution
    • drill down into exception messages related to an individual job execution, i.e. from job metrics Execution Status and Application Status
    • with ST-PI 7.40 SP20 (or higher) exception messages at ABAP job execution are collected

Detail information available in Configuration Guide 4.0 SP00 with Use Cases.