×

Welcome to Knowledge Base!

KB at your finger tips

This is one stop global knowledge base where you can learn about all the products, solutions and support features.

Categories
All
ERP-SAP
Job & Automation Monitoring Setup & Configuration

Job & Automation Monitoring Setup & Configuration

Prerequisites

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.

Setup

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

Configuration

Option to Set Run Time and Delay Threshold in Monitoring

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.

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.

Configuration of Events

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

Housekeeping

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.

Troubleshooting

If the "Type" of a job or automation is missing, the reason is that run information exists without definition data.

In case of ABAP jobs, if the "Type" is missing for a small part of the jobs only (e.g. 1%), this could be a temporary issue, that disappears after one day as then resending is done. If the issue persists then the reason could be a bug in the data collector.

  • In case of an on premise ABAP system, make sure to have applied note SAP Note 3102288 and switch off the data collection for the job monitoring use case in transaction /n/SDF/ALM_SETUP and then switch it on again.
  • In case of a cloud ABAP system, the fix is automatically applied, so just switch off the data collection for the job monitoring use case communication arrangement SAP_COM_0527 and then switch it on again.

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.

Configuration to pause and restart data collection is offered from Job & Automation Monitoring, but depends on the availability of the implementation in the managed system or service. For ABAP based systems or services the availability is as follows:

  • SAP S/4HANA Cloud: Implementation is delivered as patch to cloud systems from 25th of January 2023 onward.
  • SAP S/4HANA and SAP Business Suite (SAP NetWeaver Application Server for ABAP (higher than 7.40)): Implementation is available with ST-PI 7.4 SP20 (RTC on 25 th of September 2022).

Note, that if the switch is disabled the status is determined based availability of job execution data from managed service (i.e. green, if job data received in the last 30 days).

Please check, if the prerequisite for exceptions to be collected for ABAP jobs is fulfilled:

  • ST-PI 7.40 SP20 or higher is implemented in the managed on-premise system
  • in /n/sdf/alm_setup use case Exception Monitoring is activated.
  • in the managed system using transaction CRIT "Auto-linking Applog-Handles for jobs" is activated
Assuming that a job / automation "failed" in the system / service for which you had created the event
  • Check that in the event configuration you have switched on
    • "Create Alert" and / or
    • "Send Email To"
  • If you have maintained filter criteria, check that
    • the value matches the value in the monitoring UI, if you use "Is" condition
    • you use the "Contains" condition, if you want to filter on parts of the value (and do no use * to indicate a pattern)
    • you enter only one value and if you need to consider several values you add the filter condition several times

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 a job as the rating does not change.

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 a new notification is sent on a "successful execution" after a "failed execution" as the rating did change.

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.

Customer Support

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

Job & Automation Monitoring - Content

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

Product Job / Automation Type Description
SAP S/4HANA Cloud

SAP Application Job

Application Jobs in SAP S/4HANA Cloud
SAP BTP ABAP Environment SAP Application Job Application Jobs in SAP S/4HANA Cloud
SAP Marketing Cloud SAP Application Job Application Jobs in SAP Marketing Cloud
SAP Integrated Business Planning for Supply Chain SAP Application Job Application Jobs in SAP Integrated Business Planning
SAP Intelligent Robotic Process Automation
SAP Intelligent RPA Job Jobs in SAP Intelligent Robotic Process Automation
SAP Build Process Automation SAP Build Automation Automation Jobs in SAP Build Process Automation
SAP SuccessFactors Employee Central Payroll SAP ABAP Job SAP ABAP Jobs (SM37)
SAP S/4HANA and SAP Business Suite SAP Application Job

Application Jobs in S/4HANA

SAP S/4HANA and SAP Business Suite SAP ABAP Job SAP ABAP Jobs (SM37)
SAP S/4HANA and SAP Business Suite SAP BW Process Chain SAP BW Process Chains
Read article
Job & Automation Monitoring Videos

Job & Automation Monitoring - Videos

How To Setup Job & Automation Monitoring

Set Up Application Monitoring for SAP S/4HANA Cloud and SAP Marketing Cloud

  • Prerequisites for this video:
    • Download SAP Cloud ALM service key
    • You need a user with the role SAP_BR_ADMINISTRATOR in the SAP Marketing Cloud tenant.

Set Up Monitoring for SAP S/4 HANA, SAP Business Suite or SAP Employee Central Payroll

  • Prerequisites for this video:
    • Download the SAP Cloud ALM service key
    • Find prerequisites in the ABAP system here

How to Configure Alerting for Job & Automation Monitoring

  • In this video, you will learn how to Set up Job & Automation Monitoring for SAP Intelligent Robotics Process Automation:
    • Set up the PUSH monitoring connection
    • Activate the monitoring data connection in SAP Intelligent RPA
    • Check the monitoring data collection in SAP Cloud ALM

How To Configure Job & Automation Monitoring

How to Configure Alerting for Job & Automation Monitoring

  • In this video, you will learn how to configure Job & Automation Monitoring:
    • Alerting for the key aspects of job execution
    • Notifications for a job monitoring alert

How To Use Job & Automation Monitoring

How to Use Job & Automation Monitoring for SAP S/4HANA and SAP Business Suite

  • In this video, you will learn:
    • How to get an overview on the job and automation situation for one or more systems
    • How to drill down into a failing job or automation execution
    • How to navigate from the central monitor to the failing execution in the remote service

How to Use Job & Automation Monitoring for SAP Intelligent RPA Jobs

How to Use Job & Automation Monitoring for SAP Intelligent RPA Jobs

  • In this video, you will learn:
    • How to get an overview on the job and automation situation for one or more systems or services
    • How to drill down into a failing job or automation execution
    • How to navigate from the central monitor to the failing execution in the remote service

Read article
Real User Monitoring

Real User Monitoring

Scope & Content

Scope

The purpose of Real User Monitoring is to provide transparency about the usage (executions) and the performance (response times) of user interactions . It supports the monitoring request executions from different platforms with a unified user experience using a common look-and-feel and handling pattern.

The basic concept is to get all user interactions and the relevant server requests which are the correlated in the Real User Monitoring application. Request executions are rated not based on fixed thresholds but on historical values.

Real User Monitoring shall help IT users and Business users to understand how often applications are executed and what is the response times for the end-users.

Content

Real User Monitoring in Cloud ALM collects front-end measurements and display these as  following types:

  • SAPUI5/Fiori
  • SAP Web Dynpro (available since SAP_UI 7.53)
  • SAPGUI for HTML (Web GUI) (available since SAP_UI 7.53)

Real User Monitoring in Cloud ALM collects back-end measurements and display these as  following types:

  • HTTP(S)
  • RFC(S) (only on-premise)
  • Dialog (only on-premise)
  • Web Service

Supported Solutions

  • SAP BTP ABAP Environment
  • SAP BTP Neo
  • SAP Business Suite
  • SAP Integrated Business Planning for Supply Chain
  • SAP Marketing Cloud
  • SAP S/4HANA
  • SAP S/4HANA Cloud
  • SAP S/4HANA Private Cloud Edition
  • SAP Sales & Services Cloud (Cloud for Customer)
  • SAP SuccessFactors Employee Central Payroll

Features

Overview

Overview of the performance metric for services in your scope and your favorites in the selected time range is displayed as the Apdex (Application Performance Index).

This is an open standard developed for measuring the performance of applications. For more information, see https://en.wikipedia.org/wiki/Apdex.

The page consists of two sections, for more information, see the in-app help of the sections:

In the Overview the development of the Apdex over time for the services in scope is displayed.

In the Favorites the Apdex for your favorites is displayed.

The rating is done based on historical values.


By clicking on a request type you navigate to the Request Overview with filtered settings.

Request Overview


The Request Overview provides for the selected time range.

  • Application (Fiori ID) or request name (URL for HTTPS)
  • Type (SAPUI5, HTTPS,..)
  • Number of red executions
  • Number of total executions
  • Average response time
  • Number of distinct users


By choosing the icon in the last column you drilldown and see further details which (user) actions have been executed.


By choosing the icon in the last column you drilldown and see further details at which timestamps the actions have been executed.

Analysis View

Analysis View provides flexible selection of metrics and dimensions for analysis and download functionality

Available metrics:

  • E2E Response Time
  • Backend Time
  • Network Time
  • Executions

Dimensions:

  • Application/Request Name
  • Request Type
  • User Name

Frontend Overview

In this page, the most important front-end usage and performance metrics for the following frond-end request types are displayed:

  • SAPUI5
  • Web Dynpro
  • Web GUI

Setup & Configuration

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

To help troubleshoot issues, check the Real User Monitoring Troubleshooting page.

Read article
Real User Monitoring Troubleshooting

Real User Monitoring Troubleshooting

This page contains some hints for troubleshooting when for example some pages or views are empty.

As starting point you should classify the problem:

  • Is it a general problem in the application that seems to affect all or several different parts of the application?
  • Or is it rather missing data on some particular views?

Missing Data

Is the configuration for managed system executed?

Is the communication arrangement for scenario SAP_COM_0527 created and :

  • Property Collect Performance Data is set
  • Job is scheduled on minute base
  • You have not entered a path under the scheduler i.e. the Service URL is like https://eu10.alm.cloud.sap:443/
  • Try to save the communication arrangement again

Setup with /SDF/ALM_SETUP

  • Has the setup been executed with transaction /SDF/ALM_SETUP?
    • When selecting the Destination and hitting enter the LMS ID should be displayed on the screen and in step 3 a green tick must be displayed.
    • Is the use case Performance Monitoring activated?

Scheduled Jobs

Are the scheduled jobs running?

  • Check SM37 for jobs with program name /SDF/CALM_SCHEDULER and User Name = *
  • Is it the right client?
  • In case data sis sent to multiple destinations the job name contains the destination name.
  • Is Job period correct? (<5 min).

Application Log

Problems during setup, data collection or push are logged in application log.

  • Check SLG1 for object /SDF/CALM

Time zone settings

Wrong time zone settings might be the reason for missing data.

Execute report RSDBTIME or TZCUSTHELP . If they report an issue like
ERROR: ABAP system timezone setting inconsistent!
ABAP system timezone (DB table TTZCU) is: CET
This is inconsistent with date and time of ABAP-Processor and database!

or
System time zone or UTC timer is incorrect.

Correct the time zone settings for that system(client).

Read article
Real User Monitoring Setup & Configuration

Real User Monitoring - Setup & Configuration

Prerequisites

Before you can set up Real User Monitoring in SAP Cloud ALM, you have to connect your subscribed SAP cloud services to your SAP Cloud ALM instance.

This is done by setting up the Landscape Management Service. Please follow the Setting Up Landscape Management guide in SAP Help  on how to perform the setup.

Setup

Connect Managed Services / Systems

Please follow the documentation below on how to connect the managed services and systems to SAP Cloud ALM.

After connecting the managed services and systems, you have to activate the Real User Monitoring data collection for the managed services or systems that use PULL data collection. This is described in the next section.

  • SAP BTP, ABAP Environment*
  • SAP BTP, Neo Environment
  • SAP Business Suite*
  • SAP Integrated Business Planning for Supply Chain*
  • SAP Marketing Cloud*
  • SAP S/4HANA*
  • SAP S/4HANA Cloud*
  • SAP S/4HANA private cloud edition*
  • SAP Sales & Services Cloud
  • SAP SuccessFactors Employee Central Payroll*

* To setup Real User Monitoring please follow the monitoring setup guide and make sure 'Collect Performance' is flagged.

Activate Real User Monitoring Data Collection

For services and systems that use PULL data collection, you will have to activate the monitoring data collection, after creating the endpoint in Landscape Management.

Currently the following services or systems use PULL data collection:

  • SAP BTP, Neo environment
  • SAP Sales & Services Cloud

To activate the data collection proceed as following:

  1. Open the "Real User Monitoring" application from the launchpad
  2. Add the relevant cloud service or system to the scope
    1. Open the scope selection
    2. Search for your service or system
    3. Mark the checkbox in front of the service or systems
    4. Click "Apply"
  3. Open the configuration panel, by clicking on the rack-wheel icon in the upper right corner
  4. Open the "Systems" panel and activate the data collection for your service or system by switching the slider from "OFF" to "ON"

Housekeeping

Under Configuration it is possible to specify the retention time in days for single executions (maximum 14 days) and aggregated executions (maximum 370 days).

After the configured days for single executions data is aggregated per hour for that dimensions:

  • Service
  • UI Application/Request Name
  • User Action
  • User Name

After the configured days for aggregated executions data is deleted.

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.

FAQ's

There is no direct impact on the end-users.

For ABAP based systems a job is scheduled collecting every few minutes (depending on the entered collection period) for each use case the data. These collections are started via aRFC if enough work processes (WP) are free. The runtime depends an the amount of data to be collected.

The user names are hashed in case that the user doesn´t have the role to access the sensitive data; Only the user has the role of Real User Analyst Sensitive or Real User Analyst Administrator is able to see the real user names.

The user actions are dependent of the application. Therefore all user actions are displayed per application.
In the Analysis View you can create your own query to display for example all executed applications and actions.

The percentage in the upper right corner is the percentage spent net in that component. Some requests are executed in parallel and some time is spent on network (between the boxes).

Customer Support

In case you encounter problems using or setting up Real User Monitoring in SAP Cloud ALM, please report an incident using one of the following components:

  • SV-CLM-OP-RUM - Real User Monitoring UI
  • SV-CLM-OP-PM – Performance Monitoring Service

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

Read article

Still Thinking?
Give us a try!

We embrace agility in everything we do.
Our onboarding process is both simple and meaningful.
We can't wait to welcome you on AiDOOS!