SAP GUI_VSS_DOWNLOAD Function Module for
GUI_VSS_DOWNLOAD is a standard gui vss download SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 gui vss download FM, simply by entering the name GUI_VSS_DOWNLOAD into the relevant SAP transaction such as SE37 or SE38.
Function Group: SFES
Program Name: SAPLSFES
Main Program: SAPLSFES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function GUI_VSS_DOWNLOAD 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 'GUI_VSS_DOWNLOAD'".
EXPORTING
* CODEPAGE = "
FILENAME = "
IMPORTING
FILELENGTH = "Number of bytes transferred
TABLES
DATA_TAB = "Transfer table
EXCEPTIONS
FILE_WRITE_ERROR = 1 ACCESS_DENIED = 10 DP_OUT_OF_MEMORY = 11 DISK_FULL = 12 DP_TIMEOUT = 13 DATAPROVIDER_EXCEPTION = 14 CONTROL_FLUSH_ERROR = 15 NO_BATCH = 2 GUI_REFUSE_FILETRANSFER = 3 NO_AUTHORITY = 4 UNKNOWN_ERROR = 5 DP_ERROR_CREATE = 6 DP_ERROR_SEND = 7 DP_ERROR_WRITE = 8 UNKNOWN_DP_ERROR = 9
IMPORTING Parameters details for GUI_VSS_DOWNLOAD
CODEPAGE -
Data type: ABAP_ENCODINGOptional: Yes
Call by Reference: No ( called with pass by value option)
FILENAME -
Data type: STRINGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for GUI_VSS_DOWNLOAD
FILELENGTH - Number of bytes transferred
Data type: IOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for GUI_VSS_DOWNLOAD
DATA_TAB - Transfer table
Data type:Optional: No
Call by Reference: Yes
EXCEPTIONS details
FILE_WRITE_ERROR - Cannot Write to File
Data type:Optional: No
Call by Reference: Yes
ACCESS_DENIED - Access to File Denied
Data type:Optional: No
Call by Reference: Yes
DP_OUT_OF_MEMORY - Not Enough Memory in Data Provider
Data type:Optional: No
Call by Reference: Yes
DISK_FULL - Storage Medium Full
Data type:Optional: No
Call by Reference: Yes
DP_TIMEOUT - Timeout of Data Provider
Data type:Optional: No
Call by Reference: Yes
DATAPROVIDER_EXCEPTION - General Exception Error in Data Provider
Data type:Optional: No
Call by Reference: Yes
CONTROL_FLUSH_ERROR - Error in Control Framework
Data type:Optional: No
Call by Reference: Yes
NO_BATCH - Front-End Function Cannot Be Executed in Background
Data type:Optional: No
Call by Reference: Yes
GUI_REFUSE_FILETRANSFER -
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORITY - No Download Authorization
Data type:Optional: No
Call by Reference: Yes
UNKNOWN_ERROR -
Data type:Optional: No
Call by Reference: Yes
DP_ERROR_CREATE - Cannot Create Data Provider
Data type:Optional: No
Call by Reference: Yes
DP_ERROR_SEND - Error Sending Data with Data Provider
Data type:Optional: No
Call by Reference: Yes
DP_ERROR_WRITE - Error Writing Data with DataProvider
Data type:Optional: No
Call by Reference: Yes
UNKNOWN_DP_ERROR - Error Calling Data Provider
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for GUI_VSS_DOWNLOAD 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_codepage | TYPE ABAP_ENCODING, " | |||
| lt_data_tab | TYPE STANDARD TABLE OF ABAP_ENCODING, " | |||
| lv_filelength | TYPE I, " | |||
| lv_file_write_error | TYPE I, " | |||
| lv_access_denied | TYPE I, " | |||
| lv_dp_out_of_memory | TYPE I, " | |||
| lv_disk_full | TYPE I, " | |||
| lv_dp_timeout | TYPE I, " | |||
| lv_dataprovider_exception | TYPE I, " | |||
| lv_control_flush_error | TYPE I, " | |||
| lv_filename | TYPE STRING, " | |||
| lv_no_batch | TYPE STRING, " | |||
| lv_gui_refuse_filetransfer | TYPE STRING, " | |||
| lv_no_authority | TYPE STRING, " | |||
| lv_unknown_error | TYPE STRING, " | |||
| lv_dp_error_create | TYPE STRING, " | |||
| lv_dp_error_send | TYPE STRING, " | |||
| lv_dp_error_write | TYPE STRING, " | |||
| lv_unknown_dp_error | TYPE STRING. " |
| CALL FUNCTION 'GUI_VSS_DOWNLOAD' " |
| EXPORTING | ||
| CODEPAGE | = lv_codepage | |
| FILENAME | = lv_filename | |
| IMPORTING | ||
| FILELENGTH | = lv_filelength | |
| TABLES | ||
| DATA_TAB | = lt_data_tab | |
| EXCEPTIONS | ||
| FILE_WRITE_ERROR = 1 | ||
| ACCESS_DENIED = 10 | ||
| DP_OUT_OF_MEMORY = 11 | ||
| DISK_FULL = 12 | ||
| DP_TIMEOUT = 13 | ||
| DATAPROVIDER_EXCEPTION = 14 | ||
| CONTROL_FLUSH_ERROR = 15 | ||
| NO_BATCH = 2 | ||
| GUI_REFUSE_FILETRANSFER = 3 | ||
| NO_AUTHORITY = 4 | ||
| UNKNOWN_ERROR = 5 | ||
| DP_ERROR_CREATE = 6 | ||
| DP_ERROR_SEND = 7 | ||
| DP_ERROR_WRITE = 8 | ||
| UNKNOWN_DP_ERROR = 9 | ||
| . " GUI_VSS_DOWNLOAD | ||
ABAP code using 7.40 inline data declarations to call FM GUI_VSS_DOWNLOAD
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