SAP ISU_M_FILE_CHECK Function Module for INTERNAL: IS-U Migration - Check Whether File Exists
ISU_M_FILE_CHECK is a standard isu m file check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for INTERNAL: IS-U Migration - Check Whether File Exists processing and below is the pattern details for this FM, 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 isu m file check FM, simply by entering the name ISU_M_FILE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: EMIG_FILE
Program Name: SAPLEMIG_FILE
Main Program: SAPLEMIG_FILE
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function ISU_M_FILE_CHECK 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 'ISU_M_FILE_CHECK'"INTERNAL: IS-U Migration - Check Whether File Exists.
EXPORTING
* X_PATH = "Migration path
X_FILE = "
IMPORTING
Y_FILE_EXIST = "
IMPORTING Parameters details for ISU_M_FILE_CHECK
X_PATH - Migration path
Data type: TEMFD-PATHOptional: Yes
Call by Reference: No ( called with pass by value option)
X_FILE -
Data type: TEMFD-FILEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISU_M_FILE_CHECK
Y_FILE_EXIST -
Data type: TEMFD-EMG_CHECKOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_M_FILE_CHECK 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_x_path | TYPE TEMFD-PATH, " | |||
| lv_y_file_exist | TYPE TEMFD-EMG_CHECK, " | |||
| lv_x_file | TYPE TEMFD-FILE. " |
|   CALL FUNCTION 'ISU_M_FILE_CHECK' "INTERNAL: IS-U Migration - Check Whether File Exists |
| EXPORTING | ||
| X_PATH | = lv_x_path | |
| X_FILE | = lv_x_file | |
| IMPORTING | ||
| Y_FILE_EXIST | = lv_y_file_exist | |
| . " ISU_M_FILE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM ISU_M_FILE_CHECK
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 PATH FROM TEMFD INTO @DATA(ld_x_path). | ||||
| "SELECT single EMG_CHECK FROM TEMFD INTO @DATA(ld_y_file_exist). | ||||
| "SELECT single FILE FROM TEMFD INTO @DATA(ld_x_file). | ||||
Search for further information about these or an SAP related objects