collect statement

Former Member — Tue, 02 Dec 2008 07:42:44 GMT

I have got my final internal table with "valuation class" and "Obsollete Value". Now I want to get the total

obsolete value based on valuation class. How to use Collect statement for the same.

Re: collect statement

Former Member — Tue, 02 Dec 2008 07:45:52 GMT

Hi,

Search SCN. You will get lot of threads on use of collect statement.

Here is one of those:

Regards,

Nitin.

Re: collect statement

Former Member — Tue, 02 Dec 2008 14:18:36 GMT

HI,

Collect can work use it like:

loop at <int_tab> into <wa>

collect <wa> into <int_tab>

endloop.

Edited by: Neha Shukla on Dec 2, 2008 7:51 PM

Re: collect statement

BH2408 — Tue, 02 Dec 2008 14:25:33 GMT

Hi ,

Instead of collect use the sum it will better .

Collect will sum the all non char fields...

Regards,

Bharani

Re: collect statement

Former Member — Tue, 02 Dec 2008 15:25:41 GMT

You can achieve like this.

data: lf_tab1 type <same as itab>,

lw_tab1 type <line of itab>.

Sort itab by class.

loop at itab.

at end of class.

sum.

lw_tab1-value = itab-value.

lw_tab1-class = itab-class.

append lw_tab1 to itab1.

endat.

endloop.

Regards

Raj

Re: collect statement

Former Member — Wed, 03 Dec 2008 06:04:09 GMT

sort itab by aufnr matnr.

loop at itab.

at end of matnr.

sum.

move-corresponding itab to t_charg.

collect t_charg.

endat.

endloop.

Re: collect statement

Former Member — Wed, 03 Dec 2008 06:45:40 GMT

hi,

actually , next time when you come across the key word issue, what you can do is check the key word help documents:

write the key word in the abap editor, then place the cursor on it and press F1.

Syntax

COLLECT wa INTO itab [result].

Effect

This statement inserts the contents of a work area wa either as single row into an internal table itab or adds the values of its numeric components to the corresponding values of existing rows with the same key. As of Release 6.10, you can use result to set a reference to the inserted or changed row in the form of a field symbol or data reference.

Prerequisite for the use of this statement is that wa is compatible with the row type of itab and all components that are not part of the table key must have a numeric data type (i, p, f).

In standard tables that are only filled using COLLECT, the entry is determined by a temporarily created hash administration. The workload is independent of the number of entries in the table. The hash administration is temporary and is generally invalidated when the table is accessed for changing. If further COLLECT statements are entered after an invalidation, a linear search of all table rows is performed. The workload for this search increases in a linear fashion in relation to the number of entries.

In sorted tables, the entry is determined using a binary search. The workload has a logarithmic relationship to the number of entries in the table.

In hashed tables, the entry is determined using the hash administration of the table and is always independent of the number of table entries.

If no line is found with an identical key, a row is inserted as described below, and filled with the content of wa:

In standard tables the line is appended.

In sorted tables, the new line is inserted in the sort sequence of the internal table according to its key values, and the table index of subsequent rows is increased by 1.

In hashed tables, the new row is inserted into the internal table by the hash administration, according to its key values.

If the internal table already contains one or more rows with an identical key, those values of the components of work area wa that are not part of the key, are added to the corresponding components of the uppermost existing row (in the case of index tables, this is the row with the lowest table index).

The COLLECT statement sets sy-tabix to the table index of the inserted or existing row, in the case of standard tables and sorted tables, and to the value 0 in the case of hashed tables.

Outside of classes, you can omit wa INTO if the internal table has an identically-named header line itab. The statement then implicitly uses the header line as the work area.

COLLECT should only be used if you want to create an internal table that is genuinely unique or compressed. In this case, COLLECT can greatly benefit performance. If uniqueness or compression are not required, or the uniqueness is guaranteed for other reasons, the INSERT statement should be used instead.

The use of COLLECT for standard tables is obsolete. COLLECT should primarily be used for hashed tables, as these have a unique table key and a stable hash administration.

If a standard table is filled using COLLECT, it should not be edited using any other statement with the exception of MODIFY. If the latter is used with the addition TRANSPORTING, you must ensure that no key fields are changed. This is the only way to guarantee that the table entries are always unique and compressed, and that the COLLECT statement functions correctly and benefits performance. The function module ABL_TABLE_HASH_STATE can be used to check whether a standard table is suitable for editing using COLLECT.

Example

Compressed insertion of data from the database table sflight into the internal table seats_tab. The rows in which the key components carrid and connid are identical are compressed by adding the number of occupied seats to the numeric component seatsocc.


DATA: BEGIN OF seats, 
        carrid   TYPE sflight-carrid, 
        connid   TYPE sflight-connid, 
        seatsocc TYPE sflight-seatsocc, 
      END OF seats. 

DATA seats_tab LIKE HASHED TABLE OF seats 
               WITH UNIQUE KEY carrid connid. 

SELECT carrid connid seatsocc 
       FROM sflight 
       INTO seats. 
  COLLECT seats INTO seats_tab. 
ENDSELECT.

topic collect statement in Application Development and Automation Discussions

collect statement

Re: collect statement

Re: collect statement

Re: collect statement

Re: collect statement

Re: collect statement

Re: collect statement