Performance - table LTAP

[Former Member]

SAP 4.7 6.20 ORACLE 10G WINDOWS SERVER 2008

I have several selects to table LTAB which seem to be very slow.

The clause of this select is : where MANDT = A0 and LGNUM = A1 and TANUM in (A2, A3, A4, A5, A6).

In sm66 it's in sequential read, and in st04 it's using INDEX RANGE SCAN LTAP~M which is an SAP index.

This index is by : MANDT, LGNUM, PQUIT, MATNR.

And the slow programs are standard.

But the keys of the table are : MANDT, LGNUM, TANUM, TAPOS, so I don't understand why it's using the index instead of reading by the own table.

Sometimes I see in sm66 4, 5 programs accessing this table with this select at the same time, and it takes some time for them to disappear.

And I don't understand why.

Does anybody have a clue ?

Eduardo

[eduardo_hinojosa]

Hi,

SAP Note 191492 - Performance: Customer developments in MM/WM has a question about this table.

If the problem is in an standard report, search notes, surely it's an error or performance note. It's sure if you have applied recently support-packages or you are using this functionality since a recent time. If you don't find it, send a message to SAP. Check Note 67739 - Priorities of problem messages.

Regards,

Eduardo

[Rui_Dantas]

I would start by making sure that the statistcs are up to date. The table key should definitely be selected by the optimizer for that access.