Job & Automation Monitoring Details


You need to have the role / authorization for Job and Automation Monitoring in SAP Cloud ALM and job data needs to be pushed from your cloud services as described below. 


SAP S/4HANA based Application Jobs are used in various SAP products (like SAP Integrated Business Planning, SAP Marketing Cloud and SAP S/4HANA Cloud, essentials edition). For job data of this job type to be pushed in the managed S4HANA Cloud service you need to activate scenario SAP_COM_0527 'Application Monitoring Push Integration' and make sure to have 'Collect Job Monitoring' flagged.

SAP Intelligent Robotic Process Automation Jobs data is pushed after doing some configuration steps in your iRPA tenant as described here in SAP Help.


In order to configure alerting for specific jobs, you need to have role Job Monitoring Administrator assigned. Expand the configuration pane and then access the service, for which you want to configure alerting.

Per service you can define alerts of category Critical Execution Status or Critical Application status.

In order to specify, which jobs should be considered for the alert you can specify job name, executing user and the name of the job executable. The filter conditions for the different parameters are connected with AND for the same parameter with OR.

On saving, the alert is activated. If you want to deactivate, but not yet delete an alert, switch it off.

In order to adjust the rating of the Start Delay and Run Time metric in the Job & Automation Monitoring application role Job Monitoring Consumer is sufficient. Below you see the default settings. Note, that the setting is not persisted, i.e. if you relaunch the application the default will be applied again.



In SAP Cloud ALM job data is reorganized with a default rule that you cannot adjust: For every job at least the last 15 executions are kept and all failed executions for 3 days. Jobs that are deleted in the managed service, i.e. that are not scheduled any more, are flagged as deleted in SAP Cloud ALM and removed from the database after 2 weeks together with the related executions and schedules.

Note: If you have configured alerts, please ensure to confirm alerts as job executions with open alerts are not removed from the data base.

Customer Support

In case you encounter problems configuring or using SAP Cloud Application Lifecycle Management, please report an incident using one of the following components:

  • SV-CLM-OP - SAP Cloud Application Lifecycle Management for Operations Services
    • SV-CLM-OP-AEM - Alert and Event Management Service
    • SV-CLM-OP-JM  - Job Monitoring Service
    • SV-CLM-OP-LMS - Landscape Management Service
  • SV-CLM-INF – SAP Cloud Application Lifecycle Management Cross Topics
    • SV-CLM-INF-ONB - Onboarding and Decommissioning process
    • SV-CLM-INF-UAM - User Access Management

Please select one of your SAP Cloud Platform Integration Systems when reporting the incident.