topic Problem using GUI_UPLOAD in Application Development and Automation Discussions

Problem using GUI_UPLOAD

Former Member — Mon, 11 Jun 2007 09:18:38 GMT

Hi All,

I am using GUI_UPLOAD to upload data into app server.The flat file has multiple records with each record of lenght around 90 characters.But its reading only record with around 60 characters only.What could be wrong?

Thanks,

Rakesh.

Re: Problem using GUI_UPLOAD

Former Member — Mon, 11 Jun 2007 09:20:10 GMT

check the declaration of the itab, make sure its not less thna 90

Re: Problem using GUI_UPLOAD

Former Member — Mon, 11 Jun 2007 09:22:13 GMT

Hi ,

Check the length of the record in the internal table that you are passing to the function gui_upload.

It is possibly of 60 characters only

Regards,

Suruchi

Re: Problem using GUI_UPLOAD

Former Member — Mon, 11 Jun 2007 09:25:21 GMT

see the below sample code there is one work area which is of charater type with 255 ..... <b> wa_string(255) type c....</b>use it similar way and work it out .

REPORT  zuploadtab                    .

PARAMETERS: p_infile  LIKE rlgrap-filename
                        OBLIGATORY DEFAULT  '/usr/sap/'..

DATA: ld_file LIKE rlgrap-filename.

*Internal tabe to store upload data
TYPES: BEGIN OF t_record,
    name1 like pa0002-VORNA,
    name2 like pa0002-name2,
    age   type i,
    END OF t_record.
DATA: it_record TYPE STANDARD TABLE OF t_record INITIAL SIZE 0,
      wa_record TYPE t_record.

*Text version of data table
TYPES: begin of t_uploadtxt,
  name1(10) type c,
  name2(15) type c,
  age(5)  type c,
 end of t_uploadtxt.
DATA: wa_uploadtxt TYPE t_uploadtxt.

*String value to data in initially.
DATA: wa_string(255) type c.

constants: con_tab TYPE x VALUE '09'.

*If you have Unicode check active in program attributes then you will
*need to declare constants as follows:

*class cl_abap_char_utilities definition load.
*constants:
*    con_tab  type c value cl_abap_char_utilities=>HORIZONTAL_TAB.



************************************************************************
*START-OF-SELECTION
START-OF-SELECTION.
ld_file = p_infile.
OPEN DATASET ld_file FOR INPUT IN TEXT MODE ENCODING DEFAULT.
IF sy-subrc NE 0.
ELSE.
  DO.
    CLEAR: wa_string, wa_uploadtxt.
    READ DATASET ld_file INTO wa_string.
    IF sy-subrc NE 0.
      EXIT.
    ELSE.
      SPLIT wa_string AT con_tab INTO wa_uploadtxt-name1
                                      wa_uploadtxt-name2
                                      wa_uploadtxt-age.
      MOVE-CORRESPONDING wa_uploadtxt TO wa_upload.
      APPEND wa_upload TO it_record.
    ENDIF.
  ENDDO.
  CLOSE DATASET ld_file.
ENDIF.


************************************************************************
*END-OF-SELECTION
END-OF-SELECTION.
*!! Text data is now contained within the internal table IT_RECORD

* Display report data for illustration purposes
  loop at it_record into wa_record.
    write:/     sy-vline,
           (10) wa_record-name1, sy-vline,
           (10) wa_record-name2, sy-vline,
           (10) wa_record-age, sy-vline.
  endloop.

reward points if it is usefull ..

Girish

Re: Problem using GUI_UPLOAD

Former Member — Mon, 11 Jun 2007 09:33:49 GMT

Hi Rakesh,

It looks like that the record length defined in internal table is 60 character in your program. GUI_UPLOAD does not limit the record length. Secondly use the type 'BIN' as it worked correctly while others were giving issues.

Hope it helps.

Regards Johnny