Acessing MSEG Table

[Former Member]

hi,

we have a report which in which it display how much material is recived till date and how much is issued till date, that report is made on MSEG table which makes the report very slow, is there any way out to get the report from any other tables instead of the using MSGE or MKPF tables, i want to optimise this report as it tales lots of resources on the server due to which the server performance goes down.

thanx

abhishek suppal

[Former Member]

Hi, As I know the table like MSEG BSEG is link to a cluster table, and the content of it is collected by serveral physical table.

But before select data from other source, there is still thing you can do to upgrade the performance.

Reduce the access time to BSEG as little as possible.

Check the select statement of SELECT BSEG, is there any optimize you can do?

If the report make you server performance go down, try to move it to run in background, if possible.

Hope it will be helpful.

[christian_wohlfahrt]

Hi,

you might start with purchase / sales orders - but I don't see how this should reduce number of hits and being faster.

So try to use indices for MKPF / MSEG selection. There is an index BUD on MKPF for posting date, be sure to use this. If you have some different document types and your report is only interested in one at a time, create a additional index including BLART.

Access on MSEG will then be with primary key. If you are only interested in one (or some view) materials, start with MSEG might be possible, too. But hits for one material without date restriction might be higher then just one day - have a look.

If a join doesn't use indices (or in a wrong order), then try to update database statistics first (DB20). If this is no help, make two separate selects, second one with 'for all entries'.

And of course: select only needed columns (no select *), use as much where conditions as possible...

Regards,

Christian

[Former Member]

- If you need to see PO history about entries (101-102), you better use table EKBE (than MSEG)

- If you need to see Order history about entries (101-102) and consumption (261-262), you better use table AUFM (than MSEG)

Hope it helps,

JG