SAP START_OF_BACKGROUNDTASK Function Module for Set Start Date/Time for Transactional RFC
START_OF_BACKGROUNDTASK is a standard start of backgroundtask SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set Start Date/Time for Transactional RFC processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for start of backgroundtask FM, simply by entering the name START_OF_BACKGROUNDTASK into the relevant SAP transaction such as SE37 or SE38.
Function Group: ARFC
Program Name: SAPLARFC
Main Program: SAPLARFC
Appliation area: S
Release date: 19-Apr-1995
Mode(Normal, Remote etc): Normal Function Module
Update:
Function START_OF_BACKGROUNDTASK pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'START_OF_BACKGROUNDTASK'"Set Start Date/Time for Transactional RFC.
EXPORTING
* STARTDATE = "Execution time
* STARTTIME = "Execution time
* NOSEND = ' ' "'X': Do not execute tRFC request
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLARFC_001 Asynchronous RFC: Parameter Settings
IMPORTING Parameters details for START_OF_BACKGROUNDTASK
STARTDATE - Execution time
Data type: SY-DATUMOptional: Yes
Call by Reference: No ( called with pass by value option)
STARTTIME - Execution time
Data type: SY-UZEITOptional: Yes
Call by Reference: No ( called with pass by value option)
NOSEND - 'X': Do not execute tRFC request
Data type: SY-INPUTDefault: SPACE
Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for START_OF_BACKGROUNDTASK Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.DATA: | ||||
lv_startdate | TYPE SY-DATUM, " | |||
lv_starttime | TYPE SY-UZEIT, " | |||
lv_nosend | TYPE SY-INPUT. " SPACE |
  CALL FUNCTION 'START_OF_BACKGROUNDTASK' "Set Start Date/Time for Transactional RFC |
EXPORTING | ||
STARTDATE | = lv_startdate | |
STARTTIME | = lv_starttime | |
NOSEND | = lv_nosend | |
. " START_OF_BACKGROUNDTASK |
ABAP code using 7.40 inline data declarations to call FM START_OF_BACKGROUNDTASK
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8."SELECT single DATUM FROM SY INTO @DATA(ld_startdate). | ||||
"SELECT single UZEIT FROM SY INTO @DATA(ld_starttime). | ||||
"SELECT single INPUT FROM SY INTO @DATA(ld_nosend). | ||||
DATA(ld_nosend) | = ' '. | |||
Search for further information about these or an SAP related objects