Objectives
Adam, now well-versed in the fundamentals of Application Jobs, including job types, statuses, templates, and layer codes, is aiming to schedule an administration job. GloManCorp’s IT security policy mandates that business users should be locked if they remain inactive for at least 180 days.
In this practice simulation, you learn how to create an administrative Application Job using a global pre-installed job template.
As an administrator, you want to create an administrative application job in SAP S/4HANA Cloud Public Edition. For this you use a predefined global application job template.
Many business activities have to be run periodically. To avoid starting these actions manually, SAP delivers application job templates for many business purposes. Typically, business users define a periodic start condition and set further parameter values for the application job execution.
There is no point in scheduling application jobs. Most of the offered application job scheduling apps are business-driven and called specialized application jobs apps, and can be accessed via the respective business area. Nevertheless, besides these apps, SAP delivers the general application jobs app as part of the Technical Monitoring. The intention of this app is the usage for administrative purposes.
When creating a business-related application job, different input values have to be provided in the flow of the application job wizard. A job template and a job name have to be selected as mandatory fields. Furthermore, the preferred scheduling options and the recurrence of the job can be defined. The core part of the application job definition covers the adjustment of application-specific parameters. Finally, you are able to let the system check if the entries are consistent. When almost done, the decision has to be made, whether you want to define it as a template or schedule the application job directly.
In this practice simulation you learn how to create a business-related Application Job using a shared custom job template.
In SAP S/4HANA Cloud Public Edition, a job log serves as a chronicle of activities for a running job. It becomes a valuable resource for diagnostic purposes when a job fails or exhibits unexpected behavior.
If an application job or a sequence of application jobs, which may comprise one or more steps, is marked as Failed, Canceled, or User Error, it can be re-initiated. To accomplish this, identify the job and select one of the following alternatives from the drop-down menu:
This option will bypass all steps preceding the error step and execute all subsequent steps (including the error step).
This option will bypass all steps up to and including the error step and execute all subsequent steps. Please note that this option is not applicable for jobs consisting of a single step.
The newly initiated job will be executed immediately under the original job user.
Adam explores how to modify the owner and user of application jobs that have been established from a job template. This is a crucial skill, especially in dynamic business environments.
For instance, consider a scenario where an employee gets promoted or transferred to a different department. In such cases, their previous responsibilities, including managing certain application jobs, may need to be reassigned to another individual. Similarly, if an employee leaves the organization, their associated business user account may need to be removed, and the jobs they were handling reassigned.
This ensures a smooth transition of responsibilities and maintains the continuity of important tasks within your organization.
Participate in the following practice simulation with Carl and Adam. This will help you understand how Carl takes over the administrative application job previously scheduled by Adam and sets himself as the new job owner.
As an administrator, you need to modify the owner and user of application jobs in dynamic business environments. For example, when an employee is promoted or transferred, you must reassign their job responsibilities to another individual. Similarly, if an employee leaves the organization, you may need to remove their associated business user account and reassign their jobs to another person.
SAP Cloud ALM - Job & Automation Monitoring is a central solution designed to monitor all SAP products, enhancing local job scheduling. It provides transparency about the status of various automation processes, including execution status, application status, start delay, and run-time. The system collects individual job execution data and related exceptions, rating the execution based on historical data. This rating is then propagated to the job definition level. Users can drill down from the job to the list of executions and navigate directly to the corresponding job instance in the executing service for detailed analysis.
Carl and Adam also discuss the fundamental aspects of Job and Automation Monitoring in SAP Cloud ALM. Adam often had to deal with this in his on-premise systems and would like to know what is available in SAP S/4HANA Cloud Public Edition.
The Overview serves as a comprehensive report on the status of job execution for the services we're focusing on. It details the latest job execution, highlighting Execution Status, Additionally, it shows the count of alert situations - jobs that have generated an alert but have not yet received confirmation.
Selecting a service card directs you to the Monitoring view, displaying jobs and automations sorted by Execution Status. Direct access to Monitoring shows jobs for all services, rated on Execution Status, Application Status, Start Delay, and Run Time. Each status is color-coded: green (successful), red (errors), and yellow (warnings). Clicking a name shows executions for the selected job or automation. The information icon provides more details and a direct link to the job via the Run ID.
The Analysis view is designed to help you spot jobs that are characterized by the longest response times and the maximum number of exceptions. A trend icon is available to signify whether the failure rate or response time has risen or fallen within the selected time frame, with the midpoint of the time frame serving as a comparison point.
For each job, it provides a comprehensive overview of key metrics such as total and average run time, number of executions, and number of failed executions (based on Execution Status or Application Status), as well as the derived failure rate. By clicking on the arrow at the end of each line, you can explore various trend charts for these metrics in more detail.
The Exceptions view monitors service and system exceptions. Job exception data is collected automatically during execution. Supported jobs include SAP Intelligent RPA and ABAP, which send failure notifications and exceptions affecting their ratings.
The Alerting view enables you to monitor and customize alerts for job executions. It evaluates job data every minute, providing almost immediate alerts for any anomalies. Each alert is specific to a job and includes all failed executions. The system triggers a downstream action at every new occurrence but can be configured to trigger at every occurrence.