SAP AS ABAP Administration · Background Processing & Job Scheduling

Your time-driven jobs start fine on every app server, but event-triggered jobs only ever fire on one instance. Is something broken?

Answer locked. Get the free KnowCard app to reveal it — plus spaced-repetition review so it actually sticks.

This is one card from the KnowCard library — thousands more across SAP, Linux, Python and more. In the app you get the answer, AI explanations, and cards that come back right before you would forget them. Free to start on iOS, Android or the web.

More in Background Processing & Job Scheduling

An external command runs in a job step but its OS error messages never appear in the job log. Which step setting controls that?

In SM37, what's the operational difference between a job in Released status and one in Ready status?

A long-running active job seems stuck and you want to inspect it in the ABAP debugger without killing it. What does the job overview let you do, and which authorization gates it?

SAP_REORG_JOBS and SAP_REORG_SPOOL are running, yet ST22 short dumps keep piling up forever. Which standard job actually cleans those?

Across a landscape you need one place to request, document, schedule, and monitor background jobs. Where in SAP Solution Manager?

You run several instances with background processes and want to spread the scheduler's own polling load. What can you vary per instance?

Start learning today

Free to start — download the app or use it in your browser.