SAP EDI_DATA_INCOMING Function Module for EDI: Call inbound processing for IDoc file
EDI_DATA_INCOMING is a standard edi data incoming SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for EDI: Call inbound processing for IDoc file 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 edi data incoming FM, simply by entering the name EDI_DATA_INCOMING into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDIN
Program Name: SAPLEDIN
Main Program: SAPLEDIN
Appliation area: S
Release date: 17-Sep-1996
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function EDI_DATA_INCOMING 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 'EDI_DATA_INCOMING'"EDI: Call inbound processing for IDoc file.
EXPORTING
PATHNAME = "Complete file name
PORT = "Port name
IMPORTING Parameters details for EDI_DATA_INCOMING
PATHNAME - Complete file name
Data type: EDI_PATH-PTHNAMOptional: No
Call by Reference: No ( called with pass by value option)
PORT - Port name
Data type: EDIPO-PORTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for EDI_DATA_INCOMING 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_pathname | TYPE EDI_PATH-PTHNAM, " | |||
| lv_port | TYPE EDIPO-PORT. " |
|   CALL FUNCTION 'EDI_DATA_INCOMING' "EDI: Call inbound processing for IDoc file |
| EXPORTING | ||
| PATHNAME | = lv_pathname | |
| PORT | = lv_port | |
| . " EDI_DATA_INCOMING | ||
ABAP code using 7.40 inline data declarations to call FM EDI_DATA_INCOMING
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 PTHNAM FROM EDI_PATH INTO @DATA(ld_pathname). | ||||
| "SELECT single PORT FROM EDIPO INTO @DATA(ld_port). | ||||
Search for further information about these or an SAP related objects