You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

There are 2 steps to define a batch job:

  1. Create an entry in the batch job register.
  2. Create a confluence page for each job using the Batch Job Design template.

Batch Job Confluence page

  • The purpose of the batch job confluence page to to provide more execution details of the batch job which will be handed over to the support team to aid them in the administration and support. 
  •  The Batch Job Design template provides a guideline for the contents and writers can adapt the page and add more details. 
  • Job owners must create a batch job confluence page per job. 

Approval Process

The following diagram describes the approval process and document is approved after the tech review which will be carried out by Technology team. 

  1. Peer review is carried out by team members (same as functional specs)
  2. Tech review is performed by the technology team and the document is approved after this step.
  3.  During Tech review, the reviewer will also validate the entry in the batch job register.

FAQ

Teams responsible to setup batch jobs

This is dependent on the system.

  • Teams managing the respective SaaS applications will be responsible to schedule batch jobs in their respective systems. For example Ariba team will configure Ariba job.
  • Batch Jobs in S/4HANA will be managed by different teams depending on the type of batch jobs. Following is a guideline:
    • Basis team - SM36 Jobs
    • Functional Team - Standard SAP application jobs, Process Chains
    • Development Team - Custom SAP application jobs

Configuring Dependent Jobs

Dependencies are classified into 2 categories:

  • Within same system
  • Cross systems

Please list down the dependencies under the columns "Prerequisite Job(s)" and "Successor Job(s)" in the batch job register and also document details in the confluence page.

Within same system

Dependent batch jobs will be configured to run one after the other by the application's respective scheduler. 

For S/4HANA, Basis team will SAP events to trigger the dependent jobs. 

  • Prerequisite jobs will be configure to execute SAP standard job that triggers an SAP event as the last step.
  • Dependent job will be configured to start execution upon the SAP event.

Cross System

This will be managed on a case by case basis and might require further evaluation.

Monitoring

The actual monitoring method has not been determine but the following can be assumed:

  • System administrator will be notified or monitor for failed jobs.
  • An incident will be created and assign to the respective support team.

Notification (S/4HANA)

  • For SAP jobs, email notifications can be configured to send the job status or spool via emails.
  • For application jobs, SAP standard tile can be used to monitor the jobs.



  • No labels