Answer / raghunath

In order to avoid nested select statements we can go
for "FOR ALL ENTRIES".First fetch values from database
table to internal table and only for the values in the
internal table we can fetch values from other database
table based on conditions in the where clause.

it is mandetory that we have to declare allthe primary keys
in either select Stmt or in where condition. orelse
duplicate records will not get selected.

Answer / arasumani

All abap programers and most of the dba's that support abap
programmers are familiar with the abap clause "for all
entries". Most of the web pages I visited recently, discuss
3 major drawbacks of the "for all entries" clause:

1. duplicate rows are automatically removed
2. if the itab used in the clause is empty , all the rows in
the source table will be selected .
3. performance degradation when using the clause on big tables.

In this post I'd like to shed some light on the third issue.
Specifically i'll discuss the use of the "for all entries"
clause as a means to join tables in the abap code instead of
in db2.

Say for example you have the following abap code:
Select * from mara
For all entries in itab
Where matnr = itab-matnr.

If the actual source of the material list (represented here
by itab) is actually another database table, like:
select matnr from mseg
into corresponding fields of table itab
where ….

Then you could have used one sql statement that joins both
tables.
Select t1.*
From mara t1, mseg t2
Where t1.matnr = t2.matnr
And T2…..

So what are the drawbacks of using the "for all entires"
instead of a join ?

At run time , in order to fulfill the "for all entries "
request, the abap engine will generate several sql
statements (for detailed information on this refer to note
48230). Regardless of which method the engine uses (union
all, "or" or "in" predicates) If the itab is bigger then a
few records, the abap engine will break the itab into parts,
and rerun an sql statement several times in a loop. This
rerun of the same sql statement , each time with different
host values, is a source of resource waste because it may
lead to re-reading of data pages.

returing to the above example , lets say that our itab
contains 500 records and that the abap engine will be forced
to run the following sql statement 50 times with a list of
10 values each time.
Select * from mara
Where matnr in ( ...)

Db2 will be able to perform this sql statement cheaply all
50 times, using one of sap standard indexes that contain the
matnr column. But in actuality, if you consider the wider
picture (all 50 executions of the statement), you will see
that some of the data pages, especially the root and
middle-tire index pages have been re-read each execution.

Even though db2 has mechanisms like buffer pools and
sequential detection to try to minimize the i/o cost of such
cases, those mechanisms can only minimize the actual i/o
operations , not the cpu cost of re-reading them once they
are in memory. Had you coded the join, db2 would have known
that you actually need 500 rows from mara, it would have
been able to use other access methods, and potentially
consume less getpages i/o and cpu.

In other words , when you use the "for all entries " clause
instead of coding a join , you are depriving the database of
important information needed to select the best access path
for your application. Moreover, you are depriving your DBA
of the same vital information. When the DBA monitors & tunes
the system, he (or she) is less likely to recognize this
kind of resource waste. The DBA will see a simple statement
that uses an index , he is less likely to realize that this
statement is executed in a loop unnecessarily.

In conclusion I suggest to "think twice" before using the
"for all entries" clause and to evaluate the use of database
views as a means to:
a. simplify sql
b. simplify abap code
c. get around open sql limitations.

Answer / sunil panghal

IT IS THE ANOTHER TYPE OF JOINING TECHNIQULE WHARE WE CAN
JOIN MASTER TO HEADER AND HEADER TO ITEM AND SO ON.
INNER JOIN FOR ALL ENTRIES PROVIDES HIGER PERFORMANCE IN
TERMS OF PROCESSING SPEED

Answer / rajesh

For all entry is used to increase the performance at the
time of selecting data from data base, because once
selecting data from the data base and finally put data into
internal table

Answer / sreehari patnaik

"for all entries" is used when a developer wants to join a
transparent table with a cluster table so as to avoid the
nesting of select statements. It increases the performance
of the program.

Answer / naresh

FOR ALL ENTRIES IN IS NOTHING BUT INNER JOINS, INNER JOINS IS EXTRACTING A DATA FROM TWO DEPEND TABLES( PRIMARY AND FOREIGN) BUT IN FOR ALL ENTRIES IN EXTRACTING FROM MORE THAN TWO TABLES . MAIN ADVANTAGE OF FOR ALL ENTRIES IN IS IMPROVING PERFORMANCE OF SYSTEM (HOW)..
WE ARE SUPPURATION THE TABLES, AND USING THE INNER TABLE WITH REFERENCE OF FIELD STRINGS TYPE...AND CREATING A FINAL TABLE, IT CONTAINING A TOTAL FIELDS WHICH ARE YOU SELECTED IN
DEPENDENT TABLES ...

Answer / goutham

One of the major disadvantage of using inner Join on the
database table directly will bypass the buffer in the Appl
layer instead it hits the database directly,which is
performance costly operation.

Answer / poorna

to avoid duplaction of records

Answer / sunil

For ALL Entries is used to join two different tables. By
tables i mean the internal tables. For All Entries has an
internal where condition in it. which makes the selection
process much faster. But still it is always better to use
inner joins when you have to join two database tables.

Explain the SmartForm with an Example?

5 Answers   HP,

Polindrome Program for string and Polindrome Program for numbers in ABAP

1 Answers   IBM,

what is the standard program to check the consistency of the partner profiles?

2 Answers  

What specific statements do you using when writing a drill down report?

1 Answers  

what is the difference between invoice and proforma invoice?

14 Answers  

difference between the workarea and headerline.plz tell me the answer

6 Answers  

Can we develop program without logical database for hr module data retrieval

2 Answers   TCS,

i want to populate 10 fields in smartforms..uptil 9th it is taking but 10th one is not populating?what might be the reason?

2 Answers   Siemens,

What is the tcode to create indexes?

0 Answers  

When is the top-of-page event triggered? : abap data dictionary

0 Answers  

What are logical databases? What are the advantages of logical databases?

0 Answers  

what is 'F4' functionality?

6 Answers