SAP GUI_GBA_UPLOAD Function Module for









GUI_GBA_UPLOAD is a standard gui gba upload 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 gba upload FM, simply by entering the name GUI_GBA_UPLOAD into the relevant SAP transaction such as SE37 or SE38.

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



Function GUI_GBA_UPLOAD 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_GBA_UPLOAD'"
  EXPORTING
   FILENAME =  "

 IMPORTING
   FILELENGTH =  "

TABLES
   DATA_TAB =  "

EXCEPTIONS
   FILE_OPEN_ERROR = 1    DP_OUT_OF_MEMORY = 10    DP_TIMEOUT = 11    FILE_READ_ERROR = 2    NO_BATCH = 3    GUI_REFUSE_FILETRANSFER = 4    NO_AUTHORITY = 5    UNKNOWN_ERROR = 6    BAD_DATA_FORMAT = 7    UNKNOWN_DP_ERROR = 8    ACCESS_DENIED = 9
.



IMPORTING Parameters details for GUI_GBA_UPLOAD

FILENAME -

Data type: STRING
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for GUI_GBA_UPLOAD

FILELENGTH -

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

TABLES Parameters details for GUI_GBA_UPLOAD

DATA_TAB -

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

EXCEPTIONS details

FILE_OPEN_ERROR -

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

DP_OUT_OF_MEMORY -

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

DP_TIMEOUT -

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

FILE_READ_ERROR -

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

NO_BATCH -

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

GUI_REFUSE_FILETRANSFER -

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

NO_AUTHORITY -

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

UNKNOWN_ERROR -

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

BAD_DATA_FORMAT -

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

UNKNOWN_DP_ERROR -

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

ACCESS_DENIED -

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

Copy and paste ABAP code example for GUI_GBA_UPLOAD 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_data_tab  TYPE STANDARD TABLE OF STRING, "   
lv_filename  TYPE STRING, "   
lv_filelength  TYPE I, "   
lv_file_open_error  TYPE I, "   
lv_dp_out_of_memory  TYPE I, "   
lv_dp_timeout  TYPE I, "   
lv_file_read_error  TYPE I, "   
lv_no_batch  TYPE I, "   
lv_gui_refuse_filetransfer  TYPE I, "   
lv_no_authority  TYPE I, "   
lv_unknown_error  TYPE I, "   
lv_bad_data_format  TYPE I, "   
lv_unknown_dp_error  TYPE I, "   
lv_access_denied  TYPE I. "   

  CALL FUNCTION 'GUI_GBA_UPLOAD'  "
    EXPORTING
         FILENAME = lv_filename
    IMPORTING
         FILELENGTH = lv_filelength
    TABLES
         DATA_TAB = lt_data_tab
    EXCEPTIONS
        FILE_OPEN_ERROR = 1
        DP_OUT_OF_MEMORY = 10
        DP_TIMEOUT = 11
        FILE_READ_ERROR = 2
        NO_BATCH = 3
        GUI_REFUSE_FILETRANSFER = 4
        NO_AUTHORITY = 5
        UNKNOWN_ERROR = 6
        BAD_DATA_FORMAT = 7
        UNKNOWN_DP_ERROR = 8
        ACCESS_DENIED = 9
. " GUI_GBA_UPLOAD




ABAP code using 7.40 inline data declarations to call FM GUI_GBA_UPLOAD

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



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!