Performance Issue..

[Former Member]

Hi all,

Does the declaration of ranges using an internal table.

eg : DATA: BEGIN OF r_saknr OCCURS 0,

sign TYPE c LENGTH 1,

option TYPE c LENGTH 2,

low LIKE ska1-saknr,

high LIKE ska1-saknr,

END OF r_saknr .

Affect the performance..

Or is the below definition faster...

ranges: r_saknr for ska1-saknr.

Can u please help me in deciding this..It is urgent.

Thanks and Regards,

Seema

[Former Member]

U can use the ranges directly

[dani_mn]

<b>ranges: r_saknr for ska1-saknr.</b>

this is better. because you can use 'IN' operator with 'RANGES' declaration not with internal table.

Regards,

[Former Member]

Hi,

Both are same..Ranges will internally declare the internal table like the one you have declared..

I believe performance will not be affected by this..

Thanks,

Naren

[Former Member]

range is better option but i don't think it effect on performance of ur code....

use that one which u feel easy....

[Former Member]

try to USE option = 'BT' over option = 'EQ'.

like

1.matnr range = 1 - 10 which gives good performance than

2.matnr = 1

= 2.....etc.

u have to reduce the DB cost.

check DBcost in ST05.

Regards

Prabhu