SAP DX_FILE_WHERE_USED Function Module for
DX_FILE_WHERE_USED is a standard dx file where used 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 dx file where used FM, simply by entering the name DX_FILE_WHERE_USED into the relevant SAP transaction such as SE37 or SE38.
Function Group: DX_FILE_REG
Program Name: SAPLDX_FILE_REG
Main Program: SAPLDX_FILE_REG
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DX_FILE_WHERE_USED 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 'DX_FILE_WHERE_USED'".
EXPORTING
FILETYPE = "File type (L=logical, P=physical)
FILENAME = "File Name
IMPORTING
ACTIVERUN = "Data Transfer Run to R/3
TABLES
* TASKS = "Assignment of Files to Tasks
EXCEPTIONS
DB_ERROR = 1
IMPORTING Parameters details for DX_FILE_WHERE_USED
FILETYPE - File type (L=logical, P=physical)
Data type: DXFILE-FILETYPEOptional: No
Call by Reference: Yes
FILENAME - File Name
Data type: DXFILE-FILENAMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for DX_FILE_WHERE_USED
ACTIVERUN - Data Transfer Run to R/3
Data type: DXRUNOptional: No
Call by Reference: Yes
TABLES Parameters details for DX_FILE_WHERE_USED
TASKS - Assignment of Files to Tasks
Data type: DXTASKSOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
DB_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DX_FILE_WHERE_USED 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_tasks | TYPE STANDARD TABLE OF DXTASKS, " | |||
| lv_db_error | TYPE DXTASKS, " | |||
| lv_filetype | TYPE DXFILE-FILETYPE, " | |||
| lv_activerun | TYPE DXRUN, " | |||
| lv_filename | TYPE DXFILE-FILENAME. " |
|   CALL FUNCTION 'DX_FILE_WHERE_USED' " |
| EXPORTING | ||
| FILETYPE | = lv_filetype | |
| FILENAME | = lv_filename | |
| IMPORTING | ||
| ACTIVERUN | = lv_activerun | |
| TABLES | ||
| TASKS | = lt_tasks | |
| EXCEPTIONS | ||
| DB_ERROR = 1 | ||
| . " DX_FILE_WHERE_USED | ||
ABAP code using 7.40 inline data declarations to call FM DX_FILE_WHERE_USED
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 FILETYPE FROM DXFILE INTO @DATA(ld_filetype). | ||||
| "SELECT single FILENAME FROM DXFILE INTO @DATA(ld_filename). | ||||
Search for further information about these or an SAP related objects