topic Re: in prob -need solution...... in Application Development and Automation Discussions

in prob -need solution......

Former Member — Tue, 05 Dec 2006 06:50:42 GMT

Anybody couls tell me what the exact meaning of this syntax. here for all entrien in t_kna1 mean what?. confuse a bit....plz help me....

SELECT KUNNR VKORG PARVW FROM KNVP INTO TABLE T_KNVP

FOR ALL ENTRIES IN T_KNA1

WHERE KUNNR = T_KNA1-KUNNR.

Re: in prob -need solution......

Former Member — Tue, 05 Dec 2006 06:55:17 GMT

For each entry T_KNA1 internal tables it gets the data from KNVP and dumps that into T_KNVP tables.

This is used to avoid firing select statements inside a internal table loop.

Regards,

Ravi

Note - Please mark all the helpful answers

Re: in prob -need solution......

Former Member — Tue, 05 Dec 2006 06:56:28 GMT

Hi Abhay

Internal Table: T_KNA1 holds the records of all customers.

The statement is to extract the Customer Partners from KNVP for each of the customer in internal table T_KNA1.

Kind Regards

Eswar

Re: in prob -need solution......

jayanthi_jayaraman — Tue, 05 Dec 2006 07:01:32 GMT

Hi,

This code will fetch the values of the fields KUNNR,VKORG,PARVW from database table KNVP and then places the records in internal table T_KNVP.But the records from KNVP are selected if there exists a corresponding entry in internal table T_KNA1 for KUNNR value.The specified select statement should be in if sy-subrc eq 0.

Kindly reward points by clikcing the star on the left fo reply,if it helps.

Re: in prob -need solution......

Former Member — Tue, 05 Dec 2006 07:17:40 GMT

The basic reason for using 'FOR ALL ENTRIES' is to avoid a full scan of database search on the table KNVP which would cause a performance issue.

For the first database search from KNA1 we are making a full scan of the database table. And by using the 'FOR ALL ENTRIES' we are narrowing our database search to only those found satisfying in the table T_KNA1.

Before firing a select with the construct 'FOR ALL ENTRIES IN T_KAN1' try checking if the the table T_KNA1 is not initial, otherwise it would result in all the customer numbers from KNVP getting selected which would be a performace issueand also illogical at times. Please note all these are done to make the search more efficient and increase the performance.

Note: Please give a point if you are convinced

Re: in prob -need solution......

Former Member — Wed, 06 Dec 2006 13:46:54 GMT

SELECT KUNNR VKORG PARVW FROM KNVP INTO TABLE T_KNVP

FOR ALL ENTRIES IN T_KNA1

WHERE KUNNR = T_KNA1-KUNNR.

Let, before this statement t_kna1 have some data of 100 records of kunnr (1 to 100).

This select statement reads the KUNNR VKORG PARVW fields from the table knvp into t_knvp for all the entries in the table t_kna1(ie, from record 1 to 100).

read it carefully.

Thanx.

Re: in prob -need solution......

Former Member — Thu, 07 Dec 2006 10:22:40 GMT

Hi Abhay Singh

Syntax

... FOR ALL ENTRIES IN itab WHERE ... col operator itab-comp ...

Effect

If the addition FOR ALL ENTRIES is specified before the language element WHERE, then the components comp of the internal table itab can be used as operands when comparing with relational operators.

The internal table itab must have a structured line type and the component comp must be compatible with the column col.

The logical expression sql_cond of the WHERE condition can comprise various logical expressions by using AND and OR. However, if FOR ALL ENTRIES is specified, there must be at least one Comparison with a column of the internal table itab, which can be specified either statistically or dynamically (Release 6.40 and higher). In a statement with a SELECTstatement with FOR ALL ENTRIES, the addition ORDER BY can only be used with the addition PRIMARY KEY.

The whole logical expression sql_cond is evaluated for each individual line of the internal table itab. The resulting set of the SELECT statement is the union of the resulting sets from the individual evaluations. Duplicate lines are automatically removed from the resulting set. If the internal table itab is empty, the whole WHERE statement is ignored and all lines in the database are put in the resulting set.

Notes

In Release 6.10 and higher, the same internal table can be specified after FOR ALL ENTRIES and after INTO.

The addition FOR ALL ENTRIES is only possible before WHERE conditions of the SELECT statement.

Example

Exporting all flight data for a specified departure city. The relevant airlines and flight numbers are first put in an internal table entry_tab, which is evaluated in the WHERE condition of the subsquent SELECT statement.

PARAMETERS p_city TYPE spfli-cityfrom.

TYPES: BEGIN OF entry_tab_type,

carrid TYPE spfli-carrid,

connid TYPE spfli-connid,

END OF entry_tab_type.

DATA: entry_tab TYPE TABLE OF entry_tab_type,

sflight_tab TYPE SORTED TABLE OF sflight

WITH UNIQUE KEY carrid connid fldate.

SELECT carrid connid

FROM spfli

INTO CORRESPONDING FIELDS OF TABLE entry_tab

WHERE cityfrom = p_city.

SELECT carrid connid fldate

FROM sflight

INTO CORRESPONDING FIELDS OF TABLE sflight_tab

FOR ALL ENTRIES IN entry_tab

WHERE carrid = entry_tab-carrid AND

connid = entry_tab-connid.