BACKGROUND WORKPROCESS
What is Background work process?
It is used to process (execute) user request (program) till the completion of the
job(program)
(or) it is used to process long running or time consuming jobs or expensive jobs
Points to remember :
Background work process are configured by using parameter
rdisp/wp_no_btc = 2 (minimum 2)
Background work process are dedicated to user request till the completion of the program(job) and
there is no time limit to execute the program
We can schedule the program whenever we want and we can define periodic option(hourly, daily,
weekly, monthly)
SM36 tcode is used to schedule standard jobs
SM 37 tcode is used to monitor background job status
“Btctrns1”,it is used to pause(hold) the running background jobs
“Btctrns2” ,it is used to unpause(resume) the running background jobs
Background work process Internal flow:
When we schedule a program in the background using the tcode SM36,it stores in tables in “Tbtct” and
“Tbtcs”,internally a program “Sapmssy2” triggers for every 60 seconds,and reads this “Tbtct” and
“Tbtcs” values,and it will be processed by background workprocesses.
Note : “Sapmssy2” program execution frequency is defined by using parameter
rdisp/btctime = 60 s
Note : It is a dynamic parameter,if we want we can change the parameter value as per our requirement.
Background workprocess job statuses :
A total of six(6) statuses are there,they are schedule,running,ready,active,finished and
cancelled
1.Scheduled : when a job is defined in the background
2.Released : when we specify the background job execution time,then job status changes from schedule
to release
3.Ready : when a specified time has occured
4.Active : when a job is processed by backgroud workprocess
5.Finished : when a job has been completed
6.Cancelled : when a job has been terminated