Learn How to Avoid Lackluster System Performance When Using the 'FOR ALL ENTRIES IN' Clause: An ABAP Developer's Guide

  • by David F. Jenkins, Independent Consultant
  • July 15, 2001
All ABAP programmers are familiar with the Open SQL SELECT … FOR ALL ENTRIES IN construct frequently used to access data from a database. While the use of FOR ALL ENTRIES IN ("FAEI") can ease your programming load, it can also cause immense performance problems if not wisely used. This article goes far beyond standard SAP documentation to help you avoid such problems — it reveals how FAEI really works and techniques for minimizing its performance drain.

David F. Jenkins

David F. Jenkins has been involved with IT since 1957, when he started in the business as a punched card machine operator. Dave worked for a Houston bank for nine years before receiving his B.S. in Math from the University of Houston. He then joined IBM, where he worked in various marketing support positions, supporting contractors at the NASA Johnson Space Center. While at IBM, Dave spent a year teaching at New Mexico Highlands University as part of IBM’s Faculty Loan Program. Since leaving IBM, Dave has received a master’s in Management, Computing and Systems from Houston Baptist University, and has finished coursework for a Ph.D. in Management Information Systems at the University of Houston. Since 1996, Dave has been a consultant specializing in ABAP development — his most recent client assignment has been at ChevronTexaco, supporting their installation of SAP IS-Oil Production and Revenue Accounting. Dave is married with four children, and two beautiful grandchildren. He and his wife Joy live in the country 80 miles west of Houston, where they enjoy the wide-open spaces and fresh air, and their dog, cats, fish, and especially their colony of purple martins.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.