SAP BM_RFC_OBJECT_NAVIGATE Function Module for
BM_RFC_OBJECT_NAVIGATE is a standard bm rfc object navigate 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 rfc object navigate FM, simply by entering the name BM_RFC_OBJECT_NAVIGATE 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): Remote-Enabled
Update:

Function BM_RFC_OBJECT_NAVIGATE 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_RFC_OBJECT_NAVIGATE'".
EXPORTING
I_OBJECT_TYPE = "Object Type
* I_RFC_DESTINATION = ' ' "Logical Destination (Specified in Function Call)
I_OBJECT_ID = "Object ID
* I_COMP_OBJ_ID = ' ' "
* I_NAV_CODE = '1' "Single-Character Flag
* I_MODE = 'SHOW' "CICO Mode
* I_LANGUAGE = SY-LANGU "SAP R/3 System, Current Language
* I_EXTENSION = ' ' "Structure enhancement ID
* I_INITIAL_SCREEN = ' ' "Data element for Flag - Any use
* I_POPUP = ' ' "Data element for Flag - Any use
IMPORTING
E_OBJECT_ID = "Object Definition
E_OBJECT_DATA = "
E_MESSAGE = "Transfer structure for messages
E_CANCELLED = "Data element for Flag - Any use
EXCEPTIONS
RFC_FAILURE = 1
IMPORTING Parameters details for BM_RFC_OBJECT_NAVIGATE
I_OBJECT_TYPE - Object Type
Data type: BMOBJECT-TYPEOptional: No
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)
I_OBJECT_ID - Object ID
Data type: BMOBJECT-IDOptional: No
Call by Reference: No ( called with pass by value option)
I_COMP_OBJ_ID -
Data type: BMOBJECT-IDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_NAV_CODE - Single-Character Flag
Data type: CHAR1Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_MODE - CICO Mode
Data type: RPYGSGF-MODEDefault: 'SHOW'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LANGUAGE - SAP R/3 System, Current Language
Data type: SY-LANGUDefault: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_EXTENSION - Structure enhancement ID
Data type: HIER_NAMESDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_INITIAL_SCREEN - Data element for Flag - Any use
Data type: UFFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_POPUP - Data element for Flag - Any use
Data type: UFFLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BM_RFC_OBJECT_NAVIGATE
E_OBJECT_ID - Object Definition
Data type: BMOBJECT-IDOptional: No
Call by Reference: No ( called with pass by value option)
E_OBJECT_DATA -
Data type: BMOBJDATAOptional: No
Call by Reference: No ( called with pass by value option)
E_MESSAGE - Transfer structure for messages
Data type: BMMSGOptional: No
Call by Reference: No ( called with pass by value option)
E_CANCELLED - Data element for Flag - Any use
Data type: UFFLAGOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
RFC_FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BM_RFC_OBJECT_NAVIGATE 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_e_object_id | TYPE BMOBJECT-ID, " | |||
| lv_rfc_failure | TYPE BMOBJECT, " | |||
| lv_i_object_type | TYPE BMOBJECT-TYPE, " | |||
| lv_i_rfc_destination | TYPE RFCDEST, " SPACE | |||
| lv_i_object_id | TYPE BMOBJECT-ID, " | |||
| lv_e_object_data | TYPE BMOBJDATA, " | |||
| lv_e_message | TYPE BMMSG, " | |||
| lv_i_comp_obj_id | TYPE BMOBJECT-ID, " SPACE | |||
| lv_i_nav_code | TYPE CHAR1, " '1' | |||
| lv_e_cancelled | TYPE UFFLAG, " | |||
| lv_i_mode | TYPE RPYGSGF-MODE, " 'SHOW' | |||
| lv_i_language | TYPE SY-LANGU, " SY-LANGU | |||
| lv_i_extension | TYPE HIER_NAMES, " SPACE | |||
| lv_i_initial_screen | TYPE UFFLAG, " SPACE | |||
| lv_i_popup | TYPE UFFLAG. " SPACE |
|   CALL FUNCTION 'BM_RFC_OBJECT_NAVIGATE' " |
| EXPORTING | ||
| I_OBJECT_TYPE | = lv_i_object_type | |
| I_RFC_DESTINATION | = lv_i_rfc_destination | |
| I_OBJECT_ID | = lv_i_object_id | |
| I_COMP_OBJ_ID | = lv_i_comp_obj_id | |
| I_NAV_CODE | = lv_i_nav_code | |
| I_MODE | = lv_i_mode | |
| I_LANGUAGE | = lv_i_language | |
| I_EXTENSION | = lv_i_extension | |
| I_INITIAL_SCREEN | = lv_i_initial_screen | |
| I_POPUP | = lv_i_popup | |
| IMPORTING | ||
| E_OBJECT_ID | = lv_e_object_id | |
| E_OBJECT_DATA | = lv_e_object_data | |
| E_MESSAGE | = lv_e_message | |
| E_CANCELLED | = lv_e_cancelled | |
| EXCEPTIONS | ||
| RFC_FAILURE = 1 | ||
| . " BM_RFC_OBJECT_NAVIGATE | ||
ABAP code using 7.40 inline data declarations to call FM BM_RFC_OBJECT_NAVIGATE
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 ID FROM BMOBJECT INTO @DATA(ld_e_object_id). | ||||
| "SELECT single TYPE FROM BMOBJECT INTO @DATA(ld_i_object_type). | ||||
| DATA(ld_i_rfc_destination) | = ' '. | |||
| "SELECT single ID FROM BMOBJECT INTO @DATA(ld_i_object_id). | ||||
| "SELECT single ID FROM BMOBJECT INTO @DATA(ld_i_comp_obj_id). | ||||
| DATA(ld_i_comp_obj_id) | = ' '. | |||
| DATA(ld_i_nav_code) | = '1'. | |||
| "SELECT single MODE FROM RPYGSGF INTO @DATA(ld_i_mode). | ||||
| DATA(ld_i_mode) | = 'SHOW'. | |||
| "SELECT single LANGU FROM SY INTO @DATA(ld_i_language). | ||||
| DATA(ld_i_language) | = SY-LANGU. | |||
| DATA(ld_i_extension) | = ' '. | |||
| DATA(ld_i_initial_screen) | = ' '. | |||
| DATA(ld_i_popup) | = ' '. | |||
Search for further information about these or an SAP related objects