SAP RKE_EXIT Function Module for









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

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



Function RKE_EXIT 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 'RKE_EXIT'"
  EXPORTING
   I_EXIT_ID =  "
*  I_COUNT_PARAMS = 0 "

CHANGING
*  X_PARAM_1 =  "
*  X_PARAM_10 =  "
*  X_PARAM_11 =  "
*  X_PARAM_12 =  "
*  X_PARAM_2 =  "
*  X_PARAM_3 =  "
*  X_PARAM_4 =  "
*  X_PARAM_5 =  "
*  X_PARAM_6 =  "
*  X_PARAM_7 =  "
*  X_PARAM_8 =  "
*  X_PARAM_9 =  "

EXCEPTIONS
   ERROR = 1
.



IMPORTING Parameters details for RKE_EXIT

I_EXIT_ID -

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

I_COUNT_PARAMS -

Data type: I
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for RKE_EXIT

X_PARAM_1 -

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

X_PARAM_10 -

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

X_PARAM_11 -

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

X_PARAM_12 -

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

X_PARAM_2 -

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

X_PARAM_3 -

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

X_PARAM_4 -

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

X_PARAM_5 -

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

X_PARAM_6 -

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

X_PARAM_7 -

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

X_PARAM_8 -

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

X_PARAM_9 -

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

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RKE_EXIT 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_error  TYPE STRING, "   
lv_i_exit_id  TYPE KEEX_EXIT_ID, "   
lv_x_param_1  TYPE ANY, "   
lv_x_param_10  TYPE ANY, "   
lv_x_param_11  TYPE ANY, "   
lv_x_param_12  TYPE ANY, "   
lv_x_param_2  TYPE ANY, "   
lv_i_count_params  TYPE I, "   0
lv_x_param_3  TYPE ANY, "   
lv_x_param_4  TYPE ANY, "   
lv_x_param_5  TYPE ANY, "   
lv_x_param_6  TYPE ANY, "   
lv_x_param_7  TYPE ANY, "   
lv_x_param_8  TYPE ANY, "   
lv_x_param_9  TYPE ANY. "   

  CALL FUNCTION 'RKE_EXIT'  "
    EXPORTING
         I_EXIT_ID = lv_i_exit_id
         I_COUNT_PARAMS = lv_i_count_params
    CHANGING
         X_PARAM_1 = lv_x_param_1
         X_PARAM_10 = lv_x_param_10
         X_PARAM_11 = lv_x_param_11
         X_PARAM_12 = lv_x_param_12
         X_PARAM_2 = lv_x_param_2
         X_PARAM_3 = lv_x_param_3
         X_PARAM_4 = lv_x_param_4
         X_PARAM_5 = lv_x_param_5
         X_PARAM_6 = lv_x_param_6
         X_PARAM_7 = lv_x_param_7
         X_PARAM_8 = lv_x_param_8
         X_PARAM_9 = lv_x_param_9
    EXCEPTIONS
        ERROR = 1
. " RKE_EXIT




ABAP code using 7.40 inline data declarations to call FM RKE_EXIT

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!