Differennce b/w workarea and header line

can any one tell me the difference between workarea and header line.

Hi
Difference between Work Area and Header Line
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.
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb36a1358411d1829f0000e829fbfe/content.htm
If useful reward.
Vasanth

Similar Messages

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

Flat file having multiple header lines , how to separate the same and pushit into my intrnal table

Hi Guys,
                I got an issue , My flat file having multiple header lines
TPS27RPR MOME                                      THRIFT (SAVING) PLAN SYSTEM                                           Page    2
09:54 05 JAN 2014                          List of Contributors w/Company Contributions                           Phase DAY Unit TRE
Company No: xxxxxxxx - xxxxxxxxxxxxx.
                                                                        Employee/       Employee/
Employee Full Name/                                                       Company         Company                        Allocation
Number ID Number                           PS PN End Date        Contribution          Profit        Total Balance   Percentage
some lines of data and again
TPS27RPR MOME                                      THRIFT (SAVING) PLAN SYSTEM                                           Page    2
09:54 05 JAN 2014                          List of Contributors w/Company Contributions                           Phase DAY Unit TRE
Company No: xxxxxxxx - xxxxxxxxxxxxx.
                                                                        Employee/       Employee/
Employee Full Name/                                                       Company         Company                        Allocation
Number ID Number                           PS PN End Date        Contribution          Profit        Total Balance   Percentage
in this case how could I separate the header lines from the flat file and update the details to my internal table.
kindly help me on this issue.
Thanks and regards,
M.S.Amirtharajvijay.

Hi Amirthraj,
If the flat file is static (if the content within it is same for all) then use the offset concept. First get the contents of the flat file into an internal table and later find the field that has to be in final internal table within the line, calculate the offset for the line and get the value into an workarea. Finally modify/append the work area into an internal table. Also wait for other experts answers for any other hassle free way to achieve the requirement.
With Regards,
Giriesh M

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.

Is there a way to create a heading with shading behind the text and thin lines above and below?

I'm working with InDesign CS6, Windows 7.
Is there a way, using paragraph rules, to create a heading with shading behind the text and thin lines above and below the text?
I'd like to create headings that look like these:
Thank you!

I have a document where I almost do such, but without the fill. I use a Head Style which Spans Columns for this instance; it allows the haeds to flow and fill the width.
Paragraph Rules above and below are turned on with plenty of offset.
I tweaked my setting to accomodate your need - It required only one instance, not above and below, and changing the stroke to a double stroke.
It may be necessary to create a custom stroke to modify the proportion of stroke vs fill. There is a difference of thin-thin and thick-thick, neither of which seemed perfect but might be dependent on the Character height.
Creating custom strokes is accomplished via the Strokes Panel.

Extra header lines appearing in payload after singning and encrypting in Mail Receiver adapter PI 7.31

Hi,
We have a mail receiver adapter which is sending out a edi payload as attachment to the external receiver.
When we send the normal .edi file it is ok.
But when we sign and encrypt the payload and send it out, the external customer receiver decrypts and validates the message successfully but when their application tries to read the edi payload it finds the extra header lines as below :
content-id:
<[email protected]>
Content-Disposition: attachment; filename=xxxxxxxx.edi Content-Type:
application/xml
At their end, their application (DataPower) expects the first three characters of the payload
(decrypted payload) to be either UNA or UNB.This is how it validates whether the incoming message is an EDI message.
But it encounters the extra MIME headers in the payload.
Therefore it gets rejected by DataPower which thinks the content is an
unknown message type.
How to suppress the header lines appearing in the payload(after decryption and validation).
Thanks,
Guest

hi,
try content-type as "text/xml"

Line item and header records in the same infopackage

Gurus,
I wanted to check how can I make sure that I get all the line item documents in the same package with the header document record in the same infopackage? Is there some setting for that? If I am writing a custom extractore how can I make sure of this in ABAP?
Thanks
AK

Dear AKBW,
This is not very clear why you want to use same infopackage for line-item as well as header data. Normally there are 2 different datasources for line item and for header data.
Say you are woking with Sales Order Data in ECC.
So Line-item datasource for sales order data - 2LIS_11_VAITM
and Header datasource for sales order data - 2LIS_11_VAHDR.
Now as they are 2 different datasource, so you must need 2 different infopackages.
Now if you have created one custom datasource in ECC, then just check if its extracting line-item level or header level data. Normally when we create any custom datasource, we try to make it line-item level, to have all the itemwise detail. Though its not mandatory.
So if you have 2 different datasources (SAP or Custom), you definitely need 2 different infopackages.
Please let me know, if you still have any more doubt. You can also give me the other detail of the custom datsource you are creating.( type, fields, what it is supposed to extract etc)..

Difference between Journal batch,journal header and journal line

Hi,
Can someone explain what the difference between Journal batch, Journal header and journal line are?
Can we post only one batch at a time?

Hi,
Journal Batch means it contains batch name, description, status, running total debits and credits, and other information.
Journal Headers means it contains batch ID, the journal entry name
and description, and other information about the journal entry.
Journal Lines means it contains journal entry header ID, the line number, the associated code combination ID, and the debits or credits associated with the journal line.
So here is the replationships.
Batch--- 1 to many -- Headers
Headers -- 1 to many -- Lines.
--Basava.S

No page break between table header and first line of the table main area

Hi all.
I'm printing a form which contains a lot of tables. Sometimes while printing the table header line remains at the bootom of the page and the lines of internal table are printed on the next page (also with header because i have marked 'at page break' in the header). How is it possible not to break header line of 'Table'-node and the first line of internal table?
Regards, Nikolai.

Hello Niki,
try to use page protection......
create a folder and place the text that r to be displayed without break.........
and check the checkbox page protection.
I think you cannot put an entire table in a folder & turn "Page Protection" on simultaneously.
Any ideas?
BR,
Suhas

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

Header, Line Item and Cache Techniques Using Hashed Tables

Hi,
How can I work with header, line item, and a cache techniques using hashed tables?
Thanks,
Shah.

Hi,
Here is an example to clarify the ideas:
In general, every time you have a header-> lines structure you have a unique key for the lines that has at least header key plus one or more fields. I'll make use of this fact.
I'll try to put an example of how to work with header -> line items and a cache technique using hashed tables.
Just suppose that you need a list of all the material movements '101'-'901' for a certain range of dates in mkpf-budat. We'll extract these fields:
mkpf-budat
mkpf-mblnr,
mseg-lifnr,
lfa1-name1,
mkpf-xblnr,
mseg-zeile
mseg-charg,
mseg-matnr,
makt-maktx,
mseg-erfmg,
mseg-erfme.
I'll use two cache: one for maintaining lfa1 related data and the other to maintain makt related data. Also I'll only describe the data gathering part. The showing of the data is left to your own imagination.
The main ideas are:
1. As this is an example I won't use inner join. If properly desingned may be faster .
2. I'll use four hashed tables: ht_mkpf, ht_mseg, ht_lfa1 and ht_makt to get data into memory. Then I'll collect all the data I want to list into a fifth table ht_lst.
3. ht_mkpf should have (at least) mkpf's primary key fields : mjahr, mblnr.
4. ht_mseg should have (at least) mseg primary key fields: mjahr mblnr and zeile.
5. ht_lfa1 should have an unique key by lifnr.
6. ht_makt should have an unique key by matnr.
7. I prefer using with header line because makes the code easier to follow and understand. The waste of time isn't quite significant (in my experience at least).
Note: When I've needed to work from header to item lines then I added a counter in ht_header that maintains the count of item lines, and I added an id in the ht_lines so I can read straight by key a given item line. But this is very tricky to implement and to follow. (Nevertheless I've programmed it and it works well.)
The data will be read in this sequence:
select data from mkpf into table ht_mkpf
select data from mseg int table ht_mseg having in count all the data in ht_mkpf
loop at ht_mseg (lines)
filter unwanted records
read cache for lfa1 and makt
fill in ht_lst and collect data
endloop.
tables
tables: mkpf, mseg, lfa1, makt.
internal tables:
data: begin of wa_mkpf, "header
mblnr like mkpf-mblnr,
mjahr like mkpf-mjahr,
budat like mkpf-budat,
xblnr like mkpf-xblnr,
end of wa_mkpf.
data ht_mkpf like hashed table of wa_mkpf
with unique key mblnr mjahr
with header line.
data: begin of wa_mseg, " line items
mblnr like mseg-mblnr,
mjahr like mseg-mjahr,
zeile like mseg-zeile,
bwart like mseg-bwart,
charg like mseg-charg,
matnr like mseg-matnr,
lifnr like mseg-lifnr,
erfmg like mseg-erfmg,
erfme like mseg-erfme,
end of wa_mseg,
data ht_mseg like hashed table of wa_mseg
with unique key mblnr mjahr zeile
with header line.
data: begin of wa_lfa1,
lifnr like lfa1-lifnr,
name1 like lfa1-name1,
end of wa_lfa1,
data ht_lfa1 like hashed table of wa_lfa1
with unique key lifnr
with header line.
data: begin of wa_makt,
matnr like makt-matnr,
maktx like makt-maktx,
end of wa_makt.
data: ht_makt like hashed table of wa_makt
with unique key matnr
with header line.
result table
data: begin of wa_lst, "
budat like mkpf-budat,
mblnr like mseg-mblnr,
lifnr like mseg-lifnr,
name1 like lfa1-name1,
xblnr like mkpf-xblnr,
zeile like mseg-zeile,
charg like mseg-charg,
matnr like mseg-matnr,
maktx like makt-maktx,
erfmg like mseg-erfmg,
erfme like mseg-erfme,
mjahr like mseg-mjahr,
end of wa_mseg,
data: ht_lst like hashed table of wa_lst
with unique key mblnr mjahr zeile
with header line.
data: g_lines type i.
select-options: so_budat for mkpf-budat default sy-datum.
select-options: so_matnr for mseg-matnr.
form get_data.
select mblnr mjahr budat xblnr
into table ht_mkfp
from mkpf
where budat in so_budat.
describe table ht_mkpf lines g_lines.
if lines > 0.
select mblnr mjahr zeile bwart charg
matnr lifnr erfmg erfme
into table ht_mseg
from mseg
for all entries in ht_mkpf
where mblnr = ht_mkpf-mblnr
and mjahr = ht_mjahr.
endif.
loop at ht_mseg.
filter unwanted data
check ht_mseg-bwart = '101' or ht_mseg-bwart = '901'.
check ht_mseg-matnr in so_matnr.
read header line.
read table ht_mkpf with table key mblnr = ht_mseg-mblnr
mjahr = ht_mseg-mjahr.
clear ht_lst.
note : this may be faster if you specify field by field.
move-corresponding ht_mkpf to ht_lst.
move-corresponding ht_mseg to ht_lst.
perform read_lfa1 using ht_mseg-lifnr changing ht_lst-name1.
perform read_makt using ht_mseg-matnr changing ht_lst-maktx.
insert table ht_lst.
endloop.
implementation of cache for lfa1.
form read_lfa1 using p_lifnr changing p_name1.
read table ht_lfa1 with table key lifnr = p_lifnr
transporting name1.
if sy-subrc <> 0.
clear ht_lfa1.
ht_lfa1-lifnr = p_lifnr.
select single name1
into ht_lfa1-name1
from lfa1
where lifnr = p_lifnr.
if sy-subrc <> 0. ht_lfa1-name1 = 'n/a in lfa1'. endif.
insert table ht_lfa1.
endif.
p_name1 = ht_lfa1-name1.
endform.
implementation of cache for makt
form read_makt using p_matnr changing p_maktx.
read table ht_makt with table key matnr = p_matnr
transporting maktx.
if sy-subrc <> 0.
ht_makt-matnr = p_matnr.
select single maktx into ht_matk-maktx
from makt
where spras = sy-langu
and matnr = p_matnr.
if sy-subrc <> 0. ht_makt-maktx = 'n/a in makt'. endif.
insert table ht_makt.
endif.
p_maktx = ht_makt-maktx.
endform.
Reward points if found helpfull...
Cheers,
Siva.

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

Trying to publish an event to fb from iPhoto '09, 8.1.2. Getting error message: "Line 22: Opening and ending tag mismatch: meta line 0 and head".

Trying to publish an event to fb from iPhoto '09, 8.1.2. Getting error message: "Line 22: Opening and ending tag mismatch: meta line 0 and head". Never had any trouble before. What in the world?

See if you can export those same photos to a folder on your Desktop.
OT

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.

With header line & with out header line ?

what is difference between with header line & without header line ?

When you create an internal table object you can also declare a header line with the same name. You can use the header line as a work area when you process the internal table. The ABAP statements that you use with internal tables have short forms that you can use if your internal table has a header line. These statements automatically assume the header line as an implicit work area. The following table shows the statements that you must use for internal tables without a header line, and the equivalent statements that you can use for internal tables with a header line:
Operations without header line
Operations with header line
Operations for all Table Types
INSERT <wa> INTO TABLE <itab>.
INSERT TABLE ITAB.
COLLECT <wa> INTO <itab>.
COLLECT <itab>.
READ TABLE <itab> ... INTO <wa>.
READ TABLE <itab> ...
MODIFY TABLE <itab> FROM <wa> ...
MODIFY TABLE <itab> ...
MODIFY <itab> FROM <wa> ...WHERE ...
MODIFY <itab> ... WHERE ...
DELETE TABLE <itab> FROM <wa>.
DELETE TABLE <itab>.
LOOP AT ITAB INTO <wa> ...
LOOP AT ITAB ...
Operations for Index Tables
APPEND <wa> TO <itab>.
APPEND <itab>.
INSERT <wa> INTO <itab> ...
INSERT <itab> ...
MODIFY <itab> FROM <wa> ...
MODIFY <itab> ...
Using the header line as a work area means that you can use shorter statements; however, they are not necessarily easier to understand, since you cannot immediately recognize the origin and target of the assignment. Furthermore, the fact that the table and its header line have the same name can cause confusion in operations with entire internal tables. To avoid confusion, you should use internal tables with differently-named work areas.
The following example shows two programs with the same function. One uses a header line, the other does not.
With header line:
TYPES: BEGIN OF LINE,
COL1 TYPE I,
COL2 TYPE I,
END OF LINE.
DATA ITAB TYPE HASHED TABLE OF LINE WITH UNIQUE KEY COL1
WITH HEADER LINE.
DO 4 TIMES.
ITAB-COL1 = SY-INDEX.
ITAB-COL2 = SY-INDEX ** 2.
INSERT TABLE ITAB.
ENDDO.
ITAB-COL1 = 2.
READ TABLE ITAB FROM ITAB.
ITAB-COL2 = 100.
MODIFY TABLE ITAB.
ITAB-COL1 = 4.
DELETE TABLE ITAB.
LOOP AT ITAB.
WRITE: / ITAB-COL1, ITAB-COL2.
ENDLOOP.
Without header line:
TYPES: BEGIN OF LINE,
COL1 TYPE I,
COL2 TYPE I,
END OF LINE.
DATA: ITAB TYPE HASHED TABLE OF LINE WITH UNIQUE KEY COL1,
WA LIKE LINE OF ITAB.
DO 4 TIMES.
WA-COL1 = SY-INDEX.
WA-COL2 = SY-INDEX ** 2.
INSERT WA INTO TABLE ITAB.
ENDDO.
WA-COL1 = 2.
READ TABLE ITAB FROM WA INTO WA.
WA-COL2 = 100.
MODIFY TABLE ITAB FROM WA.
WA-COL1 = 4.
DELETE TABLE ITAB FROM WA.
LOOP AT ITAB INTO WA.
WRITE: / WA-COL1, WA-COL2.
ENDLOOP.
The list, in both cases, appears as follows:
1 1
2 100
3 9
The statements in the program that does not use a header line are easier to understand. As a further measure, you could have a further work area just to specify the key of the internal table, but to which no other values from the table are assigned.
Internal table with header line
you can use anywhere except obkect oriented concept.
Internal table without header line :
You should use in Object oriented concept..
Always try to use without header line,performance point of view it is best..
Example :
Without header line.
Structure
types : begin of ty_itab ,
matnr type mara-matnr,
end of ty_itab.
Internal table
data i_itab type standard table of ty_itab .
Work area
data wa_itab like line of i_itab
With header line
data : begin of i_itab occurs 0,
matnr like mara-matnr,
end of i_itab
itab with header lines are obsolete, anyway it will work but not recommended. instead use work area or more effiecient is field symbols. so donot use itab with header line.
i will explain use of itab w/o header line.
Data: itab1 type standard table of mara with header line occurs 0,
itab2 type standard table of mara,
wa_itab2 type mara.
loop at itab1.
"This will work fine.
endloop.
loop at itab2.
"This will give erro that itabd does not hav workarea
endloop.
"so write
loop at itab2 into wa_itab2.
"This will work
endloop.
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
regards,
srinivas
*reward for useful answers*

Differennce b/w workarea and header line

Similar Messages

Maybe you are looking for