hi experts,
I have written a code for taking debtors list for SD.I have used bkpf,bseg,bsid,bsad for this ALv report. When i run this report it is taking 4 minutes.I fear that it may take more than that in future.So what can i do for this .Bseg is a cluster table thats the reason for it .But how to access it.
regards,
mani
3 Answers
-
Former MemberPosted on Jan 21, 2008 at 07:44 AMGo to tranx SE30 here you will get Tips and Trciks for the performance tuning.
Check it carefully and check whether you can do something for improving performance of you code.
It will help you a lot and will reduce your Execution time.
If you are using READ TABLE command in your program then you can check whether you can use HASHED TABLE it will improve performance of your code a lot but it has some restrictions.
Mukesh Kumar.
Add a comment
-
Former MemberPosted on Jan 21, 2008 at 08:50 AM
Hi Mani,
I will explain some of the points to improve the performance of the report try to write code according to that ok.
SOME STEPS USED TO IMPROVE UR PERFORMANCE:
1. Avoid using SELECT...ENDSELECT... construct and use SELECT ... INTO TABLE.
2. Use WHERE clause in your SELECT statement to restrict the volume of data retrieved.
3. Design your Query to Use as much index fields as possible from left to right in your WHERE statement
4. Use FOR ALL ENTRIES in your SELECT statement to retrieve the matching records at one shot.
5. Avoid using nested SELECT statement, SELECT within LOOPs.
6. Avoid using INTO CORRESPONDING FIELDS OF TABLE. Instead use INTO TABLE.
7. Avoid using SELECT * and Select only the required fields from the table.
8. Avoid nested loops when working with large internal tables.
9. Use assign instead of into in LOOPs for table types with large work areas
10. When in doubt call transaction SE30 and use the examples and check your code
11. Whenever using READ TABLE use BINARY SEARCH addition to speed up the search. Be sure to sort the internal table before binary search. This is a general thumb rule but typically if you are sure that the data in internal table is less than 200 entries you need not do SORT and use BINARY SEARCH since this is an overhead in performance.
12. Use "CHECK" instead of IF/ENDIF whenever possible.
13. Use "CASE" instead of IF/ENDIF whenever possible.
14. Use "MOVE" with individual variable/field moves instead of "MOVE-
CORRESPONDING", creates more coding but is more effcient.
Reward points if helpful.
Kiran Kumar.G.A
Add a comment
Add a comment