SAP RKE_PROT_WRITE Function Module for
RKE_PROT_WRITE is a standard rke prot write 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 prot write FM, simply by entering the name RKE_PROT_WRITE into the relevant SAP transaction such as SE37 or SE38.
Function Group: KEP7
Program Name: SAPLKEP7
Main Program: SAPLKEP7
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RKE_PROT_WRITE 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_PROT_WRITE'".
EXPORTING
* I_APPLCLASS = "
* I_READ_MODE = "
* I_GUID = "
* I_PROCESSING_MODE = "
* I_ERKRS = "
* I_NUMREC = "
* I_NUMREC_DB = "
* I_TIME = "
* I_SUBCLASS = "
* I_TABNAME = "
* I_TRCATNR = "
* I_ACTUAL_DATA = "
* I_PROGNAME = "
* I_TCODE = "
* I_PA_TYPE = "
* I_CALLER_DETAIL = "
TABLES
* IT_SEL_TR = "
* IT_SEL_EP = "
IMPORTING Parameters details for RKE_PROT_WRITE
I_APPLCLASS -
Data type: TKETR-APPLCLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_READ_MODE -
Data type: CEDDB-METHODOptional: Yes
Call by Reference: No ( called with pass by value option)
I_GUID -
Data type: GUID_22Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PROCESSING_MODE -
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ERKRS -
Data type: TKEB-ERKRSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_NUMREC -
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
I_NUMREC_DB -
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TIME -
Data type: NUMC15Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SUBCLASS -
Data type: TKETR-SUBCLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TABNAME -
Data type: TKETR-TABNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TRCATNR -
Data type: TKETRL-TRCATNROptional: Yes
Call by Reference: No ( called with pass by value option)
I_ACTUAL_DATA -
Data type: CEDDB-FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PROGNAME -
Data type: SY-CPROGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_TCODE -
Data type: SY-TCODEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PA_TYPE -
Data type: RKB1X-PA_TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CALLER_DETAIL -
Data type: RKE_TRPR_CALLDOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RKE_PROT_WRITE
IT_SEL_TR -
Data type: CEDDBSELOptional: Yes
Call by Reference: Yes
IT_SEL_EP -
Data type: CEDSTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for RKE_PROT_WRITE 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: | ||||
| lt_it_sel_tr | TYPE STANDARD TABLE OF CEDDBSEL, " | |||
| lv_i_applclass | TYPE TKETR-APPLCLASS, " | |||
| lv_i_read_mode | TYPE CEDDB-METHOD, " | |||
| lv_i_guid | TYPE GUID_22, " | |||
| lv_i_processing_mode | TYPE FLAG, " | |||
| lv_i_erkrs | TYPE TKEB-ERKRS, " | |||
| lv_i_numrec | TYPE I, " | |||
| lv_i_numrec_db | TYPE I, " | |||
| lv_i_time | TYPE NUMC15, " | |||
| lt_it_sel_ep | TYPE STANDARD TABLE OF CEDST, " | |||
| lv_i_subclass | TYPE TKETR-SUBCLASS, " | |||
| lv_i_tabname | TYPE TKETR-TABNAME, " | |||
| lv_i_trcatnr | TYPE TKETRL-TRCATNR, " | |||
| lv_i_actual_data | TYPE CEDDB-FLAG, " | |||
| lv_i_progname | TYPE SY-CPROG, " | |||
| lv_i_tcode | TYPE SY-TCODE, " | |||
| lv_i_pa_type | TYPE RKB1X-PA_TYPE, " | |||
| lv_i_caller_detail | TYPE RKE_TRPR_CALLD. " |
|   CALL FUNCTION 'RKE_PROT_WRITE' " |
| EXPORTING | ||
| I_APPLCLASS | = lv_i_applclass | |
| I_READ_MODE | = lv_i_read_mode | |
| I_GUID | = lv_i_guid | |
| I_PROCESSING_MODE | = lv_i_processing_mode | |
| I_ERKRS | = lv_i_erkrs | |
| I_NUMREC | = lv_i_numrec | |
| I_NUMREC_DB | = lv_i_numrec_db | |
| I_TIME | = lv_i_time | |
| I_SUBCLASS | = lv_i_subclass | |
| I_TABNAME | = lv_i_tabname | |
| I_TRCATNR | = lv_i_trcatnr | |
| I_ACTUAL_DATA | = lv_i_actual_data | |
| I_PROGNAME | = lv_i_progname | |
| I_TCODE | = lv_i_tcode | |
| I_PA_TYPE | = lv_i_pa_type | |
| I_CALLER_DETAIL | = lv_i_caller_detail | |
| TABLES | ||
| IT_SEL_TR | = lt_it_sel_tr | |
| IT_SEL_EP | = lt_it_sel_ep | |
| . " RKE_PROT_WRITE | ||
ABAP code using 7.40 inline data declarations to call FM RKE_PROT_WRITE
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 APPLCLASS FROM TKETR INTO @DATA(ld_i_applclass). | ||||
| "SELECT single METHOD FROM CEDDB INTO @DATA(ld_i_read_mode). | ||||
| "SELECT single ERKRS FROM TKEB INTO @DATA(ld_i_erkrs). | ||||
| "SELECT single SUBCLASS FROM TKETR INTO @DATA(ld_i_subclass). | ||||
| "SELECT single TABNAME FROM TKETR INTO @DATA(ld_i_tabname). | ||||
| "SELECT single TRCATNR FROM TKETRL INTO @DATA(ld_i_trcatnr). | ||||
| "SELECT single FLAG FROM CEDDB INTO @DATA(ld_i_actual_data). | ||||
| "SELECT single CPROG FROM SY INTO @DATA(ld_i_progname). | ||||
| "SELECT single TCODE FROM SY INTO @DATA(ld_i_tcode). | ||||
| "SELECT single PA_TYPE FROM RKB1X INTO @DATA(ld_i_pa_type). | ||||
Search for further information about these or an SAP related objects