-
Technical Assistance
Request product support from SAP
-
Non-Technical Assistance
Request non-product support or provide feedback on SAP Support Portal site
Technical Assistance
Request product support from SAP
Non-Technical Assistance
Request non-product support or provide feedback on SAP Support Portal site
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 will replace 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 to the related job definition and evaluate every execution using historical data. The rating of the last execution is propagated to the job level and finally to the service level so that you can easily understand the current status of many jobs that are executed in the different systems. In case of issues with job executions, context-based navigation is offered from the aggregate to the individual job execution and finally a direct navigation to the corresponding job instance in the executing system (or service) to provide 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 status of the automation processes, cross all involved cloud services and systems. The aggregated historical data shall help to detect deteriorations to avoid downtimes. In case of a SAP ABAP system it shall help you to efficiently monitor Standard Jobs, which are those jobs that are scheduled by the SM36 Standard Job functionality or in SAP S/4HANA systems by the Technical Job Repository (see SAP Note 2190119).
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.
Job & Automation Monitoring in SAP Focused Run collects data for these job types:
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 Application Overview provides a card-based overview, with more details:
In the Alert Ticker you see the most recent Job & Automation Monitoring alerts for the services in scope.
Please note that alerts that currently rated green are not shown in the alert ticker, whereas Job & Automation Monitoring considers all alerts that are not confirmed. Consequently, the alert number in the Status Overview section is typically higher than in the Alert Ticker.
To drill-down to a failed execution of a job in the remote system:
Alerts are created for every distinct job name and job type. You can get alerted, if a job has a red Executions Status, a red or yellow Application Status, if it's Delay or Run Time exceeds a threshold that you have set.
The alert Additional Key contains the NAME, TYPE and CONTEXT of the job. In the alert details you see the alerted executions of the job and have a direct link to the managed system like from the job monitoring application.
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 can navigate to the trend graphs for the job.
Note that hourly aggregates are built for the data. In case of a large time frame this could lead to many data points and therefore the hourly aggregates are summed up to daily values automatically for better readability.
Flag and save the use case setting.
SAP ABAP Jobs and SAP BW Process Chains data is collected via the Simple Diagnostic Agent. To get this data collected for a technical system, you need to configure for it the data collection. In below picture for the top 3 systems data collection is activated. For the first system there are issues.
If you switch to "On", then by default for job type SAP ABAP Job the job execution data is collected from all clients. In the detail view you can restrict clients and collect data for further job types. Currently SAP ABAP Job and SAP BW Process Chain is offered for Application Server ABAP.
SAP Application Jobs from S/4HANA CE and SAP Intelligent Robotic Process Automation Jobs are pushed from the respective services via the so-called SAP Cloud ALM Push Proxy to SAP Focused Run.
Once job data is loaded from the managed system, you will see that Execution Status, Application Status, Start Delay and Run Time are rated. The rating is set according to the Rating Rules, for which you can adjust the thresholds for Start Delay and Run Time. Please note that this change is applied only to your session, it is not (yet) possible to save the setting.
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.
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:
In below example the linking is restricted to jobs executed in client 200. Please note, that with "Option" [=] the value * will be interpreted as *. For patterns make sure to use "Option" [x].
To configure alerting for specific jobs, expand the configuration pane and then access the system, for which you want to configure alerting.
Alerts are created for every distinct job name and job type as this information is written into the “Additional Alert Keys”. If you do not maintain filter values all jobs for a system are considered.
If you adjust the alert configuration adjust the Alert Name to describe, what is monitored. For example, if you restrict via filter an alert to specific jobs or set specific thresholds. If you configure several alerts of the same type, please avoid redundancies, i.e., overlapping the filter conditions.
Job Monitoring Alerting is integrated with SAP Focused Run downtime management, i.e., an alert for a job is created only, if the executing system is currently not in a planned downtime.
The following Alert Types are offered:
In the Alert Settings section you can find and maintain the typical SAP Focused Run alert and notification settings:
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.
Mandatory jobs are those jobs, that you expect to run in a system just like you have scheduled them (with the defined executables and with the defined periodicity).
In view Job Definitions all recurring jobs are listed and you have the option to flag them “Mandatory” via the button above the table. With utility report REPT_ADD_STD_JOB_TO_MANDT_JOBS you can set all standard jobs “mandatory” for a specified system (ExtendedSID).
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 and consequently 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
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
* possible as of SAP Focused Run 3.0 FP03 by defining one or more jobs as mandatory and configuring the (new) alert type "Missing Execution of Mandatory Job"
** possible as of SAP Focused Run 3.0 FP03 via the (new) view "Analysis" and the (new) view "Trend Graphs")
In SAP Focused Run Job & Automation Monitoring data reorganization is as follows:
Note: Please ensure to confirm alerts as alerted job executions are not removed from the data base.
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
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.
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:
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.
Detail information available in Configuration Guide with Use Cases.
Detail information available in Configuration Guide with Use Cases.