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

Similar Messages

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

Creating Cascading LOV

Hello All,
I am creating webi from universe based on Bex Queries.
I want to create a Cascading LOV for Organizational Level in my webi report. (having Level 1 , Level2 , ....).
But when i am going in Tools -> Cascade LOV option in universe and assign different levels and click on generate LOV, nothing happens or the functionality of cascading LOV doesn't work in OLAP Universes as we can not edit LOV.
The version being used BO XI 3.1 SP2
SAP BW 7.1 Patch Level 17
Pls Help.

Hi Akhil,
I am working on BO XI R3.1 SP2.
The functionality of cascading LoVs work in case of OLAP universe too. But you do not have the option to change the
Cascading LoVs i.e. you can-not edit the levels one it is generated.
Moreover, here in cascading LoVs Prompt doesn't get displayed for each level instead the values are generated in the
hierarchially.
If you need to change the levels, you need to generate it again. Hope this helps you.
Regards,
Rohit

Dynamic Cascading Prompt based on Universe

Hi,
I am attempting to build a universe-query-based report which allows the user to select inputs based on a dynamic cascading prompt. I have created the cascading LOVs in the Universe design. However, when the user is asked to select inputs, the prompts do not appear to cascade. They show all possible values independent of each input(there are 3 inputs). When I try to manually create the dynamic cascading prompt on the actual report, I select dynamic parameter but it does not show any values under the Choose Data Source option. All it shows is "(None)". Any suggestions on how I can get this cascading prompt to work? I am using CR 2008 also.
Thanks for you help!
David

Hey David,
Steps to create connection in Business View Manager:
1) Go to Start -> Program files > Business objects xir2> business objects enterprise > businessview manager.
2) Click on New >
3) Steps to create is Create a Data connection > Select Data Connection > Data sources > Save the data foundation.
4) Second is to create a data foundation.
Click New > Data foundation > Select the Data Connection and Select the Table.
5) Third is to create a data element.
Click New >Data Element > Select the Data Foundation Select the required fields for Lov from the table.
6) Is to create a business view > New > Business View >select the data element > save the business view.
7) Is to create a Lov> New > LOV > Select the business view > Select the fields for dynamic cascading parameter fields and save the LOV
8) Open the crystal report designer > connect to the repository > create a new parameter > select dynamic> Select Existing > Select the LOV created through the business view manager.
Note : Should Save all the Connection, data Foundation, business elements, business view and LOV separately and instantly.
Let me know if any.
Regards,
Naveen.

Unable to remove cascading LOV in designer

Hi Experts
I'm Using BOE 3.1
I created cascading Lov's in universe Month-->day and gerated Lov's and now i want to delete the cascading LOV but there is no option to remove cascading Lov;s ,when i check in webi i got an error with database error wis 10901 .
How can i remove caccading lov
Please help me with this ,very urgent
sunil

hi
request to kindly delete the cascading LOV .means the place where you have created .You can pull out of from that arena .Save the universe and export .
Do refereshe the webi and see
thanks

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

Cascaded LOV do not work in derived universe

Hi all,
Can ay body help me on this.
Cascaded LOV do not work in derived universe. The same cascaded LOV works
well in component / core universe.
For Example:
say object state is generated as Cascaded LOV's with city. in core universe. when you create a webi report based on the core uiverse and drag the object state it Cascaded LOV's are generated.
now say you create aother universe as derived with the same universe as core universe. Now create a webi report based on derived universe try to drag the state object the cascaded LOV's do not get displayed.
Note:we have not included any object of the core in the derived universe.
Any help would be appreciated.
Thanks,
Florencio.

Hi Joe,
Thank you for your reply. Actually this is not a migrated derived universed. Yes it is the case with migrated reports from R2 to R3.1 till FP 1.3. But it is resoved in Fixpack 1.4 and above.
In addition it is also a issue in Plain R3.1 with even sample universes that is e-fashion. it is resolved in FP 1.4.
Thanks Again!!!!
Florencio.

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

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

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.

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 creation process questions and proposals

We have created an OLAP universe based on a BW-Query. The automatical creation of the OLAP universe does not produce a satisfying result.
We are working with the latest available releases (BOE XI 3.1 SP2 and SAP Integration KIT SP2, SAP BI 7 EHP1).
We have detected that all dimension objects store the name instead of the key field.
Example:
Customer Dimension Object (L01 Customer) = Customer Name
Customer Key Detail Object (L01 Customer Key) = Customer Number
Customer Name Detail Object (L01 Customer Name) = Customer Name
This is not usable for end user because of the following reasons:
1. The detail objects can not be used for merge dimensions, so it is not possible to merge on the supplier number.
2. If you filter on the dimension object you will only see the text in the list of values (LOV) and it is not possible to edit the list of values in the universe to add the supplier number to the LOV as it is possible in relational universes
3. If the user select the detail object always the dimension object in inserted into the report query
4. The "Business Explorer" general setting "Display" of an InfoObject has no effect on the OLAP universe dimension object. If you change it to key always the text is shown. Even if you change the "ValueDisplay as" in the underlying BW Query to "key" is has no effect.
5. The renaming of the L01 object to blank is not possible. You need to rename to " " and then remove on each object the blank.
So we need to modify manually every universe to change the "detail key object" to a "dimension object" and the "detail name object" to reference the new "dimension object" with the key. This manual process has a huge work effort in time. Is there a better solution or enhancements planned in the next releases?
Additionally there should be an option to disable the automatic creation of each characteristic as a subclass in the universe. A wizard should ask if a subclass should be created or not for each characteristic. Currently there are to many subclasses generated which were mostly not needed.

Hi,
First of all I would say u are lucky to start with SP2. Because whatever modifications you do in Universe those are retained.
We had a big trouble in using BOXIR3.1 FP1.7.
Anyways.. Back to your Questions and My asnwers for those:
1. The detail objects can not be used for merge dimensions, so it is not possible to merge on the supplier number.
Ans: True, Dimension object always shows Short text values by default. but if you can create the logic at SAP BI query level to map short text with keys then your problem will be solved.
2. If you filter on the dimension object you will only see the text in the list of values (LOV) and it is not possible to edit the list of values in the universe to add the supplier number to the LOV as it is possible in relational universes.
Ans: True u cannt edit LOV, but alternate solution to it is create the variable in SAP BI Query, that will appear as prompt in universe which will display the List of values with Key as well as Description.
3. If the user select the detail object always the dimension object in inserted into the report query.
Ans: Logically its correct, because Detail object is always associated with Dimension. Buit if you dont want that dimension in query you can remove that dimension by dragging back.
4. The "Business Explorer" general setting "Display" of an InfoObject has no effect on the OLAP universe dimension object. If you change it to key always the text is shown. Even if you change the "ValueDisplay as" in the underlying BW Query to "key" is has no effect.
Ans: In Query designer even if you ValueDisplay as "Key", but at Object level if there is Text and Key associated for perticulat Infoobject, then so by default the dimension will show the Text and there will be seperate Detail object in universe for Key.
5. The renaming of the L01 object to blank is not possible. You need to rename to " " and then remove on each object the blank.
Ans: Yes this is a big trouble.
Regards,
Nisha

Linking Olap universe built on two different BEx Queries

Hi,
I need help on following:
I have a universe A build on Bex query 1 and universe B build on Master Data.
I want to link Universe A to Universe B so that i can filter the values in universe B based on user logged in and use them in Universe A.
Can any one let me know if this is supported at first place linking two olap universes in BusinessObjects XI R3.1 SP2/SP3?
If yes how can i acheive this?
Is ther any document that has details about linking the Olap universe in BOXI R3.1 SP2/SP3
If anyone knows about this please let me know ASAP.
Thanks,
Shashank
Edited by: smisha23 on Dec 23, 2010 8:43 AM

Hi Ingo,
thanks for the help.
Let me explain my scenarion so as to why i am trying link universe option.
I have a requirement where in i am suppose to populate the Lov's based on userlogged in BOXIR3.1
i have a BEx query from which i have build a universe when I develop a report from this universe I get some default prompts coming from the bex query which has all the values from master data table now i want to limit this lovs to pouplate only those values which are specific to that user instead of all the values.
Please can you sugeest some way around for this?
Thanks,
Shashank

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

Get('XML') doesn't work, but get() does in javascript - CASCADING LOVs

I'm trying to get cascading LOVs working in Apex 3.1.0 in Oracle 11g. When I call get.get('XML') it returns null in firefox and empty string in IE6. If I change it to call get.get() then it returns the XML as a string into Javascript.
The Application process is getting called in both scenarios as i've put PL/SQL logging to disk in order to prove it. The XML being returned is very basic so i'm sure it's not a problem with formatting. I'm not getting any exceptions thrown in javascript either.
Is it possible to use get.get() and then convert the text into an XML object which is returned as per get.get('XML') which at least will allow me to get something working ?
thanks
<script language="JavaScript" type="text/javascript">
function getBusinessFieldJS(pThis, pSelect)
alert('getBusinessFieldJS');
try
var l_Return = null;
var l_Select = html_GetElement(pSelect);
var get = new htmldb_Get(null, html_GetElement('pFlowId').value, 'APPLICATION_PROCESS=GET_DATA_FIELDS_XML', 0);
/*get.add('F120_GETBUSINESSFIELD_ITEM',pThis.value);*/
gReturn = get.get('XML');
alert('gReturn=' + gReturn);
alert('gReturn.value=' + gReturn.value);
if (gReturn == null)
alert('gReturn is null');
if(gReturn && l_Select)
var l_Count = gReturn.getElementsByTagName("option").length;
alert('l_count='+l_Count);
l_Select.length = 0;
for(var i=0;i<l_Count;i++)
var l_Opt_Xml = gReturn.getElementsByTagName("option")+;+
+ appendToSelect(l_Select, l_Opt_Xml.getAttribute('value'),+
+ l_Opt_Xml.firstChild.nodeValue)+
+ }+
+ }+
+
get = null;+
+ }+
+ catch (e)+
+ {+
+ alert('Exception : ' + e);+
+
}+
+}+

Hi,
I've been trying to replicate your problem here: [http://apex.oracle.com/pls/otn/f?p=37055:1]
My application process is:
BEGIN
OWA_UTIL.mime_header ('text/xml', FALSE);
HTP.p('Cache-Control: no-cache');
HTP.p('Pragma: no-cache');
OWA_UTIL.http_header_close;
HTP.prn('<select>');
HTP.prn('<option value="-1">Please Select</option>');
HTP.prn('</select>');
END;(Just copied from your post and XML changed to xml, otherwise untouched)
And my page has a simple HTML region with the source of:
<div id="XMLOUTPUT" style="border:1px solid blue; width:200px; height:200px;"></div>
<div id="XMLOUTPUT2" style="border:1px solid blue; width:200px; height:200px;"></div>
<script type="text/javascript">
function getMyXML()
var l_Return = null;
var get = new htmldb_Get(null, html_GetElement('pFlowId').value, 'APPLICATION_PROCESS=RETURN_XML', 0);
gReturn = get.get('XML');
var d = html_GetElement('XMLOUTPUT');
d.innerHTML = gReturn;
var d2 = html_GetElement('XMLOUTPUT2');
d2.innerHTML = get.get();
var s = gReturn.getElementsByTagName("select");
alert(s.length);
</script>
<a href="javascript:getMyXML();">Click</a>Click on Click at the bottom of the page. The first DIV gets the get.get('XML') object and the second one the get.get() and a popup message tells you how many "select" items are in the XML version.
As far as I can see, this works fine.
Andy

Cascading LOV in OLAP UNIVERSE

Similar Messages

Maybe you are looking for