topic Re: internal tables in Application Development and Automation Discussions

internal tables

Former Member — Mon, 21 Nov 2005 13:40:22 GMT

Hi,

Can someone please give me the code for initializing an internal table. Also, some code showing how to add data to or extract data from the table would also be helpful. The table needs to have two fields that are string and another that is long integer.

thanks-

Kevin

Re: internal tables

Former Member — Mon, 21 Nov 2005 13:46:32 GMT

&----

*& Module pool YRT_TEST1

&----

PROGRAM YRT_TEST1.

*parameters : date1 like sy-datum,

date2 like sy-datum.

*data: days(3) type n.

*data: years(10) type p decimals 3.

*start-of-selection.

*days = date2 - date1.

*years = days / 365.

*write: / days,

years.

data: begin of itab occurs 0,

str type string,

inte type i,

end of itab.

initialization.

itab-str = 'My name'.

itab-inte = 12.

append itab.

clear itab.

itab-str = 'My address'.

itab-inte = 13.

append itab.

clear itab.

Start-of-selection.

*adding data

itab-str = 'additional data'.

itab-inte = 15.

append itab.

clear itab.

*extracting data

loop at itab.

write:/ itab-str,

itab-inte.

endloop.

Re: internal tables

RichHeilman — Mon, 21 Nov 2005 13:48:17 GMT

You can use the following line to clear out all data in your internal table.

clear itab. refresh itab.

Regards,

Rich Heilman

Re: internal tables

Former Member — Mon, 21 Nov 2005 13:48:26 GMT

data: begin of itab ocuurs 0,

field1 like tab1-field1,

field2 like tab1-field2,

end of itab.

clear: itab[],

itab.

select field1 field2 from itab into table itab

where <condition1> and <condition2>.

Re: internal tables

Former Member — Mon, 21 Nov 2005 14:09:27 GMT

what does "occurs 0" mean? THANK YOU all! This is very helpful!!

Re: internal tables

Former Member — Mon, 21 Nov 2005 14:10:48 GMT

with occurs 0 you are specifing that your table doesn't have a predefinited size (number of record)

bye

enzo

Re: internal tables

RichHeilman — Mon, 21 Nov 2005 14:13:25 GMT

The OCCURS systax is obselete in newer version and in ABAP objects. I would suggest starting to use the new syntax for creating internal tables.

Types: begin of ttab, 
       fld1 type c,
       fld2 type c,
       end of ttab.

data: itab type table of ttab.
data: wa type ttab.

Regards,

Rich Heilman

Re: internal tables

Former Member — Mon, 21 Nov 2005 14:26:59 GMT

Okay, thanks.

One more question... I just ran my program and got:

The function module "ALSM_EXCEL_TO_INTERNAL_TABLE" was called, but cannot be found in the function library.

Does the NW sneak preview on Linux have this function included? I copied the Excel file to Linux and attempted to import it to my internal table.

thanks!

Re: internal tables

RichHeilman — Mon, 21 Nov 2005 14:28:34 GMT

Not sure. Go to SE37, enter ALSM_EXCEL_TO_INTERNAL_TABLE into the function module field and click display. This will tell you if it exists of not.

Regards,

Rich Heilman

Re: internal tables

Former Member — Mon, 21 Nov 2005 14:32:31 GMT

Does not exist. Does it exist on the NW sneak preview for windows? I need to get off Linux somehow, but I cannot change the name of my laptop on the Windows side. Is there some work-around that allows you to install the free Netweaver without changing the computer name?

Re: internal tables

RichHeilman — Mon, 21 Nov 2005 14:42:21 GMT

No, it does not exists in my sneak preview version.

Regards,

RIch Heilman

Re: internal tables

Former Member — Mon, 21 Nov 2005 14:53:19 GMT

Wow, so the Windows sneak preview does not have this function module? Am I trying to import data using deprecated code? All I'm trying to do, really, is import data into SAP, preferably from an Excel table.

Re: internal tables

RichHeilman — Mon, 21 Nov 2005 14:55:42 GMT

Try using the function module GUI_UPLOAD.

Or the class/method, CL_GUI_FRONTEND_SERVICES=>GUI_UPLOAD.

They both exists in my sneak preview.

Regards,

Rich Heilman

Re: internal tables

Former Member — Mon, 21 Nov 2005 15:06:15 GMT

Good, I have that one -thanks! Do you happen to know the code for calling this? My ABAP book doesn't mention it.

Re: internal tables

Former Member — Mon, 21 Nov 2005 15:09:22 GMT

DATA: g_file TYPE string.

DATA: i_dataf TYPE char2000 OCCURS 0 WITH HEADER LINE.

CALL FUNCTION 'GUI_UPLOAD'

EXPORTING

filename = g_file

FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = ' '
HEADER_LENGTH = 0
READ_BY_LINE = 'X'
IMPORTING
FILELENGTH =
HEADER =

TABLES

data_tab = i_dataf

EXCEPTIONS

file_open_error = 1

file_read_error = 2

no_batch = 3

gui_refuse_filetransfer = 4

invalid_type = 5

no_authority = 6

unknown_error = 7

bad_data_format = 8

header_not_allowed = 9

separator_not_allowed = 10

header_too_long = 11

unknown_dp_error = 12

access_denied = 13

dp_out_of_memory = 14

disk_full = 15

dp_timeout = 16

OTHERS = 17

IF sy-subrc <> 0.

*error message

ENDIF.

Alternatively you can call any Function module by pressing the Pattern button on the appl tool bar in se38 editor. and give the FM name.

It will give the code for you.

You need to uncomment the parameters which you need to pass.

If you want to call a method belonging to a class, the use the pattern button. select the ABAP Object patterns radio-button,

Give the class/interface name and the method name.

This will give you semi-finished code, for which you need to pass the required parameters.

Message was edited by: Ravi Kanth Talagana

Re: internal tables

RichHeilman — Mon, 21 Nov 2005 15:13:43 GMT

Sure.....I would suggest using comma delimited text files here. Once you have them uploaded to the flat itab, then you can loop thru ITAB and SPLIT the record up into its individual fields using the SPLIT statement.




report zrich_0001
       no standard page heading.

types: begin of ttab,
       rec(1000) type c,
       end of ttab.

parameters: p_file type localfile.

data: itab type table of ttab.
data: file_str type string.


file_str = p_file.

call function 'GUI_UPLOAD'
     exporting
          filename                = file_str
     tables
          data_tab                = itab
     exceptions
          file_open_error         = 1
          file_read_error         = 2
          no_batch                = 3
          gui_refuse_filetransfer = 4
          invalid_type            = 5
          no_authority            = 6
          unknown_error           = 7
          bad_data_format         = 8
          header_not_allowed      = 9
          separator_not_allowed   = 10
          header_too_long         = 11
          unknown_dp_error        = 12
          access_denied           = 13
          dp_out_of_memory        = 14
          disk_full               = 15
          dp_timeout              = 16
          others                  = 17.



*  - OR -

call method cl_gui_frontend_services=>gui_upload
  exporting
    filename                = file_str
  changing
    data_tab                = itab
  exceptions
    file_open_error         = 1
    file_read_error         = 2
    no_batch                = 3
    gui_refuse_filetransfer = 4
    invalid_type            = 5
    no_authority            = 6
    unknown_error           = 7
    bad_data_format         = 8
    header_not_allowed      = 9
    separator_not_allowed   = 10
    header_too_long         = 11
    unknown_dp_error        = 12
    access_denied           = 13
    dp_out_of_memory        = 14
    disk_full               = 15
    dp_timeout              = 16
    others                  = 17.

Please remember to award points for helpful answers. Thanks.

Regards,

Rich HEilman

Re: internal tables

Former Member — Mon, 21 Nov 2005 16:19:42 GMT

I cannot get this code to work... any ideas? The error is "cannot interpret data in file" and then it takes me completely out of the abap editor! How do I modify the code so when I hit the green check, it takes me back to the code?

My text file is simply this (tab delimited):

Joe Bloggs 25

Dave Smith 36

Jane Walker 23

Code:

REPORT Z_SECOND_PROGRAM.

*Data Declarations

*Declare the internal table data structure

data: begin of itab occurs 0,

str1 type string,

str2 type string,

int1 type i,

end of itab.

data: g_file TYPE string.

*Initialize the table

initialization.

itab-str1 = 'Kevin was here'.

itab-str2 = 'Another string'.

itab-int1 = 23.

append itab.

*Display the table

loop at itab.

write:/ itab-str1,

itab-str2,

itab-int1.

endloop.

clear itab. refresh itab.

call function 'GUI_UPLOAD'

EXPORTING

filename = '/root/datafile1'

*HAS_FIELD_SEPARATOR='|'

TABLES

data_tab = itab

EXCEPTIONS

file_open_error=1

file_read_error=2

no_batch=3

gui_refuse_filetransfer=4

invalid_type=5

no_authority=6

unknown_error=7

bad_data_format=8

header_not_allowed=9

separator_not_allowed=10

header_too_long=11

unknown_dp_error=12

access_denied=13

dp_out_of_memory=14

disk_full=15

dp_timeout=16

OTHERS=17

IF sy-subrc <> 0.

*error message

ENDIF.

*Redisplay the table

loop at itab.

write:/ itab-str1,

itab-str2,

itab-int1.

endloop.

Re: internal tables

Former Member — Mon, 21 Nov 2005 17:31:31 GMT

Kevin,

Please do not use the FM's with name GUI* to interact with the application server. As the name clearly suggests, GUI_UPLOAD or the method suggested by Rich are to upload data from the local system.

Regards,

Kalidas.

Re: internal tables

RichHeilman — Mon, 21 Nov 2005 17:33:20 GMT

I think that he is trying to upload from frontend, it just so happens that he is bringing from linux, hence the file path/name.

Regards,

Rich Heilman

Message was edited by: Rich Heilman

Re: internal tables

Former Member — Mon, 21 Nov 2005 19:04:20 GMT

Rich,

I just recopied your code and got it to work. I needed to add "with header line" to itab. It does not display the field names when I print using:

loop at itab.

write / itab.

endloop.

Do you know how to do so?

thanks,

Kevin