Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Table View not using Indices

Former Member
0 Likes
449

Good morning,

We created a new view for a search help. This view is between a header table (DFKKKO) and Items (DFKKOP) where 99.9% of the records have a 1 to 1 relationship between the tables. The fields in the view either exist in the main index or secondary indices of the joined tables.

When we do the searches on the main tables, we get results quite fast, but we're now experiencing timeouts on the view searches which only leads me to believe it is not using the secondary indices.

Any idea what we can do additionally? We're thinking of just creating two separate search helps for each table, but the users are not happy with that solution.

Thanks

Thys

3 REPLIES 3
Read only

Former Member
0 Likes
407

could be,,,

but have you tried this view: V_FKKCO

Read only

RaymondGiuseppi
Active Contributor
0 Likes
407

- Did you [analyze the execution plan via SQL trace|http://help.sap.com/saphelp_nw70/helpdata/en/d1/801ff1454211d189710000e8322d00/frameset.htm] as the use of a join view main prevent SQL to find the correct index to use ?

- You could use a [search-help exit|http://help.sap.com/saphelp_nw04s/helpdata/en/cf/21ee52446011d189700000e8322d00/frameset.htm], in which you can susbtitute the routine that read data from database with your own logic to improve performance.

Regards,

Raymond

Read only

volker_borowski2
Active Contributor
0 Likes
407

...which only leads me to believe it is not using the secondary indices.

Hi,

do not assume! Do a trace and make sure.

Check if MANDT is in the join condition and the indexes involved.

Volker