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.
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.
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
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
Then you could have used one sql statement that joins both
From mara t1, mseg t2
Where t1.matnr = t2.matnr
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.
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 ...
1.Have you created custom table? Do you always use existing
data elements and domains or create new ones? whatis the
transaction code to see existing data elements and domains?
2.Performance wise inner join is better or For..ALL
3.Where will you place data element domain and field
together in an ABAP Program?
4.How will you pass the data/programs from one system to
5.How will you print TOP-OF-PAGE in ALV Report?How will you
make ALV Report interactive?
6.In Interactive report if i try to go to 20th list and my
report has only 19 list what will be output?
7.Have you worked on Function Modules?How will you raise
EXCEPTIONS in function modules?
8.Why you say Call transaction is faster than session?
9.How the business is carried out in your organisation?How
did you get specs for coding ? Explain me complete step by
step scenario from client deciding to switch SAP to your
role of coding and after coding explain me how the object
reaches back to client? Dont explain me about 5 phases like
Business blueprint,realization etc?
10.To find User exit in SD module we can use development
class VMOD and find out related exits. Which development
class you use for MM FICO and PP Modules?