SAP BMLM_OBJECTS_SELECT Function Module for
BMLM_OBJECTS_SELECT is a standard bmlm objects select 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 bmlm objects select FM, simply by entering the name BMLM_OBJECTS_SELECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SF23
Program Name: SAPLSF23
Main Program: SAPLSF23
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BMLM_OBJECTS_SELECT 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 'BMLM_OBJECTS_SELECT'".
EXPORTING
SYNCH_PARTNER = "GUID of LM DB synching wiht R/3
TIME_STAMP = "Objects last change later than time stamp
OBJ_TYPE = "Object type
* HIER_STRUCTURE = ' ' "' ' = Object 'X' = Children 'V' = Variants
* USER_NAME = SY-UNAME "' ' = everybody's objects
* INCLUDE_NON_ORIGINALS = ' ' "Include non TADIR originals
IMPORTING
ERROR_OCCURRED = "
PROCESSING_STATUS = "
TABLES
SYNCH_LIST = "List of objects to by snchronized
* ERRORS = "
IMPORTING Parameters details for BMLM_OBJECTS_SELECT
SYNCH_PARTNER - GUID of LM DB synching wiht R/3
Data type: BMLMIDS-IDENTOptional: No
Call by Reference: No ( called with pass by value option)
TIME_STAMP - Objects last change later than time stamp
Data type: TZONREF-TSTAMPS_LOOptional: No
Call by Reference: No ( called with pass by value option)
OBJ_TYPE - Object type
Data type: BMLMIDS-OBJ_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
HIER_STRUCTURE - SPACE = Object 'X' = Children 'V' = Variants
Data type: RPYGSGF-FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
USER_NAME - SPACE = everybody's objects
Data type: SY-UNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)
INCLUDE_NON_ORIGINALS - Include non TADIR originals
Data type: RPYGSGF-FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BMLM_OBJECTS_SELECT
ERROR_OCCURRED -
Data type: RPYGSGF-ERR_EXISTOptional: No
Call by Reference: No ( called with pass by value option)
PROCESSING_STATUS -
Data type: RPYGSGF-PROC_STATOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BMLM_OBJECTS_SELECT
SYNCH_LIST - List of objects to by snchronized
Data type: BMLMSYNCHOptional: No
Call by Reference: No ( called with pass by value option)
ERRORS -
Data type: RPYGSEROptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BMLM_OBJECTS_SELECT 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_synch_list | TYPE STANDARD TABLE OF BMLMSYNCH, " | |||
| lv_synch_partner | TYPE BMLMIDS-IDENT, " | |||
| lv_error_occurred | TYPE RPYGSGF-ERR_EXIST, " | |||
| lt_errors | TYPE STANDARD TABLE OF RPYGSER, " | |||
| lv_time_stamp | TYPE TZONREF-TSTAMPS_LO, " | |||
| lv_processing_status | TYPE RPYGSGF-PROC_STAT, " | |||
| lv_obj_type | TYPE BMLMIDS-OBJ_TYPE, " | |||
| lv_hier_structure | TYPE RPYGSGF-FLAG, " SPACE | |||
| lv_user_name | TYPE SY-UNAME, " SY-UNAME | |||
| lv_include_non_originals | TYPE RPYGSGF-FLAG. " SPACE |
|   CALL FUNCTION 'BMLM_OBJECTS_SELECT' " |
| EXPORTING | ||
| SYNCH_PARTNER | = lv_synch_partner | |
| TIME_STAMP | = lv_time_stamp | |
| OBJ_TYPE | = lv_obj_type | |
| HIER_STRUCTURE | = lv_hier_structure | |
| USER_NAME | = lv_user_name | |
| INCLUDE_NON_ORIGINALS | = lv_include_non_originals | |
| IMPORTING | ||
| ERROR_OCCURRED | = lv_error_occurred | |
| PROCESSING_STATUS | = lv_processing_status | |
| TABLES | ||
| SYNCH_LIST | = lt_synch_list | |
| ERRORS | = lt_errors | |
| . " BMLM_OBJECTS_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM BMLM_OBJECTS_SELECT
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 IDENT FROM BMLMIDS INTO @DATA(ld_synch_partner). | ||||
| "SELECT single ERR_EXIST FROM RPYGSGF INTO @DATA(ld_error_occurred). | ||||
| "SELECT single TSTAMPS_LO FROM TZONREF INTO @DATA(ld_time_stamp). | ||||
| "SELECT single PROC_STAT FROM RPYGSGF INTO @DATA(ld_processing_status). | ||||
| "SELECT single OBJ_TYPE FROM BMLMIDS INTO @DATA(ld_obj_type). | ||||
| "SELECT single FLAG FROM RPYGSGF INTO @DATA(ld_hier_structure). | ||||
| DATA(ld_hier_structure) | = ' '. | |||
| "SELECT single UNAME FROM SY INTO @DATA(ld_user_name). | ||||
| DATA(ld_user_name) | = SY-UNAME. | |||
| "SELECT single FLAG FROM RPYGSGF INTO @DATA(ld_include_non_originals). | ||||
| DATA(ld_include_non_originals) | = ' '. | |||
Search for further information about these or an SAP related objects