topic Re: collect issue in Application Development and Automation Discussions

collect issue

Former Member — Thu, 31 May 2007 03:26:59 GMT

hi,

any wrong with my collect? why fkimg accumulated even vbeln is different? thanks

DATA: BEGIN OF it_tab OCCURS 0,

vbelv LIKE vbfa-vbelv,

vbeln LIKE vbfa-vbeln,

fkimg like vbrp-fkimg,

END OF it_tab.

DATA: wa_tab like it_tab.

in between data get populated in it_tab.

sort it_tab by vbelv vbeln.

clear wa_tab.

loop at it_tab into wa_tab.

collect wa_tab into it_tab.

endloop.

Re: collect issue

Former Member — Thu, 31 May 2007 03:30:19 GMT

Should be vbelv and vbeln are same then it sum the qty ,otherwise it will not.

Re: collect issue

Former Member — Thu, 31 May 2007 03:30:52 GMT

Hi,

collect the values to another internal table..instead of the same internal table..

DATA: it_collect like table of it_tab.

loop at it_tab into wa_tab.

collect wa_tab into it_collect.

endloop.

Thanks,

Naren

Re: collect issue

Former Member — Thu, 31 May 2007 03:31:29 GMT

DATA: BEGIN OF it_tab OCCURS 0,

vbelv LIKE vbfa-vbelv,

vbeln LIKE vbfa-vbeln,

fkimg like vbrp-fkimg,

END OF it_tab.

DATA: wa_tab like it_tab.

DATA: BEGIN OF it_tab1 OCCURS 0,

vbelv LIKE vbfa-vbelv,

vbeln LIKE vbfa-vbeln,

fkimg like vbrp-fkimg,

END OF it_tab1.

in between data get populated in it_tab.

sort it_tab by vbelv vbeln.

clear wa_tab.

loop at it_tab into wa_tab.

collect wa_tab into it_tab1.

endloop.

Re: collect issue

Former Member — Thu, 31 May 2007 03:32:47 GMT

Hi,

You need to collect into different table...

TYPES: BEGIN OF it_tab,

vbelv like vbfa-vbelv,

vbeln LIKE vbfa-vbeln,

fkimg like vbrp-fkimg,

END OF it_tab.

DATA: wa_tab type it_tab.

data: it_itab type standard table of it_itab,

itab2 type standard table of it_itab.

in between data get populated in it_tab.

sort it_tab by vbelv vbeln.

clear wa_tab.

loop at it_tab into wa_tab.

collect wa_tab into itab2.

endloop.

Regards,

Vidya.

Re: collect issue

Former Member — Thu, 31 May 2007 03:33:01 GMT

Only the quantity field will be accumulated. Vbeln is a character field, so it will not be accumulated.

Re: collect issue

Former Member — Thu, 31 May 2007 03:33:22 GMT

collect will sum only if vbelv and vbeln are same.....

clear workarea after collect and checkout

loop at it_tab into wa_tab.

collect wa_tab into it_tab.

clear wa_tab.

endloop.

Re: collect issue

Former Member — Thu, 31 May 2007 03:35:19 GMT

COLLECT

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.

Re: collect issue

Former Member — Thu, 26 Jul 2007 07:17:41 GMT

Strange, did noone notice that, or am I wrong ? Doesn't the program just multiply by 2 fkimg of each row in the internal table

Re: collect issue

Former Member — Thu, 26 Jul 2007 07:26:40 GMT

Collect the wa to another internal table

& it wil collect only the Qty field not char fields.