Functions in background

Former Member — Tue, 01 Jan 2008 21:12:05 GMT

Hi,

Can anyone explain me the difference between calling a function IN BACKGROUND TASK and IN BACKGROUND UNIT (which added in release 7.0) ?

Re: Functions in background

Former Member — Tue, 01 Jan 2008 21:48:59 GMT

IN BACKGROUND TASK

#1 Flags the function module func to be run asynchronously.

#2 It is not executed at once, but the data passed with EXPORTING then executes the function module in another work process.

#3 Background-task updates already executed for the current DESTINATION are not rolled back.

#4 All further background-task requests for the same DESTINATION are thrown away.

#5 Other previously executed updates are rolled back.

#6 No error message appears on the screen.

AS SEPARATE UNIT

#1 The normal tRFC calls with the addition AS SEPARATE UNIT map a separate LUW in the target system.

#2 qRFC calls with the addition AS SEPARATE UNIT are processed depending on the queue, but independent of the actual LUW.

#3 The relevant function module is executed in a separate context, a context in which the global data of the function group is not influenced by previous calls. Each function module that is registered with the addition AS SEPARATE UNIT is given a separate transaction ID. Without the addition AS SEPARATE UNIT, the usual description is applicable for the context of the called function modules. What this means is that, when using the same destination for multiple calls of function modules belonging to the same function group, the global data of this function group is accessed collectively.

Vinodh Balakrishnan

Re: Functions in background

Former Member — Wed, 02 Jan 2008 14:21:46 GMT

Thanks,

But I have wanted to know the difference between calling a function in background UNIT or in background TASK.

topic Re: Functions in background in Application Development and Automation Discussions

Functions in background

Re: Functions in background

Re: Functions in background