SAP DOWNLOAD_STATUS_WRITE Function Module for NOTRANSL: Download-Status-Sätze und -positionen schreiben in Tabelle WDLS
DOWNLOAD_STATUS_WRITE is a standard download status write 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: Download-Status-Sätze und -positionen schreiben in Tabelle WDLS 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 status write FM, simply by entering the name DOWNLOAD_STATUS_WRITE 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_STATUS_WRITE 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_STATUS_WRITE'"NOTRANSL: Download-Status-Sätze und -positionen schreiben in Tabelle WDLS.
EXPORTING
PI_ITEM_UPDATE = "Flag, change one old item only
* PI_I_WDLS = '' "Download status record
* PI_I_WDLSP = '' "Download status item
* PI_INFO_OUTPUT = ' ' "
IMPORTING
PE_DLDNR = "assigned status number for new status records
PE_LFDNR = "Item number assigned for new items
PE_I_WDLS = "Download status record (updated)
PE_I_WDLSP = "Download status item (updated)
EXCEPTIONS
NO_INSERT = 1 NO_ITEM_INSERT = 2 NO_ITEM_UPDATE = 3 NO_UPDATE = 4
IMPORTING Parameters details for DOWNLOAD_STATUS_WRITE
PI_ITEM_UPDATE - Flag, change one old item only
Data type: WDL_FLAG-XFELDOptional: No
Call by Reference: No ( called with pass by value option)
PI_I_WDLS - Download status record
Data type: WDLSDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_I_WDLSP - Download status item
Data type: WDLSPDefault: ''
Optional: Yes
Call by Reference: No ( called with pass by value option)
PI_INFO_OUTPUT -
Data type: WDL_FLAG-XFELDDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DOWNLOAD_STATUS_WRITE
PE_DLDNR - assigned status number for new status records
Data type: WDLS-DLDNROptional: No
Call by Reference: No ( called with pass by value option)
PE_LFDNR - Item number assigned for new items
Data type: WDLSP-LFDNROptional: No
Call by Reference: No ( called with pass by value option)
PE_I_WDLS - Download status record (updated)
Data type: WDLSOptional: No
Call by Reference: No ( called with pass by value option)
PE_I_WDLSP - Download status item (updated)
Data type: WDLSPOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_INSERT - Download status record not inserted
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ITEM_INSERT - Download status item not inserted
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ITEM_UPDATE - Download status item not up to date
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_UPDATE - Download status record not up to date
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DOWNLOAD_STATUS_WRITE 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_pe_dldnr | TYPE WDLS-DLDNR, " | |||
| lv_no_insert | TYPE WDLS, " | |||
| lv_pi_item_update | TYPE WDL_FLAG-XFELD, " | |||
| lv_pe_lfdnr | TYPE WDLSP-LFDNR, " | |||
| lv_pi_i_wdls | TYPE WDLS, " '' | |||
| lv_no_item_insert | TYPE WDLS, " | |||
| lv_pe_i_wdls | TYPE WDLS, " | |||
| lv_pi_i_wdlsp | TYPE WDLSP, " '' | |||
| lv_no_item_update | TYPE WDLSP, " | |||
| lv_no_update | TYPE WDLSP, " | |||
| lv_pe_i_wdlsp | TYPE WDLSP, " | |||
| lv_pi_info_output | TYPE WDL_FLAG-XFELD. " ' ' |
|   CALL FUNCTION 'DOWNLOAD_STATUS_WRITE' "NOTRANSL: Download-Status-Sätze und -positionen schreiben in Tabelle WDLS |
| EXPORTING | ||
| PI_ITEM_UPDATE | = lv_pi_item_update | |
| PI_I_WDLS | = lv_pi_i_wdls | |
| PI_I_WDLSP | = lv_pi_i_wdlsp | |
| PI_INFO_OUTPUT | = lv_pi_info_output | |
| IMPORTING | ||
| PE_DLDNR | = lv_pe_dldnr | |
| PE_LFDNR | = lv_pe_lfdnr | |
| PE_I_WDLS | = lv_pe_i_wdls | |
| PE_I_WDLSP | = lv_pe_i_wdlsp | |
| EXCEPTIONS | ||
| NO_INSERT = 1 | ||
| NO_ITEM_INSERT = 2 | ||
| NO_ITEM_UPDATE = 3 | ||
| NO_UPDATE = 4 | ||
| . " DOWNLOAD_STATUS_WRITE | ||
ABAP code using 7.40 inline data declarations to call FM DOWNLOAD_STATUS_WRITE
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 DLDNR FROM WDLS INTO @DATA(ld_pe_dldnr). | ||||
| "SELECT single XFELD FROM WDL_FLAG INTO @DATA(ld_pi_item_update). | ||||
| "SELECT single LFDNR FROM WDLSP INTO @DATA(ld_pe_lfdnr). | ||||
| DATA(ld_pi_i_wdls) | = ''. | |||
| DATA(ld_pi_i_wdlsp) | = ''. | |||
| "SELECT single XFELD FROM WDL_FLAG INTO @DATA(ld_pi_info_output). | ||||
| DATA(ld_pi_info_output) | = ' '. | |||
Search for further information about these or an SAP related objects