SAP FILE_READ_AND_CONVERT_SAP_DATA Function Module for NOTRANSL: Einlesen einer Datei und Konvertierung ins SAP Format
FILE_READ_AND_CONVERT_SAP_DATA is a standard file read and convert sap data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Einlesen einer Datei und Konvertierung ins SAP Format 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 file read and convert sap data FM, simply by entering the name FILE_READ_AND_CONVERT_SAP_DATA into the relevant SAP transaction such as SE37 or SE38.
Function Group: TRUX
Program Name: SAPLTRUX
Main Program: SAPLTRUX
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FILE_READ_AND_CONVERT_SAP_DATA 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 'FILE_READ_AND_CONVERT_SAP_DATA'"NOTRANSL: Einlesen einer Datei und Konvertierung ins SAP Format.
EXPORTING
I_FILENAME = "Logical file name
* I_SERVERTYP = C_APPLICATION_SERVER "
* I_FILEFORMAT = "
* I_FIELD_SEPERATOR = "Character Field Length 1
* I_LINE_HEADER = "Character Field Length 1
IMPORTING
E_BIN_FILELENGTH = "
TABLES
* I_TAB_RECEIVER = "
EXCEPTIONS
FILE_NOT_FOUND = 1 CLOSE_FAILED = 2 AUTHORIZATION_FAILED = 3 OPEN_FAILED = 4 CONVERSION_FAILED = 5
IMPORTING Parameters details for FILE_READ_AND_CONVERT_SAP_DATA
I_FILENAME - Logical file name
Data type: FILENAME-FILEINTERNOptional: No
Call by Reference: No ( called with pass by value option)
I_SERVERTYP -
Data type: TRUXS_SERVERDefault: C_APPLICATION_SERVER
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_FILEFORMAT -
Data type: TRUXS_FILEFORMATOptional: Yes
Call by Reference: No ( called with pass by value option)
I_FIELD_SEPERATOR - Character Field Length 1
Data type: CHAR01Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LINE_HEADER - Character Field Length 1
Data type: CHAR01Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FILE_READ_AND_CONVERT_SAP_DATA
E_BIN_FILELENGTH -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FILE_READ_AND_CONVERT_SAP_DATA
I_TAB_RECEIVER -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FILE_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CLOSE_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
AUTHORIZATION_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OPEN_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
CONVERSION_FAILED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for FILE_READ_AND_CONVERT_SAP_DATA 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_i_filename | TYPE FILENAME-FILEINTERN, " | |||
| lv_file_not_found | TYPE FILENAME, " | |||
| lt_i_tab_receiver | TYPE STANDARD TABLE OF FILENAME, " | |||
| lv_e_bin_filelength | TYPE FILENAME, " | |||
| lv_i_servertyp | TYPE TRUXS_SERVER, " C_APPLICATION_SERVER | |||
| lv_close_failed | TYPE TRUXS_SERVER, " | |||
| lv_i_fileformat | TYPE TRUXS_FILEFORMAT, " | |||
| lv_authorization_failed | TYPE TRUXS_FILEFORMAT, " | |||
| lv_open_failed | TYPE TRUXS_FILEFORMAT, " | |||
| lv_i_field_seperator | TYPE CHAR01, " | |||
| lv_i_line_header | TYPE CHAR01, " | |||
| lv_conversion_failed | TYPE CHAR01. " |
|   CALL FUNCTION 'FILE_READ_AND_CONVERT_SAP_DATA' "NOTRANSL: Einlesen einer Datei und Konvertierung ins SAP Format |
| EXPORTING | ||
| I_FILENAME | = lv_i_filename | |
| I_SERVERTYP | = lv_i_servertyp | |
| I_FILEFORMAT | = lv_i_fileformat | |
| I_FIELD_SEPERATOR | = lv_i_field_seperator | |
| I_LINE_HEADER | = lv_i_line_header | |
| IMPORTING | ||
| E_BIN_FILELENGTH | = lv_e_bin_filelength | |
| TABLES | ||
| I_TAB_RECEIVER | = lt_i_tab_receiver | |
| EXCEPTIONS | ||
| FILE_NOT_FOUND = 1 | ||
| CLOSE_FAILED = 2 | ||
| AUTHORIZATION_FAILED = 3 | ||
| OPEN_FAILED = 4 | ||
| CONVERSION_FAILED = 5 | ||
| . " FILE_READ_AND_CONVERT_SAP_DATA | ||
ABAP code using 7.40 inline data declarations to call FM FILE_READ_AND_CONVERT_SAP_DATA
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 FILEINTERN FROM FILENAME INTO @DATA(ld_i_filename). | ||||
| DATA(ld_i_servertyp) | = C_APPLICATION_SERVER. | |||
Search for further information about these or an SAP related objects