SAP DOWNLOAD_EDI_STATUS_CONTROL Function Module for NOTRANSL: Versendekontrolle für den Download-Status









DOWNLOAD_EDI_STATUS_CONTROL is a standard download edi status control 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: Versendekontrolle für den Download-Status 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 download edi status control FM, simply by entering the name DOWNLOAD_EDI_STATUS_CONTROL into the relevant SAP transaction such as SE37 or SE38.

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



Function DOWNLOAD_EDI_STATUS_CONTROL 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 'DOWNLOAD_EDI_STATUS_CONTROL'"NOTRANSL: Versendekontrolle für den Download-Status
IMPORTING
PE_ALL_ALREADY_OK = "All downloads have already been sent correctly

TABLES
PI_T_WDLS = "Download status records
PI_T_WDLSP = "Download status items

EXCEPTIONS
NO_EDI_STATUS = 1
.



EXPORTING Parameters details for DOWNLOAD_EDI_STATUS_CONTROL

PE_ALL_ALREADY_OK - All downloads have already been sent correctly

Data type: WDL_FLAG-XFLAG
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for DOWNLOAD_EDI_STATUS_CONTROL

PI_T_WDLS - Download status records

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

PI_T_WDLSP - Download status items

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

EXCEPTIONS details

NO_EDI_STATUS - There is no EDI status

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

Copy and paste ABAP code example for DOWNLOAD_EDI_STATUS_CONTROL 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_pi_t_wdls  TYPE STANDARD TABLE OF WDLS, "   
lv_no_edi_status  TYPE WDLS, "   
lv_pe_all_already_ok  TYPE WDL_FLAG-XFLAG, "   
lt_pi_t_wdlsp  TYPE STANDARD TABLE OF WDLSP. "   

  CALL FUNCTION 'DOWNLOAD_EDI_STATUS_CONTROL'  "NOTRANSL: Versendekontrolle für den Download-Status
    IMPORTING
         PE_ALL_ALREADY_OK = lv_pe_all_already_ok
    TABLES
         PI_T_WDLS = lt_pi_t_wdls
         PI_T_WDLSP = lt_pi_t_wdlsp
    EXCEPTIONS
        NO_EDI_STATUS = 1
. " DOWNLOAD_EDI_STATUS_CONTROL




ABAP code using 7.40 inline data declarations to call FM DOWNLOAD_EDI_STATUS_CONTROL

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 XFLAG FROM WDL_FLAG INTO @DATA(ld_pe_all_already_ok).
 
 


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!