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

Function BM_APPL_COMPS_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 'BM_APPL_COMPS_SELECT'".
EXPORTING
* SHOW = ' ' "Display mode
PROJECT_NAME = "Project ID
* PROJECT_LANGUAGE = SY-LANGU "Project Language
* PROJECT_TEXT = ' ' "
* NO_DIALOG = ' ' "
IMPORTING
SELECTION_CHANGED = "
TABLES
* SEL_COMPONENTS = "Selected functions
* IMG_ACTIVITIES = "Selected chapters
EXCEPTIONS
DATA_ERROR = 1 UNDEFINED_COMPONENTS = 2
IMPORTING Parameters details for BM_APPL_COMPS_SELECT
SHOW - Display mode
Data type: BMT_FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
PROJECT_NAME - Project ID
Data type: TPROJECT-PROJECT_IDOptional: No
Call by Reference: No ( called with pass by value option)
PROJECT_LANGUAGE - Project Language
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
PROJECT_TEXT -
Data type: DF50T-NAMEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
NO_DIALOG -
Data type: BMT_FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BM_APPL_COMPS_SELECT
SELECTION_CHANGED -
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BM_APPL_COMPS_SELECT
SEL_COMPONENTS - Selected functions
Data type: APPL_COMPSOptional: Yes
Call by Reference: No ( called with pass by value option)
IMG_ACTIVITIES - Selected chapters
Data type: DSYSOBJOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DATA_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNDEFINED_COMPONENTS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BM_APPL_COMPS_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: | ||||
| lv_show | TYPE BMT_FLAG, " SPACE | |||
| lv_data_error | TYPE BMT_FLAG, " | |||
| lt_sel_components | TYPE STANDARD TABLE OF APPL_COMPS, " | |||
| lv_selection_changed | TYPE CHAR1, " | |||
| lv_project_name | TYPE TPROJECT-PROJECT_ID, " | |||
| lt_img_activities | TYPE STANDARD TABLE OF DSYSOBJ, " | |||
| lv_undefined_components | TYPE DSYSOBJ, " | |||
| lv_project_language | TYPE SY-LANGU, " SY-LANGU | |||
| lv_project_text | TYPE DF50T-NAME, " SPACE | |||
| lv_no_dialog | TYPE BMT_FLAG. " SPACE |
|   CALL FUNCTION 'BM_APPL_COMPS_SELECT' " |
| EXPORTING | ||
| SHOW | = lv_show | |
| PROJECT_NAME | = lv_project_name | |
| PROJECT_LANGUAGE | = lv_project_language | |
| PROJECT_TEXT | = lv_project_text | |
| NO_DIALOG | = lv_no_dialog | |
| IMPORTING | ||
| SELECTION_CHANGED | = lv_selection_changed | |
| TABLES | ||
| SEL_COMPONENTS | = lt_sel_components | |
| IMG_ACTIVITIES | = lt_img_activities | |
| EXCEPTIONS | ||
| DATA_ERROR = 1 | ||
| UNDEFINED_COMPONENTS = 2 | ||
| . " BM_APPL_COMPS_SELECT | ||
ABAP code using 7.40 inline data declarations to call FM BM_APPL_COMPS_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.| DATA(ld_show) | = ' '. | |||
| "SELECT single PROJECT_ID FROM TPROJECT INTO @DATA(ld_project_name). | ||||
| "SELECT single LANGU FROM SY INTO @DATA(ld_project_language). | ||||
| DATA(ld_project_language) | = SY-LANGU. | |||
| "SELECT single NAME FROM DF50T INTO @DATA(ld_project_text). | ||||
| DATA(ld_project_text) | = ' '. | |||
| DATA(ld_no_dialog) | = ' '. | |||
Search for further information about these or an SAP related objects