Hi Diya,
in the st05 trace, mark the row and click "explain".
The trick now, is to find out, which indexe, the SQL statement uses.
I use "text explain".
There you have to look for the "where" restrictions in this statement.
The clustered Index of table VBFA is MANDT, VBELV, POSNV, VBELN, POSNN, VBTYP_N.
To get an fast return, the statement should use the columns in the index, in this same order.
e.g.
if the where statment is kind of:
WHERE "MANDT" = @P0 AND "VBELV" = @P1 AND "VBELN" = @P3
the SQL optimizer can use MANDT and VBELV, because they are on the first and second position.
The third value VBELN, cannot be used by the optimizer to narrow the output, because the next column is POSNV.
In the "text explain" you will find a row like this:
SELECT
|--Clustered Index Seek(OBJECT:([SID].[xxx].[VBFA].[VBFA~0]), SEEK:([VBFA].
Here you see, which index the optimizer is using. Here it is VBFA~0.
The solution for my example above may be to create a new index with the following columns in this order:
VBFA~Z01: MANDT, VBELV, VBELN.
But, do not create indexes whithout searching for notes, regarding slow statments on VBFA. There are a lot!
You say it is in the standard transaction VA01. I think there is no own coding?
Check it, which ABAP Statement it is.
In ST05, mark the row, and press Button "ABAP Coding" to find out, which programm it is. If it is a standard SAP Programm, also try to search for notes reardging this problem.
Kind regards
Manuel.
Edited by: Manuel Herr on Apr 11, 2011 9:42 AM
also use this!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.