secondary index on CE4XXXX and CE3XXXX tables

[Former Member]

Hi ,

KE30 transaction performance is very slow.

Some variant reports in KE30 when the load is high it is getting timeout in foreground.

Sequential read is showing on CE4XXXX table.

We are using following selection criterion for the variant.

company code

period/year from

period/year to

currency type

We have already have the secondary index for the table CE4DOC1 with fields MANDT, AKTBO , KNDNR ,ARTNR ,BUKRS ,WERKS ,VTWEG.

What would be the ideal secondary index for the above selection criterion.

further increasing the performance can we create the secondary index for CE3DOC1.what would be the ideal fields for secondary index.

Regards,

ARNS

[Former Member · Accepted solution]

I recommend the usual technical approach if your CO-PA experts are currently on leave or don't have a good answer: I.e. do a SQL trace via ST05 and check the execution plan for the slow SQL statements. You'll see which fields are used for accessing the table and get an idea if an appropriate index exists or if you possibly should define a new one (with the usual caveats mentioned tons of times in the forums that you should know what you're doing when defining a new index).

Now, if you have defined a new suitable secondary index, but the database doesn't pick it up, then outdated or missing database statistics might be your problem (your SQL trace will show that clearly).

In general I also recommend taking a look at OSS. A good starting point might be the (old) [OSS note 35288 - Profitability Analysis: Technical Documentation|https://service.sap.com/sap/support/notes/35288] and [140880 - Long access times to table CE4xxxx|https://service.sap.com/sap/support/notes/140880].