Welcome to Knowledge Base!

This portal page describes the monitoring setup for SAP Business ByDesign tenants.

The following monitoring content is available for SAP Business ByDesign:

To perform the necessary setup steps in the SAP Business ByDesign, please refer to:

• Setup SAP Business ByDesign

To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.

Below you find category-specific information for the monitoring categories available for SAP Business ByDesign.

Please note:

• If an input help is available for the filter parameters, this input help is filled based on the messages and exceptions collected in SAP Cloud ALM so far.
• If no filter is set up for the data collection, all messages or exceptions will be collected for the category.

The following monitoring content is available for SAP Omnichannel Promotion Pricing

To perform the necessary setup steps in the SAP Omnichannel Promotion Pricing, please refer to:

• Setup SAP Omnichannel Promotion Pricing

To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.

Below you find category-specific information for the monitoring categories available for SAP Omnichannel Promotion Pricing.

Please note:

• If an input help is available for the filter parameters, this input help is filled based on the messages and exceptions collected in SAP Cloud ALM so far.
• If no filter is set up for the data collection, all messages or exceptions will be collected for the category.

The purpose of Job & Automation Monitoring is to provide transparency about the current status of automation processes regarding execution status, application status, start delay and run time . It supports the monitoring of automation processes (for simplification called “jobs” in the later text) that run on the different platforms with a unified user experience using a common look-and-feel and handling pattern.

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 understand easily the current status of the jobs executed. 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 service to support a more detailed analysis, e.g. in order to stop a not ending execution or to restart a failed execution.

Job & Automation Monitoring shall help IT and Business users to understand the success of the automation processes they are responsible for, cross all involved cloud services and systems.

On top of showing the current status and indicate exceptional situations, job analytics is offered for the different monitored aspects (e.g. runtime and exception trend reporting) so that critical trends can be discovered and downtimes avoided.

Job & Automation Monitoring in SAP Cloud ALM collects data for these job types:

• SAP Application Jobs
• SAP ABAP Jobs
• SAP BW Process Chains
• SAP Intelligent RPA Jobs
• SAP Build Process Automation Jobs

Job & Automation Monitoring in SAP Cloud ALM collects data for these solutions and products.

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

The Overview provides a summary status regarding job execution for the services in scope . It shows the status of the latest execution of every job with regards to the Execution Status , Application Status and Run Time . On top it displays the number of alert situations, i.e. jobs for which an alert had been created, that is not yet confirmed.

Clicking on card Automations with Technical Issues you are navigated to the list of jobs sorted by Execution Status. If you click on Automations with Application Issues or Automations with Performance Issues you are forwarded to the same list, sorted accordingly. On clicking on Automations with Open Alerts you are navigated to the list of open alerts.

If you directly navigate to the Monitoring view, then you get a status summary per cloud service , i.e. the status of the latest execution of every job with regards to the Execution Status , Application Status , Start Delay and Run Time . On top you see the number of monitored jobs and the number of alert situations.

By clicking on the Service Name, you are navigated to the list of jobs for a service sorted by Execution Status rating in a descending order. You see also ratings regarding Application Status , Start Delay , and Run Time . The summary rating of a job is the latest non-grey rating of the respective aspect. If you click on any of the rating icons, you are navigated to the list sorted by the corresponding aspect.

By clicking on a name , you can view the list of executions of the selected job sorted by planned start time.

By clicking on the information icon next to each execution, you can view further details and navigate directly to the job in the managed cloud service or on-premise system* by clicking on the Run ID value .

*Note: If you use a SAP Web Dispatcher please maintain the URL of the Web Dispatcher as Logon URL for the respective System in SAP Cloud ALM Landscape Management .

In Monitoring in the job list view you can filter the list for specific jobs and have the option to define this list as favorite. After you have created the favorite by pressing the * icon, go to the home page and set a speaking title and subtitle (via the star icon) for the card.

From the favorite card you can forward navigate to monitoring, namely to the list of jobs that you have defined as favorite.

Use the Analysis view to identify those jobs that have the longest response times and highest number of exceptions. A trend icon indicates, if the failure rate or response time is up or down in the time frame selected taking the mid point of the time frame as comparison point.

For any job it offers aggregated information on total and average run time, number of executions and number of failed executions (regarding Execution Status or Application Status ) and the resulting failure rate. By clicking on the arrow at the end of every line, you can drill down into various trend charts for the metrics.

Use the Exceptions view to check for exceptions of the services and systems in scope.

To get exception data collected in general please follow the instructions provided in Integration & Exception Monitoring. In case of issue with the view, please report it via component.

• SV-CLM-OP-EXM – Exception Monitoring Service

To get exception data collected related job exceptions, no additional configuration is needed as those are collected together with the job execution data. Currently the following job types are supported:

1. SAP Intelligent RPA Job executions send notifier execution failures and the job execution gets a red Application Status rating.
2. SAP ABAP Job executions send *
   • Job Log exceptions and the job execution gets a red or yellow Execution Status rating.
   • Application Log exceptions and the job execution gets a red or yellow Application Status rating.

On click on the rating icon you are forward navigated to the list of exceptions related to the job execution.

*Prerequisite: ST-PI 7.40 SP20 or higher is implemented in the managed on-premise system and in /n/sdf/alm_setup use case Exception Monitoring is activated.

Use the Alerting view to check the job execution related alerts for the services in scope. You can configure to get alerted, if a job has a red or yellow Executions Status , a red or yellow Application Status, if its Run Time or Start Delay exceeds a defined threshold.

As you can adjust the Alert Name you can indicate what you have configured, e.g. the filters used. In the alert Object Details the name of the job is contained. In the alert list UI, you can filter for the content of the object details, i.e. the job name.

Alerts are raised per job and alert type and contain all failed executions of a specific job. From the Run Id value, you can navigate to the corresponding job execution in the managed cloud service, just like from the job execution popup in the monitoring application.

Please note, that a downstream action (like email) is triggered when there is a change in the event rating (green to yellow / red, yellow to red / green or red to yellow / green). This means also, that no new notification is sent on consecutive failures of the same job as the rating does not change.

Below we list the most important use cases that Job & Automation Monitoring offers:

• See if there is a job, which latest execution
  • did not finish successfully
  • did not process its data successfully
  • started more than x minutes after the planned start time
  • had an exceptionally long run time
• See exception message details for a job execution (via drill down from Execution Status or Application Status into Exceptions view)
• See the status of a defined set of jobs (via Favorites )
• Get alerted and / or notified
  • if a job has a red Execution Status , which is the case, if it aborts/cancels
  • if a job has a yellow Execution Status , which is the case for ABAP jobs, if they write warnings or errors into the job log
  • if a job has a red or yellow Application Status , which is the case
    • if an ABAP or Application Job writes an error or warning into the application log message
    • if an SAP Intelligent RPA job execution has a notifier failure (see here).
  • if any job that executes a specific program fails (via event filter option “Job / Automation Executable Name”)
    
  • if a job runs longer than a threshold
  • if a job start delay is above a threshold
• Analyze
  • which jobs have long run time or a high failure rate
  • if there are jobs that deteriorate regarding run time or failure rate

For more details on prerequisites, setup, housekeeping, and customer support, please check the Job & Automation Monitoring -  Setup & Configuration page.

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 SAP Intelligent Robotic Process Automation please follow the configuration steps for job data push in your tenant as described here in SAP Help or here in more detail with some demo videos.
• for SAP Build Process Automation please follow the configuration steps for job data push in your tenant as described here in SAP Help or here in more detail with some demo videos.
• for ABAP based systems please follow the monitoring setup guides and make sure 'Collect Job Monitoring' is flagged.
  
  • SAP S/4HANA Cloud
  • SAP S/4HANA, private cloud edition (prerequisite is ST-PI 740 SP16 or higher and SAP Note 3102288 applied) *
    
  • SAP S/4HANA and SAP Business Suite (prerequisite is ST-PI 740 SP16 or higher and SAP Note 3102288 applied) *
  • SAP SuccessFactors Employee Central Payroll (prerequisite is ST-PI 740 SP16 or higher and note SAP Note 3102288 applied) *
  • SAP BTP ABAP Environment based products
  • SAP Marketing Cloud
  • SAP Integrated Business Planning for Supply Chain

* 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

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].

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 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:

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.

To configure events for 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 events of category

• Critical Execution Status: The event is raised, if the Executions Status of a job is rated red or yellow, which is the case if an execution aborts or finishes with errors or warnings in the job log.
• Critical Application Status: The event 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) or yellow in case of an application warning. You have the option to restrict the event on the Application Status rating.
• Critical Runtime: The event is raised if the run time of a job execution exceeds the threshold set by you.
• Critical Delay: The event is raised if the start-delay of a job execution exceeds the threshold set by you.

If you want events to be raised only for certain jobs you can make use of the filter options and specify the job name ("Job / Automation Name"), what is being executed ("Job / Automation Executable Name") or who is executing the executable ("Job / Automation Execution User"). The filter conditions for the different parameters are connected with AND for the same parameter with OR.

The filter options offered are "Is", "Is not" and "Contains". The entered value is interpreted as a string, if for example you want to get alerted

• for 2 distinct jobs, have two filter parameters "Job / Automation Name". Enter one job name into the 1st filter and the other job name into the 2nd filter (if you need to specify more job names use the + button to add filter parameters).
• for a group of jobs sharing a job name pattern, use the "Contains" option (do not use * to indicate the pattern)

To get alerted, make sure to switch on Create Alert and save. If you want to stop to get alerted, you can switch off the Event Action , or deactivate or delete the event in the list of events. Note that events are not raised for services, if those are in Maintenance or Disruption state (maintained in Business Service Management).

In order to send notifications for alerts to an email address

1. in Recipient Management the address needs to be registered
2. in Job & Automation Monitoring Event Configuration the email needs to be maintain in Send Email To

In SAP Cloud ALM 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 15 executions are kept, all from the last 3 days and all that are referenced in an alert.
• 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 365 days. You can change the default to a value between 30 and 750 days.

Note: If you have configured alerts, please ensure to confirm them. To avoid data growth only the last 100 alerted executions are kept.

Be aware that SAP provides you in fair usage concept 8 GB HANA memory per month. If you extend the given memory you might need to subscribe additional memory blocks with our BTP service SAP Cloud ALM memory extension.

In case you encounter problems using or setting up Job & Automation Monitoring in SAP Cloud ALM, please report an incident using the following component:

• SV-CLM-OP-JM  - Job and Automation Monitoring Service

Please select your SAP Cloud ALM tenant when reporting the incident.

Job & Automation Monitoring in SAP Cloud ALM for Operations is currently offered for following products.