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

Function BM_NAVIGATION_POPUP 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_NAVIGATION_POPUP'".
EXPORTING
NAV_TYP = "Type of object being navigated from
NAV_OBJ = "ID of the object being navigated from
* GRAPHIC_ACTIVE = ' ' "'X' if a graphics window is already open
* MODIFY = ' ' "
* REP_INFOSYSTEM = ' ' "'X' if called up from Rep. InfoSys (graphics)
* SEL_ID = ' ' "
IMPORTING
ACTION = "
IMPORTING Parameters details for BM_NAVIGATION_POPUP
NAV_TYP - Type of object being navigated from
Data type: DF41S-NODE_TYPOptional: No
Call by Reference: No ( called with pass by value option)
NAV_OBJ - ID of the object being navigated from
Data type: DF41S-PARENT_OBJOptional: No
Call by Reference: No ( called with pass by value option)
GRAPHIC_ACTIVE - 'X' if a graphics window is already open
Data type: BMT_FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MODIFY -
Data type: BMT_FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
REP_INFOSYSTEM - 'X' if called up from Rep. InfoSys (graphics)
Data type: BMT_FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
SEL_ID -
Data type: DF55L-SEL_IDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BM_NAVIGATION_POPUP
ACTION -
Data type: DM02L-ENTIDOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BM_NAVIGATION_POPUP 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_action | TYPE DM02L-ENTID, " | |||
| lv_nav_typ | TYPE DF41S-NODE_TYP, " | |||
| lv_nav_obj | TYPE DF41S-PARENT_OBJ, " | |||
| lv_graphic_active | TYPE BMT_FLAG, " SPACE | |||
| lv_modify | TYPE BMT_FLAG, " SPACE | |||
| lv_rep_infosystem | TYPE BMT_FLAG, " SPACE | |||
| lv_sel_id | TYPE DF55L-SEL_ID. " SPACE |
|   CALL FUNCTION 'BM_NAVIGATION_POPUP' " |
| EXPORTING | ||
| NAV_TYP | = lv_nav_typ | |
| NAV_OBJ | = lv_nav_obj | |
| GRAPHIC_ACTIVE | = lv_graphic_active | |
| MODIFY | = lv_modify | |
| REP_INFOSYSTEM | = lv_rep_infosystem | |
| SEL_ID | = lv_sel_id | |
| IMPORTING | ||
| ACTION | = lv_action | |
| . " BM_NAVIGATION_POPUP | ||
ABAP code using 7.40 inline data declarations to call FM BM_NAVIGATION_POPUP
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 ENTID FROM DM02L INTO @DATA(ld_action). | ||||
| "SELECT single NODE_TYP FROM DF41S INTO @DATA(ld_nav_typ). | ||||
| "SELECT single PARENT_OBJ FROM DF41S INTO @DATA(ld_nav_obj). | ||||
| DATA(ld_graphic_active) | = ' '. | |||
| DATA(ld_modify) | = ' '. | |||
| DATA(ld_rep_infosystem) | = ' '. | |||
| "SELECT single SEL_ID FROM DF55L INTO @DATA(ld_sel_id). | ||||
| DATA(ld_sel_id) | = ' '. | |||
Search for further information about these or an SAP related objects