KEMBAR78
Background Workprocess | PDF | Computers
0% found this document useful (0 votes)
28 views2 pages

Background Workprocess

Background work processes are used to process long-running or time-consuming jobs without time limits. They are configured using the rdisp/wp_no_btc parameter to have a minimum of 2 processes. Jobs scheduled using transaction codes SM36 and SM37 are stored in tables and checked every 60 seconds by the Sapmssy2 program, which assigns them to available background work processes. The jobs progress through statuses like scheduled, ready, active, finished, and cancelled as they are defined, triggered, running, completed or terminated in the background.

Uploaded by

arfath khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
28 views2 pages

Background Workprocess

Background work processes are used to process long-running or time-consuming jobs without time limits. They are configured using the rdisp/wp_no_btc parameter to have a minimum of 2 processes. Jobs scheduled using transaction codes SM36 and SM37 are stored in tables and checked every 60 seconds by the Sapmssy2 program, which assigns them to available background work processes. The jobs progress through statuses like scheduled, ready, active, finished, and cancelled as they are defined, triggered, running, completed or terminated in the background.

Uploaded by

arfath khan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

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

You might also like