Table types and internal table

Hi all,
What is the relationship between table type in ABAP dictionary and internal table?
Moderator message : Search for available information OR read ABAP documentation. Thread locked.
Edited by: Vinod Kumar on Jul 16, 2011 11:16 AM

You can INCLUDE TYPE.
Types: begin of itab,
       field1 type string,
       field2 type string,
*      More Fields in here.
       Field30 type string,
       End of itab.
Data: lt_itab type table of itab.
TYPES BEGIN OF new_itab.
       INCLUDE type itab.
TYPES: field31 type string,
       field32 type string,
END OF new_itab.
Regards,
Rich Heilman

Similar Messages

Difference between line type and internal table?

Hi..
I wanted to know, what is the difference between Line type and Internal Table?

Hi,
Before the 4.7 release in SAP if we want to define an internal table we have to write the defination using the occurs statement and we need to define all the fields using INCLUDE STRUCTURE or indidually all the fields ine by one.
From 4.7 release of R/3 SAP introduced the Line type concept and it's part of the ABAP OOPS concept. for internal table defination we don't need to use the occur statements. Instead INCLUDE structure we need to create a Line type for that structure in Se11 and then we can define the internal table like :
DATA : ITAB TYPE TABLE OF <LINE_TYPE>.
Only thing is this table will be a table without header. So for internal table processing we need to define a work area structure of type line of line type . EX:
DATA: WA_ITAB TYPE LINE OF <LINE_TYPE>.
Hope this helps.
Thanks,
Greetson

Help regarding 'table controls' and 'internal table' updation

Hi all.
Basically this is what i have done..... I have created a table control in module pool program. I declared an Internal table and also have populated it from a database table. I have also used insert statement to insert an blank record in the table control view and delete statements to delete any record, also in the table control view... .
But I am not able to update any new record into an Internal table or the original table ..
Any Ideas how to do it ,Gurus
Thanks

HEllo,
Check thsi simple report.
REPORT ZTFH_TABLECONTROL .
TABLES : ZEMPTABLE.
DATA : SELLINE .
DATA : FLD(20).
DATA : LINNO TYPE I , OFF TYPE I.
DATA : ITAB LIKE ZEMPTABLE OCCURS 10 WITH HEADER LINE.
CONTROLS : CON_TAB TYPE TABLEVIEW USING SCREEN 100.
SELECT * FROM ZEMPTABLE INTO TABLE ITAB.
DESCRIBE TABLE ITAB LINES CON_TAB-LINES.
CALL SCREEN 100.
*&      Module EXT_COMM INPUT
*       text
MODULE EXT_COMM INPUT.
LEAVE PROGRAM.
ENDMODULE.                 " EXT_COMM INPUT
*&      Module TAB_UPDATE INPUT
*       text
MODULE TAB_UPDATE INPUT.
CASE SY-UCOMM.
WHEN 'DEL'.
      IF SELLINE = 'X'.
        DELETE ITAB WHERE EMPNO = ITAB-EMPNO.
        MESSAGE I000(ZYF_DEL).
      ENDIF.
WHEN 'UPD'.
    IF SELLINE = 'X'.
         MODIFY ITAB INDEX CON_TAB-CURRENT_LINE.
         MESSAGE I001(ZYF_DEL).
    ENDIF.
WHEN 'INS'.
     IF SELLINE = 'X'.
      GET CURSOR FIELD FLD LINE LINNO OFFSET OFF.
      SET CURSOR FIELD FLD LINE LINNO OFFSET OFF.
      IF FLD CP 'ITAB*' AND SY-SUBRC = 0.
        IF LINNO >= 1.
          LINNO = LINNO + CON_TAB-TOP_LINE - 1.
          CLEAR ITAB.
          INSERT ITAB INDEX LINNO.
          CON_TAB-LINES = CON_TAB-LINES + 1.
        ELSE.
          CLEAR ITAB.
          APPEND ITAB.
          CON_TAB-LINES = CON_TAB-LINES + 1.
        ENDIF.
      ENDIF.
    ENDIF.
WHEN 'SAV'.
MODIFY ITAB INDEX CON_TAB-CURRENT_LINE.
MESSAGE I002(ZYF_DEL).
ENDCASE.
ENDMODULE.                 " TAB_UPDATE INPUT
FLOW LOGIC
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
LOOP AT ITAB WITH CONTROL CON_TAB.
ENDLOOP.
PROCESS AFTER INPUT.
MODULE USER_COMMAND_0100.
MODULE EXT_COMM AT EXIT-COMMAND.
LOOP AT ITAB.
MODULE TAB_UPDATE.
ENDLOOP.
REgards,
Vasanth

Creating Types and Internal table

Hi,
I created
Types: begin of itab,
           field 1 ...
            Field 30,
        End of itab.
Data: lt_itab type table of itab.
I need to create a second type itab1 with all the itab fields and also new fields field31 and field32.
I dont want to declare all the 30 fields again for the second one.
Can any one tell me how to create this?
Thanks.
rajesh

You can INCLUDE TYPE.
Types: begin of itab,
       field1 type string,
       field2 type string,
*      More Fields in here.
       Field30 type string,
       End of itab.
Data: lt_itab type table of itab.
TYPES BEGIN OF new_itab.
       INCLUDE type itab.
TYPES: field31 type string,
       field32 type string,
END OF new_itab.
Regards,
Rich Heilman

Diference between DATA: and TYPES: on internal tables

Hi people,
Can somebody help me. I wanna know whats the diference between DATA: and TYPES: on internal tables
and whitch has the best performance, here is a eg:
DATA: BEGIN OF ti_sbook occurs 0,
          carrid   LIKE sbook-carrid,
          fldate   LIKE sbook-fldate,
          customid LIKE sbook-customid,
          loccuram LIKE sbook-loccuram,
       END OF ti_sbook.
AND
TYPES: BEGIN OF ti_sbook ,
          carrid   LIKE sbook-carrid,
          fldate   LIKE sbook-fldate,
          customid LIKE sbook-customid,
          loccuram LIKE sbook-loccuram,
       END OF ti_sbook.
DATA: gw_sbook       TYPE TABLE OF ti_sbook,
gs_sbook       TYPE ti_sbook.
witch of both types is better?
thanks.

Hi Marcelo,
For compatibility matters is better to create internal tables with a work area separately. So yes it's better to use types. When you work with Object Oriented coding you will need to use internal tables defined with types. Also when defining tables with types is the new way of coding, the another coding is getting obsolete defined by SAP. That's why when working in ABAP with OO (Object Oriented) code you'll have to define tables with types and not the other way.
Hope it helps.
Regards,
Gilberto Li

SAP QUERY LOOPS AND INTERNAL TABLE

Hi All, I have a query which i have made. It runs from Table EKPO which has PO details and what I want to do is now via ABAP Code pull through the total of goods receipt for the PO and Line Item into a field. Sounds Easy enough..Problem now,
The table which contains the GR data is EKBE which agains a PO and Line Item can have many 101 movements and 102 movements so what I want is an ABAP Statent to basically sum up the total of 101 for the PO & LINE ITEMS and then minus this from the total of 102 for the PO & LINE ITEMS and post the result in to this new field I have created.
I am pretty decent with ABAP Code in Querys I.e Select statements etc but from what I can see i need to create an internal table and do a loop and collect statement but I keep on failing due to not enough knowledge. Please can some one help me with this and provide me with the code and explanation as i would like to understand,
POINTS WILL BE REWARDED
Thanks
Kind Regards
Adeel Sarwar

Hi,
This is the full code i have entered but its not working. Any help would be appreciated. If you could rectify the code and internal tables that would be great.
Thanks
TABLES: EKBE.
DATA: PurO LIKE EKPO-EBELN,
      POLI LIKE EKPO-EBELP.
*New Table and Vars defined
DATA:   BEGIN OF IT_EKBE,
          IT_EKBE LIKE EKBE,
        END OF IT_EKBE.
DATA: BEGIN OF IT_SUM OCCURS 0,
          EBELN TYPE EBELN,
          EBELP TYPE EBELP,
          DMBTR TYPE DMBTR,
          MENGE TYPE MENGE,
      END OF IT_SUM.
CLEAR: QTYD.
MOVE: EKPO-EBELN TO PurO,
      EKPO-EBELP TO POLI.
SELECT * FROM EKBE INTO IT_EKBE
    WHERE EBELN = PurO
    AND   EBELP = POLI
    AND   BEWTP = 'E'
LOOP AT IT_EKBE.
MOVE CORRESPOING IT_EKBE TO IT_SUM.
IF IT_EKBE-BWART = '102'.
    IT_SUM-DMBTR = IT_SUM-DMBTR * -1.
    IT_SUM-MENGE = IT_SUM-MENGE * -1.
ENIDF.
COLLECT IT_SUM.
CLEAR IT_SUM.
ENDLOOP.
ENDSELECT.
If sy-subrc = 0.
QTYD = IT_SUM.
ELSE.
QTYD = 0.
ENDIF.

Export - Import In ABAP ( for variables and internal table)

how can we pass value for the variable and internal table using Export and Import?
data: var type sy-uzeit.
var = sy-uzeit.
EXPORT var TO MEMORY ID 'TIME'.
data: var type sy-uzeit.
IMPORT var FROM MEMORY ID 'TIME'.
write:/ var,sy-subrc,sy-uzeit.
i found var value 0 while importing.
what is the right syntax for passing value of variable and internaltable.
regards,
dushyant.

Hi,
There are two possible solutions.
Solution1:
Program1.Should be run before atleast once so that TIME should be filled.
data: var type sy-uzeit.
var = sy-uzeit.
EXPORT var TO MEMORY ID 'TIME'.
Program2.IF the TIME is filled,then only it will produce the result.
data: var type sy-uzeit.
clear var.
IMPORT var FROM MEMORY ID 'TIME'.
write:/ var, sy-subrc, sy-uzeit.
Solution2:
Single program:
data: var type sy-uzeit.
var = sy-uzeit.
EXPORT var TO MEMORY ID 'TIME'.
clear var.
IMPORT var FROM MEMORY ID 'TIME'.
write:/ var, sy-subrc, sy-uzeit.
Kindly reward points by clikcing the star on the left of reply,if it helps.

Types of internal tables with regard to EFFICIENCY

Will any one tell me syntax to define each type of internal table (standard, sorted , hashed , database) . how to compare their efficincy ( access time which is more effficent) is there any documantation or programme of such type exist then please tell . i want to declare each type of above table and also to compare them w.r.t to efficeny thanks want urgent reply

Hi,
There are 3 types of Internal tables.
Standard Internal Tables:
Standard tables have a linear index. You can access them using either the index or the key. If you use the key, the response time is in linear relationship to the number of table entries. The key of a standard table is always non-unique, and you may not include any specification for the uniqueness in the table definition.
This table type is particularly appropriate if you want to address individual table entries using the index. This is the quickest way to access table entries. To fill a standard table, append lines using the (APPEND) statement. You should read, modify and delete lines by referring to the index (INDEX option with the relevant ABAP command). The response time for accessing a standard table is in linear relation to the number of table entries. If you need to use key access, standard tables are appropriate if you can fill and process the table in separate steps. For example, you can fill a standard table by appending records and then sort it. If you then use key access with the binary search option (BINARY), the response time is in logarithmic relation to the number of table entries.
Sorted Internal Tables:
Sorted tables are always saved correctly sorted by key. They also have a linear key, and, like standard tables, you can access them using either the table index or the key. When you use the key, the response time is in logarithmic relationship to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique, or non-unique, and you must specify either UNIQUE or NON-UNIQUE in the table definition. Standard tables and sorted tables both belong to the generic group index tables.
This table type is particularly suitable if you want the table to be sorted while you are still adding entries to it. You fill the table using the (INSERT) statement, according to the sort sequence defined in the table key. Table entries that do not fit are recognised before they are inserted. The response time for access using the key is in logarithmic relation to the number of table entries, since the system automatically uses a binary search. Sorted tables are appropriate for partially sequential processing in a LOOP, as long as the WHERE condition contains the beginning of the table key.
Hashed Internal Tables:
Hashes tables have no internal linear index. You can only access hashed tables by specifying the key. The response time is constant, regardless of the number of table entries, since the search uses a hash algorithm. The key of a hashed table must be unique, and you must specify UNIQUE in the table definition.
This table type is particularly suitable if you want mainly to use key access for table entries. You cannot access hashed tables using the index. When you use key access, the response time remains constant, regardless of the number of table entries. As with database tables, the key of a hashed table is always unique. Hashed tables are therefore a useful way of constructing and
using internal tables that are similar to database tables.
http://help.sap.com/saphelp_470/helpdata/EN/fc/eb35de358411d1829f0000e829fbfe/frameset.htm
Regards,
Kiran Sure

DIFF: Field string ,Structure and Internal table declaration

Hai,
       what is the diference between Field string ,Structure in ABAP program and Internal table declaration and how it will work ?
Thank you
ASHOK KUMAR.

hi,
Look this u will get a good idea.
*& Report ZTYPES                                                      *
REPORT ZTYPES                                                  .
* Table declaration (old method)
DATA: BEGIN OF tab_ekpo OCCURS 0,             "itab with header line
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
END OF tab_ekpo.
*Table declaration (new method)     "USE THIS WAY!!!
TYPES: BEGIN OF t_ekpo,
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
END OF t_ekpo.
DATA: it_ekpo TYPE STANDARD TABLE OF t_ekpo INITIAL SIZE 0,      "itab
      wa_ekpo TYPE t_ekpo.                    "work area (header line)
* Build internal table and work area from existing internal table
DATA: it_datatab LIKE tab_ekpo OCCURS 0,      "old method
      wa_datatab LIKE LINE OF tab_ekpo.
* Build internal table and work area from existing internal table,
* adding additional fields
TYPES: BEGIN OF t_repdata.
        INCLUDE STRUCTURE tab_ekpo. "could include EKKO table itself!!
TYPES: bukrs TYPE ekpo-werks,
       bstyp TYPE ekpo-bukrs.
TYPES: END OF t_repdata.
DATA: it_repdata TYPE STANDARD TABLE OF t_repdata INITIAL SIZE 0,   "itab
      wa_repdata TYPE t_repdata.                 "work area (header line)
Regards
Reshma

Dynamic Structures and Internal Tables

Hi All,
I am doing a report to create condition records based on the condition type and condition table. Assume the condition type as PR00 and it as condition table of 304,305,306.Each condition table as its own header and item fields.Based on the condition table that the user specifies in the selection screen
the header and item structures of my report should change dynamically and these should be moved to the dynamic internal table that contains both header and item fields.Can anyone give an idea how to achieve it. Thanks in advance.
Regards,
Chakradhar.

Hi All,
Thanks for your replies.
SPLIT i_string_line-input_str AT cl_abap_char_utilities=>horizontal_tab
INTO i_header_line-header
          i_header_line-vkorg
          i_header_line-vtweg
          i_header_line-pltyp
         i_header_line-waerk.
In the above syntax based on the condition table I selected on selection screen my flat file is as below.
case 1: If condition table given is 304
H    SalesOrganization    DistributionChannel    Customer
I    Material    Releasestatus    Amount    Currency    ValidFrom    ValidTo
case 2: If condition table given is 305
H    SalesOrganization    DistributionChannel
I    Material    Releasestatus    Amount    Currency    ValidFrom    ValidTo
case 3: If condition table given is 306
H    SalesOrganization    DistributionChannel     PriceListType     DocumentCurrency
I    Material    Releasestatus    Amount    Currency    ValidFrom    ValidTo
In the above code i_string_line-input_str contains the following heading of fields based on the condition table we select in selection screen.when I want to split them into respective fields
using INTO clause my structure should change dynamically.How can I achieve it and my entire program is in OOPS ALV.Thanks in Advance.
Regards,
Chakradhar.

Difference between the Field Group and Internal Table.

Hi all,
Can anybody tell me the difference between the Field group and Internal table and when they will used?
Thanks,
Sriram.

Hi
Internal Tables: They are used to store record type data in tabular form temporarily in ABAP programming. Or we can say, it stores multiple lines of records for temporary use in ABAP programming.
A field group is a user-defined grouping of characteristics and basic key figures from the EC-EIS or EC-BP field catalog.
Use
The field catalog contains the fields that are used in the aspects. As the number of fields grows, the field catalog becomes very large and unclear. To simplify maintenance of the aspects, you can group fields in a field group. You can group the fields as you wish, for example, by subject area or responsibility area. A field may be included in several field groups.
When maintaining the data structure of an aspect, you can select the field group that contains the relevant characteristics and basic key figures. This way you limit the number of fields offered.
Regards
Ashish

Group by and internal table

Hi everyone,
Please help me. Is it possible to select data from database table into an internal table with group by?
For example:
select carrid connid SUM(seatsocc)
from sflight
into(internal-table-carrid, internal-table-connid, sum)
group by carrid connid
where fldate between ***
endselect
thank you in advance!
Linda

yes,
select carrid connid SUM( seatsocc )
from sflight
into (sflight-carrid, sflight-connid, sflight-seatsocc)
where fldate = sy-datum group by carrid connid
endselect.
The problems with yours were:
. no space after SUM(
. group by in wrong spot (before where)
Here's the into table version:
data ts type table of sflight with header line.
select carrid connid SUM( seatsocc ) as seatsocc
from sflight
into corresponding fields of table ts
where fldate = sy-datum group by carrid connid
This is not the most efficient way though. It is probably better to select into a table and sort and aggregate into another table in abap.

Work area and internal table

hi friends,
Please let me know when do we use work area and when do we use internal table.
Thanks in advance
Tina Wilson

Work areas are used with internal tables. For example if you have an internal table defined like this.
data: itab type table of mara.
This internal table can hold many rows of data, right? SO say you need to read this data. Well you will need to LOOP or READ the internal table, since this internal table has no header line(please to put the read data), you need to have a work area to put the data into.
data: wa like line of itab.
Loop at itab into wa.
endloop.
Now if you defined the internal table with a header line, there is no reason to have the work area and you can just do the same like this.
data: itab type table of mara with header line.
Loop at itab.
endloop.
It is now best practice to use work areas instead of header lines because in ABAP OO, header lines are not allowed.
Regards,
Rich Heilman

Hi I want to know the difference between the type of internal tables.

I know the types of internal table but i dont know the difference between them can any one explain me in simple sentence.

Hi,
Standard Internal Tables
Standard tables have a linear index. You can access them using either the index or the key. If you use the key, the response time is in linear relationship to the number of table entries. The key of a standard table is always non-unique, and you may not include any specification for the uniqueness in the table definition.
This table type is particularly appropriate if you want to address individual table entries using the index. This is the quickest way to access table entries. To fill a standard table, append lines using the (APPEND) statement. You should read, modify and delete lines by referring to the index (INDEX option with the relevant ABAP command). The response time for accessing a standard table is in linear relation to the number of table entries. If you need to use key access, standard tables are appropriate if you can fill and process the table in separate steps. For example, you can fill a standard table by appending records and then sort it. If you then use key access with the binary search option (BINARY), the response time is in logarithmic relation to
the number of table entries.
Sorted Internal Tables
Sorted tables are always saved correctly sorted by key. They also have a linear key, and, like standard tables, you can access them using either the table index or the key. When you use the key, the response time is in logarithmic relationship to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique, or non-unique, and you must specify either UNIQUE or NON-UNIQUE in the table definition. Standard tables and sorted tables both belong to the generic group index tables.
This table type is particularly suitable if you want the table to be sorted while you are still adding entries to it. You fill the table using the (INSERT) statement, according to the sort sequence defined in the table key. Table entries that do not fit are recognised before they are inserted. The response time for access using the key is in logarithmic relation to the number of
table entries, since the system automatically uses a binary search. Sorted tables are appropriate for partially sequential processing in a LOOP, as long as the WHERE condition contains the beginning of the table key.
Hashed Internal Tables
Hashes tables have no internal linear index. You can only access hashed tables by specifying the key. The response time is constant, regardless of the number of table entries, since the search uses a hash algorithm. The key of a hashed table must be unique, and you must specify UNIQUE in the table definition.
This table type is particularly suitable if you want mainly to use key access for table entries. You cannot access hashed tables using the index. When you use key access, the response time remains constant, regardless of the number of table entries. As with database tables, the key of a hashed table is always unique. Hashed tables are therefore a useful way of constructing and
using internal tables that are similar to database tables.

Passing SELECT-OPTIONS and Internal Tables to SUBROUTINES

Hi Guys
In the code below my colleague has created her own table types in order to pass a select option and internal tables to her subroutine. Is there an easier way of making them known to the subroutine.
data : v_vbeln type vbeln_vf,
      it_bdoc type table of vbrp,
      it_t006 type table of t006a,
      wa_bdoc type vbrp,
      wa_t006 type t006a,
      it_bdoc2 type table of zsswathi_st_vbeln,
      wa_bdoc2 type zsswathi_st_vbeln
select-options s_vbeln for v_vbeln matchcode object zswathi_vbeln obligatory.
start-of-selection.
perform bdoc using s_vbeln[]
             changing it_bdoc
                      it_bdoc2
                      it_t006.
loop at it_bdoc2 into wa_bdoc2.
form bdoc using f_s_vbeln type ZSWATHI_ST_SELECT_OPTION_TA_TY       " all these are table types. for select options, a structure is created and then a table type for it is created.
        changing f_it_bdoc type zswathi_vbrp_ty_ta
                 f_it_bdoc2 type zswathi_vbeln_ty_ta
                  f_it_t006 type ZSWATHI_T006_TA_TY.
select * from vbrp into table f_it_bdoc where vbeln in f_s_vbeln.
      if f_it_bdoc is not initial.
      select vbeln sum( netwr ) prsdt from vbrp into table f_it_bdoc2 where vbeln in f_s_vbeln group by vbeln prsdt.
      sort f_it_bdoc2 by vbeln.
      "select * from t006a into table it_t006 for all entries in it_bdoc where msehi = it_bdoc-vrkme.
      select * from t006a into table f_it_t006 for all entries in f_it_bdoc where msehi = f_it_bdoc-vrkme.
   endif.
    endform.

Hi Brett,
1. you can use a select-options-range in a FORM subroutine also without passing it as a parameter because parameters and select-option range tables are global fields in their program.
2. If you need a parameter, declare it as type table or type standard table or type any table. You do not need any special table type.
Regards
Clemens

Table types and internal table

Similar Messages

Maybe you are looking for