Performance issue using selection from LOV

[Former Member]

We created a BOBJ UNIVERSE over a Bex Query based on BW-DSO.

The Bex Query has a filter object for selection during executing time.

This Object is marked as "searching from MASTER DATA" on the BEX query.

When a BOBJ query is operated on the UNV, it takes several minutes to get the LIST OF VALUE of the filter object.

The list of values is showen from the DSO and NOT from the MASTER DATA.

If we operate the BEX query in BW, we receive the LOV in seconds. (from the Master Data).

Our platform is Business Object XI 3.1 SP2 includes SAP integration KIt of the same level.

BW 7.00 support package 22 (SAPKW70022).

The DSO contains about 2,000,000 rows.

Any suggestion how to improve performance time for BOBJ query or how to enforce it to get the LOV from BW MASTER DATA ?

Thanks.

[IngoH · Accepted solution]

Hi,

let me clarify a couple of items here:

We created a BOBJ UNIVERSE over a Bex Query based on BW-DSO.

The Bex Query has a filter object for selection during executing time.

This Object is marked as "searching from MASTER DATA" on the BEX query.

>> which is a display setting for BEX - not for Web Intelligence.

When a BOBJ query is operated on the UNV, it takes several minutes to get the LIST OF VALUE of the filter object.

The list of values is showen from the DSO and NOT from the MASTER DATA.

>> That is correct

If we operate the BEX query in BW, we receive the LOV in seconds. (from the Master Data).

>> You see the first 200 values and then the values are read on demand. Bex doesn't show you all values.

You can simply switch on he delegated search in the LOV objects in the universe.

Ingo

[Former Member · Accepted solution]

Hi Ingo,

Thanks for the explanation.

It is seemed rather odd that WEBI does not use the MASTER DATA search that is defined in the BEX query, the UNV based on.

We are talking about objects that have less than 200 values in the MASTER DATA, usually it is an Authorization Object, that the User needs to select from it during runtime.

We can also change the maximum value listed from MASTER DATA to be higher than 200.

This is very poor performance to get the LOV after several minutes instead of few seconds.

Using delegating search is not always possible when the user needs to select random values.

Although delegate search improved getting the LOV from 5 minutes to 2 minutes (in our case), still waiting for 2 minutes,

just to get the LOV is very long time for an enduser. (and now he has to wait for the WEBI query to be executed).

Any idea if there is any improvement performance planed for the connection between BOBJ and BW ??

Thanks again.

[IngoH · Accepted solution]

HI,

It is seemed rather odd that WEBI does not use the MASTER DATA search that is defined in the BEX query, the UNV based on.

We are talking about objects that have less than 200 values in the MASTER DATA, usually it is an Authorization Object, that the User needs to select from it during runtime.

We can also change the maximum value listed from MASTER DATA to be higher than 200.

This is very poor performance to get the LOV after several minutes instead of few seconds.

>> first of all the BI authorization you configure are not relevant for master data unless you are using authorization variables and BEx does a paging of the values - it does not retrieve all values. it does retrieve the values in chunks

Using delegating search is not always possible when the user needs to select random values.

Although delegate search improved getting the LOV from 5 minutes to 2 minutes (in our case), still waiting for 2 minutes,

just to get the LOV is very long time for an enduser. (and now he has to wait for the WEBI query to be executed).

>> using delegated search is possible. and delegated search means you are not retrieving a list of values at all so the 2 min that you mentioned indicates you didn't configure it properly.

Ingo

[Former Member · Accepted solution]

first of all the BI authorization you configure are not relevant for master data unless you are using authorization variables and BEx does a paging of the values - it does not retrieve all values. it does retrieve the values in chunks

Yes we use authorization variables, and that's how we get the LOV from MASTER DATA in the BEX.

The WHOLE list is shown in seconds during runtime(BEX), so we do not care that it is retrieved in chucks

Why can't it be the same on the WEBI ??

using delegated search is possible. and delegated search means you are not retrieving a list of values at all so the 2 min that you mentioned indicates you didn't configure it properly.

We configure the delegated search as described in your helpful blog - BO and SAP Part 6.

No members of the LOV are loaded.

When we enter the search criteria like "A*" it takes 2 min. to get the relevant list.

When we used the LOV without delegated search if took 5-6 min. to get the whole list

Thank you again for the explanations.

It looks that we have to adjust ourselves to this performance time.