topic Re: Foreground and Background in Application Development and Automation Discussions

Foreground and Background

Former Member — Fri, 31 Jul 2009 10:35:06 GMT

Hi All,

Does the job in BAckground will take lesser time to execute as compared to same job with same input parameters run in foreground?

THanks

Saurabh

Re: Foreground and Background

former_member404244 — Fri, 31 Jul 2009 10:48:07 GMT

HI,

No ...Not like that..

If you encounter executing a program in foreground , which may take lot of time then u will get short dump in foreground..But u can run the same report in background without any dump..as it may take long time to execute the report.

Regards,

Nagaraj

Re: Foreground and Background

Former Member — Fri, 31 Jul 2009 10:51:52 GMT

Hi,

When you run a job in the foreground, there is a time out after which you will get a dump. Such processes can be run in the background without interruption. That's the basic difference.

Re: Foreground and Background

Former Member — Fri, 31 Jul 2009 11:14:04 GMT

Hi,

There wont be any difference in the time of execution in both foreground and background mode. As mentioned for reports that take longer time of execution are placed as background jobs to avoid the timeout dump.

Regards,

Vik

Re: Foreground and Background

matt — Fri, 31 Jul 2009 11:20:43 GMT


> Hi All,
> 
> Does the job  in BAckground will take lesser time to execute as compared to same job with same input parameters run in foreground?
> 
> THanks
> Saurabh

No. It may take longer, it may take less time. It depends how the system is set up. Usually, during the day, there are more dialog processes than background. ( I'm not sure, but I believe it is possible to give these a higher share of system time than background ). If there are a number of background jobs running concurrently, this will definitely slow down your job.

matt

Re: Foreground and Background

Former Member — Fri, 31 Jul 2009 11:29:11 GMT

There is a profile parameter in basis against which there is a time value set for foreground applications, exceeding which they are terminated. So anything which is database intensive should be typlically scheduled as a background process.

To add further there are work processes in an R/3 system responsible to carry out the dialog steps in an R/3 application.

Typically there are more Background WP's than Dialogue WP's (responsible for carrying out foreground jobs) in the night and vice versa. Therefore your background jobs will run faster in the night simply because there are more background work processes.

Hope you understand the concept now.

Re: Foreground and Background

Former Member — Fri, 31 Jul 2009 12:06:58 GMT

Hello Saurabh,

There are no JOBs those run in foreground. Those are dialog processes. So time required for execution is not changed only the limitation of dialog process timout can be avoided. Also, if you have multiple task done in one single dialog process then

you can divide them in multiple background JOBs provided they don't have inter-dependencies in such case time take to complete same task will be lesser than the dialog work process.

Thanks,

Augustin.

Re: Foreground and Background

Former Member — Thu, 13 Aug 2009 08:06:14 GMT

thx

Re: Foreground and Background

Former Member — Thu, 03 Nov 2011 08:53:55 GMT

Hi all,

Thanks for the great answers.

I could not find the program running in background. So it is foreground.

Any ideas ?

Thanks