17.08.2013 Views

Data Interfaces

Data Interfaces

Data Interfaces

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Function Module DOWNLOAD<br />

© SAP AG<br />

CALL FUNCTION DOWNLOAD’ DOWNLOAD’<br />

EXPORTING<br />

BIN_FILESIZE = <br />

CODEPAGE = <br />

FILENAME = <br />

FILETYPE = <br />

ITEM = <br />

MODE = <br />

WK1_N_FORMAT = <br />

WK1_N_SIZE = <br />

WK1_T_FORMAT = <br />

WK1_T_SIZE = <br />

IMPORTING<br />

ACT_FILENAME = <br />

ACT_FILETYPE = <br />

FILESIZE = <br />

TABLES<br />

DATA_TAB = <br />

For the function module DOWNLOAD, you need an internal table for the data transfer. You define this<br />

table according to your data structure at the beginning of the program and then fill it with data.<br />

You use the MODE parameter to define the write mode ('A' to extend a file, ' ' to create a new file).<br />

The specification of default values for the file name, file type and a header for the file dialog is optional.<br />

The IMPORT parameters specify the values actually entered by the user for the file name, file type and<br />

the number of downloaded bytes.<br />

You only specify a value for the export parameter CODEPAGE when performing a DOWNLOAD to<br />

DOS (the only possible value is 'IBM'). Otherwise, this parameter is not used.<br />

All EXPORTING parameters are optional.<br />

If you want to generate a binary file, you must specify the file length. In this case, the transfer table<br />

must consist of a column of type X.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!