SAP RKE_GET_CE4KEY Function Module for
RKE_GET_CE4KEY is a standard rke get ce4key 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 get ce4key FM, simply by entering the name RKE_GET_CE4KEY into the relevant SAP transaction such as SE37 or SE38.
Function Group: KED1_WRITE
Program Name: SAPLKED1_WRITE
Main Program: SAPLKED1_WRITE
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function RKE_GET_CE4KEY 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_GET_CE4KEY'".
EXPORTING
I_ERKRS = "
* I_PA_TYPE = '1' "
* I_APPLY_CCU = 'X' "
TABLES
OBJECT_TABLE = "
IMPORTING Parameters details for RKE_GET_CE4KEY
I_ERKRS -
Data type: TKEB-ERKRSOptional: No
Call by Reference: No ( called with pass by value option)
I_PA_TYPE -
Data type: CEDDB-PA_TYPEDefault: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_APPLY_CCU -
Data type:Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RKE_GET_CE4KEY
OBJECT_TABLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RKE_GET_CE4KEY 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_i_erkrs | TYPE TKEB-ERKRS, " | |||
lt_object_table | TYPE STANDARD TABLE OF TKEB, " | |||
lv_i_pa_type | TYPE CEDDB-PA_TYPE, " '1' | |||
lv_i_apply_ccu | TYPE CEDDB. " 'X' |
  CALL FUNCTION 'RKE_GET_CE4KEY' " |
EXPORTING | ||
I_ERKRS | = lv_i_erkrs | |
I_PA_TYPE | = lv_i_pa_type | |
I_APPLY_CCU | = lv_i_apply_ccu | |
TABLES | ||
OBJECT_TABLE | = lt_object_table | |
. " RKE_GET_CE4KEY |
ABAP code using 7.40 inline data declarations to call FM RKE_GET_CE4KEY
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 ERKRS FROM TKEB INTO @DATA(ld_i_erkrs). | ||||
"SELECT single PA_TYPE FROM CEDDB INTO @DATA(ld_i_pa_type). | ||||
DATA(ld_i_pa_type) | = '1'. | |||
DATA(ld_i_apply_ccu) | = 'X'. | |||
Search for further information about these or an SAP related objects