topic Re: collect append in Application Development and Automation Discussions

collect append

Former Member — Mon, 25 Feb 2008 08:20:50 GMT

hi frds plz give meresponse to this question

Difference between COLLECT & APPEND

give me my mail id

sudhakarbabu786@rediffmail.com

Re: collect append

Former Member — Mon, 25 Feb 2008 08:26:30 GMT

Hi,

APPEND :append statement will just append a new row into the table

collect: collect statement serve dual purpose . if the key field is already present in the table then it will add the integer field of new record to the exist record otherwise it will create a new record

Re: collect append

Former Member — Mon, 25 Feb 2008 08:54:06 GMT

Both statement used to populate data in internal table whan u use append statement then a new record has been appended to internal table and when u use collect statement then program will check key for character fields and for same character fields it will add all numeric fields.

ex:

APPEND line_spec TO itab SORTED BY comp result.

Addition:

... SORTED BY comp

Effect

This statement appends one or more rows line_spec to an internal index table itab. If itab is a standard table, you can use SORTED BY to sort the table in a specified way. Use result when appending a single row as of release 6.10 to set a reference to the appended row in the form of a field symbol or a data reference.

For the individual table types, appending is done as follows:

To standard tables, rows are appended directly and without checking the content of the internal table.

To sorted tables, rows are appended only if they correspond to the sort sequence and do not create duplicate entries with unique table key. Otherwise, an untreatable exception is triggered.

To hashed tables, no rows can be appended.

The APPEND statement sets sy-tabix to the table index of the last appended row.

Addition

... SORTED BY comp

Effect

This addition is allowed only if you specify a workarea wa and if you use a standard table, where wa must be compatible to the row type of the table. You can specify component comp as shown in section Specifying Components, however, you can access only one single component and no attributes of classes using the object component selector.

The statement is executed in two steps:

Starting at the last row, the table is searched for a row, in which the value of component comp is greater than or equal to the value of component comp of wa. If such a row exists, the workarea wa is included after this row. If no such row exists, the workarea wa is included before the first row. The table index of all rows following the included rows increases by one.

If the number of rows before the statement is executed is greater than or equal to the number specified in the definition of the internal table in the INITIAL SIZE addition, the newly-created last row is deleted.

Note

When using only the statement APPEND with addition SORTED BY to fill an internal table, this rule results in an internal table that contains no more than the number of rows specified in its definition after INITIAL SIZE and that is sorted in descending order by component comp (ranking).

The SORT statement should usually be used instead of APPEND SORTED BY.

Example

Creating a ranking of the three flights of a connection showing the most free seats.

PARAMETERS: p_carrid TYPE sflight-carrid,

p_connid TYPE sflight-connid.

DATA: BEGIN OF seats,

fldate TYPE sflight-fldate,

seatsocc TYPE sflight-seatsocc,

seatsmax TYPE sflight-seatsmax,

seatsfree TYPE sflight-seatsocc,

END OF seats.

DATA seats_tab LIKE STANDARD TABLE OF seats

INITIAL SIZE 3.

SELECT fldate seatsocc seatsmax

FROM sflight

INTO seats

WHERE carrid = p_carrid AND

connid = p_connid.

seats-seatsfree = seats-seatsmax - seats-seatsocc.

APPEND seats TO seats_tab SORTED BY seatsfree.

ENDSELECT.

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.

reward points if helpfull

Re: collect append

Former Member — Mon, 25 Feb 2008 09:17:25 GMT

COLLECT: When the line is inserted, the system checks whether there is already a table entry that matches the key. If there is no corresponding entry already in the table, the COLLECT statement has the same effect as inserting the new line. If an entry with the same key already exists, the COLLECT statement does not append a new line, but adds the contents of the numeric fields in the work area to the contents of the numeric fields in the existing entry.

APPEND : inserting the new line

Re: collect append

Former Member — Mon, 25 Feb 2008 09:18:58 GMT

Hi,

Append:This statement appends one or more rows line_spec to an internal index table itab.

Collect: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.

regards,

kavitha.

Re: collect append

Former Member — Mon, 25 Feb 2008 09:23:42 GMT

collect----- checks whether it is there or not. if there adds integer, packed, float otherwise remove

append-----just adding

Re: collect append

Former Member — Mon, 25 Feb 2008 10:03:48 GMT

Hi,

Append statement only add that particular record it the end it is not going to check whether that record exists or not? But collect statement going to check the record exists or not? If it exists then it will check the all character feilds . If they are same then it will add all the numeric feilds. Otherwise it works same as append.

Thanks

Sarada

Re: collect append

Former Member — Mon, 25 Feb 2008 10:13:05 GMT

COLLECT

Aggregates lines and then adds them to an internal table.

Syntax

COLLECT <line> INTO <itab>

[ASSIGNING <FS> | REFERENCE INTO <dref>].

The system checks whether there is already a table entry that matches the key. If there is no corresponding entry already in the table, the COLLECT statement has the same effect as INSERT. If an entry with the same key already exists, the COLLECT statement does not append a new line, but adds the contents of the numeric fields in the work area <line> to the contents of the fields in the existing entry. If you use ASSIGNING or INTO REFERENCE, field symbol <FS> refers to the inserted line or the relevant data reference is stored in <dref> after the statement.

APPEND

Appends a line or multiple lines to the end of an index table.

Syntax

APPEND <line>|LINES OF <jtab> TO <itab>

[ASSIGNING <FS> | REFERENCE INTO <dref>].

A line <line> or multiple lines of an internal table <jtab> are appended to index table <itab>. If you use ASSIGNING or INTO REFERENCE, field symbol <FS> refers to the appended line or the relevant data reference is stored in <dref> after the statement.

Re: collect append

Former Member — Mon, 25 Feb 2008 10:36:53 GMT

Hi,

APPEND

Appends a line or multiple lines to the end of an index table.

Syntax

APPEND <line>|LINES OF <jtab> TO <itab>

[ASSIGNING <FS> | REFERENCE INTO <dref>].

COLLECT

Aggregates lines and then adds them to an internal table.

Syntax

COLLECT <line> INTO <itab>

[ASSIGNING <FS> | REFERENCE INTO <dref>].

Regards,

Priya.

Re: collect append

Former Member — Mon, 25 Feb 2008 10:49:51 GMT

COLLECT wa INTO itab [result].

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

If the internal table does not already contain a row with an identical key, the COLLECT statement has the same effect as the following form of the INSERT statement:

APPEND

For the individual table types, appending is done as follows:

To standard tables, rows are appended directly and without checking the content of the internal table.

To sorted tables, rows are appended only if they correspond to the sort sequence and do not create duplicate entries with unique table key. Otherwise, an untreatable exception is triggered.

To hashed tables, no rows can be appended.

The APPEND statement sets sy-tabix to the table index of the last appended row.

Re: collect append

Former Member — Tue, 26 Feb 2008 04:45:48 GMT

both collect and append are used to move the date from work area to body.

but the difference is.

if we use the append,

records move from work area to body sequentially.

123456789........like this.

if we use the collect,

it avoids the duplicates.

it adds the duplicate records.

for ex;

1 300

1 400

if we use collect a the time it save it as

1 700

Re: collect append

Former Member — Tue, 26 Feb 2008 08:45:34 GMT

COLLECT is to create totals within an internal table.it compares non-numeric fields in the header line aganist the non-numeric fields in the body, then the nemeric fields are added when the exact match found.if they are not matched then it just insert that record into body.

APPEND is to push the record from the header line to the bottom of body of an internal table.

Re: collect append

Former Member — Tue, 26 Feb 2008 09:44:48 GMT

Append will insert line in internal table at last by default.

Collect will create key by combining all charactrer type fields in that internal table. If the same key values are available in that internal table, it will add values of corresponding non character type fields. otherwise it will append that row in internal table.

Re: collect append

Former Member — Tue, 26 Feb 2008 10:09:49 GMT

Append :- it appends the record seguently in internal table

Insert :- inserts s new record can be inserted either before or after existing record in internal table

Collect :- it can avoid all duplicat records in internal lable body

Re: collect append

Former Member — Tue, 26 Feb 2008 10:17:34 GMT

Collect plays major role when we in reports.

append and collect plays same when there is no numeric fields in the internal table.

if any non-numeric fields are there in the internal table then there is difference between collect and append.