---
description: This tutorial explains in detail background jobs processing in SAP. It gives steps to create/schedule and reschedule Background Job SM36
title: SAP Background Job Processing SM36
image: https://www.guru99.com/images/background-job-processing-1.png
---

[Skip to content](#main)

**⚡ Smart Summary**

Background job processing in SAP enables non-interactive execution of time-consuming programs behind normal operations, scheduled via SM36 and monitored through SM37. It supports three priority classes and six lifecycle statuses to ensure efficient workload management.

- 🔧 **Automation Benefit:** Background jobs eliminate manual effort by running resource-intensive programs during off-peak hours without user interaction.
- 📊 **Priority Management:** Assign Class A, B, or C priority to control execution order and allocate background work processes effectively.
- 📋 **Lifecycle Tracking:** Monitor job progression through six statuses — Scheduled, Released, Ready, Active, Finished, and Cancelled — using SM37.
- ⚙️ **Scheduling Precision:** Define start conditions, end dates, and periodic intervals to automate recurring job execution reliably.
- 🔄 **Deschedule Control:** Revert released or ready jobs back to scheduled status to prevent future execution when requirements change.

Read More

![SAP SM36 Transaction Code for Background Job Scheduling](https://www.guru99.com/images/background-job-processing-1.png)

## What is a Background Job in SAP?

A background job is a non-interactive process that runs behind normal interactive operations in an SAP system. Background jobs execute in parallel and do not disturb foreground processes or operations. They are scheduled using transaction code **SM36** and monitored through **SM37** by viewing job logs.

## Advantages of Background Jobs in SAP

- It reduces manual effort and automates repetitive tasks that would otherwise require user interaction.
- It can be scheduled as per the user’s choice, allowing flexible execution timing.
- It runs seamlessly in the background without requiring user input, freeing up the system for interactive work.
- Once you define the variant for a background job, the user does not have to worry about providing field values each time. This also reduces the possibility of input errors.
- It is ideal for time-consuming or resource-intensive programs, which can be scheduled to run during off-peak hours when system load is low.

|  | #1 BEST OVERALL [![GoFrugal]()](https://guru99.live/mmus9e) 9.8/10 ★★★★★ [Start Free Trial](https://guru99.live/mmus9e) | [![Xero]()](https://guru99.live/7sgags) 9.5/10 ★★★★★ [Visit Xero](https://guru99.live/7sgags) | [![Paychex]()](https://guru99.live/291q7y) 9.3/10 ★★★★★ [Visit Paychex](https://guru99.live/291q7y) |
| --- | --- | --- | --- |
| Best For | Retail & Distribution ERP | Online Accounting | Payroll & HR |
| Key Feature | *✓*POS, inventory & accounting in one | *✓*Invoicing & bank reconciliation | *✓*Payroll processing & tax filing |
| Also Includes | *✓*Cloud & mobile apps | *✓*1,000+ app integrations | *✓*Benefits administration |
| Free Trial | 30-Day Free Trial | 30-Day Free Trial | Get a Free Quote |
|  | [Start Free Trial](https://guru99.live/mmus9e) | [Visit Xero](https://guru99.live/7sgags) | [Visit Paychex](https://guru99.live/291q7y) |

#1 BEST OVERALL

1 [![GoFrugal]()](https://guru99.live/mmus9e)

9.8/10

★★★★★

Best For

Retail & Distribution ERP

Key Feature

*✓*POS, inventory & accounting in one

Also Includes

*✓*Cloud & mobile apps

Free Trial

30-Day Free Trial

[Start Free Trial](https://guru99.live/mmus9e)

2 [![Xero]()](https://guru99.live/7sgags)

9.5/10

★★★★★

Best For

Online Accounting

Key Feature

*✓*Invoicing & bank reconciliation

Also Includes

*✓*1,000+ app integrations

Free Trial

30-Day Free Trial

[Visit Xero](https://guru99.live/7sgags)

3 [![Paychex]()](https://guru99.live/291q7y)

9.3/10

★★★★★

Best For

Payroll & HR

Key Feature

*✓*Payroll processing & tax filing

Also Includes

*✓*Benefits administration

Free Trial

Get a Free Quote

[Visit Paychex](https://guru99.live/291q7y)

## Types of Background Job Priority Classes

SAP categorizes background jobs into three priority classes that determine execution order and resource allocation.

1. **Class A (High/Critical Priority):** Urgent or critical tasks must use Class A priority. It reserves one or more background work processes. Available processes for Class B and C = Total work processes (set in RZ03) minus processes reserved for Class A.
2. **Class B (Medium Priority):** Once Class A jobs complete, Class B jobs begin executing before Class C jobs.
3. **Class C (Low Priority):** Runs only after both Class A and Class B jobs have completed. Suitable for non-urgent, routine tasks.

## Possible Statuses of a Background Job

Every background job in SAP passes through a defined lifecycle. These statuses help administrators track job progress.

1. **Scheduled:** Program name and variant are defined, but start conditions (Start Date, End Date, Frequency) have not been specified. The job will not execute until start conditions are set.
2. **Released:** All required criteria are fulfilled including start conditions. The job is waiting for its scheduled start time.
3. **Ready:** All conditions are met, but the job is in a queue waiting for a background work process to become available.
4. **Active:** The job is running in the background. Its status cannot be changed once Active.
5. **Finished:** The job executed successfully without any errors.
6. **Cancelled:** The job did not complete. Either the administrator forcefully cancelled it, or an error occurred. Investigate from the job logs in SM37.

## How to Schedule a Background Job Using SM36

You can schedule a background job using transaction code **SM36**. Both planned and immediate jobs can be configured.

**Step 1)** Execute T-code **SM36**.

[![SAP SM36 Transaction Code for Background Job Scheduling]()](https://www.guru99.com/images/sap/2013/03/032013_0839_1.png)

**Step 2)** Fill in the job name, priority class (**A/B/C**), and the target server. Defining a target server helps with workload balancing across application servers.

[![Define Background Job Name and Priority in SM36]()](https://www.guru99.com/images/sap/2013/03/032013_0839_2.png)

**Step 3)** Click on “**Spool List Recipient**” to receive output in your mailbox. Check email from **SBWP**.

[![Spool List Recipient Configuration for Background Job]()](https://www.guru99.com/images/sap/2013/03/032013_0839_3.png)

**Step 4)** Insert your **SAP** username and click the Copy button.

[![Enter SAP Username for Spool Recipient]()](https://www.guru99.com/images/sap/2013/03/032013_0839_4.png)

**Step 5)** Click the **Step** button to define the [ABAP program](https://www.guru99.com/what-is-abap.html) and variant details.

[![Click Step Button to Define ABAP Program]()](https://www.guru99.com/images/sap/2013/03/032013_0839_5.png)

**Step 6)** Define the program name and variant details.

1. Enter your program name and variant name. If you have not created a variant, leave it blank.
2. Press **Save**.

[![Enter Program Name and Variant for Background Job Step]()](https://www.guru99.com/images/sap/2013/03/032013_0839_6.png)

**Step 7)** Once the job step is saved, you will see the confirmation screen.

[![Background Job Step Confirmation Screen]()](https://www.guru99.com/images/sap/2013/03/032013_0839_7.png)

**Don't Miss:**

- [How to Download & Install SAP GUI](https://www.guru99.com/guide-to-install-sap-gui-aka-frontend.html)
- [login/fails\_to\_session\_end – SAP RZ11](https://www.guru99.com/how-to-limit-logon-attempts.html "login/fails_to_session_end – SAP RZ11")
- [SAP RSBTCDEL2: How to Delete a Background Job](https://www.guru99.com/how-to-delete-a-background-job.html)
- [STMS Configuration in SAP](https://www.guru99.com/how-to-configure-tms.html)

**Step 8)** Click **Start Condition** to fill start date, end date, and frequency. Without a start condition, **the job will always remain in Scheduled status** and will never run.

1. Click on **Date/Time** for periodic jobs. Selecting “Immediate” runs the job right away as a one-time execution.
2. Define start date/time and end date/time. The job is released only when it meets its **scheduled start date/time**.
3. Press **Periodic Values**.

[![Define Start Condition and Periodic Schedule for Background Job]()](https://www.guru99.com/images/sap/2013/03/032013_0839_8.png)

**Step 9)** Select the period — Hourly, Daily, Weekly, or Other Period. We select **Other Period**.

[![Select Periodic Frequency for Background Job]()](https://www.guru99.com/images/sap/2013/03/032013_0839_9.png)

**Step 10)** Specify the recurring criteria. For example, run every 5 days from the start date. Here we select every **10 minutes**.

[![Set Custom Recurring Interval for Background Job]()](https://www.guru99.com/images/sap/2013/03/032013_0839_10.png)

**Step 11)** Click **Save**.

[![Save Periodic Values for Background Job]()](https://www.guru99.com/images/sap/2013/03/032013_0839_11.png)

**Step 12)** Click **Save** again.

[![Confirm Start Condition for Background Job]()](https://www.guru99.com/images/sap/2013/03/032013_0839_12.png)

**Step 13)** Click **Save** on the main screen.

[![Save Complete Background Job Definition in SM36]()](https://www.guru99.com/images/sap/2013/03/032013_0839_13.png)

**Step 14)** Once job step and start conditions are defined, the summary window appears.

[![Background Job Configuration Summary Window]()](https://www.guru99.com/images/sap/2013/03/032013_0839_14.png)

**Step 15)** Press **Save** to finalize the background job.

[![Finalize and Release Background Job]()](https://www.guru99.com/images/sap/2013/03/032013_0839_15.png)

## How to Monitor a Background Job Using SM37

After scheduling, verify job status using transaction code **SM37**, which provides a centralized view of all background jobs.

**Step 1)** Execute T-code **SM37**.

[![SAP SM37 Transaction Code for Job Monitoring]()](https://www.guru99.com/images/sap/2013/03/032013_0839_16.png)

**Step 2)** Select your criteria for the job you want to monitor.

1. Enter the job name and username who scheduled the job.
2. Select the status of the job.
3. Specify the date range. Here, we specify only the end date while keeping From Date open.

[![Set Job Selection Criteria in SM37]()](https://www.guru99.com/images/sap/2013/03/032013_0839_17.png)

**Step 3)** The status shows **Released**, meaning start conditions are met and the job is in the queue waiting for a **background work process to become available**.

[![Background Job Status Released in SM37 Job Overview]()](https://www.guru99.com/images/sap/2013/03/032013_0839_18.png)

## How to Deschedule a Background Job

Descheduling reverts a job from Released back to Scheduled status so it will not run in the future. You cannot deschedule a job once it reaches **Active** status.

**Step 1)** Execute **SM37**.

[![Open SM37 for Descheduling a Background Job]()](https://www.guru99.com/images/sap/2013/03/032013_0839_37.png)

**Step 2)** Fill the criteria.

1. Job name and username who scheduled the job.
2. Select status — only **Released** or **Ready** jobs can be descheduled.
3. Specify the date range.
4. Press **Execute (F8)**.

[![Filter Criteria for Descheduling Background Job]()](https://www.guru99.com/images/sap/2013/03/032013_0839_38.png)

**Step 3)** Select the job and press **Job → Released → Scheduled**.

[![Change Job Status from Released to Scheduled]()](https://www.guru99.com/images/sap/2013/03/032013_0839_39.png)

**Step 4)** A confirmation message appears in the status bar once the job is descheduled.

[![Confirmation Message for Descheduled Background Job]()](https://www.guru99.com/images/sap/2013/03/032013_0839_40.png)

## Background Job Processing vs Foreground Processing

Foreground processing requires an active user session and blocks the screen until the task completes, making it unsuitable for long-running operations. Background processing runs independently without locking the user interface. Foreground jobs suit quick interactive tasks like data entry and configuration changes. Background jobs are better for mass data uploads, period-end closings, large report generation, and scheduled data transfers. SAP best practice recommends running resource-intensive programs as background jobs during off-peak hours.

## FAQs

⚡ What is the difference between SM36 and SM37 in SAP?

SM36 is used to define and schedule background jobs, while SM37 is used to monitor, view logs, and manage existing background jobs. Together they cover the full job lifecycle.

🚀 Can you schedule a background job to run immediately in SAP?

Yes. In SM36, select “Immediate” as the start condition. The job executes right away as a one-time run but will not be configured as a periodic recurring job.

💡 What happens if a background job fails or gets cancelled?

A cancelled job appears with “Cancelled” status in SM37. Review the job log to identify the error. Common causes include program errors, missing authorizations, or insufficient background work processes.

🤖 How can AI improve SAP background job management?

AI-powered tools like [SAP Business AI](https://www.sap.com/products/artificial-intelligence.html) can predict job failures, optimize scheduling windows, and automatically reallocate work processes based on historical performance patterns.

🤖 What role does AI play in automating SAP background job monitoring?

AI-driven monitoring tools analyze job logs in real time, detect anomalies, and trigger alerts before failures occur. This reduces manual oversight and enables proactive system administration.

#### Summarize this post with:

ChatGPTPerplexityGrokGoogle AI

**Stay Updated on AI** **Get Weekly AI Skills, Trends, Actionable Advice.**

##### Sign up for the newsletter

Subscribe for Free

You have successfully subscribed.  
Please check your inbox.

![AI-Newsletter]() Chosen by over **350,000+** professionals

[Scroll to top](#wrapper)

×

Search for:

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://www.guru99.com/#organization","name":"Guru99","sameAs":["https://www.facebook.com/Guru99Official","https://twitter.com/guru99com"],"logo":{"@type":"ImageObject","@id":"https://www.guru99.com/#logo","url":"https://www.guru99.com/images/guru99-logo-v1-150x59.png","contentUrl":"https://www.guru99.com/images/guru99-logo-v1-150x59.png","caption":"Guru99","inLanguage":"en-US"}},{"@type":"WebSite","@id":"https://www.guru99.com/#website","url":"https://www.guru99.com","name":"Guru99","publisher":{"@id":"https://www.guru99.com/#organization"},"inLanguage":"en-US"},{"@type":"ImageObject","@id":"https://www.guru99.com/images/background-job-processing-1.png","url":"https://www.guru99.com/images/background-job-processing-1.png","width":"700","height":"250","inLanguage":"en-US"},{"@type":"BreadcrumbList","@id":"https://www.guru99.com/background-job-processing.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":"1","item":{"@id":"https://www.guru99.com","name":"Home"}},{"@type":"ListItem","position":"2","item":{"@id":"https://www.guru99.com/sap-basis","name":"SAP - Basis"}},{"@type":"ListItem","position":"3","item":{"@id":"https://www.guru99.com/background-job-processing.html","name":"SAP Background Job Processing SM36"}}]},{"@type":"WebPage","@id":"https://www.guru99.com/background-job-processing.html#webpage","url":"https://www.guru99.com/background-job-processing.html","name":"SAP Background Job Processing SM36","dateModified":"2026-10-09T12:11:09+05:30","isPartOf":{"@id":"https://www.guru99.com/#website"},"primaryImageOfPage":{"@id":"https://www.guru99.com/images/background-job-processing-1.png"},"inLanguage":"en-US","breadcrumb":{"@id":"https://www.guru99.com/background-job-processing.html#breadcrumb"}},{"@type":"Person","@id":"https://www.guru99.com/author/editorial","name":"Editorial Team","url":"https://www.guru99.com/author/editorial","image":{"@type":"ImageObject","@id":"https://www.guru99.com/images/favicon-new-logo.png","url":"https://www.guru99.com/images/favicon-new-logo.png","caption":"Editorial Team","inLanguage":"en-US"},"sameAs":["https://www.guru99.com/editorial-team"],"worksFor":{"@id":"https://www.guru99.com/#organization"}},{"articleSection":"SAP - Basis","headline":"SAP Background Job Processing SM36","description":"This tutorial explains in detail background jobs processing in SAP. It gives steps to create/schedule and reschedule Background Job SM36","keywords":"sap-basis, sap","speakable":{"@type":"SpeakableSpecification","cssSelector":[".entry-title",".summary"]},"@type":"Article","author":{"@id":"https://www.guru99.com/author/editorial","name":"Editorial Team"},"dateModified":"2026-10-09T12:11:09+05:30","image":{"@id":"https://www.guru99.com/images/background-job-processing-1.png"},"copyrightYear":"2026","name":"SAP Background Job Processing SM36","subjectOf":[{"@type":"HowTo","name":"How to schedule the background job?","description":"You can schedule the background job using SM36. Planned or immediate jobs can be scheduled.","step":[{"@type":"HowToStep","name":"Fill the job name, priority(A/B/C) and the target server.","text":"Background jobs once scheduled on a target server run on that server. Main purpose of defining target server is the workload balancing.","image":"https://www.guru99.com/images/sap/2013/03/032013_0839_2.png","url":"https://www.guru99.com/background-job-processing.html#step1"},{"@type":"HowToStep","name":"Click on 'spool list recipient'. You will get output in your mailbox.","text":"You can check email from SBWP.","image":"https://www.guru99.com/images/sap/2013/03/032013_0839_3.png","url":"https://www.guru99.com/background-job-processing.html#step2"},{"@type":"HowToStep","name":"Insert your SAP username and","text":"click the copy button.","image":"https://www.guru99.com/images/sap/2013/03/032013_0839_4.png","url":"https://www.guru99.com/background-job-processing.html#step3"},{"@type":"HowToStep","name":"Click Step button to define ABAP program","text":"variant\u2019s details, etc.","image":"https://www.guru99.com/images/sap/2013/03/032013_0839_5.png","url":"https://www.guru99.com/background-job-processing.html#step4"},{"@type":"HowToStep","name":"Define program name, variant details.","text":"Enter your program name, Variant name in the field. If you have not created variant as per your requirement, then leave it blank.","image":"https://www.guru99.com/images/sap/2013/03/032013_0839_6.png","url":"https://www.guru99.com/background-job-processing.html#step5"},{"@type":"HowToStep","name":"Once you schedule the job","text":"you will get the following screen.","image":"https://www.guru99.com/images/sap/2013/03/032013_0839_7.png","url":"https://www.guru99.com/background-job-processing.html#step6"},{"@type":"HowToStep","name":"Click Start conditions to fill start date, end date, frequency, etc for job.","text":"If you do not specify start condition then job will always remain in scheduled status. A job in scheduled status will never run.","image":"https://www.guru99.com/images/sap/2013/03/032013_0839_8.png","url":"https://www.guru99.com/background-job-processing.html#step7"},{"@type":"HowToStep","name":"Click on Hourly/Daily/Weekly period to define the frequency of the job as per your requirement.","text":"We will select Other Period","image":"https://www.guru99.com/images/sap/2013/03/032013_0839_9.png","url":"https://www.guru99.com/background-job-processing.html#step8"},{"@type":"HowToStep","name":"Here you specify the recurring criteria of the job.","text":"For example, You can have the Job run after every 5 days from the Start Date. Here we select job to run every 10 minutes","image":"https://www.guru99.com/images/sap/2013/03/032013_0839_10.png","url":"https://www.guru99.com/background-job-processing.html#step9"},{"@type":"HowToStep","name":"Select your criteria for the job which you want to monitor.","text":"Put your job name and username who scheduled the job.","image":"https://www.guru99.com/images/sap/2013/03/032013_0839_17.png","url":"https://www.guru99.com/background-job-processing.html#step10"},{"@type":"HowToStep","name":"You will get the following screen.","text":"Look at the status, it\u2019s a released means start conditions are met, and the job is in the queue is waiting for background work process to be free.","image":"https://www.guru99.com/images/sap/2013/03/032013_0839_18.png","url":"https://www.guru99.com/background-job-processing.html#step11"}]},{"@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is the difference between SM36 and SM37 in SAP?","acceptedAnswer":{"@type":"Answer","text":"SM36 is used to define and schedule background jobs, while SM37 is used to monitor, view logs, and manage existing background jobs. Together they cover the full job lifecycle."}},{"@type":"Question","name":"Can you schedule a background job to run immediately in SAP?","acceptedAnswer":{"@type":"Answer","text":"Yes. In SM36, select \"Immediate\" as the start condition. The job executes right away as a one-time run but will not be configured as a periodic recurring job."}},{"@type":"Question","name":"What happens if a background job fails or gets cancelled?","acceptedAnswer":{"@type":"Answer","text":"A cancelled job appears with \"Cancelled\" status in SM37. Review the job log to identify the error. Common causes include program errors, missing authorizations, or insufficient background work processes."}},{"@type":"Question","name":"How can AI improve SAP background job management?","acceptedAnswer":{"@type":"Answer","text":"AI-powered tools like SAP Business AI can predict job failures, optimize scheduling windows, and automatically reallocate work processes based on historical performance patterns."}},{"@type":"Question","name":"What role does AI play in automating SAP background job monitoring?","acceptedAnswer":{"@type":"Answer","text":"AI-driven monitoring tools analyze job logs in real time, detect anomalies, and trigger alerts before failures occur. This reduces manual oversight and enables proactive system administration."}}]}],"@id":"https://www.guru99.com/background-job-processing.html#schema-551767","isPartOf":{"@id":"https://www.guru99.com/background-job-processing.html#webpage"},"publisher":{"@id":"https://www.guru99.com/#organization"},"inLanguage":"en-US","mainEntityOfPage":{"@id":"https://www.guru99.com/background-job-processing.html#webpage"}}]}
```
