Header line and work area

Hi,
can anyone please explain me wht is the difference between header line and work area???

Hi,
INTERNAL TABLES
- Internal tables are used to obtain data from a fixed structure for
dynamic use in ABAP.
- Each line in the internal table has the same field structure.
- The main use for internal tables is for storing and formatting data from
a database table within a program.
WORK AREAS
- Work areas are single rows of data.
- It should have the same format as any of the internal tables.
- It is used to process the data in an internal table one line at a time.
Internal Tables with Header Line : Here the system automatically creates the work area. The work area has the same data type as internal table. This work area is called the HEADER line. It is here that all the changes or any of the action on the contents of the table are done. As a result of this, records can be directly inserted into the table or accessed from the internal table directly.
Internal Tables without Header Line : Here there is no work area associated with the table. Work area is to be explicitly specified when we need to access such tables. Hence these tables cannot be accessed directly.
HEADER LINE----
CREATED EXPLICITLY------
1.Internal table created by referring to another table
Syntax: Data <f> <type> with header line.
<type> refers to a table data type or table data objects using type or like.
Here internal table <f> is created of the type <type>.
Example:
DATA t_line TYPE line OCCURS 10 with header line.
2. Internal table created by referring to existing structure
Syntax: Data<f> <type> occurs n with header line.
The lines of the internal table <f> have the data type specified in <type> (Can use either like or type).
Example:
DATA flight_tab LIKE sflight OCCURS 10.
CREATED BY DEFAULT---
3. Internal table created With a new structure
Syntax: Data : Begin of <f> occurs <n>,
<component declaration>,
End of <f>.
Work area is created by default.
Example:
Data : Begin of itab occurs 10,
column1 type I,
column2(4) type C,
column3 like mara-ernam,
End of itab.
reward if useful
Regards

Similar Messages

Diff between header line and work area.

Diff between header line and work area.

Hi,
These are table with header line.
DATA: T_TABLE type table of <table_name> with header line.
data: begin of t_table occurs 0,
 field1 type ...
 field2 type ...
 field3 type ...
 end of t_table.
The result is:
TABLE
FIELD NAME |FIELD1|FIELD2|FIELD3|
HEADER LINE |EE1 |EE2 |EE3 | <---- Line 5 content
 1|AA1 |AA2 |AA3 |
 2|BB1 |BB2 |BB3 |
 3|CC1 |CC2 |CC3 |
 4|DD1 |DD2 |DD3 |
 5|EE1 |EE2 |EE3 |
These are table without header line.
DATA: T_TABLE type table of <table_name>.
DATA: T_TABLEX LIKE TABLE OF t_table.
The result is:
TABLE
FIELD NAME |FIELD1|FIELD2|FIELD3|
 0|--- |--- |--- | <---- No header Line
 1|AA1 |AA2 |AA3 |
 2|BB1 |BB2 |BB3 |
 3|CC1 |CC2 |CC3 |
 4|DD1 |DD2 |DD3 |
 5|EE1 |EE2 |EE3 |
These are work areas:
Tables <table>.
DATA: wa type <table>.
DATA: wa like t_table.
DATA: wa type line of <table>.
The result is:
WORK AREA
|EE1 |EE2 |EE3 | <---- Content
Regards.
Marcelo Ramos

Internal table with header line and work area.

data:itab like LIKE bapimepoheader.
DATA : BEGIN OF it_po_items OCCURS 0.
        INCLUDE STRUCTURE bapimepoitem.
DATA : END OF it_po_items.
DATA:it_input         TYPE STANDARD TABLE OF typ_input,
      wa_input         TYPE typ_input,
LOOP AT it_input INTO wa_input WHERE poind = 'H'.
CLEAR wa_po_header.
wa_po_header-doc_type = wa_input-bsart.
wa_po_header-comp_code = wa_input-bukrs.
wa_po_header-vendor    = wa_input-lifnr.
CLEAR it_po_items.
it_po_items-po_item = v_itemcount * 10.
it_po_items-acctasscat = wa_input-knttp.
it_po_items-material   = wa_input-matnr.
it_po_items-plant      = wa_input-werks.
it_po_items-quantity   = wa_input-menge.
it_po_items-net_price = wa_input-netpr.
it_po_items-po_unit    = wa_input-meins.
it_po_items-free_item = wa_input-umson.
it_po_items-tax_code   = wa_input-mwskz.
it_po_items-gr_ind     = wa_input-wepos.
it_po_items-gr_non_val = wa_input-weunb.
it_po_items-incoterms1 = wa_input-inco1.
it_po_items-incoterms2 = wa_input-inco2.
it_po_items-vend_mat   = wa_input-idnlf.
it_po_items-taxjurcode = wa_input-txjcd.
it_po_items-item_cat   = wa_input-pstyp.
APPEND it_po_items.
here my doubt is whether i can move data from work area to internal table in this way?
whether this is the correct approach or not?

hii,
u can define structure and make workarea ,internal table using that structure.
for example
types:begin of struct,
         declare all fields,
         end of struct.
data:wa type struct,
       int_tab type standard table of struct.
hope this will help u.

Schedule lines and work area

Hi All!
While entering the multiple line items in the sales order(Quotation) screen , at the 60th item the system throws following error message :
System : Schedule lines of Item 000060 is not in Work are.
Has anyone ever came across such message during quotation creation?
Early reply will be appreciated!
Thanks,
Mamata

Hello Sir,
We have the same issue appearing
Item XX for scheduled line XX is in the work area
I am not too sure about the T-Code OQ77 mentioned above. Could you please let me know the reason behind this error as the sales order the error message is appearing is a standard order (Norm Item).
I am not sure how to get rid of this error as it is appearing in a number of sales orders
Thanks in advance for the replies
Regards,
Doss

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.

Add new email header line and add Bcc recepient to this additional header.

Hi Folks,
iMS5.2p1, Solaris 8.
Just after a few directions. I have a 'catch-all' mbox, that customer POP's. The customer then uses MDaemon to deliver email, based on rules to correct recepients, works fine until a Bcc comes in, as quoted below.
Why doesn't MDaemon parse the BCC header?
BCC only works with SMTP mail. By definition, the carbon copy is "Blind".
There are no headers in the message which can be parsed using the POP3 method that would provide the address. The only hope for these kinds of messages is to get the ISP to stamp the message file with the delivery information from the SMTP session during delivery to the ISP. For example, when the person sends the BCC message to the ISP hosting the mail, some of them stamp a header called "Deliver-To:" into the message. MDaemon could pick up on such a header if it existed.
I know I would have to tackle this with either a re-write/mapping/conversion, but not sure what the best approach, ie to add and rewrite the Bcc, recepient into the new 'Deliver-To:' header.
Any good solutions/tips ?
Cheers folks.

Hi Jay,
Sorry if there is any confusion. The customer at his premises has a server running this mail app. called MDaemon, which uses filters to deliver to local mboxes for their users. The customer in question just wanted a 'catch-all' mbox with iMS for his domain (which we host), to just POP3 this mbox and then the customer's MDaemon app, parses through filters to deliver to correct local mbox. They didn't want to have each user's mbox hosted on iMS....as yet anyway, thus the need for 'catch-all' delivery of email for the customer domain to one iMS mbox.
The problem is with any Bcc email for customer's domain. As described POP3 as per definition hides the Bcc line, thus MDeamon filters at customer end will fail delivery to intended recepient. Thus the doco from MDaemon as explained to me from the customer can handle additional header lines and parse that way. Thus the need to add the recepient in the Bcc line to an additional header (ie. Deliver-To: [Bcc smtp recepient]). Then as MDeamon doco says it can be setup to parse and deliver to correct local mbox. I hope that my be a little clearer.
So I need to on iMS rewrite any Bcc recepient for customers 'catch-all' mail domain and add another header line (ie. Deliver-To: [Bcc smtp recpient]). So when customer POP's iMS mbox, Mdeamon at customer's end will parse and deliver locally.
Hope that makes sense and the best way to add an additional header and take the original Bcc line and add to to new header is.....hopefully a pointer from your good self.
Cheers.

HT1277 Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

Ok; I'm not sure what you're doing. 36 hours is rather long. Seems like a new migration. Not what I intended.
Here's what I intended: from the newly-migrated and apparently-corrupt environment, create a new user, not related to any existing user, nor any migration-created user, or any other user for that matter. That is, use  > System Preferences > Users and Groups, authenticate yourself by clicking on the padlock, and then click the + and create a wholly new user. Then log in under that user and establish the mail access.
36 hours? I'm wondering if there's an error or an exceedingly slow network here? Or a really, really slow disk? Or a sick backup? (WiFi isn't the path I'd usually choose, either.)
Failing the attempted second migration, I'd try a different tactic. Does your existing (old) system work? If so, I'd bypass the backup and connect an external (scratch) USB disk drive to the (old) sstem and then boot and use Disk Utility booted from the installer DVD disk or boot and use Disk Utility from the recovery partition or booted from a recovery partition created on some other external storage (details here vary by the OS X version and what hardware you have), and perform a full-disk backup of your original internal disk to (scratch) external storage. (Make sure you get the source and target disks chosen correctly here; copying the wrong way — from the scratch disk to your existing disk — will clobber your data!) In esssence, this will clone your existing boot disk. Then dismount the (formerly-scratch) external disk, transfer it over to the new system, and use it as the source of the migration, by performing a fresh OS X installation on the new system.
Target Disk Mode is also sometimes an option for accessing the disk for a migration, but that requires the right cable, and requires systems that have the same external connection; newer MacBook Pro systems use Thunderbolt for this, and older systems tend to use FireWire. And I'm guessing you don't have compatible hardware.
The details here can and do vary by your OS X versions and your particular Mac systems — if you'll identify the specific models and hardware, somebody might be able to better tailor the above (fairly generic) sequence to your particular configuration.

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.

The type of the database table and work area are not Unicode convertible

***Data declaration
TYPES : BEGIN OF t_zle_lagerplanung,
                   SEl, "stores which row user has selected
                   kdauf TYPE zle_lagerplanung-kdauf,
                   kdpos TYPE zle_lagerplanung-kdpos,
                   etenr TYPE zle_lagerplanung-etenr,
                   papiermaschine TYPE zle_lagerplanung-papiermaschine,
                   runnr TYPE zle_lagerplanung-runnr,
                   prio TYPE zle_lagerplanung-prio,
                   werk TYPE zle_lagerplanung-werk,
                   durchmesser TYPE zle_lagerplanung-durchmesser,
                   breite TYPE zle_lagerplanung-breite,
                   anzle TYPE zle_lagerplanung-anzle,
                   lgpla TYPE zle_lagerplanung-lgpla,
                   lgtyp TYPE zle_lagerplanung-lgtyp,
                   art TYPE zle_lagerplanung-art,
                   anzhoehe TYPE zle_lagerplanung-anzle,
                   fa TYPE zle_lagerplanung-fa,
END OF t_zle_lagerplanung.
DATA : it_zle_lagerplanung TYPE STANDARD TABLE OF t_zle_lagerplanung INITIAL SIZE 0,
            wa_zle_lagerplanung TYPE t_zle_lagerplanung.
Here I am getting the data in internal table by using thiis select statement.
SELECT kdauf kdpos etenr papiermaschine runnr prio werk durchmesser breite
              anzle lgpla lgtyp art anzhoehe fa
FROM    zle_lagerplanung INTO CORRESPONDING FIELDS OF TABLE it_zle_lagerplanung
WHERE kdauf IN s_kdauf
AND       KDPOS IN s_kdpos
AND      werk = p_werks.
But while updating the particular field in zle_lagerplanung using this statement
UPDATE zle_lagerplanung from table it_zle_lagerplanung.
it is giving syntax error
"The type of the database table and work area (or internal table)
"IT_ZLE_LAGERPLANUNG" are not Unicode convertible. "
Could any one help me out how to resolve this problem....
Thanks in advance

Dear Shayamal,
XXX....are not Unicode convertible
This error comes while inserting or updating database and the fields are not matching between data base table and structure .
Check you fields of data base table and "zle_lagerplanung" and struture "it_zle_lagerplanung" . There fields must match.
thanks and regrds,
Anup Banerjee

Difference between Field symbols and work area for Internal tables

Hi,
In ECC versions we all know that we need to declare the internal tables without headerline, and for handling the internal tables we need to use exclusive work areas.
Currently i have an issue that we have been asked to use field symbols instead of work areas...can any one help me how to use the field symbols and also let me know how it will improve the performance of the program..
Thanks and Regards,
Kathir

Hi
DATA: WA TYPE ITAB.
LOOP AT ITAB INTO WA.
IF WA-FIELD = .....
ENDIF.
ENDLOOP.[(code]
FIELD-SYMBOLS <WA> TYPE ANY.
LOOP AT ITAB ASSIGNING <WA>.
ENDLOOP.
Now the problem is you can't know the name of the fields of the table at runtime, so you can't write:
IF <WA>-FIELD = .....
ENDIF.
Anyway you can create a field-symbols strcturated like the table:
[code]FIELD-SYMBOLS <WA> TYPE ITAB.
LOOP AT ITAB ASSIGNING <WA>.
IF <WA>-FIELD = .....
ENDIF.
ENDLOOP.
I don't know which are the differences for the performance between to use a field-symbol and to use a structure as work-area.
The differnce between the field-symbols and work-area is the field-symbol is assigned directly to the record, so u don't need to do a MODIFY statament to change something:
LOOP AT ITAB INTO WA.
WA-FIELD =
MODIFY ITAB FROM WA.
ENDLOOP.
LOOP AT ITAB ASSIGNING <WA>.
<WA>-FIELD =
ENDLOOP.
These two pieces of abap code do the same action, so probably the field-symbol improve the performance because it do an access directly to the record without to use an external structure as workarea.
Max

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

What is the difference between Structure and Work area

Hi Guys,
What is the difference between Structure and work area?
Are they same with different names?
Thanks,
mini.

hey buddies,*
i had this same doubt for a long time and i have my finds with me ie wa and structure are the same but wa can hold a single record but structure cannot hold data in it but according to the previous posts folks say structure too holds data as wa does but i guess when debugging wa holds data and structure doesnt hold bcoz i tried.
types : begin of str_mara,
             matnr type mara-matnr,
            ernam type mara-ernam,
            end of str_mara.
data it_mara type table of str_mara.
select matnr ernam from mara into it_mara where matnr = '100-101'.
*********************if folks say wa = structure,this should work,isn't it?*********************************
loop at it_mara into str_mara.
write:/ str_mara-matnr , str_mara-ernam.
endloop.
*******************but it throws an error saying that str_mara is not a wa*******************************
i may not be correct too plz let me know if i'm wrong
Edited by: arun_aime on Feb 12, 2010 4:41 PM

I want to create an internal table without using header line and occurs 0?

hi experts,
Can anybody help me to declare an internal table without using headerline and occurs 0 options but still i have to use the functionalities that occurs 0 and header line options provide.

Hi Saisri,
You can use the internal table without headerline and create a header for then internal table with the same structure. We need to use the header while manipulating with the data of the internal table.
example:
types: begin of ty_afpo,
 kdauf type kdauf,
 kdpos type kdpos,
 ltrmp type ltrmp,
 end of ty_afpo.
data : t_afpo type standard table of ty_afpo, " internal table declaration
 wa_afpo type ty_afpo. " work area declaration
<after populating the data into the internal table>
loop at t_afpo into wa_afpo.
write:/ wa_afpo-kdauf, wa_afpo-kdpos, wa_afpo-ltrmp.
endloop.
This I think shall give you a basic understanding of how things work.
Reward points if this helps,
Kiran

Header, line and adress details

hi experts,
actually i am working on outbound iunterface.
in the target structure it is given as ,
1.header,
2, line items,
3, adress.
using my select statements i have retrived the data and in the target structure the data should be displayed as
1.header,
2, line items,
3, adress.
plz suggest me how to do.
regards,
siri.

Hi rajesh,
Header is a workarea of the table which acts as an interface for the table. Header can have only one record at a time.
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.
example,
internal table.
data: begin of itab occurs 0,
matnr like mara-matnr,
maktx like makt-maktx,
end of itab.
workarea.
data: begin of itab,
matnr like mara-matnr,
maktx like makt-maktx,
end of itab.
also,
workarea:
types: begin of type_mat,
matnr like mara-matnr,
maktx like makt-maktx,
end of type_mat.
internal table
data: t_mat type standard table of type_mat.
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.

Confusion b/w term.Roll area and Work area

Hi,
Can someone explain me these Two Term in simple english.
1)Roll Area
2)Work Area
How aou distinguish b/w them.
Thanks.
Samir.

Hi Samir,
Welcome to SDN.
1. The first & main difference is
 WORK AREA : Refers when we talk about ABAP Programming
 ROLL AREA : Refers when we talk about R/3 Instance
 (on server)
2. Work Area :
 We can call it nothing but a VARIABLE.
 But this variables/ terminology is used for the purpose
 of internal table.
 for eg.
 Loop at ITAB.
 (When itab is defined with header line,
 the header line becomes the work area,
 ie temporary storage)
 Loop at ITAB into wa.
 (here it is used when itab is not defined
 with header line, instead, a field-string WA
 is defined , same as itab structure)
3. ROLL AREA :
 SAP Gui <----
> R/3 Server
 There is a constant interaction between
 the above two.
 In a program, many variables are used,
 there are many screens each having
 their own logic.
 Many users are running the same program.
 To keep track of all these, the
 r/3 instance on the server,
 keeps information about EACH and EVERYTHING
 in its memory RAM.
 This BUNCH of INFORMATION
 about EACH SESSION and the PROGRAM
 is called work area.
I hope it helps.
Regards,
Amit M.
Message was edited by: Amit Mittal

Header line and work area

Similar Messages

Maybe you are looking for