Function called IN BACKGROUND TASK goes to work process DIA, not BGD

[Former Member]

I'm calling a function IN BACKGROUND TASK

In SM50, I see it running in a DIA work process.

I want it to run in a BGD work process.

Can this be done? If so, how? If not, why not?

[Former Member]

As a small addition, I remember having read that dialog process are used for RFCs (like the tRFC started by IN BACKGROUND TASK) because in contrast to background processes they have a configurable time out period and can put those tasks "on hold" (i.e. making the workprocess availabe for other tasks) that are waiting for certain results like a response from a remote system.

I am almost certain that there is no option to use background processes instead.

Thomas

[former_member212005]

Hi...

It looks like, it will always run in DIA process and not Background process...I am not sure that we can change the work process

Check the below link..

http://help.sap.com/saphelp_40b/helpdata/pt/69/c24f864ba111d189750000e8322d00/content.htm

What is written in the link is...

"Background updates (CALL FUNCTION IN BACKGROUND TASK) represent a variant of remote function call that is synchronous with the end of a transaction (COMMIT WORK). In background updating, an update is run in another dialog work process that may be in the same or in another application server and R/3 System. Because such updates run in their own LUWs, they may start only after all critical updates have been completed. Otherwise, it would not be possible to roll back background changes in the event of an error in another update component. "

IF you get the answer of whether we can change the work process then please let us know...

[ThomasZloch]

As a small addition, I remember having read that dialog process are used for RFCs (like the tRFC started by IN BACKGROUND TASK) because in contrast to background processes they have a configurable time out period and can put those tasks "on hold" (i.e. making the workprocess availabe for other tasks) that are waiting for certain results like a response from a remote system.

I am almost certain that there is no option to use background processes instead.

Thomas