How do I find SAP jobs

Background processing in SAP made easy - set up and manage automatic SAP jobs

What is a SAP job for and how is it structured?

Background jobs are used in many areas where processes are automatically executed by the system at certain times without manual intervention. In the area of ​​Unix systems, the concept of cron jobs is known and on Windows computers you can set up background processes with the task scheduler. SAP also has corresponding background processing for processes - so-called SAP jobs.

SAP jobs can be executed once or recurring - e. B. every day at midnight. In this way, for example, resource-intensive processing can be carried out at night when few or no users are logged on to the system. Another application example is the recurring collection of new EDI messages from an external B2B integration hub, as in the case of ecosio.

In the following we present the most important features and show how to set up. Then we will go into how to change existing SAP jobs and how to read processing logs from SAP jobs. In this article we will explain how you can display the IDoc number of an SD order.

Properties of SAP jobs

SAP jobs are set up using transaction SM36. The following figure shows an exemplary SAP job.

Overview of SAP Job

© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission from SAP SE.

There are unique job names that can be freely assigned. For reasons of clarity, it is advisable to adhere to a uniform system-wide naming convention.

SAP job classes

A SAP job must be assigned to a specific job class when it is created. Job classes define the priority with which a background job is executed. A distinction is made between the following three classes.

Class A - high priority

Urgent or critical background jobs can be planned with class A. These jobs are preferred to run before class B or C jobs are run.

Class B - Medium Priority

As soon as jobs of class A have been processed, jobs of class B are started.

Class C - Low Priority

Class C jobs have the lowest priority and are only started after class A and B jobs have been processed.


In addition to the assigned priority class, there is a certain status. The possible states are as follows:

  1. Planned
    The job is only scheduled, but has no start condition, no end date, no frequency of execution, etc. and will therefore never run.
  2. Approved
    The job has assigned process steps and all parameters for an implementation are available. The job waits to be executed for the first time as soon as the start condition is met - e.g. a certain time.
  3. ready
    The job is ready for execution and has been placed in the execution queue by the job scheduler. As soon as a background processing process is free, the job is carried out.
  4. active
    The job runs in the background. The status of the job can no longer be changed during execution.
  5. Finished
    The job has been carried out successfully.
  6. Canceled
    The job was canceled. The cancellation may have been brought about manually by an administrator, or a problem occurred while the job was being carried out. The exact details can be read out in the job logs and in the spool (see description below).


Every SAP job consists of one or more processing steps - so-called steps. The following figure shows an exemplary step.

SAP job - process step

© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission from SAP SE.

A step in a SAP job can have three different characteristics:

  1. ABAP program
    In this case, an ABAP program is started, whereby a variant and the language can be transferred. In the screenshot above, for example, the ABAP program / EPO1 / EXC_ECOSIO_FETCH is executed with the FETCH variant, which periodically picks up messages from the ecosio Integration Hub.
  2. External command
    With this function, a command predefined by the system administrator can be called and parameters can also be transferred for the call.
  3. External program
    In this case, an external program is started, whereby parameters can also be transferred here.

Set up

In the first step, as already mentioned, the job name and job class are defined in transaction SM36. Then the individual steps of the job are defined, which are executed one after the other - from top to bottom.

The next step is to select the start condition of the job.

SAP job start condition

© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission from SAP SE.

Usually, the start condition is a certain time, from when the job is to be executed, as well as a repetition interval - e.g. every 10 minutes. If you do not specify a time, the job remains in the "planned" state and will not be executed.

After specifying a time and a repetition frequency, the job is saved. Then it changes to "released" and waits for its first execution. Alternatively, a job can also be executed immediately by clicking on "Immediately".

To change

To change a SAP job, switch to transaction SM37. There you can get an overview of all jobs in the various states. To change a job that has already been released, mark it in the overview and then select "Job> Released - Planned" in the menu bar.

SAP job overview

© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission from SAP SE.

This means that the job can now be edited again and then released again.

View logs

Just as with a regularly executed process, processing of a SAP job can also terminate unexpectedly. In this case, it is advisable to take a look at the logs. Here, too, access is again via transaction SM37. The first step is to mark one of the jobs that have already been carried out and then select “Spool” or “Job Log”.

Log data of a SAP job

© 2020. SAP SE or an SAP affiliate company. All rights reserved. Used with permission from SAP SE.

With the help of these two functions you get an overview of the logs themselves as well as the individual process steps. The prerequisite is of course that the process steps also write processing logs.

By the way: with the introduction of SAP S / 4HANA, the IDoc format has undergone some changes. You can find out what these are in detail in this article.

To ask?

Do you still have questions about SAP jobs or the connection of external systems to the SAP ERP or SAP S / 4HANA system? Do not hesitate and contact us. We are always happy to answer any questions you may have.

SAP ERP and SAP S / 4HANA are the trademarks or registered trademarks of SAP SE or its affiliated companies in Germany and several other countries.