Background Processing

In what ways can a background processing event be raised?

Which transaction monitors background jobs, and what can you filter by?

Which ST-A/PI report gives a graphical analysis of background jobs to troubleshoot bottlenecks?

What are the three ways a background job can be started?

What do background job priority classes A, B, and C represent?

What can you do when creating a background job manually in SM36 that the job wizard (SM36WIZ) does not allow?

When a job step runs, whose authorizations are checked — the user who scheduled the job, or someone else?

Which authorization object lets a user assign a step user other than themselves to a background job?

Which report starts due time-dependent background jobs, and how often does it run on each instance?

An admin coming from SAP NetWeaver looks under SM36's 'Standard Jobs' in S/4HANA and can't find the housekeeping jobs — where did they move, and where are they monitored now?

Under which user do the technical job repository's job steps run by default?

What is the key runtime difference between a background job and an online dialog transaction?

A background job is made up of several steps. Across how many background work processes is the whole job executed?

Which authorization object controls the use of external commands in background steps?

A class A job has been running for an hour when a new class C job starts. At what moment did the class A job's priority class actually matter?

Why is running periodic background jobs under a normal dialog user's account risky, and what user type avoids it?

Where can you review the history of background processing events?

In SM37 a job shows a large value in the Delay column — what does that signal?

Which profile parameter sets the number of background (BTC) work processes on an instance, and what is the minimum for a server that imports transports?

What are the three types a background job step can be?

What does the parameter rdisp/btctime control, and what is its default?

What makes external programs (as opposed to external commands) in background steps a security concern?

How can you make background jobs that have no specified target server load-balance automatically across all servers?

What is the difference between a system event and a user event in background processing?

After a system crash, several jobs are stuck in 'active' even though nothing is running. How do you clean this up?

Why must an ABAP program have a variant to run as a background job step?

How does the SAP system run an external command or external program from a background step at the operating-system level?

What statuses does a background job pass through from scheduling to completion?

How often does the technical job repository regenerate the housekeeping jobs, and which parameter controls it?

Which transactions let you verify that background processing works and check its configuration consistency?