topic Re: Work Area in Application Development and Automation Discussions

Work Area

Former Member — Thu, 07 Jun 2007 04:20:46 GMT

Why do we use work area. When we have Itab to use. Please give any code example where I can see the proper use of work area.

Regards.......

Re: Work Area

anversha_s — Thu, 07 Jun 2007 04:21:39 GMT

hi,

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.

The work area is the temporary space in SAP memory that you are working as an ABAPer and is for the duration that your program is running, you also define that area and space as you define internal tables etc

Each row in a table is a record and each column is a field.

A work area is nothing more than a variable in your program which usually has some strucure. This work area holds data at runtime. A lot of times a work area is used to read lines of an internal table into.

Loop at itab into wa.

write:/ wa-fld1, wa_fld2.

endloop.

Rgds

'Anversha

Re: Work Area

Former Member — Thu, 07 Jun 2007 04:25:05 GMT

Hi,

Work area(WA) is used when we declare internal table without header line...

Now in OO context, internal table with header line is deprecated, hence we use WA which is like line of table.

Get values into WA and append it to ITAB.

Code Example..

data : itab type standard table of MARA,
	wa like line of itab.

wa-matnr = '000223'.
wa-ERSDA = '01122006'.
wa-AENAM = 'XYZ'.
...
append wa to itab.

TYPES : begin of wat,
	matnr type MATNR,
	ersda type ERSDA,
	ERNAM type ERNAM,
	end of wat.

data : itab type standard table of wat,
	wa like line of itab.

wa-matnr = '000223'.
wa-ERSDA = '01122006'.
wa-AENAM = 'XYZ'.

append wa to itab.

Hope this helps.

Do reward each useful answer..!

Thanks,

Tatvagna.

Message was edited by:

Tatvagna Shah

Re: Work Area

dev_parbutteea — Thu, 07 Jun 2007 04:27:38 GMT

Hi,

data: begin of t_type.

kunnr2 type bkpf-mandt,

kunnr type bkpf-mandt,

DATA: END OF t_type.

DATA:i_table type standard TABLE OF t_type,

wa_table type t_type.

wa_table-kunnr = '01'.

wa_table-kunnr2 = '06'.

APPEND wa_table to i_table.

wa_table-kunnr = '06'.

wa_table-kunnr2 = '09'.

APPEND wa_table to i_table.

LOOP AT i_table into wa_table.

WRITE:/ wa_table-kunnr2 , wa_table-kunnr.

ENDLOOP.

Regards,

Sooness

Re: Work Area

Former Member — Thu, 07 Jun 2007 04:28:52 GMT

Hi,

Work area is like a structure which contain one record at a time.

When you define an internal table the system arranges a part of memory area in two parts:

- The first one is to stores all records loaded in the table;

- The second one is to store the single record is elaborated,

So when you loop an internal table, the system picks up the record from the first area and puts it to the second one;

The part of memory to store all records is obligatory, so the system'll always create it when an internal table is defined.

The part of memory to store the single record is not necessary, you have to use it only if it needs to read the table: this one is called HEADER LINE or WORK AREA.

So you can decide to declare a table with or without an header line in according to what you need to do.

A) If you need to read the table you need to have a table with header line or work area:

- WITH HEADER LINE

DATA: BEGIN OF ITAB OCCURS 0,

FIELD1,

FIELD2,

FIELD3,

END OF ITAB.

LOOP AT ITAB.

WRITE ITAB.

ENDLOOP.

While looping the table the system automatically fills the header line;

- WITH WORK AREA:

DATA: BEGIN OF WA_ITAB,

FIELD1,

FIELD2,

FIELD3,

END OF WA_ITAB.

DATA: ITAB LIKE STANDARD TABLE OF WA_ITAB.

LOOP AT ITAB INTO WA_ITAB.

WRITE WA_ITAB.

ENDLOOP.

While looping the table the system automatically fills the work area.

So it can say the header line is a work area the system automatically creates by internal table defination.

It's the same to use the header line or work area, because you need them when you have to read the records of an internal table.

A) If you don't need to read the table, you can define a table without header line:

SELECT-OPTIONS: SO_ERDAT FOR SY-DATUM.

DATA: IT_MATERIAL LIKE MARA-MATNR OCCURS 0.

DATA: IT_MARC LIKE STANDARD TABLE OF MARC WITH HEADER LINE.

SELECT MATNR FROM MARA INTO TABLE IT_MATERIAL WHERE ERDAT IN SO_ERDAT.

IF SY-SUBRC = 0.

SELECT * FROM MARC

FOR ALL ENTRIES IN IT_MATERIAL WHERE MATNR = IT_MATERIAL.

ENDIF.

LOOP AT IT_MARC.

WRITE IT_MARC.

ENDLOOP.

In this example the internal table IT_MATERIAL is used only to select the data from MARC using the option FOR ALL ENTRIES. This options doesn't use the header line of the table, so it's useless to define a table with an heaader line.

For More Info,

http://help.sap.com/saphelp_47x200/helpdata/en/fc/eb36a1358411d1829f0000e829fbfe/content.htm

Regards,

Padmam.

Re: Work Area

seshatalpasai_madala — Thu, 07 Jun 2007 04:33:06 GMT

Hi,

Work area is Structure where as Internal table is a collection of such structure with no size limit.

So if you want to copy one row at a time from an internal table you have to use the structure like this.

DATA: struc type spfli,

itab type table of spfli.

Loop at itab into struc.

*FOr each loop pass one row's data will be copied on to the workarea.

So with in the loop you can use the data or change the data and push the data back using MODIFY satement.

endloop.

If your internal table is declared using WITH HEADERLINE addition then

itab is used as workarea and itab[] is used as the collection.

Regards,

Sesh

Re: Work Area

Former Member — Thu, 07 Jun 2007 04:37:07 GMT

Hi ,

If your issue is resolved, Please Reply/Reward/Close this thread.

Thanks,

Tatvagna.

Re: Work Area

Former Member — Thu, 07 Jun 2007 04:41:34 GMT

Thanks...

My question is been answeres by sdn guys.

regards....

Abhay Singh

Re: Work Area

Former Member — Thu, 07 Jun 2007 04:50:36 GMT

hi abhay,

work areas are useful in situations where nesting of internal tables are used.

for nesting of internal tables then that tables must be with out header lines. for such reasons we for work areas.

in general situations also internal tables with out header lines are used then we have to create a workarea which is similar to inetrnal table n use it.

any operation which we perform on internal tables is done through workarea or header line only.

for ex:

data: begin of t_type.

kunnr2 type bkpf-mandt,

kunnr type bkpf-mandt,

DATA: END OF t_type.

DATA:i_table type standard TABLE OF t_type,

wa_table type t_type.

wa_table-kunnr = '01'.

wa_table-kunnr2 = '06'.

APPEND wa_table to i_table.

wa_table-kunnr = '06'.

wa_table-kunnr2 = '09'.

APPEND wa_table to i_table.

LOOP AT i_table into wa_table.

WRITE:/ wa_table-kunnr2 , wa_table-kunnr.

ENDLOOP

if useful reward soem points.

with regards,

suresh

Re: Work Area

Former Member — Thu, 07 Jun 2007 04:52:27 GMT

we can declare internal table in two ways

1. with header line

2. with out headerline

so when ever we read data fron internal table we need to move data to header line and then read it. we cannot directly read form internal table.

so for table without header line inorder to read data we create workarea of the same structure as the internal table. then we move the data to workarea and read from it.

internal table withe headerline eg

types: begin of itab_rec,

name(10) type c,

number type i,

end of itab_rec.

data: itab type standard table of itab_rec with headerline.

or it can be declared as follow

data: itab type itab_rec occurs 0 with headerline.

so when reading data from internal table with headerline it will be as follows

loop at itab.

write: itab-name,

itab-no.

endloop

when using internal table without headerline we use workarea.

types: begin of itab_rec,

name type c,

number type i,

end of itab_rec.

data: itab type standard table of itab_rec.

wa_ itab type itab_rec.

here wa_itab is the work area. so when reading data it will be as follows

loop at itab into wa_itab.

write: wa_itab-name,

wa_itab-no.

endloop

Re: Work Area

Former Member — Thu, 07 Jun 2007 04:52:49 GMT

hi,

We can process internal table data through it's workarea only, we r not processing data directly from it's body.

If we r creating internal table with header line, in this case no need to create workarea because internal table created with implicity workarea.

in few areas we must create internal table with out header line( abap objects not supported internal table with headerline). in such situation we create workarea to process internal table data.

WORK AREA must have the same structure of INTERNAL TABLE.

*declaration.

data: begin of inernaltable occurs 0,

x type c,

y type i,

end of itab.

*initializing headerline

internaltable-x = 'd'.

internaltable-y = 34.

*storing value into internal table

append internaltable .

*reading internal table

loop at itab .

write: / internaltable-x, internaltable-y. "writes to output list

endloop.

for brief details follow these links.

http://sap.mis.cmich.edu/sap-abap/abap04/sld013.htm

http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/content.htm

http://www.sapbrain.com/TUTORIALS/TECHNICAL/internaltables_tutorial.html

regards,

sudheer.