"Range Table" and ABAP dump

Range statements have a limitation because the way they are converted into native SQL.

Example of a problematic Range table used in a IN clause of a SELECT statement.

* Fetching cnum from PA0185 table
SELECT pernr icnum FROM pa0185
INTO TABLE it_id
WHERE icnum IN l_range_cnum.

If internal table L_RANGE_CNUM contains more than 10,000 entries, it will usually result in ABAP dump.
The above statement will get converted into a native SQL like below.

SELECT pernr icnum FROM pa0185
INTO TABLE it_id
WHERE icnum eq cnum1 OR
icnum eq cnum2 OR
icnum eq cnum3 OR
icnum eq cnum4 OR ........

When u have more entries in the range table this select statement grows too huge resulting in a dump.

Solution: Solution is to use "For All Entries" like below.

* Fetching cnum from PA0185 table
SELECT pernr icnum FROM pa0185
INTO TABLE it_id
for all entries in l_cnum WHERE icnum = l_cnum-cnum.

This solution will get converted into several small SELECT statements and will not result in a dump.