Function called IN BACKGROUND TASK goes to work pr...
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
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.
"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...
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.
Bluesky
