SAP DMEE_PROCESS_INCOMING_FILE Function Module for NOTRANSL: DMEE: Bearbeite eingehende Datei









DMEE_PROCESS_INCOMING_FILE is a standard dmee process incoming file 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: DMEE: Bearbeite eingehende Datei 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 dmee process incoming file FM, simply by entering the name DMEE_PROCESS_INCOMING_FILE into the relevant SAP transaction such as SE37 or SE38.

Function Group: DMEE8
Program Name: SAPLDMEE8
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DMEE_PROCESS_INCOMING_FILE 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 'DMEE_PROCESS_INCOMING_FILE'"NOTRANSL: DMEE: Bearbeite eingehende Datei
  EXPORTING
   I_TREE_TYPE =  "DMEE: tree type
   I_TREE_ID =  "DMEE: unique description for a DMEE format tree
*  I_PARAMETER =  "DMEE: Control Parameter for DMEE Controller

 IMPORTING
   E_LOGH_SUMMARY =  "Application Log: Log Handle
   E_LOGH_ERROR =  "Application Log: Log Handle

TABLES
   FILE_INPUT =  "DMEE: Structure for Transferring Line Content
   RESULT_TAB1 =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  RESULT_TAB2 =  "DE-EN-LANG-SWITCH-NO-TRANSLATION

EXCEPTIONS
   TREE_INCOMPLETE = 1    TREE_INCONSISTENT = 2
.



IMPORTING Parameters details for DMEE_PROCESS_INCOMING_FILE

I_TREE_TYPE - DMEE: tree type

Data type: DMEE_TREETYPE
Optional: No
Call by Reference: No ( called with pass by value option)

I_TREE_ID - DMEE: unique description for a DMEE format tree

Data type: DMEE_TREEID
Optional: No
Call by Reference: No ( called with pass by value option)

I_PARAMETER - DMEE: Control Parameter for DMEE Controller

Data type: DMEE_PAR_INCOMING
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for DMEE_PROCESS_INCOMING_FILE

E_LOGH_SUMMARY - Application Log: Log Handle

Data type: BALLOGHNDL
Optional: No
Call by Reference: No ( called with pass by value option)

E_LOGH_ERROR - Application Log: Log Handle

Data type: BALLOGHNDL
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for DMEE_PROCESS_INCOMING_FILE

FILE_INPUT - DMEE: Structure for Transferring Line Content

Data type: DMEE_INPUT_FILE
Optional: No
Call by Reference: Yes

RESULT_TAB1 - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

RESULT_TAB2 - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

TREE_INCOMPLETE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

TREE_INCONSISTENT - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for DMEE_PROCESS_INCOMING_FILE 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:
lt_file_input  TYPE STANDARD TABLE OF DMEE_INPUT_FILE, "   
lv_i_tree_type  TYPE DMEE_TREETYPE, "   
lv_e_logh_summary  TYPE BALLOGHNDL, "   
lv_tree_incomplete  TYPE BALLOGHNDL, "   
lv_i_tree_id  TYPE DMEE_TREEID, "   
lt_result_tab1  TYPE STANDARD TABLE OF DMEE_TREEID, "   
lv_e_logh_error  TYPE BALLOGHNDL, "   
lv_tree_inconsistent  TYPE BALLOGHNDL, "   
lv_i_parameter  TYPE DMEE_PAR_INCOMING, "   
lt_result_tab2  TYPE STANDARD TABLE OF DMEE_PAR_INCOMING. "   

  CALL FUNCTION 'DMEE_PROCESS_INCOMING_FILE'  "NOTRANSL: DMEE: Bearbeite eingehende Datei
    EXPORTING
         I_TREE_TYPE = lv_i_tree_type
         I_TREE_ID = lv_i_tree_id
         I_PARAMETER = lv_i_parameter
    IMPORTING
         E_LOGH_SUMMARY = lv_e_logh_summary
         E_LOGH_ERROR = lv_e_logh_error
    TABLES
         FILE_INPUT = lt_file_input
         RESULT_TAB1 = lt_result_tab1
         RESULT_TAB2 = lt_result_tab2
    EXCEPTIONS
        TREE_INCOMPLETE = 1
        TREE_INCONSISTENT = 2
. " DMEE_PROCESS_INCOMING_FILE




ABAP code using 7.40 inline data declarations to call FM DMEE_PROCESS_INCOMING_FILE

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!