Hierarchy Variable Selection very slow

[Former Member]

Hi all,

We have a hierarchy on profit center. We created an authorization hierarchy node variable on this hierarchy and when the user runs the report his authorized region will come up in the selection screen. When we want to choose another sub region present below the node by clicking on the small box on the right of the variable entry (in Portal), it takes for ever to show the hierarchy. In the back end we see that the SID table of the Profit Center is read sequentially. Any idea how to fix this.

We are on BI 7.0 SP 13 and Java Stack 12.

Thank you for you time,

Prabhu.

[Former Member · Accepted solution]

Try using the 3rd option shownbelow "The Values in Master Data Table" from the infoobject-->Bex tab maintenance

Query Execution Filter Val. Selection should help you a lot in improving performance for F4.

Three options are available for the Query Execution Filter Val. Selection field on the BEx tab that directly affect F4 searches.

1)"The Only Posted Values for Navigation" 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 slowest performance in terms of the F4 search.

2)"Only Values in InfoProvider" 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.

3)"The Values in Master Data Table" 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 fastest F4 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.

Important Notes for F4 - Performance -

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..

[Former Member · Accepted solution]

Thanks a lot Chetan,

I changed the Infoobject BEx property to the third option and now the filter help comes up very quickly.

Regards,

Prabhu.

[Former Member · Accepted solution]

Welcome Bro

Good Luck

Hope it Helps

Chetan

@CP..