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

Function BM_OBJECT_TYPE_F4_HELP 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_OBJECT_TYPE_F4_HELP'".
EXPORTING
I_OBJECT_TYPE = "
* I_OBJECT_ID = "Object ID
* I_DISPLAY = "Data element for Flag - Any use
* I_MULTIPLE_SELECTION = "Data element for Flag - Any use
* I_SELECTION_VARIANT = ' ' "Variant Name
* I_RFC_DESTINATION = ' ' "Logical Destination (Specified in Function Call)
TABLES
* E_OBJECT_IDS = "Object IDs
EXCEPTIONS
CANCELLED = 1 RFC_FAILURE = 2
IMPORTING Parameters details for BM_OBJECT_TYPE_F4_HELP
I_OBJECT_TYPE -
Data type: BMOBJECT-TYPEOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJECT_ID - Object ID
Data type: BMOBJECT-IDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DISPLAY - Data element for Flag - Any use
Data type: UFFLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_MULTIPLE_SELECTION - Data element for Flag - Any use
Data type: UFFLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
I_SELECTION_VARIANT - Variant Name
Data type: RSVAR-VARIANTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_RFC_DESTINATION - Logical Destination (Specified in Function Call)
Data type: RFCDESTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BM_OBJECT_TYPE_F4_HELP
E_OBJECT_IDS - Object IDs
Data type: BMOBJDEFSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
CANCELLED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RFC_FAILURE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BM_OBJECT_TYPE_F4_HELP 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_cancelled | TYPE STRING, " | |||
| lt_e_object_ids | TYPE STANDARD TABLE OF BMOBJDEFS, " | |||
| lv_i_object_type | TYPE BMOBJECT-TYPE, " | |||
| lv_i_object_id | TYPE BMOBJECT-ID, " | |||
| lv_rfc_failure | TYPE BMOBJECT, " | |||
| lv_i_display | TYPE UFFLAG, " | |||
| lv_i_multiple_selection | TYPE UFFLAG, " | |||
| lv_i_selection_variant | TYPE RSVAR-VARIANT, " SPACE | |||
| lv_i_rfc_destination | TYPE RFCDEST. " SPACE |
|   CALL FUNCTION 'BM_OBJECT_TYPE_F4_HELP' " |
| EXPORTING | ||
| I_OBJECT_TYPE | = lv_i_object_type | |
| I_OBJECT_ID | = lv_i_object_id | |
| I_DISPLAY | = lv_i_display | |
| I_MULTIPLE_SELECTION | = lv_i_multiple_selection | |
| I_SELECTION_VARIANT | = lv_i_selection_variant | |
| I_RFC_DESTINATION | = lv_i_rfc_destination | |
| TABLES | ||
| E_OBJECT_IDS | = lt_e_object_ids | |
| EXCEPTIONS | ||
| CANCELLED = 1 | ||
| RFC_FAILURE = 2 | ||
| . " BM_OBJECT_TYPE_F4_HELP | ||
ABAP code using 7.40 inline data declarations to call FM BM_OBJECT_TYPE_F4_HELP
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 TYPE FROM BMOBJECT INTO @DATA(ld_i_object_type). | ||||
| "SELECT single ID FROM BMOBJECT INTO @DATA(ld_i_object_id). | ||||
| "SELECT single VARIANT FROM RSVAR INTO @DATA(ld_i_selection_variant). | ||||
| DATA(ld_i_selection_variant) | = ' '. | |||
| DATA(ld_i_rfc_destination) | = ' '. | |||
Search for further information about these or an SAP related objects