SAP ARFC_RUN Function Module for









ARFC_RUN is a standard arfc run SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 arfc run FM, simply by entering the name ARFC_RUN into the relevant SAP transaction such as SE37 or SE38.

Function Group: ARFC
Program Name: SAPLARFC
Main Program: SAPLARFC
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ARFC_RUN 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 'ARFC_RUN'"
EXPORTING
TID = "
* FORCED = ' ' "
* NO_SERIAL = ' ' "

IMPORTING
ASTATE = "Transactional tRFC queue status

TABLES
DATA = "
STATES = "

EXCEPTIONS
COMMUNICATION_FAILED = 1 SYSTEM_FAILED = 2
.




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 ARFC_RUN

TID -

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

FORCED -

Data type: SY-BATCH
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_SERIAL -

Data type: SY-BATCH
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ARFC_RUN

ASTATE - Transactional tRFC queue status

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

TABLES Parameters details for ARFC_RUN

DATA -

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

STATES -

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

EXCEPTIONS details

COMMUNICATION_FAILED -

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

SYSTEM_FAILED -

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

Copy and paste ABAP code example for ARFC_RUN 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, "   
lt_data  TYPE STANDARD TABLE OF ARFCSDATA, "   
lv_astate  TYPE TRFCQOUT-QSTATE, "   
lv_communication_failed  TYPE TRFCQOUT, "   
lv_forced  TYPE SY-BATCH, "   SPACE
lt_states  TYPE STANDARD TABLE OF ARFCSSTATE, "   
lv_system_failed  TYPE ARFCSSTATE, "   
lv_no_serial  TYPE SY-BATCH. "   SPACE

  CALL FUNCTION 'ARFC_RUN'  "
    EXPORTING
         TID = lv_tid
         FORCED = lv_forced
         NO_SERIAL = lv_no_serial
    IMPORTING
         ASTATE = lv_astate
    TABLES
         DATA = lt_data
         STATES = lt_states
    EXCEPTIONS
        COMMUNICATION_FAILED = 1
        SYSTEM_FAILED = 2
. " ARFC_RUN




ABAP code using 7.40 inline data declarations to call FM ARFC_RUN

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 QSTATE FROM TRFCQOUT INTO @DATA(ld_astate).
 
 
"SELECT single BATCH FROM SY INTO @DATA(ld_forced).
DATA(ld_forced) = ' '.
 
 
 
"SELECT single BATCH FROM SY INTO @DATA(ld_no_serial).
DATA(ld_no_serial) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!