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

Function F4_DXFILENAME_TOPRECURSION 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 'F4_DXFILENAME_TOPRECURSION'".
EXPORTING
* I_LOCATION_FLAG = ' ' "Flag: Application or presentation server
* I_SERVER = '?' "Application Server
* I_PATH = "
* FILEMASK = '*.*' "
* FILEOPERATION = 'R' "
IMPORTING
O_LOCATION_FLAG = "
O_SERVER = "
O_PATH = "
ABEND_FLAG = "
EXCEPTIONS
RFC_ERROR = 1 ERROR_WITH_GUI = 2
IMPORTING Parameters details for F4_DXFILENAME_TOPRECURSION
I_LOCATION_FLAG - Flag: Application or presentation server
Data type: DXFIELDS-LOCATIONDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_SERVER - Application Server
Data type: MSXXLIST-NAMEDefault: '?'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_PATH -
Data type: DXFIELDS-LONGPATHOptional: Yes
Call by Reference: No ( called with pass by value option)
FILEMASK -
Data type: DXFIELDS-FILEMASKDefault: '*.*'
Optional: Yes
Call by Reference: No ( called with pass by value option)
FILEOPERATION -
Data type: DXFIELDS-FILEOPERDefault: 'R'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for F4_DXFILENAME_TOPRECURSION
O_LOCATION_FLAG -
Data type: DXFIELDS-LOCATIONOptional: No
Call by Reference: No ( called with pass by value option)
O_SERVER -
Data type: MSXXLIST-NAMEOptional: No
Call by Reference: No ( called with pass by value option)
O_PATH -
Data type: DXFIELDS-LONGPATHOptional: No
Call by Reference: No ( called with pass by value option)
ABEND_FLAG -
Data type: DXFIELDS-ABENDFLAGOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
RFC_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR_WITH_GUI -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for F4_DXFILENAME_TOPRECURSION 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_rfc_error | TYPE STRING, " | |||
| lv_i_location_flag | TYPE DXFIELDS-LOCATION, " ' ' | |||
| lv_o_location_flag | TYPE DXFIELDS-LOCATION, " | |||
| lv_i_server | TYPE MSXXLIST-NAME, " '?' | |||
| lv_o_server | TYPE MSXXLIST-NAME, " | |||
| lv_error_with_gui | TYPE MSXXLIST, " | |||
| lv_i_path | TYPE DXFIELDS-LONGPATH, " | |||
| lv_o_path | TYPE DXFIELDS-LONGPATH, " | |||
| lv_filemask | TYPE DXFIELDS-FILEMASK, " '*,*' | |||
| lv_abend_flag | TYPE DXFIELDS-ABENDFLAG, " | |||
| lv_fileoperation | TYPE DXFIELDS-FILEOPER. " 'R' |
|   CALL FUNCTION 'F4_DXFILENAME_TOPRECURSION' " |
| EXPORTING | ||
| I_LOCATION_FLAG | = lv_i_location_flag | |
| I_SERVER | = lv_i_server | |
| I_PATH | = lv_i_path | |
| FILEMASK | = lv_filemask | |
| FILEOPERATION | = lv_fileoperation | |
| IMPORTING | ||
| O_LOCATION_FLAG | = lv_o_location_flag | |
| O_SERVER | = lv_o_server | |
| O_PATH | = lv_o_path | |
| ABEND_FLAG | = lv_abend_flag | |
| EXCEPTIONS | ||
| RFC_ERROR = 1 | ||
| ERROR_WITH_GUI = 2 | ||
| . " F4_DXFILENAME_TOPRECURSION | ||
ABAP code using 7.40 inline data declarations to call FM F4_DXFILENAME_TOPRECURSION
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 LOCATION FROM DXFIELDS INTO @DATA(ld_i_location_flag). | ||||
| DATA(ld_i_location_flag) | = ' '. | |||
| "SELECT single LOCATION FROM DXFIELDS INTO @DATA(ld_o_location_flag). | ||||
| "SELECT single NAME FROM MSXXLIST INTO @DATA(ld_i_server). | ||||
| DATA(ld_i_server) | = '?'. | |||
| "SELECT single NAME FROM MSXXLIST INTO @DATA(ld_o_server). | ||||
| "SELECT single LONGPATH FROM DXFIELDS INTO @DATA(ld_i_path). | ||||
| "SELECT single LONGPATH FROM DXFIELDS INTO @DATA(ld_o_path). | ||||
| "SELECT single FILEMASK FROM DXFIELDS INTO @DATA(ld_filemask). | ||||
| DATA(ld_filemask) | = '*.*'. | |||
| "SELECT single ABENDFLAG FROM DXFIELDS INTO @DATA(ld_abend_flag). | ||||
| "SELECT single FILEOPER FROM DXFIELDS INTO @DATA(ld_fileoperation). | ||||
| DATA(ld_fileoperation) | = 'R'. | |||
Search for further information about these or an SAP related objects