SAP ID_OF_BACKGROUNDTASK Function Module for Get Transactional RFC ID
ID_OF_BACKGROUNDTASK is a standard id 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 Get Transactional RFC ID 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 id of backgroundtask FM, simply by entering the name ID_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): Remote-Enabled
Update:
Function ID_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 'ID_OF_BACKGROUNDTASK'"Get Transactional RFC ID.
EXPORTING
* DEST = ' ' "Destination When Using qRFC
IMPORTING
TID = "ID of the LUW
FNUM = "Function Number Within LUW
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 ID_OF_BACKGROUNDTASK
DEST - Destination When Using qRFC
Data type: RFCDES-RFCDESTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ID_OF_BACKGROUNDTASK
TID - ID of the LUW
Data type: ARFCTIDOptional: No
Call by Reference: No ( called with pass by value option)
FNUM - Function Number Within LUW
Data type: QRETSTATE-QRFNUMOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ID_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_tid | TYPE ARFCTID, " | |||
lv_dest | TYPE RFCDES-RFCDEST, " SPACE | |||
lv_fnum | TYPE QRETSTATE-QRFNUM. " |
  CALL FUNCTION 'ID_OF_BACKGROUNDTASK' "Get Transactional RFC ID |
EXPORTING | ||
DEST | = lv_dest | |
IMPORTING | ||
TID | = lv_tid | |
FNUM | = lv_fnum | |
. " ID_OF_BACKGROUNDTASK |
ABAP code using 7.40 inline data declarations to call FM ID_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 RFCDEST FROM RFCDES INTO @DATA(ld_dest). | ||||
DATA(ld_dest) | = ' '. | |||
"SELECT single QRFNUM FROM QRETSTATE INTO @DATA(ld_fnum). | ||||
Search for further information about these or an SAP related objects