SAP CONTROL_CALL_METHOD Function Module for CALL METHOD









CONTROL_CALL_METHOD is a standard control call method SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CALL METHOD 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 control call method FM, simply by entering the name CONTROL_CALL_METHOD into the relevant SAP transaction such as SE37 or SE38.

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



Function CONTROL_CALL_METHOD 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 'CONTROL_CALL_METHOD'"CALL METHOD
EXPORTING
H_CONTROL = "
* P6 = "
* P7 = "
* P8 = "
* P9 = "
* P10 = "
* P11 = "
* P12 = "
* P13 = "
* P14 = "
* P15 = "
METHOD = "
* P16 = "
* P_COUNT = "
* NO_FLUSH = "
* P1 = "
* P2 = "
* P3 = "
* P4 = "
* P5 = "

IMPORTING
RETURN = "

EXCEPTIONS
CNTL_SYSTEM_ERROR = 1 CNTL_ERROR = 2
.



IMPORTING Parameters details for CONTROL_CALL_METHOD

H_CONTROL -

Data type: CNTL_HANDLE
Optional: No
Call by Reference: Yes

P6 -

Data type:
Optional: Yes
Call by Reference: Yes

P7 -

Data type:
Optional: Yes
Call by Reference: Yes

P8 -

Data type:
Optional: Yes
Call by Reference: Yes

P9 -

Data type:
Optional: Yes
Call by Reference: Yes

P10 -

Data type:
Optional: Yes
Call by Reference: Yes

P11 -

Data type:
Optional: Yes
Call by Reference: Yes

P12 -

Data type:
Optional: Yes
Call by Reference: Yes

P13 -

Data type:
Optional: Yes
Call by Reference: Yes

P14 -

Data type:
Optional: Yes
Call by Reference: Yes

P15 -

Data type:
Optional: Yes
Call by Reference: Yes

METHOD -

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

P16 -

Data type:
Optional: Yes
Call by Reference: Yes

P_COUNT -

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

NO_FLUSH -

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

P1 -

Data type:
Optional: Yes
Call by Reference: Yes

P2 -

Data type:
Optional: Yes
Call by Reference: Yes

P3 -

Data type:
Optional: Yes
Call by Reference: Yes

P4 -

Data type:
Optional: Yes
Call by Reference: Yes

P5 -

Data type:
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CONTROL_CALL_METHOD

RETURN -

Data type:
Optional: No
Call by Reference: Yes

EXCEPTIONS details

CNTL_SYSTEM_ERROR -

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

CNTL_ERROR -

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

Copy and paste ABAP code example for CONTROL_CALL_METHOD 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_return  TYPE STRING, "   
lv_h_control  TYPE CNTL_HANDLE, "   
lv_cntl_system_error  TYPE CNTL_HANDLE, "   
lv_p6  TYPE CNTL_HANDLE, "   
lv_p7  TYPE CNTL_HANDLE, "   
lv_p8  TYPE CNTL_HANDLE, "   
lv_p9  TYPE CNTL_HANDLE, "   
lv_p10  TYPE CNTL_HANDLE, "   
lv_p11  TYPE CNTL_HANDLE, "   
lv_p12  TYPE CNTL_HANDLE, "   
lv_p13  TYPE CNTL_HANDLE, "   
lv_p14  TYPE CNTL_HANDLE, "   
lv_p15  TYPE CNTL_HANDLE, "   
lv_method  TYPE C, "   
lv_cntl_error  TYPE C, "   
lv_p16  TYPE C, "   
lv_p_count  TYPE I, "   
lv_no_flush  TYPE C, "   
lv_p1  TYPE C, "   
lv_p2  TYPE C, "   
lv_p3  TYPE C, "   
lv_p4  TYPE C, "   
lv_p5  TYPE C. "   

  CALL FUNCTION 'CONTROL_CALL_METHOD'  "CALL METHOD
    EXPORTING
         H_CONTROL = lv_h_control
         P6 = lv_p6
         P7 = lv_p7
         P8 = lv_p8
         P9 = lv_p9
         P10 = lv_p10
         P11 = lv_p11
         P12 = lv_p12
         P13 = lv_p13
         P14 = lv_p14
         P15 = lv_p15
         METHOD = lv_method
         P16 = lv_p16
         P_COUNT = lv_p_count
         NO_FLUSH = lv_no_flush
         P1 = lv_p1
         P2 = lv_p2
         P3 = lv_p3
         P4 = lv_p4
         P5 = lv_p5
    IMPORTING
         RETURN = lv_return
    EXCEPTIONS
        CNTL_SYSTEM_ERROR = 1
        CNTL_ERROR = 2
. " CONTROL_CALL_METHOD




ABAP code using 7.40 inline data declarations to call FM CONTROL_CALL_METHOD

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!