Dear experts,
I am preparing custom SAP code for HANA and found the following:
1. Not only pool and cluster tables are affected, but also transparent ones (We have a customer on HANA who reported such cases).
2. SCI Code Inspector cannot find such code in all cases:
Currently there is a check: "Search problematic statements for result of SELECT/OPEN CURSOR without ORDER BY",
but! It works only if you perform specific operations after "SELECT .. INTO TABLE", for example:
* READ TABLE itab ... BINARY SEARCH
* DELETE ADJECENT DUPLICATES FROM itab
and etc. (they are all mentioned in the description of SCI Inspector check).
So if you just have a select into table without order by, but no specific operations mentioned in description if SCI check,
you code is not optimized for HANA and you are not aware of it. This select will not appear in Code Inspector result list.
For example, if we show documents list using just a select from table and immediately sending results to ALV, then user will see unsorted documents list.
Please advise how could such situations be found