Table VAKPA. Index.

[Former Member]

Hi, all

Table vakpa.

Sales Index: Orders by Partner Function

Are anybody creating indexes for this table?

Is it correct to create indexes for sales index tables?

Denis

[eduardo_hinojosa · Accepted solution]

Hi

See Note 185530 - Performance: Customer developments in SD. It says:

"The R/3 System contains no secondary indexes to the most important SD

transaction data tables in the delivery. Instead, the R/3 System has

proprietary index tables (sales document indexes, for example the tables

VAKPA and VAPMA, matchcode tables for example M_VMVAB, M_VMVAC or matchcode

views for example M_VMVAA, M_VMVAE), which allow an efficient access."

I hope this helps you

Regards

Eduardo

[Lakshmipathi]

You can run the Report RVV05IVB as indicated in the following note which sets right the table VAKPA.  

• Note 128947 - Correction of SD document indexes with RVV05IVB

Else, have a look at the following notes:-

• Note 190793 - Performance sales summary: VAKPA
• Note 178328 - Problems due to incorrect user exits in SD

G. Lakshmipathi

[Former Member]

Hi, colleagues

Thank you.

The problem is:

Select from VAKPA is performing long time... (via standard FM)

Is someone create an index for table VAKPA?

Is it good practice?

Denis

[VishnAndr]

Hi, Denis.

There are even some notes suggested to create indexes for such tables. For instance Note 323067 - Long update times when changing sales orders