SAP J_2G_WS_DOWNLOAD Function Module for File transfer: Itab -> PC file

Search SAP Function Modules

J_2G_WS_DOWNLOAD is a standard j 2g ws download SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for File transfer: Itab -> PC file 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 j 2g ws download FM, simply by entering the name J_2G_WS_DOWNLOAD into the relevant SAP transaction such as SE37 or SE38.

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

Function J_2G_WS_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 'J_2G_WS_DOWNLOAD'"File transfer: Itab -> PC file
  EXPORTING
*  BIN_FILESIZE = ' ' "File length for binary files
*  FILENAME = ' ' "Local file for upload/download
*  FILETYPE = 'ASC' "File type (ASC, BIN, DAT)
*  MODE = ' ' "Writing mode (' ' = overwrite, 'A' = append)
*  TRUNC_TRAILING_BLANKS = ' ' "Do not write blanks at the end of char fields

 IMPORTING
   FILELENGTH =  "Number of bytes transferred

TABLES
   DATA_TAB =  "Transfer table

EXCEPTIONS
   INVALID_TYPE = 1    NO_BATCH = 2    NO_AUTHORITY = 3    DOWNLOAD_ERROR = 4 

.

IMPORTING Parameters details for J_2G_WS_DOWNLOAD

BIN_FILESIZE - File length for binary files

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

FILENAME - Local file for upload/download

Data type: RLGRAP-FILENAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

FILETYPE - File type (ASC, BIN, DAT)

Data type: RLGRAP-FILETYPE
Default: 'ASC'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MODE - Writing mode (' ' = overwrite, 'A' = append)

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

TRUNC_TRAILING_BLANKS - Do not write blanks at the end of char fields

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

EXPORTING Parameters details for J_2G_WS_DOWNLOAD

FILELENGTH - Number of bytes transferred

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

TABLES Parameters details for J_2G_WS_DOWNLOAD

DATA_TAB - Transfer table

Data type:
Optional: No
Call by Reference: Yes

EXCEPTIONS details

INVALID_TYPE - Invalid value for parameter FILETYPE

Data type:
Optional: No
Call by Reference: Yes

NO_BATCH - Front-End Function Cannot Be Executed in Backgrnd

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORITY - No Download Authorization

Data type:
Optional: No
Call by Reference: Yes

DOWNLOAD_ERROR - Other GUI_DOWNLOAD error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for J_2G_WS_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.

ABAP code using 7.40 inline data declarations to call FM J_2G_WS_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