SAP EDM01_SELECT_EDID4 Function Module for NOTRANSL: Selektion EDID4
EDM01_SELECT_EDID4 is a standard edm01 select edid4 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: Selektion EDID4 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 edm01 select edid4 FM, simply by entering the name EDM01_SELECT_EDID4 into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDM01
Program Name: SAPLEDM01
Main Program: SAPLEDM01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EDM01_SELECT_EDID4 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 'EDM01_SELECT_EDID4'"NOTRANSL: Selektion EDID4.
TABLES
IT_EDIDC = "Control Record (IDoc)
OT_EDID4 = "IDoc Data Records from 4.0 onwards
EXCEPTIONS
NODATA = 1 PROGERROR = 2
TABLES Parameters details for EDM01_SELECT_EDID4
IT_EDIDC - Control Record (IDoc)
Data type: EDIDCOptional: No
Call by Reference: Yes
OT_EDID4 - IDoc Data Records from 4.0 onwards
Data type: EDID4Optional: No
Call by Reference: Yes
EXCEPTIONS details
NODATA - No Data Found
Data type:Optional: No
Call by Reference: Yes
PROGERROR - Program Error
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for EDM01_SELECT_EDID4 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_nodata | TYPE STRING, " | |||
| lt_it_edidc | TYPE STANDARD TABLE OF EDIDC, " | |||
| lt_ot_edid4 | TYPE STANDARD TABLE OF EDID4, " | |||
| lv_progerror | TYPE EDID4. " |
|   CALL FUNCTION 'EDM01_SELECT_EDID4' "NOTRANSL: Selektion EDID4 |
| TABLES | ||
| IT_EDIDC | = lt_it_edidc | |
| OT_EDID4 | = lt_ot_edid4 | |
| EXCEPTIONS | ||
| NODATA = 1 | ||
| PROGERROR = 2 | ||
| . " EDM01_SELECT_EDID4 | ||
ABAP code using 7.40 inline data declarations to call FM EDM01_SELECT_EDID4
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.Search for further information about these or an SAP related objects