There are no prerequisite steps to be done in SAP Cloud ALM. You need to have the role / authorization for Job Monitoring in SAP Cloud ALM, and you need to configure in your SAP cloud service(s) the push of job execution data as described under "Setup" below. This initial one-time activity needs to be done in every monitored service.

• for ABAP based systems please follow the monitoring setup guides and make sure 'Collect Job Monitoring' is flagged.
  
  • SAP S/4HANA Public Cloud
  • SAP S/4HANA Private Cloud Edition (prerequisite is ST-PI 740 SP16 with note 3102288 applied)
  • SAP S/4HANA On-Premise Edition (prerequisite is ST-PI 740 SP16 with note 3102288 applied)
  • SAP Business Suite (prerequisite is ST-PI 740 SP16 with note 3102288 applied)
  • SAP Marketing Cloud
  • SAP Integrated Business Planning for Supply Chain
• for SAP Intelligent Robotic Process Automation please follow the configuration steps for job data push in your tenant as described here in SAP Help.
  

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, Critical Application Status, Critical Runtime and Critical Delay. If you want alerts to be created only for certain jobs you can specify job name, executing user and the name of what is being executed. 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 stop to get alerted, you can switch off the alert or delete the configuration.

In the Monitoring UI jobs are evaluated with a default Rating Rule that you can adjust, if you have role Job Monitoring Consumer. Please note, that the setting is not persisted, i.e. if you relaunch the application the default will be applied again. Below you see the default settings.

In SAP Cloud ALM Job & Automation Monitoring data is reorganized with a default rule that you cannot change. The rule is, that for every job at least the last 15 executions are kept and on top 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 alerted job executions are not removed from the data base.

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 and Automation 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.