How to maintain and monitor background jobs via SAP - Basis Corner (2023)

The following document provides general procedures for creating, maintaining, and monitoring background (batch) jobs in SAP. The procedures explain the most basic and common activities. However, the creation and maintenance of SAP background jobs can become quite complex, and much of the detail is beyond the scope of this document.


All system maintenance personnel should review this document.


For more information the following sources are recommended:

BC - System Administration Guide, Chapter 4: Managing Background Processing

(Video) SAP Background Jobs

SAP Extended Help (Select Extended Help from the Help menu while in transaction)


Creating a Background (Batch) Job in SAP

  1. To create a background job in SAP, enter the Define Background Job screen by using transaction code SM36 or menu path System ® Services ® Background jobs ® Job definition.
  2. Enter a descriptive job name in the Job name field. See document 15020 for naming conventions and reference.
  3. Enter the background job priority in the Job class field. The different priority levels, from highest to lowest, are A, B, and C. The job class determines how the background jobs are queued. Jobs that are absolutely crucial should be classified as A, those that must run, but can be delayed without causing great disruption to operations should be classified as B, and jobs that the least imperitive to business functions (such as most reports, for example) should be classified as C.
  4. Enter the host (server) that will run the background job in the Target host field. Click the down arrow on the right side of the field to get a listing of possible entries. If this field is empty, the job will run on the host (server) that you are logged into.
  5. To schedule the background job, click on the Start time pushbutton. This will bring up the Start Time pop-up window.
  6. There are several scheduling options:
  • Immediate This option will be used on several occasions:

- When a job is run on request by a user.

- When a job fails and must be restarted.

- For some monthend jobs or jobs with dependencies on other platforms, they may need

(Video) SAP Basis - Job Monitoring

to be run when resources are available, or there predesessor jobs finish.

  • Date/Time The date and time the job will release. It may not start until resources are available. If a job is scheduled to be periodic, it will release at that time the next day, week, month, etc based on the selected period.
  • After job Jobs with dependencies will be scheduled to release upon completion of its predecessor. A status indicator may be checked. If it is, the successor job will only release if the predecessor finishes completeley.
  • After event Jobs may be set to release after pre-defined events are raised. These events can be coded into ABAP/4 programs.
  • At operation mode These jobs will release when operation mode switching completes. This would be useful if many batch jobs need to be released around the same time. They can be set to release when the operation mode switches a number of dialogue sessions to batch, ensuring adequate resources.

To schedule the background job according to one of the options, click the corresponding pushbutton at the top of the window. After the selection, the appropriate entry fields will become active in the window. The two most common options will probably be Immediate and Date/Time.

To schedule a background job to run immediately, click the Immediate pushbutton, and then the active Save button. No additional entries are required.

To schedule a background job according to a specific date and time, click the Date/Time pushbutton. Several fields will appear. Enter the desired values in the Scheduled start fields. Entries in these fields are required. The background job will be released at this data and time but may wait in a queue. To prevent a job waiting in the queue from running after a certain time, enter the desired values in the No start after fields. The values in the Date fields should follow the default format for the login ID used. (To determine this format, use transaction SU50 or menu path System ® User profile ® User defaults to see the user defaults.) The values in the Time fields should be in military format.

(Video) How to create a background job in SAP

When either the Immediate or Date/Time options are chosen, the Periodic job click box will appear at the bottom of the screen. Click this box if you want to run this job at periodic intervals. Options for periodic scheduling appear when the Period values pushbutton is clicked. The background job will run at periodic intervals after the first background job runs. In addition, a Restrictions pushbutton will appear. In the Restrictions window, there are several options. Click only on workdays to limit the days the job releases on. You limit these days by specifying a calendar at the bottom of the window. Separate calendars for Monday to Friday, Monday to Saturday, Everyday, and others will be created. One of four buttons must also be set. Always Execute will cause the job to releasee according to its period valued REGARDLESS OF ANY WORKDAY/CALENDAR RESTRICTIONS. This is the default value, but it should almost always be changed. Cancel Job will simply cancel the job on non-workdays. Move to previous day will release the job on the workday previous to the date determined by the period value. Move to next workday will release the job on the next available workday. To schedule a background according to the other options, use the F1 function key to obtain more information.

  1. After entering all the scheduling information, click the Save pushbutton. This will bring back the Define Background Job screen.
  2. Click the Steps pushbutton to bring up the Step List and Create Step 1 windows. These windows define the program(s) that will run in the background.
  3. To run an ABAP/4 program, click the ABAP/4 pushbutton.

10. Enter the name of the ABAP/4 program in the Name field and, if necessary, enter the variant in the Variant field. A variant specifies the set of parameters that an SAP program needs to execute. To get a list of variants that have been created for a program click the Variant list pushbutton. (Variants may defined in the ABAP/4 Program Development: Initial Screen using transaction code SE38 or menu path Tools ® CASE ® Development ® Program maintenance ® ABAP/4 development.)

11. When an ABAP/4 program uses write statements, these write statements are printed, rather than displayed on a screen , when the program runs in the background. The print job will use the print specifications of the login ID used. (To determine these specifications, use transaction SU50 or menu path System ® User profile ® User defaults to see the user defaults.) To change the print specifications, such as the printer, click the Print specifications pushbutton.

12. Note that external programs on the UNIX platform may be executed using the SAP scheduler. This will probably not be too common, but to do so, click the External program pushbutton. Enter the information in the Name and Parameter fields. For more information, use the F1 function key.

(Video) Process Chain Monitoring Part 1

13. Once the background program has been defined, click the Save pushbutton. This will save one “step,” which will now appear on the Step List screen.

14. A background job may execute more than one program. To specify additional programs, click the Create pushbutton on the Step List screen and repeat numbers 9 through 13 above for the Create Step 2 screen and so on. The Step List screen also allows the list of programs for a background job to be changed using the different pushbuttons at the top.

15. After the programs for a background job have been completely specified, click the icon with the green arrow to return to the original Define Background Job screen.

16. Click the Save (yellow folder) icon to save the background job definition and submit it.

(Video) Background Job, Debugging Background job - Day 8

Maintaining and Monitoring Scheduled Background Jobs

  1. To maintain or monitor SAP background jobs, enter the Select Background Jobs screen by using transaction code SM37 or menu path System ® Services ® Background jobs ® Job overview. The window is a selection screen. A listing of background jobs will appear according to this window.
  2. The following fields are available to query all background jobs.
  • Job name - To find a particular job, enter the job name in this field. To find all job names, enter *.
  • User name - To find jobs created by a particular user, enter the user ID in this field. To find jobs by all users, enter *.
  • Start From/To Date/Time - To find jobs with start times in a particular interval, enter the beginning of the interval in the From Date and Time fields and the end of the interval in the To Date and Time fields. The beginning or end of the interval may be left open. The values in the Date fields should follow the default format for the login ID used. (To determine this format, use transaction SU50 or menu path System ® User profile ® User defaults to see the user defaults.) The values in the Time fields should be in military format.
  • Start at event - To find jobs that were triggered by an event, enter the event in this field. Leave the field blank if it is not applicable.
  • Jobs Status - To find jobs with a particular status, select the click box associated with each status. More than one status may be chosen. Select all click boxes to get a listing of jobs, regardless of status. The statuses include:
    • Scheduled - This status applies to background jobs that have been defined by users who do not have the authority to kick them off. These jobs must be released by users who do have this authority or else they will not run at their start times.
    • Released - This status applies to background jobs that will run at their start times.
    • Ready - This status applies to background jobs that have been kicked off at their start times but have been queued to run.
    • Active - This status applies to background jobs that are currently running.
    • Finished - This status applies to background jobs that completed normally.
    • Cancelled - This status applies to background jobs that ended abnormally.
    • Jobs without start date - To find jobs without a start date, select this click box.
    • Jobs with previous job - To find jobs with previous jobs, select this click box.

The number of jobs selected will decrease as more criteria are chosen. To find more information on possible entries for each field, select the field and select the F1 function key.

  1. Once the selection criteria have been specified, click the Execute pushbutton. This will bring up the Job Overview: Alphabetic screen, which gives a listing of jobs that satisfy the criteria with the status of each job.
  2. By default, the jobs are listed alphabetically. To sort the list by different criteria, select Sort from the Edit menu.
  3. Click the Refresh pushbutton to update the information listed on the overview screen.
  4. To maintain a specific background job or obtain information about it, select the job by clicking its job name in the list. The following pushbuttons provide several options:
  • Job log - Click this pushbutton to display the results of a completed background job.
  • Display - Click this pushbutton to display general data about a job.
  • Release - Click this pushbutton to release a scheduled job. A user may schedule a job, but if the user does not have the proper authorization, the job remains in scheduled status. It will not run until, an authorized user has released it. Jobs created by authorized users are automatically released.
  • Spool list - Click this pushbutton to display a background job’s spool requests (print/fax jobs).
  • Steps - Click this pushbutton to display a background job’s Steps List (the programs that it will or has run).

Other options are provided in the Job menu. These include:

  • Schedule job - Select this to cancel, release, or repeat an existing job.
  • Copy - Select this to copy an existing job to a new one.
  • Delete - Select this to delete a job.
  • Change - Select this to change or modify the definition of a job that has not run yet.
  • Capture - Select this to capture a job that is currently running and run it in the current on-line session.
  • Cancel job - Select this to cancel a job that is currently running.


How do you schedule a background job and monitoring steps? ›

Select a Job Class priority of A for High, B for Medium, and C for Low. Define ABAP program, variant's details, etc. Click on Hourly/Daily/Weekly period to define the frequency of the job as per your requirement. Execute SM37 T-code Select specified job and press Job >> (Released >> Scheduled).

How do you set up background jobs in SAP What are the steps What are the Event Driven batch jobs? ›

Step1: Create event from transaction SM62.
  1. Give event name and description and press save button.
  2. Step2: Create a program that triggers this event by calling the FM 'BP_EVENT_RAISE'.
  3. In the initial screen give job name and job class and press "Start condition" button. ...
  4. Check the status of job created by the program.

What is Background Processing in SAP basis? ›

SAP background processing automates routine tasks and helps you optimize your organization's SAP computing resources. Using background processing, you tell the SAP System to run programs for you. Background processing lets you move long-running or resource-intensive program runs to times when the system load is low.

How do I monitor my SAP basis? ›

System monitoring involves proactive monitoring of application servers, CPU utilization, database space, monitoring log files, etc. To check the list of processes, go to Processes icon. To monitor update processes, use transaction code — SM13. In User field enter '*' and click on Execute.

Which command is used for running jobs in the background? ›

Explanation: nohup command allows running jobs in the background even when the user logs out of the system.

What are the 4 basic steps to monitoring? ›

Top 4 Project Monitoring Steps
  • Step 1: Designing an Efficient Plan For Monitoring. ...
  • Step 2: Designing Effective Report Management Mechanism. ...
  • Step 3: Recommendations For Project Improvement. ...
  • Step 4: Ensuring Guidelines And Recommendations Are Followed Accordingly.
13 Oct 2015

What are the 6 steps in the monitoring procedure? ›

  1. Step 1: Identify Program Goals and Objectives. ...
  2. Step 2: Define Indicators. ...
  3. Step 3: Define Data Collection Methods and TImeline. ...
  4. Step 4: Identify M&E Roles and Responsibilities. ...
  5. Step 5: Create an Analysis Plan and Reporting Templates. ...
  6. Step 6: Plan for Dissemination and Donor Reporting.

How do I get a list of background jobs in SAP? ›

Learn SAP ABAP A to Z - Practical Training
  1. Step 1 − Use transaction code — SM37.
  2. Step 2 − Use * in the Job Name column and select the status to see all the jobs created by this user. ...
  3. Step 3 − Upon execution, all the jobs that have been created by the mentioned user and match the selection criteria are displayed.

What is the Tcode for background job? ›

SAP Background Job Transaction Codes
1SM36Schedule background job
2SM37Overview of job selection
3SE38ABAP Editor
4XK15Create Conditions (background job)
59 more rows

How many types of background jobs are there in SAP? ›

Background jobs are classified into three categories

Class A (High/critical Priority): – Some tasks are urgent or critical and must be scheduled with class A priority job. Class A priority reserves one or more background work processes.

How do I run a background job in SAP manually? ›

  1. In the SAP GUI, enter the transaction code SM36 to open the Define Background Job window.
  2. In the Job name field, type a name of your choice. ...
  3. In the Job class field, leave C as value. ...
  4. Click the Start condition icon .
  5. In the Start Time window, click Date/Time.

How do I run a background report in SAP? ›

You can run program background in 3 ways.
  1. 1.In se38 --> enter program name >Menu bar >Program--> execute-->Background. Here selection screen will display for inputs.
  2. Programatically you can run by using FM. JOB_OPEN, JOB_SUBMIT, ...
  3. 3.In tcode SM36 you can schedule your job in background. But here no need to run daily.
5 Mar 2008

How do you debug a background job? ›

Go to Transaction SM50. From the tool bar "Program/session"->Program->Debugging. -->Catchjob . it will goto the active job in debugging mode.
Yes , it is possible to debug background job .
  1. select active job in sm37.
  2. type "jdbg" command in command field. ...
  3. Double click the job , it will go in debug mode.
28 Jan 2016

How do you process a background process? ›

In order to place a foreground proces into the background, we must first put the process to sleep, and then place it in the background. Execute the command to run your process. Press CTRL+Z to put the process into sleep. Run the bg command to wake the process and run it in the backround.

How do I monitor jobs in SAP? ›

You can configure job monitoring for a business process step.
  1. Open the Solution Documentation from the SAP Solution Manager Launchpad, using transaction SLAN, or by launching the Business Process Monitoring setup.
  2. Select your solution and open the production branch for setting up business process monitoring.

What are the types to monitor the SAP monitoring? ›

The following types of SAPGUI monitors are available:
  • SAPGUI Monitoring (ST02): Monitors buffer related metrics. ...
  • SAPGUI Monitoring (ST03N): Monitors application specific metrics. ...
  • SAPGUI Monitoring (ST04): Monitors database related metrics. ...
  • SAPGUI Monitoring (ST07): Monitors user distribution on the SAP system.

What are the monitoring tools in SAP? ›

These include SAP CCMS, Solution Manager (SolMan), Landscape Virtualization Management (LVM), SAP DBACockpit, SAP HANA Studio, SAP HANA Cockpit, including our 3rd-party solution SAP Management Packs for SCOM, and cloud-based IT-Conductor for SAP.

How do I run multiple background jobs? ›

You can use the & to start multiple background jobs. This will start multiple jobs running in the background. If you want to keep a job running in the background, once you exit the terminal you can use nohup . This will ensure that SIGHUP , is not sent to a process once you exit the terminal.

What are the 3 types of monitoring? ›

There are three basic categories of monitoring; technical monitoring, functional monitoring and business process monitoring.

What is a monitoring checklist? ›

The Monitoring Checklist is used at desk reviews and/or site visits to assess the performance of the grantees and during the competitive process to determine a past performance adjustment to the scores of the applicants.

What are the 4 types of monitoring? ›

Abstract. We describe and label four types of monitoring—surveillance, implementation, effectiveness, and ecological effects—that are designed to answer very different questions and achieve very different goals.

What are the 4 Golden signals of monitoring? ›

The answer is with the four Golden Signals: latency, traffic, error rate, and resource saturation. In this blog, we explain what the Golden Signals are, how they work, and how they can make monitoring complex distributed systems easier.

What are example monitoring methods? ›

Method of monitoring: Monitoring procedures may involve either in-line or off-line systems. In-line systems involve the taking of measurements during the process and may be either continuous, such as using an in-line thermometer or non-continuous for example by inserting a temperature probe into food.

How can I see all background jobs? ›

The jobs command will show any background jobs started within the current shell, usually by starting a background task with the & operator or ^Z bg (e.g. sleep 10 & ). If you want to see all of the background processes running on the system, you can use ps -e , or ps -eF to get some additional details.

What is the use of SP01 Tcode in SAP? ›

SP01 is used to monitor the spool requests based on statuses.

What is the use of SM66 Tcode in SAP? ›

The T-CODE SM66 is “Global servers work area”. That means it is having all the servers running with in an organization/company etc. When you again double click on any one of the server at that time is shows SM50 of that particular server.

What is the use of SM21 TCode in SAP? ›

Transaction code SM21 is used to check and analyze system logs for any critical log entries. The SAP System logs is the all system errors, warnings, user locks due to failed log on attempts from known users, and process messages in the system log.

What is SM35? ›

SM35 is used to run Batch input sessions. These sessions can be created via LSMW or any batch-input ABAP program. To run a session, select the session and press "Process".

What is SE38 in SAP? ›

SE38 is a transaction code in SAP Basis application with the description — ABAP Editor. On this page, you will find similar/related TCodes to SE38, Tables feeding data for this TCode, links to SAP documentation, Wiki and Help pages, discussion threads, and other resources.

How do I Tcode a background in SAP? ›

Click on “Program” from the menu bar. Click on “Execute in background” from the submenu. Make sure the Print Time is set to “SAP spool only for now”. Click on the “Continue” icon (green check).

What are different status of background jobs in SAP? ›

Only jobs with status Planned, Released, or Ready can still be modified, unreleased, deleted, or prevented from running.

What are the advantages of SAP background jobs? ›

Advantages of SAP Background Jobs
  • Users can schedule jobs any time and an infinite number of times.
  • SAP background jobs can decrease manual effort and automates the task.
  • It optimizes the SAP computing resources.
  • It can decrease the system load by scheduling a job in non-working hours.

Can we run BDC in background? ›

Call Transaction BDC Programs don't work in background mode (Schedule Job/Workflow), if you want BDC to work in background mode then you need to create a BDC with Session method. Session Method BDC will work in background mode.

Is cron job and background job same? ›

For that purpose, as a system administrator, you can define background jobs (for example, database clean-ups) which are executed without any need for user interaction. These jobs are typically referred to as cron jobs.

Does SAP do background checks? ›

Accurate Background, integrated with SAP® SuccessFactors® Recruiting, enables organizations to quickly order background checks and view results without leaving the SAP SuccessFactors platform.

How do I know if background job failed in SAP? ›

  1. Select Batch Jobs <repository> .
  2. Identify the instance of the job execution in which you are interested by the job name, start time, and so on.
  3. Under Job Information for that instance, click Error. The Administrator opens the Job Error Log page.

Can we debug active background job SAP? ›

Go to SM50, find the active job, and use Program/Session->Program->Debugging.

What is background process example? ›

A background process is a computer process that runs behind the scenes (i.e., in the background) and without user intervention. Typical tasks for these processes include logging, system monitoring, scheduling, and user notification.

How is background verification conducted? ›

It involves various checks in which the employer will go through your education records, past employer details, identity checks, resume checks and address checks. It is done once the candidate clears all the interview rounds and it takes up to 10 working days to carry out the process.

What are normal background processes? ›

Background processes are mini-programs that perform a specific task on your computer. They run without user input and are designed to complement other programs. These programs monitor your system, schedule updates, run backups, and provide other essential services.

How do you check a long running transaction in SAP? ›

The syslogshold table in the master database contains information about each database's oldest active transaction (if any) and Replication Server truncation point (if any) for the transaction log. This table is built dynamically when you query it.

How can you identify and troubleshoot a long running job? ›

How to troubleshoot a long running job
  1. Find the custom log file of the job.
  2. Look at the timestamp of the last log entry within the custom job log file.
  3. If the above timestamp is far from the current time, the job is most probably long running.

How do you debug a long run job? ›

How do you debug a performance issue or a long running job in Hadoop?
  1. Understand the symptom.
  2. Analyze the situation.
  3. Identify the problem areas.
  4. Propose solution.
24 Sept 2014

How do you perform a runtime analysis in SAP? ›

The runtime analysis provides an overview of the duration of your source code, from individual statements up to complete transactions. Choose SAP Menu Test Runtime Analysis or transaction SE30 to start the runtime analysis. On the initial screen, you will find the four main functions of this tool.

How many times SAP session open at a time? ›

Multiple SAP sessions - SAP ERP Tutorial

We can have up to six sessions open at one time. To open a new session, we go to the three lines in the top left corner, click and select new GUI window from the dropdown menu.

What is the use of SM51 Tcode in SAP? ›

Transaction code SM51 is to display a list of active application servers that have registered in the SAP message server. Further, you can manage & display the status, users, and work processes in all application servers belonging to the SAP System.

What is your daily task monitoring in SAP? ›

Monitoring SAP is a daily routine activity in which your IT SAP team (Basis team) is checking all processes, databases, servers, instance performance, system wide performance, logs, users, batch jobs, dumps and many other elements, to see what is running, waiting, stopped working or just behaving weird.

What are the five 5 techniques of troubleshooting? ›

Troubleshooting steps
  • Step 1: Define the problem. The first step of solving any problem is to know what type of problem it is and define it well. ...
  • Step 2: Collect relevant information. ...
  • Step 3: Analyze collected data. ...
  • Step 4: Propose a solution and test it. ...
  • Step 5: Implement the solution.
28 May 2021

What are the 7 troubleshooting steps? ›

Let's take a more in-depth look at each of these steps to determine what they really mean..
  1. Identify the Problem. ...
  2. Establish a Theory of Probable Cause. ...
  3. Test the Theory to Determine the Cause. ...
  4. Establish a Plan of Action and Implement the Solution. ...
  5. Verify Full System Functionality and Implement Preventive Measures.
6 Dec 2021

How do you debug background programs? ›

Option 1) Choose a job in transaction SM37. In addition, setting up a breakpoint at the point in the source code which you want to analyze when debugging. In SM37, enter JDBG in the OK code field, and press ENTER. The selected job is now started in debug mode, and the debugger initially stops in a system program.

How do I debug BDC in background mode? ›

Debug background Job. list of process running in the server. In order to debug the program go to Menu option: Program/Mode >Program >Debugging.

What is TCode SE30 used for? ›

The ABAP Runtime Analysis (transaction SE30) gives you one tool for solving two problems. You can measure performance and find bottlenecks. You can also analyze the program flow of your ABAP program.

What is the TCode for ABAP runtime analysis? ›

Start the ABAP Runtime Analysis (SAT) via System -> Utilities -> Runtime Analysis -> Execute or call directly the transaction “/nsat”.


1. Reduce downtime & monitor your SAP Applications anywhere with Solution Manager 7.2
2. SAP BASIS Certification -DB Administration PART14
(Reddy sri)
3. 034 Demonstration of Background Job Debugging
(ZAP Yard)
4. ERP SAP Basis - Net Weaver | AS ABAP Daily Monitoring - SAP Daily Monitoring Tcodes List |
(Edupedia World)
5. How to create a Background Job in SAP - SAP Batch Job Part 2
6. SAP Webinar Systems Reports Automation Document Enhancement Made Easy
(Manon LEMANS)
Top Articles
Latest Posts
Article information

Author: Kieth Sipes

Last Updated: 02/15/2023

Views: 6048

Rating: 4.7 / 5 (47 voted)

Reviews: 94% of readers found this page helpful

Author information

Name: Kieth Sipes

Birthday: 2001-04-14

Address: Suite 492 62479 Champlin Loop, South Catrice, MS 57271

Phone: +9663362133320

Job: District Sales Analyst

Hobby: Digital arts, Dance, Ghost hunting, Worldbuilding, Kayaking, Table tennis, 3D printing

Introduction: My name is Kieth Sipes, I am a zany, rich, courageous, powerful, faithful, jolly, excited person who loves writing and wants to share my knowledge and understanding with you.