Internal table with work area

hi all,
data: BEGIN OF it_summ OCCURS 0.
INCLUDE STRUCTURE yapn_summary.
data: END OF it_summ.
data : wa_demo1 type yapn_summary.
clear wa_demo1.
wa_demo1-sumr = 'hai'.
append wa_Demo1 to it_summ.
WRITE: it_summ-sumr.
its not get output..
i want to display for hai using it_summ.
donot use work area.
how to change it.?
reply me soon,
s.suresh.

You can't write out an internal table - you can only write out a line (or components of a line) of an internal table. So you MUST use a work area. If you use OCCURS 0 then you've a table with a headerline, and so don't need a workarea. However, later versions of ABAP discourage tables with headerline, and it is preferred to define a specific work area. So, either:
data: BEGIN OF it_summ OCCURS 0.
INCLUDE STRUCTURE yapn_summary.
data: END OF it_summ.
clear it_summ.
it_summ-sumr = 'hai'.
append wa_Demo1 to it_summ.
LOOP AT it_summ.
WRITE: it_summ-sumr.
ENDLOOP.
Now, you see here that at some points it_summ refers to the table, and at others to the header-line. This is ambiguous, and therefore BAD. It's better to define the table and work area seperately.
data: it_summ TYPE STANDARD TABLE OF yapn_summary WITH NON-UNIQUE KEY table_line.
data : wa_demo1 type yapn_summary.
clear wa_demo1.
wa_demo1-sumr = 'hai'.
append wa_Demo1 to it_summ.
LOOP AT it_summ INTO wa_demo1.
WRITE: wa_demo1-sumr.
ENDLOOP.
matt

Similar Messages

Internal table declaration - work area and body

Hi all
I have declared my internal table in my program as
data : itab_wa type ZRESULT_LINE,
       itab    type ZRESULT_ROW.
Where ZRESULT_LINE and ZRESULT_ROW are the structure and table types.
Now I want to add
data: TCOLOR TYPE SLIS_T_SPECIALCOL_ALV.
in my internal table declaration. How can I do this. Please remember I need to have work area and body in my internal table as I have used work area and body in my code.
Waiting..............
Message was edited by: Raju Boda

HI,
See the Declarion types of workarea and Internal tables
* 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
you need to maintain same structure for both workarea as well Internal table
Regards
Sudheer

Internal table and work area

Hi,
can anybody explain the concepts of Internal table and work area.Thanks in advance.

hai,
This may help u.
WORKAREA is a structure that can hold only one record at a time. It is a collection of fields. We use workarea as we cannot directly read from a table. In order to interact with a table we need workarea. When a Select Statement is executed on a table then the first record is read and put into the header of the table and from there put into the header or the workarea(of the same structure as that of the table)of the internal table and then transferred top the body of the internal table or directly displayed from the workarea.
Each row in a table is a record and each column is a field.
While adding or retrieving records to / from internal table we have to keep the record temporarily.
The area where this record is kept is called as work area for the internal table. The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
e.g.
data: begin of itab occurs 10,
ab type c,
cd type i,
end of itab. " this table will have the header line.
data: wa_itab like itab. " explicit work area for itab
data: itab1 like itab occurs 10. " table is without header line.
Internal tables are used for storing records which are obtained as a result when we use select statement on database. internal tables are run time entities and doesn't occupy any memory. they are dynamic.
internal tables are of types.
1. internal tables with header line. [header and body]
2. internal tables with out header line. [only body]
Workarea is the concept which is mainly useful when working with internal tables with out header line.
at any point of time we can access only one record through header of a internal table. every thing should be done [inserting,modifying, reading ] through header only.
ex: data: itab like standard table of mara with header line.
for internal tables with out header line we will create a work area [explicit header] as type of table for storing data into internal table.
ex: data: itab like mara,
wa like mara.
more about internal table types:
Standard table:
The key access to a standard table uses a sequential search. The time required for an access is linearly dependent on the number of entries in the internal table.
You should usually access a standard table with index operations.
Sorted table:
The table is always stored internally sorted by its key. Key access to a sorted table can therefore use a binary search. If the key is not unique, the entry with the lowest index is accessed. The time required for an access is logarithmically dependent on the number of entries in the internal table.
Index accesses to sorted tables are also allowed. You should usually access a sorted table using its key.
Hash table:
The table is internally managed with a hash procedure. All the entries must have a unique key. The time required for a key access is constant, that is it does not depend on the number of entries in the internal table.
You cannot access a hash table with an index. Accesses must use generic key operations (SORT, LOOP, etc.).
Hashed tables
This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index.
The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always
have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for
processing large amounts of data.
TYPES VECTOR TYPE HASHED TABLE OF I WITH UNIQUE KEY TABLE LINE.
TYPES: BEGIN OF LINE,
COLUMN1 TYPE I,
COLUMN2 TYPE I,
COLUMN3 TYPE I,
END OF LINE.
DATA ITAB TYPE HASHED TABLE OF SPFLI
WITH UNIQUE KEY CARRID CONNID.
with regards,
B.Sowjanya,
reward points if helpful.

Get the fieldnames of a generic internal table or work area

Hi All,
I have one generic work area which I have created in the below manner...
* ET_DATA itself is a generic table of type ANY...can have any internal table data in it.
* Create dynamic internal table
CREATE DATA lv_new_table LIKE et_data.
ASSIGN lv_new_table->* TO <fs_dyn_table>.
* Create dynamic work area and assign to fieldsymbol.
CREATE DATA lv_new_line LIKE LINE OF <fs_dyn_table>.
ASSIGN lv_new_line->* TO <fs_dyn_wa>.
Now...I need to get the field names of this dynamic internal table or work area..
I have already searched in forum...got many answers..but none them gives me the output.
Please note that I require the field names and not field position..
Awaiting your suggestions on how to get field names of this dynamic work area...

create data wa_ref like line of it_data.
assign wa_ref->* to <p_data>.
desc_table ?= cl_abap_tabledescr=>describe_by_data( it_data ).
desc_struc ?= desc_table->get_table_line_type( ).
describe field <p_data> type rtty components ncom.
This one is working in our environment without any error. it_data is an importing parameter in the signature of a method of type any table.

I need insert /update/modify ztable from internal table or work area

I have one simple problem.
TYPES: BEGIN OF t_account,
        acc_no          LIKE zztaccountheader-acc_no,
        cust_id         LIKE zztaccountheader-cust_id,
        acc_type        LIKE zztaccountheader-acc_type,
        od_option       LIKE zztaccountheader-od_option,
        od_limit        LIKE zztaccountheader-od_limit,
        od_issue_date   LIKE zztaccountheader-od_issue_date,
        END OF t_account.
data: lwa_account TYPE t_account,
     li_account TYPE STANDARD TABLE OF t_account,
bu scerrin i am inputing data :
i want modify updare or insert record into ztable by work area i put following thing
MOVE : zztaccountheader-acc_no        TO lwa_account-acc_no,
           zztcustomer-cust_id            TO lwa_account-cust_id,
           zztaccountheader-acc_type      TO lwa_account-acc_type,
           zztaccountheader-od_option     TO lwa_account-od_option,
           zztaccountheader-od_limit      TO lwa_account-od_limit,
           zztaccountheader-od_issue_date TO lwa_account-od_issue_date.
    INSERT   zztaccountheader CLIENT SPECIFIED FROM lwa_account .
    CLEAR lwa_account.
ENDIF.
i am etting error
The type of the database table and work area (or internal table)
"LWA_ACCOUNT" are not Unicode convertible.
please solve it

hi,
decalre like this.
tables : zztaccountheader.
data : t_account like zztaccountheader occurs 0 with header line.
data: lwa_account TYPE t_account,
li_account TYPE STANDARD TABLE OF t_account,
MOVE : zztaccountheader-acc_no TO lwa_account-acc_no,
zztcustomer-cust_id TO lwa_account-cust_id,
zztaccountheader-acc_type TO lwa_account-acc_type,
zztaccountheader-od_option TO lwa_account-od_option,
zztaccountheader-od_limit TO lwa_account-od_limit,
zztaccountheader-od_issue_date TO lwa_account-od_issue_date.
INSERT zztaccountheader CLIENT SPECIFIED FROM lwa_account .
CLEAR lwa_account.
ENDIF.
rgss
anver
if hlped mark points

Error: you cannot create an internal table as work area

Hi, My code is as follows and when i perform a check it gives the above mentioned error in the select statement.
TYPES: BEGIN OF t_vbrk,
        vbeln            TYPE vbrk-vbeln,
        vtweg            TYPE vbrk-vtweg,
      END OF t_vbrk.
DATA vbrktab TYPE TABLE OF t_vbrk.
SELECT      vbeln
                vtweg
         FROM   vbrk
         INTO vbrktab
         FOR ALL ENTRIES IN xxcvb
         WHERE vbeln       = xxcvb-vbeln.
      INSERT TABLE vbrktab.
    ENDSELECT.
where xxcvb is another internal table with some key values.

Hi
I don't know how you've defined XXCVB, but u should write:
TYPES: BEGIN OF T_VBRK,
         VBELN TYPE VBRK-VBELN,
         VTWEG TYPE VBRK-VTWEG,
       END OF T_VBRK.
DATA: VBRKTAB    TYPE TABLE OF T_VBRK,
      WA_VBRKTAB TYPE T_VBRK.
SELECT VBELN VTWEG FROM VBRK INTO TABLE VBRKTAB
FOR ALL ENTRIES IN XXCVB
     WHERE VBELN = XXCVB-VBELN.
LOOP AT VBRKTAB INTO WA_VBRKTAB.
ENDLOOP.
Max

Smartform Table; Internal table to work area

Hi,
I have created smartform with one table,in that internal table values are not moving into workarea,can anyone solve my issue.

Hi Bose,
If you are populating internal table values in progarm and passing this internal table to smartforms
here is the syntax and declaration to follow
data : itab_final type standard table of type_final (some type) with header line .
Pass this under tables in your Z program,
CALL FUNCTION 'smartform name'
       EXPORTING
          archive_index      = toa_dara
          archive_parameters = arc_params
          vbdkl              = vbdkl
          vbdpl              = vbdpl
          makt               = makt
          qals               = qals
          vbco3              = vbco3
        TABLES
          g_final            = g_final
        EXCEPTIONS
          FORMATTING_ERROR   = 1
          INTERNAL_ERROR     = 2
          SEND_ERROR         = 3
          USER_CANCELED      = 4
          OTHERS             = 5.
In Smartforms,
Declare this internal table in form interface under tables as,
G_FINAL     TYPE     Z_TT_FINAL_COA(table type)
And work area in global data as,
WA_G_FINAL     TYPE     ZFINAL_COA (structure)
Now it can be used used in table control under data column as
G_FINAL          INTO                  WA_G_FINAL
Regards,
Sagar.

Structure of table and work area are not compatible - table control wizard

Structure of table and work area are not compatible is the error i am getting when specifying my internal table and work area in my table control? What am I doing wrong?

hii
this error comes when you have different structure of work area then internal table..so work area will not work here and you will not be able to append records in internal table.
check strucure of internal table and work area.it should be like below.
TYPES:
BEGIN OF type_s_kna1,
     kunnr LIKE kna1-kunnr,            " Customer Number
     name1 LIKE kna1-name1,            " Name
     vbeln LIKE vbap-vbeln,            " Sales Document
END OF type_s_kna1.
* Internal Table And Work Area Declarations For Customer Details      *
DATA : t_kna1 TYPE STANDARD TABLE OF type_s_kna1,
         fs_kna1 TYPE type_s_kna1.
regards
twinkal

Internal table with and with out work area.

Hi all,
in performance terms which one is better 1) internal table with header line or 2) itab w/o header line and explicit work area for that itab.
which one is better and how?
Thanks in advance.
SAI

Hai Sai Ram
Internal Table with header Line Improves the Performence
1)
TABLES CUSTOMERS.
Defining an internal table with header line
DATA ALL_CUSTOMERS LIKE CUSTOMERS OCCURS 100
                   WITH HEADER LINE.
Reading all entries of the database table into the internal table
SELECT * FROM CUSTOMERS INTO TABLE ALL_CUSTOMERS.
2)
Check the following code for the Difference
REPORT ZWRITEDOC LINE-SIZE 124 NO STANDARD PAGE HEADING.
   TABLES: DD03L, "
           DD04T, "R/3-DD: Textos de los elementos de datos
           DD02T. "R/3-DD: Textos de tablas SAP
Tabla temporal con las lineas de cada tabla
   DATA: BEGIN OF I_LINEAS OCCURS 100,
            LINEA(80),
         END OF I_LINEAS.
Tabla con las caracteristicas de la tabla
   DATA: BEGIN OF I_TABLA OCCURS 100,
            CAMPO(12),
            TIPO(4),
            LONG(5) TYPE I,
            REF(20),
            DESCR(40),
         END OF I_TABLA.
   DATA: D_NOMBRE(80),
         D_DESCRIPCION(80).
   DATA : BEGIN OF SOURCE OCCURS 1000,
        LINE(72),
   END OF SOURCE.
   PARAMETERS: PROGRAM LIKE SY-REPID DEFAULT SY-REPID.
   AT USER-COMMAND.
     CASE SY-UCOMM.
       WHEN 'GRAB'.
         PERFORM GRABAR.
     ENDCASE.
   START-OF-SELECTION.
     SET PF-STATUS 'ZSTATUS1'.
     READ REPORT PROGRAM INTO SOURCE.
     DATA L_GRAB.
     CLEAR L_GRAB.
LOOP AT SOURCE.
   translate source to upper case.
       IF L_GRAB IS INITIAL.
         D_DESCRIPCION = I_LINEAS-LINEA.
       ENDIF.
       I_LINEAS = SOURCE.
       SEARCH I_LINEAS-LINEA FOR 'BEGIN OF'.
       IF SY-SUBRC = 0.
         SEARCH I_LINEAS-LINEA FOR 'DATA'.
         IF SY-SUBRC = 0.
           L_GRAB = 'X'.
           FREE I_LINEAS.
         ENDIF.
       ENDIF.
       IF L_GRAB = 'X'.
         I_LINEAS = SOURCE.
         APPEND I_LINEAS.
         SEARCH I_LINEAS-LINEA FOR 'END OF'.
         IF SY-SUBRC = 0.
           CLEAR L_GRAB.
           PERFORM PROCESAR_FICHERO.
           PERFORM IMPRIMIR.
           FREE I_LINEAS.
           CLEAR D_DESCRIPCION.
         ENDIF.
       ENDIF.
       SEARCH I_LINEAS-LINEA FOR 'WITH HEADER LINE'.
       IF SY-SUBRC = 0.
         APPEND I_LINEAS.
         PERFORM PROCESAR_FICHERO.
         PERFORM IMPRIMIR.
       ENDIF.
     ENDLOOP.
*&      Form GRABAR
      Graba el fichero en c:\temp\p.rtf y lo abre con word.
   FORM GRABAR.
     CALL FUNCTION 'LIST_DOWNLOAD'
         EXPORTING
        LIST_INDEX = SLIST_INDEX_DEFAULT
              METHOD     = 'RTF'
          EXCEPTIONS
               OTHERS     = 1.
     CALL FUNCTION 'EXECUTE_WINWORD'
          EXPORTING
               I_FILE = 'C:\TEMP\P.RTF'
          EXCEPTIONS
               OTHERS = 1.
   ENDFORM.                               " GRABAR
*&      Form PROCESAR_FICHERO
   FORM PROCESAR_FICHERO.
     DATA: L_AUX1(80),
          L_AUX2(80).
     FREE I_TABLA.
     LOOP AT I_LINEAS.
       CLEAR I_TABLA.
   translate i_lineas-linea to upper case.
       SEARCH I_LINEAS-LINEA FOR 'BEGIN OF'.
       IF SY-SUBRC = 0.
         SPLIT I_LINEAS-LINEA AT 'BEGIN OF' INTO L_AUX1 D_NOMBRE.
         SPLIT D_NOMBRE AT 'OCCURS' INTO D_NOMBRE L_AUX1.
       ENDIF.
       SEARCH I_LINEAS-LINEA FOR '('.
       IF SY-SUBRC = 0.
          SPLIT I_LINEAS-LINEA AT '(' INTO L_AUX1 L_AUX2.
         CONDENSE L_AUX1.
         I_TABLA-CAMPO = L_AUX1.
         SPLIT L_AUX2 AT ')' INTO L_AUX1 L_AUX2.
         CONDENSE L_AUX1.
         IF L_AUX1 CO '0123456789 '.
           I_TABLA-LONG = L_AUX1.
         ENDIF.
         I_TABLA-TIPO = 'CHAR'.
       ENDIF.
       SEARCH I_LINEAS-LINEA FOR 'LIKE'.
       IF SY-SUBRC = 0.
         SPLIT I_LINEAS-LINEA AT 'LIKE' INTO L_AUX1 L_AUX2.
         CONDENSE L_AUX1.
         I_TABLA-CAMPO = L_AUX1.
           SPLIT L_AUX2 AT ',' INTO L_AUX1 L_AUX2.
         CONDENSE L_AUX1.
         I_TABLA-REF = L_AUX1.
       ENDIF.
       SEARCH I_LINEAS-LINEA FOR 'TYPE'.
       IF SY-SUBRC = 0.
         SPLIT I_LINEAS-LINEA AT 'TYPE' INTO L_AUX1 L_AUX2.
         IF I_TABLA-CAMPO IS INITIAL.
           CONDENSE L_AUX1.
           I_TABLA-CAMPO = L_AUX1.
         ENDIF.
             SPLIT L_AUX2 AT ',' INTO L_AUX1 L_AUX2.
        CONDENSE L_AUX1.
         CASE L_AUX1.
           WHEN 'I'.
             I_TABLA-TIPO = 'INT'.
             I_TABLA-LONG = 4.
           WHEN 'C'.
             I_TABLA-TIPO = 'CHAR'.
           WHEN 'N'.
             I_TABLA-TIPO = 'NUMC'.
           WHEN 'T'.
             I_TABLA-TIPO = 'TIME'.
             I_TABLA-LONG = 8.
           WHEN OTHERS.
             I_TABLA-TIPO = L_AUX1.
         ENDCASE.
       ENDIF.
       SEARCH I_LINEAS-LINEA FOR '"'.
       IF SY-SUBRC = 0.
         SPLIT I_LINEAS-LINEA AT '"' INTO L_AUX1 L_AUX2.
         CONDENSE L_AUX2.
         I_TABLA-DESCR = L_AUX2.
       ENDIF.
       SEARCH I_LINEAS-LINEA FOR 'INCLUDE STRUCTURE'.
       IF SY-SUBRC = 0.
         SPLIT I_LINEAS-LINEA AT 'INCLUDE STRUCTURE' INTO L_AUX1 L_AUX2.
         SPLIT L_AUX2 AT '.' INTO L_AUX1 L_AUX2.
         CONDENSE L_AUX1.
         I_TABLA-CAMPO = 'INCLUDE STR'.
         I_TABLA-REF   = L_AUX1.
       ENDIF.
       SEARCH I_LINEAS-LINEA FOR 'WITH HEADER LINE'.
         IF SY-SUBRC = 0.
           IF NOT I_LINEAS-LINEA CA '"'.
             SPLIT I_LINEAS-LINEA AT 'OCCURS' INTO L_AUX1 L_AUX2.
             IF SY-SUBRC = 0.
               SPLIT L_AUX1 AT 'LIKE' INTO L_AUX1 L_AUX2.
               IF SY-SUBRC = 0.
                 CONDENSE L_AUX2.
                 IF NOT L_AUX2 IS INITIAL.
                   I_TABLA-CAMPO = '...'.
                   I_TABLA-TIPO = 'TABI'.
                   I_TABLA-REF   = L_AUX2.
                   SELECT SINGLE * FROM DD02T
                    WHERE TABNAME = L_AUX2
                      AND DDLANGUAGE = SY-LANGU.
                   IF SY-SUBRC = 0.
                   I_TABLA-TIPO = 'TABE'.
                   I_TABLA-DESCR   = DD02T-DDTEXT.
                   ENDIF.
                   IF L_AUX1 CA ':'.
                     SPLIT L_AUX1 AT 'DATA:' INTO L_AUX1 L_AUX2.
                   ELSE.
                     SPLIT L_AUX1 AT 'DATA' INTO L_AUX1 L_AUX2.
                   ENDIF.
                   D_NOMBRE = L_AUX2.
                 ENDIF.
               ENDIF.
             ENDIF.
           ENDIF.
         ENDIF.
       IF NOT I_TABLA-CAMPO IS INITIAL.
         APPEND I_TABLA.
       ENDIF.
     ENDLOOP.
     LOOP AT I_TABLA WHERE NOT REF IS INITIAL.
        SPLIT I_TABLA-REF AT '-' INTO L_AUX1 L_AUX2.
       SELECT SINGLE * FROM DD03L
        WHERE TABNAME = L_AUX1
          AND FIELDNAME = L_AUX2.
       IF SY-SUBRC = 0.
         I_TABLA-TIPO = DD03L-DATATYPE.
         I_TABLA-LONG = DD03L-INTLEN.
         IF I_TABLA-DESCR IS INITIAL.
           SELECT SINGLE * FROM DD04T
            WHERE ROLLNAME = DD03L-ROLLNAME
              AND DDLANGUAGE = SY-LANGU.
           IF SY-SUBRC = 0.
             I_TABLA-DESCR = DD04T-DDTEXT.
           ENDIF.
         ENDIF.
         MODIFY I_TABLA.
       ENDIF.
     ENDLOOP.
   ENDFORM.                               " PROCESAR_FICHERO
*&      Form IMPRIMIR
   FORM IMPRIMIR.
   DATA L_AUX(80).
     FORMAT COLOR COL_NORMAL INTENSIFIED ON.
     ULINE AT 1(80).
     WRITE: / SY-VLINE,
             (76)     D_NOMBRE CENTERED,
              SY-VLINE.
     SPLIT D_DESCRIPCION AT '*' INTO L_AUX D_DESCRIPCION.
     WRITE: / SY-VLINE,
             (76)     D_DESCRIPCION CENTERED,
              SY-VLINE.
     NEW-LINE.
     ULINE AT 1(80).
     DETAIL.
     FORMAT COLOR OFF.
     WRITE: /
           SY-VLINE,
         (10) 'CAMPO',
           SY-VLINE,
         (4) 'TIPO',
           SY-VLINE,
         (4) 'LONG',
           SY-VLINE,
         (16) 'REFERENCIA',
           SY-VLINE,
         (30) 'DESCRIPCION',
           SY-VLINE.
     NEW-LINE.
     ULINE AT 1(80).
     DETAIL.
     LOOP AT I_TABLA.
       WRITE: /
             SY-VLINE,
          (10)   I_TABLA-CAMPO,
             SY-VLINE,
             I_TABLA-TIPO,
             SY-VLINE,
          (4)   I_TABLA-LONG,
             SY-VLINE,
          (16)   I_TABLA-REF,
             SY-VLINE,
          (30)   I_TABLA-DESCR,
             SY-VLINE.
     ENDLOOP.
     NEW-LINE.
     ULINE AT 1(80).
     SKIP 2.
   ENDFORM.                               " IMPRIMIR
Thanks & regards
Sreeni

What are the advantages of using an internal table with workarea

Hi,
can anyone tell me
What are the advantages of using an internal table with workarea
over an internal table with header line?
thnks in adv
regards
nagi

HI,
Internal tables are a standard data type object which exists only during the runtime of the program. They are used to perform table calculations on subsets of database tables and for re-organising the contents of database tables according to users need.
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/content.htm
<b>Difference between Work Area and Header Line</b>
While adding or retrieving records to / from internal table we have to keep the record temporarily.
The area where this record is kept is called as work area for the internal table. The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
e.g.
data: begin of itab occurs 10,
ab type c,
cd type i,
end of itab. " this table will have the header line.
data: wa_itab like itab. " explicit work area for itab
data: itab1 like itab occurs 10. " table is without header line.
The header line is a field string with the same structure as a row of the body, but it can only hold a single row.
It is a buffer used to hold each record before it is added or each record as it is retrieved from the internal table. It is the default work area for the internal table
1) The difference between
whih header line and with out heater line of internal table.
ex:-
a) Data : itab like mara occurs 0 with header line.
b) Data: itab like mara occurs 0.
-While adding or retrieving records to / from internal table we have to keep the record temporarily.
-The area where this record is kept is called as work area for the internal table.
-The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
-Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
a) Data : itab like mara occurs 0 with header line.
table is with header line
b) Data: itab like mara occurs 0.
table is without header line
2)work area / field string and internal table
which one is prefarable for good performance any why ?
-The header line is a field string with the same structure as a row of the body, but it can only hold a single row , whereas internal table can have more than one record.
In short u can define a workarea of an internal table which means that area must have the same structure as that of internal table and can have one record only.
Example code:
data: begin of itab occurs 10,
ab type c,
cd type i,
end of itab. " this table will have the header line.
data: wa_itab like itab. " explicit work area for itab
data: itab1 like itab occurs 10. " table is without header line.
Regards,
Padmam.

The type of the database table and work area (or internal table)...

Hello
I am trying to use a database and select all records from it and store them into an internal table.
My code:
Select * from xixi_dbcurrency into table gt_currency.
The error:
"The type of the database table and work area (or internal table) "GT_CURRENCY" are not Unicode-convertible . . . . . . . . . .     "
Any suggestions?
Thank you

Hi Thomas,
Thank you for your inputs above.
But as you suggested is we use INTO CORRESPONDING FIELDS OF TABLE then it resolve the error.
But I have below piece of code:
DATA:    it_new_source TYPE STANDARD TABLE OF _ty_s_sc_1,
              wa_source TYPE _ty_s_sc_1,
              wa_new_source TYPE _ty_s_sc_1,
              ls_target_key TYPE t_target_key.
SELECT * INTO CORRESPONDING FIELDS OF TABLE it_new_source
       FROM /bic/afao06pa100
       FOR ALL ENTRIES IN SOURCE_PACKAGE
       where /bic/fcckjobno = SOURCE_PACKAGE-/bic/fcckjobno
       and /bic/fcckjitid = SOURCE_PACKAGE-/bic/fcckjitid.
But since this is reading into corresponding fields of table the data load from one DSO to other DOS is running for long more that 15 hours and still not getting completed and giving dump.
So if I switch the search to below:
SELECT * FROM /bic/afao06pa100
   INTO TABLE it_new_source
       FOR ALL ENTRIES IN SOURCE_PACKAGE
       where /bic/fcckjobno = SOURCE_PACKAGE-/bic/fcckjobno
       and /bic/fcckjitid = SOURCE_PACKAGE-/bic/fcckjitid.
Then I am getting below error:E:The type of the database table and work area (or internal table) "IT_NEW_SOURCE" are not Unicode convertible.
Can you please advice on this, as performance need to improve in start routine code.
Thank You.

How to create an dynamic internal table with the structure of a ddic table

Hi all,
I want to fill ddic-tables (which I already created) in my abap dictionary with data out of CSV-files (which are located on the CRM-Server). The ddic tables have different amount of fields.
I started with creating a table which contains the name of the tables and the path to the matching CSV-file.
At the beginning I'm filling an internal table with part of this data (the name of the ddic-tables) - after that I am looping at this internal table.
LOOP AT lt_struc ASSIGNING <lfs_struc>.
     LOOP AT lv_itab1 INTO lv_wa1 WHERE ztab_name = <lfs_struc>.
     lv_feld = lv_wa1-zdat_name.
    ENDLOOP.
    CONCATENATE 'C:\-tmp\Exportierte Tabellen\' lv_feld INTO lv_pfad.
    Do.
    OPEN DATASET lv_pfad FOR INPUT IN TEXT MODE ENCODING NON-UNICODE IGNORING CONVERSION ERRORS.
    READ DATASET lv_pfad INTO lv_rec.
    IF sy-subrc NE 0.
      EXIT.
    ENDIF.
    enddo.
    REPLACE ALL OCCURRENCES OF '"' IN lv_rec WITH ''.
    SPLIT lv_rec AT ';' INTO TABLE lt_str_values.
    INSERT into (<lfs_struc>) values lr_str_value.
    CLOSE DATASET lv_pfad.
endloop.
This is not the whole code, but it's working until
SPLIT lv_rec AT ';' INTO TABLE lt_str_values.
I want to split all the data of lv_rec into an internal table which has the structure of the current ddic-table, but I didn't find out how to do give the internal table the structure of the ddic-table. In the code I used an internal tyble type string but I should be the structure of the matching tabel.
If I try to create an internal table by using a fiel symbol, I am told, that the data types are not matching.
Has anyone an idea?

Hi Mayari,
though you were successfull with
METHOD cl_alv_table_create=>create_dynamic_table
I must warn you not to use it. The reason is that the number of tables created is limited, the method uses GENERATE SUBROUTINE statement and this triggers an unwanted database commit.
If you know the DDIC structure, it is (starting with ECC6.0) much easier:
field-symbols:
<table> type standard table.
data:
lr_data type ref to data.
Create data lr_data type table of (<DDIC structure>).
assign lr_data->* to <table>.
The split code can be simplified gaining speed loosing complexity not loosing functionality.
field-symbols:<fs_s> type any.
field-symbols:<fs_t> type any.
SPLIT lv_rec AT ';' INTO table it_string.
loop at it_string assigning <fs_s>.
assign component sy-tabix of wa_string to <fs_t>.
if sy-subrc = 0.
<fs_t> = <fs_s>.
endif.
at last.
append <fs_itwa3> to <ft_itab3>.
endat.
endloop.
Though it may work as Keshav.T suggested, there is no need to do that way.
Regards,
Clemens

Import from database an internal table with generic Type : Web Dynpro ABAP

Hi everyone,
i have a requirement in which i'm asked to transfer data flow between two frameworks, from WD Component to another. The problem is that i have to transfer internal tables with generic types. i used the import/ export from database approache but in that way i get an error message saying "Object references and data references not yet supported".
Here is my code to extract a generic internal table from memory.
    DATA l_table_f4 TYPE TABLE OF REF TO data.
FIELD-SYMBOLS: <l_table_f4> TYPE STANDARD TABLE.
DATA lo_componentcontroller TYPE REF TO ig_componentcontroller .
DATA: ls_indx TYPE indx.
lo_componentcontroller =   wd_this->get_componentcontroller_ctr( ).
lo_componentcontroller->fire_vh_search_action_evt( ).
ASSIGN l_table_f4 TO <l_table_f4>.
*-- Import table for Help F4
IMPORT l_table_f4 TO <l_table_f4> FROM DATABASE indx(v1) TO ls_indx ID 'table_help_f4_ID'.
The error message is desplayed when last instruction is executed " IMPORT l_table_f4...".
I saw another post facing the same problem but never solved "Generic Type for import Database".
Please can anyone help ?
Thanks & Kind regards.

hi KIan,
go:
general type
TYPE : BEGIN OF ty_itab,
           field1 TYPE ztab-field1,
           field2 TYPE ztab-field2,
*your own fields here:
           field TYPE i,
           field(30) TYPE c,
           END OF ty_itab.
work area
DATA : gw_itab TYPE ty_itab.
internal table
DATA : gt_itab TYPE TABLE OF ty_itab.
hope this helps
ec

Internal table with Dynamic and Non dynamic fileds

Hi Experts,
How to get the internal table with Dynamic and Non-Dynamic Fields.
Could u please help me.
Thanks,
Varun

Hi,
Execute the below sample code or analyze it there is appropriate description provided.
*& Report ZTEST_PRM_DYN_ALV
REPORT ZTEST_PRM_DYN_ALV.
type-pools: slis.
field-symbols: <dyn_table> type standard table,
<dyn_wa>.
data: alv_fldcat type slis_t_fieldcat_alv,
it_fldcat type lvc_t_fcat.
selection-screen begin of block b1 with frame title text-001.
parameters: p_flds(5) type c.
selection-screen end of block b1.
start-of-selection.
*build the dynamic internal table
perform build_dyn_itab.
*write 5 records to the alv grid
do 5 times.
perform build_report.
enddo.
*call the alv grid.
perform call_alv.
*Build_dyn_itab
form build_dyn_itab.
data: new_table type ref to data,
new_line type ref to data,
wa_it_fldcat type lvc_s_fcat.
*Create fields .
clear wa_it_fldcat.
wa_it_fldcat-fieldname = 'name1'.
wa_it_fldcat-datatype = 'mara-matnr'.
wa_it_fldcat-intlen = 5.
append wa_it_fldcat to it_fldcat .
*clear wa_it_fldcat.
wa_it_fldcat-fieldname = sy-index.
wa_it_fldcat-datatype = 'CHAR'.
wa_it_fldcat-intlen = 5.
append wa_it_fldcat to it_fldcat .
do p_flds times.
clear wa_it_fldcat.
wa_it_fldcat-fieldname = sy-index.
wa_it_fldcat-datatype = 'CHAR'.
wa_it_fldcat-intlen = 6.
append wa_it_fldcat to it_fldcat .
enddo.
*Create dynamic internal table and assign to FS
call method cl_alv_table_create=>create_dynamic_table
exporting
it_fieldcatalog = it_fldcat
importing
ep_table = new_table.
assign new_table->* to <dyn_table>.
*Create dynamic work area and assign to FS
create data new_line like line of <dyn_table>.
assign new_line->* to <dyn_wa>.
endform.
*Form build_report
form build_report.
data: fieldname(20) type c.
data: fieldvalue(5) type c.
data: index(3) type c.
field-symbols: <fs1>.
do p_flds times.
index = sy-index.
*Set up fieldvalue
concatenate 'FLD' index into
fieldvalue.
condense fieldvalue no-gaps.
assign component index of structure <dyn_wa> to <fs1>.
<fs1> = fieldvalue.
enddo.
*Append to the dynamic internal table
append <dyn_wa> to <dyn_table>.
endform.
*CALL_ALV
form call_alv.
data: wa_cat like line of alv_fldcat.
*clear wa_cat.
wa_cat-fieldname = 'matnr'.
wa_cat-seltext_s = sy-index.
wa_cat-outputlen = '10'.
append wa_cat to alv_fldcat.
do p_flds times.
clear wa_cat.
wa_cat-fieldname = sy-index.
wa_cat-seltext_s = sy-index.
wa_cat-outputlen = '6'.
append wa_cat to alv_fldcat.
enddo.
*Call ABAP List Viewer (ALV)
call function 'REUSE_ALV_GRID_DISPLAY'
exporting
it_fieldcat = alv_fldcat
tables
t_outtab = <dyn_table>.
endform.
Hope this will help, reward if found usefull.
Cheers,
Ram.

Diff Between Internal Table with Occurs 0 & Field Groups

Hi,
Is there really any difference between just using an internal table with an OCCURS 0 statement-- which would write the entire table to paging space-- and using field-groups? How is Field-Groups is more effective than Internal tables with occurs 0 when it comes to performance?
Could anybody please give some information regarding above question?
Thanks,
Mohan.

hi,
occurs 0 means it wont create any extra memory. based on the records only the memory is allocated to internal tables at run time. but when an internal table is created it can hold data of type to which it is declared.
i.e data: itab like mara occurs 0 with header line.
can take data only from mara table
we can also do in another way as using types keyword we can declare a standard structure and create a internal table of that type. its also not that useful as we have to change the structure depending on changes for storing data.
for this purpose field symbols are used. field symbols can hold any data means that they can point to tables, fields, any standard or user-defined types. field symbols actually points to respective types by which we can directly access to that types using field symbols.
filed symbols works more faster than internal tables.
if helpful reward some points.
with regards,
Suresh.A

Internal table with work area

Similar Messages

Maybe you are looking for