Why do we use CALL FUNCTION ..IN BACKGROUND TASK and CALL FUNCTION ...STARTING NEW TASK?

What is the difference?

Answer Posted / sathish kumar

The IN BACKGROUND TASK statement allows you to execute remote enabled function modules in a background task asynchronously. Be careful thought as it might not quite work as it appears too i.e. If you debug the ABAP program logic it will step over the FM onto the next line of code, not waiting for this function module to finish it processing. But this doesn�t mean it has gone off to start the processing at this point as it has not!! It has simply created the background task ready for processing and will not actually be executed until a commit work is reached in the current logical unit of work. 




So basically if you want it to go off and perform this background processing straight away you need to add a commit work after the call function� in background task command. 




Just in case you are interested in the technical details when you make the call using the in background task addition SAP stores the FM name, destination and any parameters in tables ARFCSSTATE & ARFCSDATA for the current Logical unit of work. These entries can also been seen using tcode SE58. Please note this data is not available here after the task has finished processing. 




Although this may seem strange at first it does allow you to perform other functionality first and only triggers the background task if all is well with that and it is committed to the database ok. Also the background tasks will be processed in the order they have been registered. 




AS SEPARATE UNIT 
The �as separate unit� addition is used if you are calling the same FM multiple times or FM�s within the same function group. It basically ensures each call is processed within its own context and is not affected by global data changes from other function calls. 




DESTINATION 
This simple allows you to specify a different RFC destination 




Example ABAP code to Execute FM in background task




CALL FUNCTION 'Z_FMODULE' IN BACKGROUND TASK
  EXPORTING
    P_UNAME       = sy-uname.








*IN BACKGROUND TASK additional options
CALL FUNCTION 'Z_FMODULE' IN BACKGROUND TASK
      AS SEPARATE UNIT
      DESTINATION 'NONE'
  EXPORTING
    P_UNAME       = sy-uname.








break-point. "does not wait and continues with next line of ABAP code




Commit Work. "Background task is only triggered at this point.




"loop at itab into wa_itab.
"...
"endloop.

The STARTING NEW TASK statement allows you to call a function module but it will be executed in a separate processing task asynchronously so the ABAP program logic does not wait for this FM to finish its processing but continues with the next line of abap code. The clever thing about this statement is that once the FM has finished processing it will then execute the specified FORM within the original program to continue processing. 




This small example is actually the basis for reports which auto-refresh themselves. i.e. the program calls a function module in a new task which then waits a few seconds (WAIT 10 seconds). Once it returns to the program and performs the return form it basically re-runs the whole report again. This especially creates an endless loop so report keeps updating itself until it is cancelled by the user.




Execute FM in update task within separate unit of work




CALL FUNCTION 'Z_FMODULE'
  starting new task 'UPDATE'
             destination 'NONE'
              performing processing_done on end of task
  EXPORTING
    P_UNAME       = sy-uname.




"program does not wait for FM to finish processing and continues with next line of ABAP code
break-point.
"...perform display_report.












FORM processing_done.
* In the mean time once processing of FM Z_FMODULE is complete this abap FORM is then executed.
WIthin here you can perform any processing you like, including re-displaying a report




"...perform display_report.
ENDFORM.

Is This Answer Correct ?    0 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

How many types of data classes are there in sap?

680


What is the difference between refresh and free statements?

774


In sap script how to print bar code in vertical manner

2730


How do u set up background jobs in SAP? What r the steps? What are the event driven batch jobs?

736


How to find Kernal badi ?

1258






If a table that is to be extended contains a long field, we cannot use append structures why? : abap data dictionary

755


What is the disadvantage of using exec sql statement in abap?

622


What is table buffer?

674


How can you display frames (horizontal and vertical lines) in lists?

706


When a function module is activated syntax checking is performed automatically. State yes or no. : abap modularization

698


What are pooled tables? : abap data dictionary

773


what is the difference between Blocked ALV and interactive ALV?

1997


How to creat transactions? : abap data dictionary

736


What two statements are required in an abap program to output an icon using a write statement?

626


What is the difference between skip and reserve?

699