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

Function BDS_CALL_NAVIGATOR 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 'BDS_CALL_NAVIGATOR'".
EXPORTING
* LOGICAL_SYSTEM = "Logical System
CLASSNAME = "Class Name
CLASSTYPE = "Class Type
* OBJKEY = "Object Key
* CLIENT = SY-MANDT "Client
* DISPLAY_SINGLE_DOC = "If only One Document Exists -> Display
* DISPLAY_DOC = "Document to Be Displayed
TABLES
* SIGNATURE = "
* EXCLUDING = "
* FIXED_ATTRIBUTES = "List of Fixed Attributes
* FRAMEWORK = "
EXCEPTIONS
INTERNAL_ERROR = 1 NOT_AUTHORIZED = 2
IMPORTING Parameters details for BDS_CALL_NAVIGATOR
LOGICAL_SYSTEM - Logical System
Data type: BAPIBDS01-LOG_SYSTEMOptional: Yes
Call by Reference: No ( called with pass by value option)
CLASSNAME - Class Name
Data type: BAPIBDS01-CLASSNAMEOptional: No
Call by Reference: No ( called with pass by value option)
CLASSTYPE - Class Type
Data type: BAPIBDS01-CLASSTYPEOptional: No
Call by Reference: No ( called with pass by value option)
OBJKEY - Object Key
Data type: BAPIBDS01-OBJKEYOptional: Yes
Call by Reference: No ( called with pass by value option)
CLIENT - Client
Data type: BAPIBDS01-CLIENTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
DISPLAY_SINGLE_DOC - If only One Document Exists -> Display
Data type: BAPIBDS01-XOptional: Yes
Call by Reference: No ( called with pass by value option)
DISPLAY_DOC - Document to Be Displayed
Data type: BDN_CONOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BDS_CALL_NAVIGATOR
SIGNATURE -
Data type: BAPISIGNATOptional: Yes
Call by Reference: Yes
EXCLUDING -
Data type: BDN_FKTOptional: Yes
Call by Reference: Yes
FIXED_ATTRIBUTES - List of Fixed Attributes
Data type: BAPIPROPEROptional: Yes
Call by Reference: Yes
FRAMEWORK -
Data type: BDN_SELECTOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOT_AUTHORIZED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BDS_CALL_NAVIGATOR 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_signature | TYPE STANDARD TABLE OF BAPISIGNAT, " | |||
| lv_internal_error | TYPE BAPISIGNAT, " | |||
| lv_logical_system | TYPE BAPIBDS01-LOG_SYSTEM, " | |||
| lv_classname | TYPE BAPIBDS01-CLASSNAME, " | |||
| lt_excluding | TYPE STANDARD TABLE OF BDN_FKT, " | |||
| lv_not_authorized | TYPE BDN_FKT, " | |||
| lv_classtype | TYPE BAPIBDS01-CLASSTYPE, " | |||
| lt_fixed_attributes | TYPE STANDARD TABLE OF BAPIPROPER, " | |||
| lv_objkey | TYPE BAPIBDS01-OBJKEY, " | |||
| lt_framework | TYPE STANDARD TABLE OF BDN_SELECT, " | |||
| lv_client | TYPE BAPIBDS01-CLIENT, " SY-MANDT | |||
| lv_display_single_doc | TYPE BAPIBDS01-X, " | |||
| lv_display_doc | TYPE BDN_CON. " |
|   CALL FUNCTION 'BDS_CALL_NAVIGATOR' " |
| EXPORTING | ||
| LOGICAL_SYSTEM | = lv_logical_system | |
| CLASSNAME | = lv_classname | |
| CLASSTYPE | = lv_classtype | |
| OBJKEY | = lv_objkey | |
| CLIENT | = lv_client | |
| DISPLAY_SINGLE_DOC | = lv_display_single_doc | |
| DISPLAY_DOC | = lv_display_doc | |
| TABLES | ||
| SIGNATURE | = lt_signature | |
| EXCLUDING | = lt_excluding | |
| FIXED_ATTRIBUTES | = lt_fixed_attributes | |
| FRAMEWORK | = lt_framework | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| NOT_AUTHORIZED = 2 | ||
| . " BDS_CALL_NAVIGATOR | ||
ABAP code using 7.40 inline data declarations to call FM BDS_CALL_NAVIGATOR
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 LOG_SYSTEM FROM BAPIBDS01 INTO @DATA(ld_logical_system). | ||||
| "SELECT single CLASSNAME FROM BAPIBDS01 INTO @DATA(ld_classname). | ||||
| "SELECT single CLASSTYPE FROM BAPIBDS01 INTO @DATA(ld_classtype). | ||||
| "SELECT single OBJKEY FROM BAPIBDS01 INTO @DATA(ld_objkey). | ||||
| "SELECT single CLIENT FROM BAPIBDS01 INTO @DATA(ld_client). | ||||
| DATA(ld_client) | = SY-MANDT. | |||
| "SELECT single X FROM BAPIBDS01 INTO @DATA(ld_display_single_doc). | ||||
Search for further information about these or an SAP related objects