F4 on Variable Screen for a DataStore Object Produces Long Run Time

Question

We experiencing a long run time in returning values when we select F4 for the Variable 0COMP_CODE when we process query for a DataStore.  Before our upgrade to NW04S, we did not experience this issue.  As background, the DataStore (ODS) has not changed, the variable has not changed, and the query has not changed.
0COMP_CODE has the following configuration in RSD1:
Query Def. Filter Value Selection – Values in Master Data Table
Query Execution Filter Val. Selectn – Only Posted Values for Navigation.
These settings are exactly like this in our BW 3.5 system.
In my review of the differences, I found that in BW 3.5, the runtime is short because the selection that is returned is the Company Codes in the Master Data table, but in NW04S, the selection that is returned is the Company Codes within the ODS. 
Has anyone experienced this before and if so what was your resolution?
Thanks!

Answer 1

<b>Query Execution Filter Val. Selection</b> should help you a lot in improving performance for F4.
Three options are available for the <b>Query Execution Filter Val. Selection</b> field on the BEx tab that directly affect F4 searches.
<b>The Only Posted Values for Navigation</b> setting limits an F4 search to the values related to the query’s navigation state. It is the recommended setting if you’re working with less savvy BW end users who may have trouble identifying applicable values or are confused when faced with long lists of characteristics. This setting yields the <b>slowest performance</b> in terms of the F4 search.
<b>Only Values in InfoProvider</b> is a better option if you need a list of characteristic values for a variable that is limited to the transactional records in the InfoProvider that a query is being executed against. This setting is ideal for restricting users to the appropriate source when data is available in different InfoProviders with different values. For example, let’s say you have an InfoCube with billing data for Europe and another for the US. Each sales office will have different values, so by using this setting a variable can be restricted to the correct values.
<b>The Values in Master Data Table</b> setting allows users to list all possible characteristic values when they run F4. Recommend that you use it when you have transactional records for almost all the values across InfoProviders and users are aware of the relevance of the values for the navigation state.
While the Values in Master Data Table setting is the <b>fastest F4</b> search setting, you need to be aware of a couple of situations when using it. Users with authorization restrictions may have an F4 list returned with all the values from the master data table, but a subsequent query may not report the result. Instead it will generate an error message informing the user of the authorization restriction. Likewise, users may select values from the master data table that are not valid for the current query due to other restrictions. There may not be any records for an InfoObject in its underlying InfoProvider designed for a query, so the system returns a “no applicable data found” message.
<b>Important Notes for F4 - Performance -</b>
748623 Input help (F4) has a very long runtime—recommendations
661251 Filter value selection displays too few/too many values
581802 Variable dialog boxes: performance of the F4 help
581079 Performance for the F4 help of navigation attributes
626887 F4 variables and InfoObject settings.
Hope it Helps
Chetan
@CP..