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

Similar Messages

Olap universe(creating new object)

All,
I am using bo 4.0 version and i have created an olap universe on top of bex query.i am new to olap universe.
I have a need to create a new customized object in my olap universe out of two existing objects.As of now i am creating variables in my webi report generated out of the olap universe to fit my need.Instead i want to create a condition object or some kind of object in the universe itself.
how can i do this?Any ideas or suggestions.
For ex:
my requirement looks like this,not exactly the same as indicated below but similar.
existing objects
city object has certain values 'hyd','new york'
currency objecthas 'rupee','dollar'
new person object out of the above mentioned existing objects
if city='hyd' and currency='rupee' then 'indian' else 'non indian'
how can i do this?Any ideas or suggestions.
Regards,
Reji.
Edited by: reji2011 on Dec 7, 2011 11:10 PM

Hi,
there's a function builder / formula editor in Universe Designer, with OLAP universes this uses MDX syntax with XML markup.
to build up some logic, you need to use the "IIF" operator.
regards,
H
p.s. in BI 4.0, route-one should be the BICS BEx connection, not the OLAP .unv ..

SAP BW Universe OLAP @prompt LOV using object reference not working

I have tried to follow Didier MAZOUÉ's "[OLAP universes best practices|https://boc.sdn.sap.com/node/20081]" document to create calculated measure in a OLAP universe built on top of a BW cube directly. The objective is to get the revenue figure from the same period of the previous year. I wanted to be able to have a LOV to specify a period when the object is used in a webi report.
When I hard coded the LOV as a data set as displayed in the following example ( {'[CD2007009]','[CD2007010]'} ) The prompt worked as expected.
(PARALLELPERIOD(.[LEVEL01],1,[0FISCPER].@Prompt('Period?',A,{'[CD2007009]','[CD2007010]'},mono,free)),[Measures].[0G_AERLOS])</EXPRESSION>
When I build my expression using an object referece as ( 'TimeFiscal year period' ), I was given an error msg saying "invaid prompt definition". I verified my spellings and syntax and they were correct based on the examples provided by the best practice document.
(PARALLELPERIOD(.[LEVEL01],1,[0FISCPER].@Prompt('Period?',A,'TimeFiscal year period',mono,free)),[Measures].[0G_AERLOS])</EXPRESSION>
Is there anything obvious that I missed. Or there are some extra configuration I have to do on SAP BW or Universe side?

Hi Mr. MAZOUÉ,
After a few days of struggling with this particular prompt issue, I finally figured out what was wrong with it. The object reference in the @prompt function is not able to process object references in a subclass correctly.
For example:
@Prompt('Period?','A','TimeFiscal year periodL01 Fiscal year period',mono,free)
The 'Fiscal year period' is a subclass under the main class 'Time'. If you use this prompt function in a MDX expression, it parse correctly. But it generates a prompting failure when referencing the object with the embeded prompt function in a webi report.
However, if I move the 'L01 Fiscal year period' object underneath the 'Time' class and change the prompt as @Prompt('Period?','A','TimeL01 Fiscal year period',mono,free). I was able to get a list of values when I designed a webi report using the object.
This seems to me is a limitation from the current OLAP Universe implementation.
Looking forward to your feedbacks!
thanks

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

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

Create new object (measure) with IIF function on BW Olap universe:mdx error

hello
i have a universe based on a BEX query
i want to create a new object (a measure) with the IIF(,,) function
i created the following select:
<EXPRESSION>IIF(@Select(Currency Type\CurrencyTypeCode)="10",@Select(Key Figures\RevenueGlobalCurrency),@Select(Key Figures\RevenueLocalCurrency))</EXPRESSION>
defined as number
where
CurrencyTypeCode is a dimension (character format)
RevenueGlobalCurrency and RevenueLocalCurrency are measure (number format)
i always have a parse which is OK but
when i want to use the object on a webi report i always have an MDX error : ...invalid MDX with .... (WIS 10901)
and advise ?
Thanks

Hi Didier,
Thanks a lot for your help.
Now it works : i do not understand why
i explain:
the correct syntaxe of my new measure is :
<EXPRESSION>([Measures].[4FVLHG7OAJMNY9WC06X6JLOZQ], [0CURTYPE].[10])</EXPRESSION>
it does not works with my "L01 currency type" BO dimension
([0CURTYPE].[LEVEL01])
when i had :
-my universe is based on a BW BEX query
-my universe has been automaticaly generated with the assistant
-the Currency Type Class was define as below:
       - 1 BO dimension object : L01 Currency Type =>
[0CURTYPE].[LEVEL01]
       - 3 BO detail objects : L01 Currency Type techName =>
[0CURTYPE].[LEVEL01].[TECH_NAME]
                                          L01 Currency Type Key =>
[0CURTYPE].[LEVEL01].[[20CURTYPE]].[Value]
                                         L01 Currency Type Long Name =>
[0CURTYPE].[LEVEL01].[[40CURTYPE]].[Value]
i always had a wrong mdx syntax error on the webi report
i updated the class with the follow
     - 1 BO dimension object : L01 Currency Type =>
[0CURTYPE].[LEVEL01] (idem)
       - 3 BO detail objects : L01 Currency Type techName =>
[0CURTYPE].[LEVEL01].[TECH_NAME] (idem)
                                          L01 Currency Type Key =>
[0CURTYPE].[LEVEL01].[NAME] (updated)
                                         L01 Currency Type Long Name =>
[0CURTYPE].[LEVEL01].[DESCRIPTION] (updated)
then it was working
Then i tried to reproduce from scratch and now it also works with the previous version of the class.
I do not understand anything
Is there something like a cache file of the MDX query (in RSRT, cache mode is set to inactive for the bex query) ?
ps: this is the same if a use webi under infoview (java) or webi rich client...
Edited by: Frederic Nez on Jan 19, 2010 6:35 PM
(edit : there is mistake in the post : objects are always between [] even if it is not dispay => change objects to code mode)

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

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

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.

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

BW OLAP universe object with Aggregate

How to create an BW OLAP universe object with Aggregate to a higher level than the underlying query?
The objective is to synchronize 2 queries by Contract Agreement quantity range and part of the calculation is to obtain the contract total quantity in one of the queries that is by Year and Month. For that query I need the total quantity for the contract.
Example;
Contract #    Year    Month     Qty
1             2011    1         230
6             2011    2          50
14            2011    3         124
u2026
25            2011   12          87
                 Total Qty --> ?
The following syntax gives the total quantity by contract / Year / Month, not the overall contract quantity. I could not find any MDX reference to use to solve this.
The dimension is [0SALESDEAL].[LEVEL01]
<EXPRESSION> AGGREGATE({[0SALESDEAL].CurrentMember:[0SALESDEAL].CurrentMember},[Measures].[DBKTD232QCONV8CVZYB17B5P0]) </EXPRESSION>
Thanks,
Marco
Edited by: Marco R on Dec 6, 2011 3:25 AM
Edited by: Marco R on Dec 6, 2011 3:27 AM
Edited by: Marco R on Dec 6, 2011 3:31 AM
Edited by: Marco R on Dec 6, 2011 3:33 AM
Edited by: Marco R on Dec 6, 2011 3:35 AM

Hi Andrew,
Looking at your statement I get the feeling you want this as a dimension/characteristic.
Since an expression has to be numeric and a characteristic in BW cannot be numeric, this will not work.
Only measures/keyfigures are possible.
The direction from SAP is to push any modeling to the BW query or even BW itself.
Hope this helps,
Marianne

Restrictions on Measure Objects..in Universe

Hello Everybody,
I am trying to apply Restrictions on Measure Objects based on a Financial Year rather than a Calender Year.
For example: I am trying to find Total Sales for a Financial Year( that may be like 01/06/2008 to 31/05/2009) not the regular Calender Year( 01/01/2008 to 31/12/2008)...
But i am unable to figure it out, how to do it exactly in Universe...
Any Suggestions or any peace of information is really appreciated...
Thanks
Raghu...

Hi,
Here is a sample with "Calendar Year/Month" characteristic. The calculation is the aggregation from September 20005 to July 2006.
You have to write an expression such like this:
<EXPRESSION>Aggregate({[0CALMONTH].[200509]:[0CALMONTH].[200607]})</EXPRESSION>
Regards,
Didier

Edit an object's select statement of OLAP universe SAP BW

Hi everybody
I am new at working with Olap Universes BW, and I have to edit one universe SAP BW, I don't know if I can to use substring function on a select statement, for example substring([0D_DIV].[LEVEL01],5,5), I try to use this function but I have a error,
Could you help me? I need to returns part of a string, is correct to do it on a universe or is better to do at BW.

Hi,
First of all I recommend you read the documentation that gives you information about OLAP universes and especially SAP BW universes.
I also recommend to download documents related to SAP universes deployment, administration and customization:
[OLAP Universes - how to samples and recommendations |https://wiki.wdf.sap.corp/wiki/display/globalregions/OLAPUniverses-howtosamplesand+recommendations]
[SAP Integration |https://wiki.wdf.sap.corp/wiki/display/globalregions/SAP+Integration]
Now you can customize expression using MDX in OLAP universes. MDX expressions must be enclosed with <EXPRESSION></EXPRESSION> XML tags.
Unfortunately SAP BW MDX does not support calculations that return string or date values.
The onlyway to return string is to use NAME or UNOIQUENAME attribute.
See answers I already in the forum: [Forum answer |Re: Create new dimension on top of SAP BW data]
Regards
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

What is the use of creating a detail object on a measure.

Hi Experts,
In BI 4.X business layer, we can create a detail object of a dimension and as well as measure.
Can you please let me know what could be the use of the detail object of a measure object?
In the business layer, it is showing like this...
<Measure object>
-><Detail Object>
Dimensions have attributes, we create those attributes as details objects.
when we want to see the different grains of the measure in one report. we will use these details objects.
Example:
1. Query 1 returns country, sales revenue
2. Query 2 Returns Country,State,Sales revenue.
But in the report if we want to show the State wise Revenue. It is not possible bcz both the quires are returning different grain.
state object is incompatible object, so you can't drag the object into report.
in this scenario we will merge the Country dimension , create the state object as details with merged dimension, then you can drag the state details detail object.
this will give expected results Country and State wise revenue.
Normally Dimensions and details objects will drives the measures values in report.
So, Detail object on measure not helpful in case of relational database(Please correct me if i am wrong). It is useful only for OLAP database because when I have created a webi report on top of BEx query then it is automatically created a detail object on measure object.
As far I know, 'Measure attribute' introduced for OLAP based business layer. which can provides information for the formatted value like unit, currency or value.
For example:-
Amount is key figure in BEx query and when I have created Webi report on top of that then it will create three object.
1. Amount as meausre.
->2. Amount currency(detail).
->3. Amount formatted value(detail).
Below is the output after running the report.
Amount || Amount currency || Amount formatted value
30 || $ || 30.00
8 || $ || 8.00
I have found one difference, We can't implement the index awareness on detail object which we have created on measure object although we can implement the index awareness on detail object which we have created on top dimension object.
But Still I am looking for good example of Detail object on measure object..
Any thought would be welcome...
Thanks,
Sachin

I moved this to the Semantic Layer space for faster response.

Olap universe lov restriction on detail object key

Similar Messages

Maybe you are looking for