SAP Function Modules

GUI_FILE_LOAD_DIALOG SAP Function module







GUI_FILE_LOAD_DIALOG 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 GUI_FILE_LOAD_DIALOG into the relevant SAP transaction such as SE37 or SE80.

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


Pattern for FM GUI_FILE_LOAD_DIALOG - GUI FILE LOAD DIALOG





CALL FUNCTION 'GUI_FILE_LOAD_DIALOG' "
* EXPORTING
*   window_title =              " string
*   default_extension =         " string
*   default_file_name =         " string
*   with_encoding =             " abap_bool
*   file_filter =               " string
*   initial_directory =         " string
  IMPORTING
    filename =                  " string
    path =                      " string
    fullpath =                  " string
    user_action =               " i
    file_encoding =             " abap_encoding
    .  "  GUI_FILE_LOAD_DIALOG

ABAP code example for Function Module GUI_FILE_LOAD_DIALOG





The ABAP code below is a full code listing to execute function module GUI_FILE_LOAD_DIALOG 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_filename  TYPE STRING ,
ld_path  TYPE STRING ,
ld_fullpath  TYPE STRING ,
ld_user_action  TYPE I ,
ld_file_encoding  TYPE ABAP_ENCODING .

DATA(ld_window_title) = 'Check type of data required'.
DATA(ld_default_extension) = 'Check type of data required'.
DATA(ld_default_file_name) = 'Check type of data required'.
DATA(ld_with_encoding) = 'Check type of data required'.
DATA(ld_file_filter) = 'Check type of data required'.
DATA(ld_initial_directory) = 'Check type of data required'. . CALL FUNCTION 'GUI_FILE_LOAD_DIALOG' * EXPORTING * window_title = ld_window_title * default_extension = ld_default_extension * default_file_name = ld_default_file_name * with_encoding = ld_with_encoding * file_filter = ld_file_filter * initial_directory = ld_initial_directory IMPORTING filename = ld_filename path = ld_path fullpath = ld_fullpath user_action = ld_user_action file_encoding = ld_file_encoding . " GUI_FILE_LOAD_DIALOG
IF SY-SUBRC EQ 0. "All OK 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_filename  TYPE STRING ,
ld_window_title  TYPE STRING ,
ld_path  TYPE STRING ,
ld_default_extension  TYPE STRING ,
ld_fullpath  TYPE STRING ,
ld_default_file_name  TYPE STRING ,
ld_user_action  TYPE I ,
ld_with_encoding  TYPE ABAP_BOOL ,
ld_file_encoding  TYPE ABAP_ENCODING ,
ld_file_filter  TYPE STRING ,
ld_initial_directory  TYPE STRING .

ld_window_title = 'Check type of data required'.
ld_default_extension = 'Check type of data required'.
ld_default_file_name = 'Check type of data required'.
ld_with_encoding = 'Check type of data required'.
ld_file_filter = 'Check type of data required'.
ld_initial_directory = 'Check type of data required'.

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 GUI_FILE_LOAD_DIALOG or its description.