SAP BM_CHECK_READ_PARAMETERS Function Module for
BM_CHECK_READ_PARAMETERS is a standard bm check read parameters 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 bm check read parameters FM, simply by entering the name BM_CHECK_READ_PARAMETERS into the relevant SAP transaction such as SE37 or SE38.
Function Group: BEGEN
Program Name: SAPLBEGEN
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BM_CHECK_READ_PARAMETERS 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 'BM_CHECK_READ_PARAMETERS'".
EXPORTING
CICO_REQUEST_NO = "
MODE = "
NAMES_ONLY = "
LANGUAGE = "
ADDON = "
TIME_STAMP = "
LAST_USER = "
IMPORTING
REJECTED = "
TABLES
OBJECT_IDS = "
* TYPESTOREAD = "
RETURN = "
IMPORTING Parameters details for BM_CHECK_READ_PARAMETERS
CICO_REQUEST_NO -
Data type: RPYGSGF-CICO_REQNOOptional: No
Call by Reference: No ( called with pass by value option)
MODE -
Data type: RPYGSGF-MODEOptional: No
Call by Reference: No ( called with pass by value option)
NAMES_ONLY -
Data type: BAPIBEGEN-NAMES_ONLYOptional: No
Call by Reference: No ( called with pass by value option)
LANGUAGE -
Data type: BAPI_LAISO-LANGUOptional: No
Call by Reference: No ( called with pass by value option)
ADDON -
Data type: BAPIBEGEN-ADDONOptional: No
Call by Reference: No ( called with pass by value option)
TIME_STAMP -
Data type: BAPIBEGEN-TIME_STAMPOptional: No
Call by Reference: No ( called with pass by value option)
LAST_USER -
Data type: BAPIBEGEN-LAST_USEROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BM_CHECK_READ_PARAMETERS
REJECTED -
Data type: BMT_FLAGOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BM_CHECK_READ_PARAMETERS
OBJECT_IDS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TYPESTOREAD -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
RETURN -
Data type: BAPIRET2Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BM_CHECK_READ_PARAMETERS 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_rejected | TYPE BMT_FLAG, " | |||
| lt_object_ids | TYPE STANDARD TABLE OF BMT_FLAG, " | |||
| lv_cico_request_no | TYPE RPYGSGF-CICO_REQNO, " | |||
| lv_mode | TYPE RPYGSGF-MODE, " | |||
| lt_typestoread | TYPE STANDARD TABLE OF RPYGSGF, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_names_only | TYPE BAPIBEGEN-NAMES_ONLY, " | |||
| lv_language | TYPE BAPI_LAISO-LANGU, " | |||
| lv_addon | TYPE BAPIBEGEN-ADDON, " | |||
| lv_time_stamp | TYPE BAPIBEGEN-TIME_STAMP, " | |||
| lv_last_user | TYPE BAPIBEGEN-LAST_USER. " |
|   CALL FUNCTION 'BM_CHECK_READ_PARAMETERS' " |
| EXPORTING | ||
| CICO_REQUEST_NO | = lv_cico_request_no | |
| MODE | = lv_mode | |
| NAMES_ONLY | = lv_names_only | |
| LANGUAGE | = lv_language | |
| ADDON | = lv_addon | |
| TIME_STAMP | = lv_time_stamp | |
| LAST_USER | = lv_last_user | |
| IMPORTING | ||
| REJECTED | = lv_rejected | |
| TABLES | ||
| OBJECT_IDS | = lt_object_ids | |
| TYPESTOREAD | = lt_typestoread | |
| RETURN | = lt_return | |
| . " BM_CHECK_READ_PARAMETERS | ||
ABAP code using 7.40 inline data declarations to call FM BM_CHECK_READ_PARAMETERS
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 CICO_REQNO FROM RPYGSGF INTO @DATA(ld_cico_request_no). | ||||
| "SELECT single MODE FROM RPYGSGF INTO @DATA(ld_mode). | ||||
| "SELECT single NAMES_ONLY FROM BAPIBEGEN INTO @DATA(ld_names_only). | ||||
| "SELECT single LANGU FROM BAPI_LAISO INTO @DATA(ld_language). | ||||
| "SELECT single ADDON FROM BAPIBEGEN INTO @DATA(ld_addon). | ||||
| "SELECT single TIME_STAMP FROM BAPIBEGEN INTO @DATA(ld_time_stamp). | ||||
| "SELECT single LAST_USER FROM BAPIBEGEN INTO @DATA(ld_last_user). | ||||
Search for further information about these or an SAP related objects