SAP Function Modules

BDT_FUNCTION_NAVIGATE SAP Function module







BDT_FUNCTION_NAVIGATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name BDT_FUNCTION_NAVIGATE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: BUSS
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM BDT_FUNCTION_NAVIGATE - BDT FUNCTION NAVIGATE





CALL FUNCTION 'BDT_FUNCTION_NAVIGATE' "
* EXPORTING
*   iv_handle =                 " bdt_instance_id  Handle
*   iv_vartp = '~'              " bu_vartp      Screen Sequence Category
*   iv_varnr =                  " bu_varnr      Screen Sequence
*   iv_dynid =                  " bu_dynid      Screen
*   iv_screen_type =            " bdt_screen_type
*   iv_screen_posnr =           " bu_posnr      Item Number (for Sequence)
*   iv_screen_view =            " bu_sicht      View
*   iv_screen_section =         " bu_absnr      Section
*   iv_screen_command =         " syucomm       Navigation Command
*   iv_cursorfield =            " bu_tbfld      Table field (table name-field name)
*   iv_cursorline =             " sylilli       List processing, current list line
*   iv_action =                 " bus000flds-char1
*   iv_xsimulate =              " bdt_boole_d
*   iv_xpush =                  " bdt_boole_d
*   iv_xsuppress_nav =          " bdt_boole_d
*   iv_xreset_scrollpos = SPACE  " bdt_boole_d
  IMPORTING
    ev_other_screen =           " boole_d
    ev_xscpp =                  " boole_d
    ev_spall =                  " bu_spall      Coordinates of left column (dialog box)
    ev_zeilo =                  " bu_zeilo      Coordinates of top line (dialog box)
    ev_spalr =                  " bu_spalr      Coordinates of right column (dialog box)
    ev_zeilu =                  " bu_zeilu      Coordinates of bottom line (dialog box)
    ev_pop =                    " boole_d
* TABLES
*   it_params =                 "
  EXCEPTIONS
    HANDLE_NOT_FOUND = 1        "
    ILLEGAL_SCREEN_TYPE = 2     "
    ILLEGAL_POSNR = 3           "
    FIRST_DATA_SCREEN = 4       "
    LAST_DATA_SCREEN = 5        "
    SCREEN_NOT_FOUND = 6        "
    SCREENTYPE_NOT_ACTIVE = 7   "
    GENERAL_ERROR = 8           "               Non-Specified Error
    NO_SCREEN_VISIBLE = 9       "
    .  "  BDT_FUNCTION_NAVIGATE

ABAP code example for Function Module BDT_FUNCTION_NAVIGATE





The ABAP code below is a full code listing to execute function module BDT_FUNCTION_NAVIGATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ev_other_screen  TYPE BOOLE_D ,
ld_ev_xscpp  TYPE BOOLE_D ,
ld_ev_spall  TYPE BU_SPALL ,
ld_ev_zeilo  TYPE BU_ZEILO ,
ld_ev_spalr  TYPE BU_SPALR ,
ld_ev_zeilu  TYPE BU_ZEILU ,
ld_ev_pop  TYPE BOOLE_D ,
it_it_params  TYPE STANDARD TABLE OF STRING,"TABLES PARAM
wa_it_params  LIKE LINE OF it_it_params .

DATA(ld_iv_handle) = 'Check type of data required'.
DATA(ld_iv_vartp) = 'Check type of data required'.
DATA(ld_iv_varnr) = 'Check type of data required'.
DATA(ld_iv_dynid) = 'Check type of data required'.
DATA(ld_iv_screen_type) = 'Check type of data required'.
DATA(ld_iv_screen_posnr) = 'Check type of data required'.
DATA(ld_iv_screen_view) = 'Check type of data required'.
DATA(ld_iv_screen_section) = 'Check type of data required'.
DATA(ld_iv_screen_command) = 'some text here'.
DATA(ld_iv_cursorfield) = 'some text here'.
DATA(ld_iv_cursorline) = '123 '.

DATA(ld_iv_action) = some text here
DATA(ld_iv_xsimulate) = '123 '.
DATA(ld_iv_xpush) = '123 '.
DATA(ld_iv_xsuppress_nav) = '123 '.
DATA(ld_iv_xreset_scrollpos) = '123 '.

"populate fields of struture and append to itab
append wa_it_params to it_it_params. . CALL FUNCTION 'BDT_FUNCTION_NAVIGATE' * EXPORTING * iv_handle = ld_iv_handle * iv_vartp = ld_iv_vartp * iv_varnr = ld_iv_varnr * iv_dynid = ld_iv_dynid * iv_screen_type = ld_iv_screen_type * iv_screen_posnr = ld_iv_screen_posnr * iv_screen_view = ld_iv_screen_view * iv_screen_section = ld_iv_screen_section * iv_screen_command = ld_iv_screen_command * iv_cursorfield = ld_iv_cursorfield * iv_cursorline = ld_iv_cursorline * iv_action = ld_iv_action * iv_xsimulate = ld_iv_xsimulate * iv_xpush = ld_iv_xpush * iv_xsuppress_nav = ld_iv_xsuppress_nav * iv_xreset_scrollpos = ld_iv_xreset_scrollpos IMPORTING ev_other_screen = ld_ev_other_screen ev_xscpp = ld_ev_xscpp ev_spall = ld_ev_spall ev_zeilo = ld_ev_zeilo ev_spalr = ld_ev_spalr ev_zeilu = ld_ev_zeilu ev_pop = ld_ev_pop * TABLES * it_params = it_it_params EXCEPTIONS HANDLE_NOT_FOUND = 1 ILLEGAL_SCREEN_TYPE = 2 ILLEGAL_POSNR = 3 FIRST_DATA_SCREEN = 4 LAST_DATA_SCREEN = 5 SCREEN_NOT_FOUND = 6 SCREENTYPE_NOT_ACTIVE = 7 GENERAL_ERROR = 8 NO_SCREEN_VISIBLE = 9 . " BDT_FUNCTION_NAVIGATE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 4. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 5. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 6. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 7. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 8. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 9. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_ev_other_screen  TYPE BOOLE_D ,
ld_iv_handle  TYPE BDT_INSTANCE_ID ,
it_it_params  TYPE STANDARD TABLE OF STRING ,
wa_it_params  LIKE LINE OF it_it_params,
ld_ev_xscpp  TYPE BOOLE_D ,
ld_iv_vartp  TYPE BU_VARTP ,
ld_ev_spall  TYPE BU_SPALL ,
ld_iv_varnr  TYPE BU_VARNR ,
ld_ev_zeilo  TYPE BU_ZEILO ,
ld_iv_dynid  TYPE BU_DYNID ,
ld_ev_spalr  TYPE BU_SPALR ,
ld_iv_screen_type  TYPE BDT_SCREEN_TYPE ,
ld_iv_screen_posnr  TYPE BU_POSNR ,
ld_ev_zeilu  TYPE BU_ZEILU ,
ld_iv_screen_view  TYPE BU_SICHT ,
ld_ev_pop  TYPE BOOLE_D ,
ld_iv_screen_section  TYPE BU_ABSNR ,
ld_iv_screen_command  TYPE SYUCOMM ,
ld_iv_cursorfield  TYPE BU_TBFLD ,
ld_iv_cursorline  TYPE SYLILLI ,
ld_iv_action  TYPE BUS000FLDS-CHAR1 ,
ld_iv_xsimulate  TYPE BDT_BOOLE_D ,
ld_iv_xpush  TYPE BDT_BOOLE_D ,
ld_iv_xsuppress_nav  TYPE BDT_BOOLE_D ,
ld_iv_xreset_scrollpos  TYPE BDT_BOOLE_D .

ld_iv_handle = '123 '.

"populate fields of struture and append to itab
append wa_it_params to it_it_params.
ld_iv_vartp = '123 '.
ld_iv_varnr = '123 '.
ld_iv_dynid = '123 '.
ld_iv_screen_type = '123 '.
ld_iv_screen_posnr = '123 '.
ld_iv_screen_view = '123 '.
ld_iv_screen_section = '123 '.
ld_iv_screen_command = 'some text here'.
ld_iv_cursorfield = 'some text here'.
ld_iv_cursorline = '123 '.

ld_iv_action = some text here
ld_iv_xsimulate = '123 '.
ld_iv_xpush = '123 '.
ld_iv_xsuppress_nav = '123 '.
ld_iv_xreset_scrollpos = '123 '.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name BDT_FUNCTION_NAVIGATE or its description.