27.04.2013 Views

SAP Basis

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Unit 9: Scheduling Background Tasks ADM100<br />

You can also specify a time period during which the job should be executed.<br />

To do this, you specify a time after which the job should no longer be<br />

executed. With this function, you prevent periodic jobs being executed at<br />

an undesirable time, among other things. For example, a reorganization<br />

job that should only be executed at night is delayed. With a start time<br />

window, you can avoid this job being executed during the day, when the<br />

dialog users are active and there are fewer system resources available.<br />

Load Balancing<br />

The profile parameter rdisp/bctime specifies the time period in which the<br />

time-dependent job scheduler is active (see the next figure). The execution<br />

of jobs with the start condition immediate usually avoids the time-based<br />

scheduler. In this case, the dialog work process of the scheduling user<br />

performs the job scheduling. Only if no free resources are found, is the job<br />

concerned scheduled in a time-based way. The scheduled start time then<br />

corresponds to the time point at which it should have started.<br />

Figure 100: Scheduling Jobs and Load Balancing<br />

Background work processes can be configured on every instance of the<br />

<strong>SAP</strong> system using the profile parameter rdisp/wp_no_btc.<br />

The number of background work processes required in the <strong>SAP</strong> system<br />

depends on the number of tasks to be performed in the background. If the<br />

transport system is used, there must be at least two background work<br />

processes in the system.<br />

314 © 2003 <strong>SAP</strong> AG. All rights reserved. 2003/Q3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!