CREATE A BACKGROUND JOB IN SAP

A background job in SAP refers to tasks that are executed automatically by the system at specified times or regular intervals, without the need for user intervention. These jobs typically run during off-peak hours to avoid impacting system performance.

Why Are Background Jobs Used?

• Time Efficiency: Users don’t need to manually perform repetitive tasks.

• Business Continuity: Jobs run at scheduled times, ensuring uninterrupted process flow.

• Error Reduction: Since the system handles tasks automatically, manual errors are minimized.

• Batch Processing Made Easy: Ideal for large data updates or reporting tasks.

When defining a background job in SAP, the technical details of the job are usually handled by ABAP developers. This is because the program or functions to be executed are written and optimized in ABAP code.

However, functional consultants can also contribute to job definitions in some cases, especially when:

• The job runs standard SAP functions or reports, which can be scheduled directly through SM36 by functional consultants.

• Managing variants and parameters falls within the functional consultant’s expertise, ensuring the job runs with business-relevant data.

Functional consultants may configure certain logic using SAP tools without the need for ABAP development, depending on the complexity of the process.

Scenario:

Let’s say a company runs a promotional campaign: “Buy 10 packs of filter coffee and get 2 free.”

To manage this campaign, all related orders need to be reviewed nightly. In this case, a background job can be scheduled in the system to perform the necessary checks and automatically create sales orders that include the free goods for customers who meet the criteria.

Configuration Steps:

• To create these processes, we use the SM36 transaction code. On the job definition screen that opens, the first step is to enter the Job Name for the task to be defined. Next, the Job Class is selected. There are three options for job class: High priority, Medium priority, and Low priority. When an automated job is defined in SAP and the execution conditions are met, if there are other pending jobs in the system, execution proceeds based on the assigned priority level. During the execution step, if multiple application servers (systems) are available, it must also be specified on which server the job should run.

• Next, we need to define the condition for execution. To do this, click on the Start Condition icon located at the top.

• On the screen that appears, you will see the buttons Immediate, Date/Time, After Job, After Event, and Operation Mode. If you want the job to start immediately, select Immediate. If you want it to start on a specific date and time, choose Date/Time.If the job is to be scheduled after a specific event, click on the After Event icon to create the schedule accordingly.

• Let’s assume the job is to be executed on a specific date. In this case, click on the Date/Time icon. In the pop-up window that appears, select the Start Date, and then check the box labeled Periodic Job. Next, click on the Period Values icon and choose a period based on your scenario—hourly, daily, weekly, or monthly. Finally, click the Save icon to complete the setup.

• Then, the specified date and period were saved.

Then, click on the Step icon.

• On the screen that opens, the name of the ABAP program developed for that job is entered, and the Save button is clicked. Since there is no custom-developed program in this case, I will enter an existing program just for demonstration purposes and save it.

As shown on the screen, the job has been successfully defined.