SAP DGEXC_DL41_INSERT Function Module for NOTRANSL: Datensatz zum Puffer hinzufügen
DGEXC_DL41_INSERT is a standard dgexc dl41 insert 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: Datensatz zum Puffer hinzufügen 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 dgexc dl41 insert FM, simply by entering the name DGEXC_DL41_INSERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: DGEXC_DL41
Program Name: SAPLDGEXC_DL41
Main Program: SAPLDGEXC_DL41
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DGEXC_DL41_INSERT 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 'DGEXC_DL41_INSERT'"NOTRANSL: Datensatz zum Puffer hinzufügen.
EXPORTING
I_IOTAB = "Table Type for RDGEXCTEXTSIOT(DG Exc. Long Text Master Data)
IMPORTING Parameters details for DGEXC_DL41_INSERT
I_IOTAB - Table Type for RDGEXCTEXTSIOT(DG Exc. Long Text Master Data)
Data type: EHS_DGEXCTEXTSIOT_TOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for DGEXC_DL41_INSERT 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_iotab | TYPE EHS_DGEXCTEXTSIOT_T. " |
|   CALL FUNCTION 'DGEXC_DL41_INSERT' "NOTRANSL: Datensatz zum Puffer hinzufügen |
| EXPORTING | ||
| I_IOTAB | = lv_i_iotab | |
| . " DGEXC_DL41_INSERT | ||
ABAP code using 7.40 inline data declarations to call FM DGEXC_DL41_INSERT
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