SAP TH_START_ARFC Function Module for









TH_START_ARFC is a standard th start arfc 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 th start arfc FM, simply by entering the name TH_START_ARFC into the relevant SAP transaction such as SE37 or SE38.

Function Group: THFB2
Program Name: SAPLTHFB2
Main Program: SAPLTHFB2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function TH_START_ARFC 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 'TH_START_ARFC'"
  EXPORTING
   NO_ARFC =  "
   WAIT_TIM =  "
   CALL_EXT =  "

EXCEPTIONS
   SYSTEM_FAILURE = 1    PROGRAM_TERMINATION_ERROR = 10    X_ERROR = 11    PARAMETER_EXPECTED = 12    TOO_MANY_PARAMETERS = 13    ILLEGAL_COMMAND = 14    COMMUNCATION_FAILURE = 2    RESOURCE_FAILURE = 3    NO_PERMISSION = 4    COMMAND_NOT_FOUND = 5    PARAMETERS_TOO_LONG = 6    SECURITY_RISK = 7    WRONG_CHECK_CALL_INTERFACE = 8    PROGRAM_START_ERROR = 9
.



IMPORTING Parameters details for TH_START_ARFC

NO_ARFC -

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

WAIT_TIM -

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

CALL_EXT -

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

EXCEPTIONS details

SYSTEM_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

PROGRAM_TERMINATION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

X_ERROR -

Data type:
Optional: No
Call by Reference: Yes

PARAMETER_EXPECTED -

Data type:
Optional: No
Call by Reference: Yes

TOO_MANY_PARAMETERS -

Data type:
Optional: No
Call by Reference: Yes

ILLEGAL_COMMAND -

Data type:
Optional: No
Call by Reference: Yes

COMMUNCATION_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

RESOURCE_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

NO_PERMISSION -

Data type:
Optional: No
Call by Reference: Yes

COMMAND_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

PARAMETERS_TOO_LONG -

Data type:
Optional: No
Call by Reference: Yes

SECURITY_RISK -

Data type:
Optional: No
Call by Reference: Yes

WRONG_CHECK_CALL_INTERFACE -

Data type:
Optional: No
Call by Reference: Yes

PROGRAM_START_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TH_START_ARFC 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_no_arfc  TYPE I, "   
lv_system_failure  TYPE I, "   
lv_program_termination_error  TYPE I, "   
lv_x_error  TYPE I, "   
lv_parameter_expected  TYPE I, "   
lv_too_many_parameters  TYPE I, "   
lv_illegal_command  TYPE I, "   
lv_wait_tim  TYPE I, "   
lv_communcation_failure  TYPE I, "   
lv_call_ext  TYPE I, "   
lv_resource_failure  TYPE I, "   
lv_no_permission  TYPE I, "   
lv_command_not_found  TYPE I, "   
lv_parameters_too_long  TYPE I, "   
lv_security_risk  TYPE I, "   
lv_wrong_check_call_interface  TYPE I, "   
lv_program_start_error  TYPE I. "   

  CALL FUNCTION 'TH_START_ARFC'  "
    EXPORTING
         NO_ARFC = lv_no_arfc
         WAIT_TIM = lv_wait_tim
         CALL_EXT = lv_call_ext
    EXCEPTIONS
        SYSTEM_FAILURE = 1
        PROGRAM_TERMINATION_ERROR = 10
        X_ERROR = 11
        PARAMETER_EXPECTED = 12
        TOO_MANY_PARAMETERS = 13
        ILLEGAL_COMMAND = 14
        COMMUNCATION_FAILURE = 2
        RESOURCE_FAILURE = 3
        NO_PERMISSION = 4
        COMMAND_NOT_FOUND = 5
        PARAMETERS_TOO_LONG = 6
        SECURITY_RISK = 7
        WRONG_CHECK_CALL_INTERFACE = 8
        PROGRAM_START_ERROR = 9
. " TH_START_ARFC




ABAP code using 7.40 inline data declarations to call FM TH_START_ARFC

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



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!