This removing of duplicate would create data inconsistencies, if you don’t have key fields in your selection fields part of your SELECT query. Finally, DB would remove the duplicates and give you the result set. If you don’t pass unique values, DB would reselect the records for each duplicate values. To improve the performance, you would definitely want to have unique values in the ITAB which you are using as FOR ALL ENTIRES. A silly mistake! On bright side, you are now Excel expert 🙂 Why you need Key fields If this program was not developed by you, I can imagine how much you hate that person when you realized the root cause. Next hurdle would be to explain to your Functional counterpart and your users why it was not working. To fix this you would than realize that you need to include more key fields into the SELECT. By the time, you are already expert in Excel. After few rounds of VLOOKUP and Compare in excel, you suddenly realize that FOR ALL ENTRIES is dropping few entries. You compare them and you would notice few entries are definitely missing. So you download the data from both of the ITAB – Your program and Std transaction. When you debug the std transaction and reach to SELECT, you would think, this is the same query I have. On the other hand the standard transaction would get you all the entries would a different total. In that case, system would only bring one entry instead of the multiple. The issue will happen when you have same posting for same GL using same CC in different periods. Since this query doesn’t have all the key fields, you would run into the issues when you will try to reconcile it with some of the standard transaction FAGLB03.

Mediamonkey 5 initial key field sort