Performance when accessing table VEPO

Former Member — Fri, 02 Mar 2012 15:17:13 GMT

Processing goods issue on deliveries using transaction VL06G is running slow.

A trace in ST05 shows access to table VEPO at the top. It is consuming 20% of the processing time. The code is reading the handling unit item table using a delivery number. There is no index on delivery number, so it does a table scan.

It looks like standard SAP code. Anyone have access to an ECC 6.0 system that can compare?

I read that there was a secondary index on VEPO-VBELN up to version 4.6C. Anyone know more details?

Add an index? Enter an OSS note?

Class: /ISDFPS/CL_PM_RELOCATION

Method: UI_UPDATE_RELOC_DATA

ECC 6.0

    select venum vepos from vepo                        "#EC CI_NOFIELD
                       into table lt_vepo
                       where vbeln = <mkpf>-xblnr.

Re: Performance when accessing table VEPO

eduardo_hinojosa — Fri, 02 Mar 2012 16:04:47 GMT

I'd create a secondary index after speak with a Basis Consultant, because depending of the size of VEPO you will increase its size. But if you need to do this select is evident that you need an index.

Futhermore, see these notes

SAP Note 189523 - Performance in deliv.process: Advance clarification

SAP Note 192423 - Delivery Processing Performance: Consulting

Regards

Eduardo

topic Re: Performance when accessing table VEPO in Application Development and Automation Discussions

Performance when accessing table VEPO

Re: Performance when accessing table VEPO