SAP STATUS_OF_BACKGROUNDTASK Function Module for Get status of transactional RFC

Search SAP Function Modules

STATUS_OF_BACKGROUNDTASK is a standard status 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 status of 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 status of backgroundtask FM, simply by entering the name STATUS_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 STATUS_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 'STATUS_OF_BACKGROUNDTASK'"Get status of transactional RFC
  EXPORTING
   TID =  "Transcation ID

TABLES
   ERRORTAB =  "Table into which messages are written

EXCEPTIONS
   COMMUNICATION = 1    RECORDED = 2    ROLLBACK = 3 

.

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 STATUS_OF_BACKGROUNDTASK

TID - Transcation ID

Data type: ARFCTID
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for STATUS_OF_BACKGROUNDTASK

ERRORTAB - Table into which messages are written

Data type: ARFCERRORS
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

COMMUNICATION - No link. Will try again later

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

RECORDED - aRFC is scheduled

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

ROLLBACK - Exception initialized: Rollback in the target system

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for STATUS_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.

ABAP code using 7.40 inline data declarations to call FM STATUS_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.

Search for further information about these or an SAP related objects