SAP RKE_CHECK_PRINT_OPTION Function Module for
RKE_CHECK_PRINT_OPTION is a standard rke check print option 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 check print option FM, simply by entering the name RKE_CHECK_PRINT_OPTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: KEBR
Program Name: SAPLKEBR
Main Program: SAPLKEBR
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RKE_CHECK_PRINT_OPTION 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_CHECK_PRINT_OPTION'".
EXPORTING
I_ALL_OPTIONS = "
I_CHECK_OPTION = "
IMPORTING
E_OPTION_SET = "
IMPORTING Parameters details for RKE_CHECK_PRINT_OPTION
I_ALL_OPTIONS -
Data type: RKB1F-DRUOPTIONSOptional: No
Call by Reference: No ( called with pass by value option)
I_CHECK_OPTION -
Data type: RKB1F-DRUOPTIONSOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RKE_CHECK_PRINT_OPTION
E_OPTION_SET -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RKE_CHECK_PRINT_OPTION 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_e_option_set | TYPE C, " | |||
| lv_i_all_options | TYPE RKB1F-DRUOPTIONS, " | |||
| lv_i_check_option | TYPE RKB1F-DRUOPTIONS. " |
|   CALL FUNCTION 'RKE_CHECK_PRINT_OPTION' " |
| EXPORTING | ||
| I_ALL_OPTIONS | = lv_i_all_options | |
| I_CHECK_OPTION | = lv_i_check_option | |
| IMPORTING | ||
| E_OPTION_SET | = lv_e_option_set | |
| . " RKE_CHECK_PRINT_OPTION | ||
ABAP code using 7.40 inline data declarations to call FM RKE_CHECK_PRINT_OPTION
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 DRUOPTIONS FROM RKB1F INTO @DATA(ld_i_all_options). | ||||
| "SELECT single DRUOPTIONS FROM RKB1F INTO @DATA(ld_i_check_option). | ||||
Search for further information about these or an SAP related objects