LOV Filtering on OLAP universe

Hi
i have a BOXI 3.1 SP2 FP2.6 universe on top of a bex query (BW BI 7 SP5)
my bex query contains a variable 'ready for input' which give me a prompt condition on BO universe.
My BO condition has the default LOV <Variable name> which gives me 2 hidden objects <Variable name> and <Variable name>Base.
this hidden object displays a list of values on prompt in my report. i want to filter the list of values on 2 single values (from the whole list).
I know i can define the 2 single values directly in my prompt by filling the 'value ' and 'key'. But my 'value ' are static.
I'd rather to limit the list of the LOV directly on the hidden objects <Variable name> or <Variable name>Base of the universe on the 2 key of my requested items
is it possible ?
thanks in advance,
Rgds,

Ingo, you mentioned in this posting that the functionality required is not supported for OLAP universes ... is this still the case in 3.1 ?
WE have a similar challenge here where we need to restrict the list of Vendors that is presented to the user to only Merch Vendors. I need to do this in a BEx Query, as there is a 2nd variable which returns a list of articles based on the selected Vendor, so need the selected Vendor to be available in the Post-Popup variable exit code.
I have implemented the RSR_VARIABLE_F4_RESTRICT_BADI in BW, which correctly limits the list of values in teh Vendor dropdown when the BEx query is run in RSRT / web, but in WebI this list of values doesn't apply.
Cheers,
Andrew

Similar Messages

Adding mandatory filter with own LoV to BW OLAP Universe

Dear all,
I want to add a own filter with custom LoV to a characteristics-filter in an OLAP Universe. This filter does not exist in the BEx Query, so I have to do it manually.
So when the prompt shows up in WebI, the User should be able to select the Values from the custom LoV, for example:
- Tokio
- London
- Paris
The filter has to be mandatory and Tokio should be preselected. I was testing some things with the filter-XML, but always got errors. Can somebody tell me how this works?
Thank you for help in advance!
B. Wegner

Hi,
There are a few steps involved, I would suggest approaching them one at a time.
First, try to set up a filter (condition in the universe) to only show data for Tokyo (no prompt). Ensure you can get this to work.
Next, try and turn this condition into a prompt, but just define the LoV in the prompt syntax, not a separate object. Check that this works.
Next, try and split out that LoV into it's own object that populates from the characteristic in the BEx query. This will be the tricky part (maybe), if possible, get a filter created in the BEx query (make sure it's set as 'ready for user input') so that you see how the LoV gets created.
As a last resort, have a look in the manual: http://help.sap.com/businessobject/product_guides/boexir31SP3/en/xi31_sp3_sap_olap_univ_en.pdf
Hope that helps.

Predefined filters in OLAP Universe

Hello
I am trying to create a pre-defined filter in an OLAP Universe on top of SSAS 2008. We use BOXI 3.1
Here is my object Structure
Date(Folder) -> Year(Folder) -> Year(Dimension object).
However when i try to create a simple filter as below
<FILTER
KEY="[Date].[Year].[Year]"><CONDITION
OPERATORCONDITION="InList"><CONST
ANT CAPTION="@Prompt('Calendar
Year(s)','A','Date.Year\Year',multi,constrained)"/></CONDITION></FILTER>
I keep getting "Parse Failed UNV0023 Invalid Definition" error.
What am i missing here?
Thanks
Edited by: ramaks on Dec 30, 2009 7:00 PM

Hi,
Are you sure that the parent class of the "Year" object is "Date.Year"?
The correcxt syntaw for @Select is @Select(parent class\object name)
If you have an error you hit the same problem in the @Prompt that would be like this: @Prompt('Question','A','parent class\object name',multi,constrained)
Didier

Olap universe lov restriction on detail object key

Hi,
I created a restriction on dimension lov in SAP olap universe using 0PLANT dimension on Orders keyfigure as below
<EXPRESSION>(@Select(Key Figures\Orders),[0PLANT].[1000])</EXPRESSION>
this syntax works but webi results are not matching with BEx.
Values of BEx RKF and formula object (
=[Orders] Where([L01 Plant] = "1000")
)created in webi are matching.
I am trying to create restriction on detail key object, like
<EXPRESSION>(@Select(Key Figures\Orders),[0PLANT].[LEVEL01].[[20PLANT]].[Value].[1000])</EXPRESSION>
above measure is giving error when i run the webi query.
here both L01 Plant and L01 Plant Key are having same lov as 1000,but i wanted check exact values with detail key syntax.
Can anyone please tell me the syntax for using detail objects keys for restriction in Select Clause.
Thanks,
Harsha

Hi,
why are you not creating this as a restricted key figure in the underlying BEx Query ?
Ingo

Cascading LOV in BEx Query OLAP Universe + BEx variable

Hi gurus,
we have an universe where a Cascading LOV has been defined based on a BO Hierarchy ( based on a BW hierarchy), the OLAP universe is based on a BEx query.
Now, when the users create a WebI report selecting a value from the value list, the Cascading LOV appears and the user selects the value, descending by the nodes.
We are analyzing the universe performance and we are testing to add some time BEx variables in the query ( in the current version no variables are used).
Everything works properly but when we try to select a value from the Cascading LOV and try to select a lower level the webI returns a mdx error indicanting that the time variable is not informed. (WIS 10901: A database error ocurred; MDX query can not be executed: specify a value for the variable Z... )
We thought that the mdx for the LOV get values from the MD table because in the infoobject definition, it has the Business Explorer Settings:
Query Def. Filter Value Selection = Value in Master Data Table
Query Execution Filter Val. Selectn = Value in Master Data Table
The Query Execution Filter Val. Selectn can be defined at the infoprovider also (with the provider specific Properties of the infoobject) and also at the query, whe have not modify none of them.
My first question is which settings has efect at OLAP Universes, the infoobject settings; the infocube settings or the query settings ?
Are the Cascading LOV integrated with BEx Query OLAP Universe?
Is it an application error?
Many Thanks in advanced.
Best Regards,
Nuria

Hi Ingo,
many thanks for your quick answer.
That was one of the possibilities we have analized but the problem is that the user has to inform the hierarchy level for all the reports, that kind of variables is translated in the universe as a prompt
Now we have only one universe and some business analists users create reports themselves for the business area based on that universe.
The users create WebI filters without prompts,just filtering the hierarchy node. If we add the BEx variable then the user sould inform the prompt for all the reports based on that universe.
We want to avoid that prompt, we have several hierarchies in the query for different infoobjects.
Thanks again.
Best Regards,
Nuria

Cascading LOV in OLAP UNIVERSE

Hi.
I got a problem with a lov in webi.
I have created an OLAP Universe buitl on a SAP BW 7.0 infocube and I created a hierarchy and a cascading list of value but when I go to my WEBI report it doesn`t works, it isn`t filtering the objects by the hierarchy, it duplicates the same information for all the object's concepts.
For example i got a LEVEL 1 concept u201CBuenaventurau201D and it shows in LEVEL 2 u201CEGRESOSu201D and u201CINGRESOSu201D the problem is that it show the same for all the LEVEL 1 concepts and it should only show "EGRESOS" and "INGRESOS" for LEVEL 1 concept "Buenaventura" because is the only one that has information.
Can anybody pls tell me why is having this behavior.
Thanks and regards,
Julio
Hola.
Tengo un problema con una lista de valores en cascada en un universo olap que lee un infocubo de BW 7.0. Cree una jerarquía en el universo y una lista de valores en cascada, pero cuando voy al reporte WEBI y hago un prompt a la lista de valores no me filtra por concepto, repite la misma información para todos los conceptos.
Por ejemplo tengo en el NIVEL 1 el concepto "Buenaventura" y me muestra en NIVEL 2para este concepto "EGRESOS" e "INGRESOS", el problema es que me muestra lo mismo para todos los conceptos del NIVEL 1 cuando sólo deberian aparecer para "Buenaventura".
Alguien me podría explicar por favor por qué se comporta así.
Gracias y Saludos,
Julio

Hi Julio,
As of now the cascading list of values are not supported in the universe created on top of SAP BW (Bex Queries).
In the below thread Eric has mentioned that he has got this confirmed from SAP:
Link: [Re: OLAP castcading prompt]
Regards,
Rohit

BW LOV in OLAP Universe

Hi All,
I have a little problem with BW variable (individual values, required) in query where in my OLAP universe it turns prompt in the following sturcture:
BW BEx
Infoobject Year/Month (0CALMONTH)
Variable 0PCALMON
BO Universe
Class Year/Month
Dimension L01 Year/Month
Hidden dimension Lov Year/Month Base
My report makes the search or should seek direct the LOV that contains the year in infoobject BW ("JUL 2011", "AUG 2011", ...) but it does not return expected. It simply returns "01.0000", "02.0000", "11.0821", "SEP 1787" ... and only at the end of LOV it returns the correct values or are in the InfoCube ("JUL 2011, AUG 2011", ...)
I'm using BO XI 3.1 SP3 and BW 7
Any suggestions ?
Tks,

Hi,
These values come straight out of the BW masterdata.
My guess is you still have some old invalid values there.
Note that whenever you see the key version in stead of the formatted version,
it means no text was found associated with this key (in the current language).
Hope this helps (better late then never right),
Marianne

Getting Custom LOV in SAP BW OLAP Universe

Hi,
My Requirement is to create a prompt where the end user is prompted to select a Custom group(which we have to manually put in prompt and is not available in SAP BW table) and the data should be filtered by the billing document type for that group which again we have to specify in the prompt.
This is what I have created but it's not working -
<OPTIONAL><FILTER KEY="@Select(Billing Document Typ\Billing Document Typ)">
<CONDITION OPERATORCONDITION="InList">
<CONSTANT TECH_NAME="@Prompt('Enter\Select Sales Data Type: ','A',{'Merchandise Invoice Sales':'YFX':'YLXP':'ZFX':'ZLXP','Dropship Invoice':'YFXD':'ZFXD'},multi,free,Not_Persistent)"/>
</CONDITION></FILTER></OPTIONAL>
I have seen this thing working in BO with oracle as backend but it's not working here in OLAP Universe.
Please let me know if anyone has ever faced this issue.
Thanks,
Pankaj Goswami

Hi Marvin,
When you define a filter only the Where clause is available.
When you define an object both Select and Where clause are available.
For an object the Select clause is mandatory, the Where clause is optional.
So for instance if you want to define a new calculated measure, use the Select clause if you want to filter with this new object you can set the Where clause but that means that this object will be always filtered by the Where clause definition.
The other way is to create a new filter that use the object definition to filter on what you want: in that case you can use the object for any scenario and use filter only when you need it.
Last the syntax you wrote is invalid:
<EXPRESSION>(@Select (Class\Measure),filter)</EXPRESSION>
What do you want to define? What is the purpose of this new object?
Please provide all the information you can and I will try to provide you a correct definition.
Didier

OLAP Universe : Objects LOV pointing to master table in BW

The LOV's generated were pointing to master table in BW. Say like we have Material dimension along with LOV's generated by Universe based on Bex is poingting to Master table in BW. "0Material.Level 0". when we refresh or search for a purticular Material we are getting two errors: Partial Results and No Value found.
I checked in the Parameter and we dont have any restriction bringing the number od rows. Can anybody advise how to show all the Materials in LOV's. I tried using delegated search option in the Object properties. But doing that we loose Search option
and showing LOV. Because it expects User to key-in the Material Number.
Thanks
Pats.

Hi,
I believe that under universe option Under control uncheck every thing and export the universe and this will resolve the issue. If not then go to following SDN link try to apply the solution provided in this section to see if you get your issue resolved.
[Large volume data - WebI document fails;
Bashir Awan

OLAP universe query filters using multiple key values

Hi,
We are running BO over a MSAS 2005 cube and due to reporting requirements we have had to split the year out from the standard time hierarchy so we have it as a separate hierarchy from the rest of the time hierarchy. We also have 2 other dimension objects we use to find the current reporting month (shown below as Current Month and Current Year) which link to the Year and Month dimensions to give us the current year and current month.
I have created predefined filters in the universe for Last Month and Last 6 Months etc which link the 2 hierarchies together to dynamically find the correct months to pull out based on the current reporting month.
The issue i am facing is that when these filters are used in reports we are not able to pull through the Year dimension in the report as we receive the error: "The Year Hierarchy hierarchy is used more than once in the Crossjoin function"
We can however use the Month dimension in reports even though it is also referenced in the filter definition.
I have narrowed the issue down to the fact the Month dimension is mentioned in the Filter Key which allows it to be used in the reports.
Is it possible to include 2 key values or are there any other ideas on how to tackle this problem so i can include the both the year and month in reports using these filters?
Last Month filter:
<FILTER KEY="@Select(Period To Date\Month).[TECH_NAME]"><CONDITION OPERATORCONDITION="InList"><CONSTANT TECH_NAME="CASE WHEN FILTER(@Select(Period To Date\Month).Members,@Select(Period To Date\Current Month).[Y]).Item(0)= @Select(Period To Date\Month).[January] THEN {CrossJoin(FILTER(@Select(Period To Date\Month).Members,@Select(Period To Date\Current Month).[Y]).Item(0).lead(11),FILTER(@Select(Period To Date\Year).Members,@Select(Period To Date\Current Year).[Y]).Item(0).lag(1))} ELSE CrossJoin(FILTER(@Select(Period To Date\Month).Members,@Select(Period To Date\Current Month).[Y]).Item(0).lag(1),FILTER(@Select(Period To Date\Year).Members,@Select(Period To Date\Current Year).[Y]).Item(0)) END"></CONSTANT></CONDITION></FILTER>
Thanks in advance

Dear Daniel, may I ask one more question please?
what if I have 4 tables?
table1
ID * ID_Type_code * Name
0001 * 11 * abc
0002 * 12 * abcd
0003 * 13 * abcde
table2
ID * OID_type_code * Name
0001 * 22 * abc
0002 * 23 * abcd
0002 * 25 * abcd
0003 * 23 * abcde
0003 * 22 * abcde
0003 * 28 * abcde
table3
ID * OID_type_code * OGAD_line_id * address
0001 * 22 * 1 * a street
0001 * 22 * 2 * b street
0002 * 23 * 1 * c street
0002 * 25 * 1 * d street
0003 * 28 * 1 * e street
0003 * 28 * 2 * f street
0003 * 28 * 3 * g street
table 4
ID OID_type_codeOGAD_line_id*COP_line_id*phone number
0001*22*1*1*2222222222
0001*22*1*2*3333333333
0002*23*1*1*4444444444
0003*28*2*1*5555555555
0003*28*2*2*6666666666
Primary key for each table
table1, primary key is ID
table2, primary key is ID , OID_type_code
table3, primary key is ID , OID_type_code, OGAD_line_id
table4, primary key is ID , OID_type_code, OGAD_line_id , COP_line_id
I would like to show each value in each table in the separate input text fields.
Therefore, this is an advanced question based on the previous one, not only get values from one table but also from several tables based on input for example 0003 and 28 as the ID and OID_type_code?.
Let me know if you need more details,
Thank you so much,
Viola

OLAP Universe Refresh creates error

Hi,
we built an OLAP universe based on BEx Query. SAP Netweaver 7.0 EHP1, BO XI3.1 SP3 FP2, BW Integration Kit XI3.1 SP3 FP2.
BEx query contains 4 Filters that need user input.
When we create the universe for the first time, everything works fine and the Filters with variables are created as Universe Filters with prompts and LoVs.
Everytime when we refresh the universe structure, the MDX syntax of 2 of the Filters in the universe is added again which is causing an error at runtime. So when refreshing the universe 2 times, we see the MDX filter syntax 3 x in the condition field.
The filters have not been changed or moved, so we do not see why 2 filters are refreshed and 2 get addtional code. It also happens with other BEx Queries/Universes.
Thx for ideas

Hi Ingo,
we did not remove the filters from the universe.
"Added again" means, that when I refresh the universe structure, the pane with "added Elements" shows 2 filters that existed already in the universe. Universe designer adds them again.
These are the filters that create the problem.
When I open the filter syntax in the universe, the refresh added the MDX code again, so that it contains the MDX twice.
With every refresh the filter-MDX-code is added again. But only at 2 of 4 filters.
Rgds,
LK

SAP BW OLAP Universe performance issue

Hi,
Based on BO recommendation, I created a universe on top of a big BEX query which included all characteristics and key figures from a cube. I then created a webi report with 5 characteristics and 1 key figure from this universe. I also create the same report in BEX query designer(same number of objects). I ran both. The Bex query completed under a minute and the webi report took more than 12 minutes to run. I did a bunch of other test with different number of objects combination and saw similar differential in query performance.
I did a trace using 'sm50' and saw the open SQL submitted to BW from BEx was very different from what got submitted from the webi report. Here is what I saw in pseudo code.
Bex:
select dimension1.blah, dimension2.blah, dimension3.blah, dimension..... sum(measure)
from dimension1, dimension2, dimension3, dimension..... factTable
where dimension1.SID = factTable.d1SID
and dimension2.SID = factTable.d2SID
and ......
and (query filters)
OLAP Universe
select dimension1,blah, dimension1.SID
from dimension1, factTable
where dimension1.SID = factTable.d1SID
select dimension2,blah, dimension2.SID
from dimension2, factTable
where dimension2.SID = factTable.d2SID
select dimension3,blah, dimension3.SID
from dimension3, factTable
where dimension3.SID = factTable.d3SID
It seems the OLAP universe was querying the BW cube one dimension at a time and then somehow piece the result sets together to form the final result set. Dimension tables join to the fact table without any filter definitely causes performance issue. Beside, I have no idea why the query requests are submitted to the BW system like that.
I looked in varies forums and found no similar issues posted by others. Has anyone had any performance problem with there OLAP universe? Is this a matter of configurations?
My envrionment:
SAP BW 3.5
BOXI 3.0
ORACLE DB (version ??)

Hi,
You cannot compare a BEx query and a universe query by just comparing the trace.
BEx query makes ABAP calls and universe query makes MDX calls;
Moreover there is only one MDX call sent to SAP, what you have noticed is that there is one MDX call to retrieve member for a given characteristic whereas a prompt has been set on.
Last, Web Intelligence consume only flattened data (row sets) wheras BEx consume data sets.
That means that there is a flattening operation between SAP OLAP engine and the data sent to the Web Intelligence document.
A fix have been developed for a customer to improve performance on Web Intelligence queries, this fix will be available for all customers in SP2 planned in June 09.
Here is a a brief summary of what the fix provide:
- Provide data directly from SAP server to Web Intelligence document. Avoid unnecessary conversion steps: row set --> data set --> row set
- Eliminate redundant sort operations
- Other optimization operations
Didier
Edited by: Didier Mazoue on Nov 20, 2008 8:38 AM

Setting a Prompt value for KeyDate in WebI on SAP OLAP universe

I have a webi report which has as its dataprovider a query against an SAP olap universe against a BEx query which has the KeyDate parameter exposed.
Iu2019d like to get at this prompt from the SDK.
In infoview if I run the report it pulls up the keydate prompt (a special dialogue which seems to be implemented as part of the connection definition) - this prior to pulling up the full prompts dialogue and showing all universe based @prompt filters. In WebI I can see the prompt value entered using =UserResponse("dp.kd.value") . So it does seem to see the keydate as a prompt of some sorts.
I've got a little jsp that allows me to set prompts very nicely (and packeaged as a jar in the CMC that schedules ok as well) but when I put it against a report with a key date u201Cpromptu201D it just wonu2019t see it. When I call a getCount() as below it returns 0.
oDocumentInstance.getDataProviders().generateQueries();
Prompts oPrompts = oDocumentInstance.getPrompts();
out.print(oPrompts.getCount());
This is all in an attempt to get around the scheduler limitations of key date which would give me two queries, two universes and two reportsu2026 one report for scheduling (using a customer exit to set key date) and a second for user refresh (with a prompted key date) which would all be rather messey to say the least!
So any cunning ideas on how I can get hold of this key date thingymebob in the SDK?
(ps. "Fixed in V4" would be nice to hear as an aside to thisu2026 In playing with the ramp up Iu2019ve got the same issues however so Iu2019m not to hopefull )
Thanks!
Jeremy.

Hi,
First I think you have to create a support ticket because normally the object in the universe must be generated with data data type nad it is not the case.
We are awere of some limitations with data types.
Secondly, if you want to have users entering date you have to specify date in the prompt data type like this:
<OPTIONAL><FILTER KEY="[PERIOD SD].[DB Full Date].[DB Full Date]"><CONDITION OPERATORCONDITION="Equal"><CONSTANT CAPTION="@Prompt('Enter Date ','D',,mono,free)"></CONSTANT></CONDITION></FILTER></OPTIONAL>
Regards
Didier

OLAP Universes - Based on BEx Query - Month and Previous Month Functions

Hi,
I created a Universe based on SAP BEx queries and I like to create a filter so that I use in Web Intelligence report to run for "Previous Month" data always. There are "Date" filelds in BEx Query(No Month info only date data). I have no knowledge of SAP BEx Queries and new to OLAP universes. Could you help.
How to create filter that show Previous Month.
Nanda Kishore
Edited by: Nanda Kishore B on Dec 26, 2010 6:15 AM

The easiest way (but NOT the most efficient one) is to create a local variable (Dimension) in your report with the following code:
=if (Month(CurrentDate())=1 AND Month([[MyDate]])=12 AND Year([[MyDate]])=(Year(CurrentDate())-1)) OR (Month(CurrentDate())>1 AND Month([[MyDate]])=(Month(CurrentDate())-1)) then 1 else 0
where MyDate is the field from your query containing the data information
Activate the report filter area in your report design panel by pressing the Report filter icon and drag and drop your variable there and apply it to the entire report. Filter value 1 and you will get the data for the previous month.
Keep in mind that this approach is not optimal especially if you do have many rows of data delivered to your WebI report because filtering takes place only AFTER the data is retrieved. The Best practice here is to work with BEx variables.
How many rows of data does your WebI report normally fetches?
Regards,
Stratos

Olap Universe Based on BEx Query - Cascading Prompt

I need to get two prompts: 1) Division 2) Group. Division has to be selected first and then Group. I understand I have to create cascading prompt. In the universe, in default hierarchy, group stands before before division. I have created a custon hierarchy like: Division, Group. I used Tools -> List of Values ->Create cascading list of values and then selected the right dimensions and then clicked on Generate LOVs. Then I have exported it to the repository. But I cannot see any reflection at the report level. So, some questions came in my mind:
1) Where can I check in the universe whether my cascading prompt has been created or not ?
2) I am using L01 Dimension. But underneath, there are two dimensions called LovDivision and LoVDivisionBase which are in Italic. I believe integration kit creates this. It is the same as Group. So, my question is: Am I selecting the right dimesnsions ? Or, should I select those in Italic.
3) Actually, these two prompts (variables) [along with others] are already created in BEx which I can see in my report. My plan is, if my cascading prompts work, I will tell the BW developer to remove those two. Do you think that these existing prompts are creating any problem.
I would really appreciate your response.

Hi
1) Where can I check in the universe whether my cascading prompt has been created or not ?
Have you entered the cascading object in the webi query condition.At the run time it will generate hierarchy in the tree structure.
2) I am using L01 Dimension. But underneath, there are two dimensions called LovDivision and LoVDivisionBase which are in Italic. I believe integration kit creates this. It is the same as Group. So, my question is: Am I selecting the right dimensions ? Or, should I select those in Italic.
correct you are using right objects L01.By mdx driver it will create by default L00 and L01 objects.neglect the Lo00 objects.You can hide them in the universe or go to refresh structure and their is option to replace L00 definition with some other definition.
3) Actually, these two prompts (variables) along with others are already created in BEx which I can see in my report. My plan is, if my cascading prompts work, I will tell the BW developer to remove those two. Do you think that these existing prompts are creating any problem.
By default when you are creating universe based on the mdx drivers it will convert Bex query filters in the universe condition as mandatory filter and applied on the full universe.
You can go to the universe condition and open the condition and unchecked the option from their and after that these will not prompt in the webi query.
Thanks,
Amit

LOV Filtering on OLAP universe

Similar Messages

Maybe you are looking for