MSAS OLAP Universe Pre Defined Filter

Hi:
We have a Universe based on a MSAS cube. The cube has only three time u201Cdimensionu201D objects u2013 Year, Quarter and Month. All come across as Character data types. The Month object displays the year and the month concatenated together (2009.JUL, for example). What we need to do is to create a pre defined filter in the Universe that will always give us the data for rolling 16 months. So, for example, if we run the report in July, the data would be for April 2009 through July 2010 u2013 of course, if the report is run next month in August, the data would be for May 2009 through August 2010. If anyone can offer any help in what the pre defined filter in the Universe would look like, that would be much appreciated.
Thanks!

Hi Didier:
Thanks again for your response u2013 the revised filter works without any syntax errors.
There are two problems. Firstly, we need it to dynamically calculate the 16 month period based on the month when the query is run, instead of prompting the user to enter the ending period as it does now.
Secondly, the dates that it brings back donu2019t appear to be correct. Here is what it brings back, if July 2010 is entered for the prompt:
2009.MAR
2009.MAY
2009.NOV
2009.OCT
2009.SEP
2010.APR
2010.AUG
2010.DEC
2010.FEB
2010.JAN
2010.JUL
What I would expect it to bring is the following:
2009.APR
2009.AUG
2009.DEC
2009.JUL
2009.JUN
2009.MAY
2009.NOV
2009.OCT
2009.SEP
2010.APR
2010.FEB
2010.JAN
2010.JUL
2010.JUN
2010.MAR
2010.MAY
Here is the exact Filter that I am using:
<FILTER EXPRESSION="IIF([Time].[H1].currentmember.member_value <= STRTOMEMBER("@Prompt('Select period','A','Time\Month',Mono,primary_key,Persistent)").member_value AND [Time].[H1].currentmember.member_value >= STRTOMEMBER("@Prompt('Select period','A','Time\Month',Mono,primary_key,Persistent)").lag(16).member_value ,1,0)">
<CONDITION OPERATORCONDITION="Equal"><CONSTANT CAPTION="1"></CONSTANT></CONDITION></FILTER>
Also, it does not seem to change the number of months returned even if I change the lag(16) to lag(15).
BTW, I installed the Adventure Works cube and tested the query there u2013 it works as expected when I use it there, as you had suggested in thefirst example you gave me.
Thanks again for your help with this.
Regards,
Nishant.

Similar Messages

Issues in creating a Pre-defined filter in Universe

Hello Everyone,
Here is the problem...
The idea is to have a prompt (Prompt1) to allow user select the Input type ..ie."Check Number or Invoice Number". There is the second prompt (Prompt2) which will allow user to input a value. Based on Prompt1 value, the prompt2 input should be evaluated against Check Number object or Invoice Number Object.
This is using a universe based on a BEx query.
Following useful information in the OLAP universe Best practice doc available [here] which Ingo once shared with us [on this forum], I created following pre-defined filter in my universe.
<OPTIONAL><FILTER EXPRESSION="IIF(@Prompt('Select Input type','A',{'Check','Invoice'},mono,free)='Check', [ZFIAP_IS1___F20].[LEVEL01],[ZFIAP_IS1___F46].[LEVEL01])"><CONDITION OPERATORCONDITION="Equal"><CONSTANT TECH_NAME="@Prompt('Enter Check or Invoice Number','A',,mono,free)"/></CONDITION></FILTER></OPTIONAL>
Where [ZFIAP_IS1___F20].[LEVEL01] = Check Number & [ZFIAP_IS1___F46].[LEVEL01] = Invoice number.
The object is parsing without errors in the universe. But when I use it in my report, the report throws an error " failed to execute with the error Invalid MDX command with " "
I took the MDX statment and tried to run/debug using MDXTEST and could never get it to work with the above objects. It was seen that the filter created in such a way is handled [Measures] object which only accepts Numeric values and not Strings. Where as my Check number and Invoice Number values are strings. The MDx statement is given below.
Has anyone experienced this issue earlier ?
WITH MEMBER [Measures].[4C46B176-CC15-DF11-92,5D,25,C2,A9,6F,0,0] AS ' IIF(Check=Check, [ZFIAP_IS1___F20].[LEVEL01],[ZFIAP_IS1___F46].[LEVEL01]) ' SELECT { [Measures].[4GQZ1D26O6QATUDY32CGL1C38] } ON COLUMNS , NON EMPTY FILTER( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( CROSSJOIN( [ZFIAP_IS1___F93].[LEVEL01].MEMBERS, [ZFIAP_IS1___F94].[LEVEL01].MEMBERS ), [ZFIAP_IS1___F92].[LEVEL01].MEMBERS ), [ZFIAP_IS1___F71].[LEVEL01].MEMBERS ), [ZFIAP_IS1___F55].[LEVEL01].MEMBERS ), [ZFIAP_IS1___F46].[LEVEL01].MEMBERS ), [ZFIAP_IS1___F20].[LEVEL01].MEMBERS ), [Measures].[4C46B176-CC15-DF11-92,5D,25,C2,A9,6F,0,0] = 0000041924670) DIMENSION PROPERTIES [ZFIAP_IS1___F55].[2ZCCNODE01], [ZFIAP_IS1___F55].[2ZCCNODE02], [ZFIAP_IS1___F55].[2ZCCNODE03] ON ROWS FROM [ZFIAP_IS1/QZFIAP_BOUNV2]
Edited by: vaibhav patil on Feb 11, 2010 9:53 PM
Edited by: vaibhav patil on Feb 11, 2010 9:55 PM

Hi,
In fact, what you are requiring is feasible in Microsoft Analysis Services by defining a calculated meaure and a filter using this calculated measure.
Unfortunately, due to MDX restrictions in SAP, it is not possible to do it in universes.
I suggest that you create a range variable on Time to allow the user to only retrieve the dates needed.
You can retrieve all the dates and then apply a filter in Web Intelligence document: this solution might have the disadvantage to retrieve more data than necessary.
Didier

Pre-define filter for query in a BEx Report

Hi all experts, I have a question, I have created a report with WAD and Query Designer, and I need a pre-define filter for different user or different role. Anyone knows where should I set this pre-define filter to the query ? In the WAD itself, or must do it in backend ? My scenario is, lets say User A login to this report, he will have value A, B, C as filter value in characteristic Z, User B login to this report, he will have value D, E, F as filter value in characteristic Z. Perhaps you guys can understand what I trying to say.

Hi,
You can set a customer exit variable on characteristics Z. the value for Variable is populated in customer exit written in CMOD using I_STEP = 1.
You also need to maintain a mapping table for value of characteristics Z to user. Now if user A checks the Report, using the sy-uname you lookup to the mapping table and get the corresponding values of characteristics Z and populate the default value of the variable or straight away restrict it in the query by not making it ready for input.
Hope it helps....
Regards,
Umesh

Error in webi against MSAS OLAP Universe

Hi,
We have an OLAP universe against MSAS 2008. We are at BOXI3.1 SP2. I am wondering if anyone has seen this error before
"expression contains a function that cannot operate on more than 4,294, 967,296 tuples WIS10901".
We get this error when we create a webi report against the universe. The only thing unique about this report query is that it has a few numerous query filters - but then the only way this error makes sense is if BO is creating MDX against multiple sets of data and then combining that based on these additional filters ( a bit different behavior than what we might expect in a relational DB with multiple query filters).
Any suggestions on how to navigate this issue? thank you in advance.
Regards
Edited by: ramaks on Jan 12, 2011 12:02 PM

Hi,
I am not sure if it is the same problem, but I had similar issues with measure objects coming out of the universe that were defined as "database delegated" in the universe object's properties. Basically it then forces you to always refresh when you have changed anything on the report, so that it can recalculate the measure. I am not aware of differences regarding this in Rich Client vs. InfoView, but there could be. I have seen other similar issues between the two before.
Check to see if the measures are database delegated, and change them if you can to sum or count or whatever they should be.
Hope that helps.

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.

MDX syntax for current year in a Pre-defined condition

Hi,
I'm looking for assistance in building a Pre-defined condition in a universe based on an MSAS 2005 OLAP cube, that only returns the current year.
My year is defined as [Time Accounting].[Accounting].[Accounting Year]
I can create a Pre-defined filter that accepts a constant value as follows:
<FILTER KEY="[Time Accounting].[Accounting].[Accounting Year]">
     <CONDITION OPERATORCONDITION="Equal">
          <CONSTANT CAPTION="2008"/>
     </CONDITION>
</FILTER>
and it works fine, however, I would like to make it dynamic.
There is an attribute called current year that is defined as [Time Accounting].[Accounting Year].[Accounting Year].[Current Year].[Value] but when I try and put this into my pre-defined filter nothing is returned:
<FILTER KEY="[Time Accounting].[Accounting].[Accounting Year]">
     <CONDITION OPERATORCONDITION="Equal">
          <CONSTANT CAPTION="[Time Accounting].[Accounting Year].[Accounting Year].[Current Year].[Value]"/>
     </CONDITION>
</FILTER>
Is this possible? What am I doing wrong?
What I'm ultimately aiming for is a rolling 12 month condition.
Thanks,
Colin

Hi,
In OLAP universe, you cannot define a filter with CAPTION = another universe object.
What you can do is CAPTION = String or CAPTION = @Prompt.
By the way, if you want to achieve what you are requiring, I suggest you create a calculate expression such as:
<EXPRESSION>
IIF([Time Accounting].[Accounting Year.].CurrentMember.Properties("Name") = [Time Accounting].[Accounting Year.].CurrentMember.Properties("Current Year"), 1, 0)
</EXPRESSION>
Then you can define your filter on your new calculated expression and the operator to Equal and CAPTION = 1
Didier

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

Calendar Prompt in OLAP Universe does on resolved.

Hi,
I am using BO XI 3.1 with latest fix pack.
I have created a OLAP universe based on SSAS 2005 Multicube for reporting using WebI.
I have a date field in my database but when i but when i created a Universe based on that cube the date field became of type STRING. One of my requirement is that i want a calendar popup in my WebI report when i create a filter on top of that date field.
So i manually changed the type to Date format in Universe Designer in order to see the calendar popup in webi report.
My concern is when i select a date value from the calendar it does not work and i cannot see the data for that date if though the data exist for that. But when i manually enter the date value for that filter changing back the data type as CHaracter in the Universe it works and i can the see the data . The date format i am using is M/D/YYYY which is the same as calendar prompt.
Why we notice this such behavior for the date field in the WebI and every time i want a calendar prompt i have to change the date type to Date and if i have to manually enter i have to change to Character.
Kindly suggest .
Regards,
Vibhav.

Hi,
this forum is about the Integration Kit for SAP and you are referring to a MSAS OLAP Universe. Would suggest you enter this in the Universe forum.
regards
INgo Hilgefort

MDX for OLAP Universe.

Hello!
I have a scenario wherein I have to create a custom dimension restricting some values to be displayed. The dimension I am trying to restrict here is Quarter - [ZCALQRT].[LEVEL01], which has values like Q3 2011, Q4 2011, Q1 2012,Q2 2012 on a rolling quarter basis. My requirement is to restrict the last quarter to be displayed. I have tried the following menthods to achieve this:
1) Create a new dimension object with the following syntax:
<EXPRESSION>
WITH MEMBER [Measures].[Delta] ASu2019
[Measures].[4J68GNRER52B7BV68B1GHWUA8]-[Measures].[4J68GNC1P7UW62S9WMWRXSWUO]u2019
SELECT
{[Measures].[4J68GNC1P7UW62S9WMWRXSWUO],[Measures].[4J68GNRER52B7BV68B1GHWUA8], [Measures].[Delta]} ON COLUMNS,
NON EMPTY {[ZCALQRT].[LEVEL01].members} ON ROWS
FROM [$Y_ZAPOH]
WHERE (EXCEPT([ZCALQRT].[LEVEL01].[[2ZCALQRT]].[Value],[ZCALQRT].[LEVEL01].[[2ZCALQRT]].[Value].CurrentMember.LastSibling))
</EXPRESSION>
So, here I tried to restrict the dimension in the where clause using the EXCEPT(,) function. But on using this new custom dimension in Web I the error message I receive is "Some objects are not available in the Universe".
2) Create a restriction for the object in the where clause:
<EXPRESSION> (EXCEPT([ZCALQRT].[LEVEL01].[[2ZCALQRT]].[Value],[ZCALQRT].[LEVEL01].[[2ZCALQRT]].[Value].CurrentMember.LastSibling))</EXPRESSION>
This gives and error message with MDX syntax being invalid.
Can anyone please suggest a work around for restricting the dimension in the SELECT/ WHERE clause or a PRE-DEFINED FILTER.
Any inputs are highly appreciated.
Thanks,
Vivek.

Hi Ingo,
Thank you for the information. I will try doing that in the SAP BEx query end. However, I found some examples with the MDX which can filter the members based on their levels. One specific example of referring to a member is as follows:
If I need to exclude the last value in a rolling value set, I tried to use the EXCEPT(,) function and referring the member in a predefined filter:
<EXPRESSION>EXCEPT([0CALQTR].[LEVEL01],[0CALQTR],[LEVEL01].CurrentMember.LastSibling)</EXPRESSION>
Can you please suggest if anything is wrong with this MDX statement?
Any inputs are highly appreciated.
Thanks,
Vivek.

OLAP Universe Filter for Constant

Hello
I am trying to create a universe filter. We have a BO OLAP Universe on top of MSAS 2008. We are at BOXI 3.1 SP2/FP2.2
<FILTER KEY="[Date].[Calendar Date].[Date]"><CONDITION
OPERATORCONDITION="InList"><CONSTANT
CAPTION="[Today].item(0).MEMBER_CAPTION"/></CONDITION></FILTER>
Where [Today] is a calculated member.
This one parses fine, however when it comes to MDX which i capture via
profiler
WITH SET NS28B9BE741FD446A5A0414EA718F8FC_0 AS Filter([Date].[Calendar
Date].levels(4).allmembers,((([Date].[Calendar
Date].currentmember.properties("CAPTION")="[Today].item
(0).MEMBER_CAPTION"))))
SELECT { [Measures].DefaultMember } ON COLUMNS ,
NS28B9BE741FD446A5A0414EA718F8FC_0 DIMENSION PROPERTIES
MEMBER_UNIQUE_NAME, MEMBER_CAPTION ON ROWS FROM [My Cube]
This returns empty. However it works fine and returns value if i remove "" wrapping
[Today].item(0).MEMBER_CAPTION and run this query in SQL Server Management Studio ( MDX query)
However i cannot introduce the same in the filter - if i try it gives
me a parse error.
i.e the following doesnt help
<FILTER KEY="[Date].[Calendar Date].[Date]"><CONDITION
OPERATORCONDITION="InList"><CONSTANT
CAPTION=[Today].item(0).MEMBER_CAPTION/></CONDITION></FILTER>
Can you kindly advise if you have seen similar errors and what i can do possibly in this case to workaround this?
Edited by: ramaks on Oct 26, 2010 2:35 AM
Edited by: ramaks on Oct 26, 2010 2:36 AM
Edited by: ramaks on Oct 26, 2010 2:37 AM

Hi Didier,
Thank you for your response. That was exactly my original design - but it has performance implications for us. Please see an earlier thread of mine.
Query Performance in OLAP MSAS Universe using Filter
In this Case the MDX will become as below.
Which means every additional dimension i add creates multiple cross joins, and the filter will go through all possible cross-join combination to filter out that one record for that particular date. My original thread explains this more clearly.
Is there no other way to implement such a filter?
WITH
MEMBER [Measures].[2FF3DF31-5D02-4A9B-A8,BC,E7,25,C2,30,1B,61] AS
    IIF
        [Date].[Calendar Date].CurrentMember.Properties("CAPTION")
      =
        [Today].Item(0).Member_Caption
     ,1
     ,0
SELECT { [Measures].DefaultMember } ON COLUMNS ,
,NON EMPTY
    Filter
              CrossJoin
            AddCalculatedMembers
              [Date].[Calendar Date].[Date].MEMBERS
      [Measures].[2FF3DF31-5D02-4A9B-A8,BC,E7,25,C2,30,1B,61] = 1
DIMENSION PROPERTIES
MEMBER_UNIQUE_NAME, MEMBER_CAPTION ON ROWS FROM [My Cube]
Edited by: ramaks on Oct 26, 2010 4:26 PM

Error: pre-defined filters are no longer available in the universe

Hi All,
I'm getting following error message while schedule the webi report .
"Some pre-defined filters are no longer available in the universe. See your Business Objects administrator. (Error: WIS 00003) ".
I have migrated the universe and reports from XIR2 to XIR3.1 ; and getting above error in XI3.1 , its works fine XIr2.
Based on this error i have checked the Predefine filter in universe and its available . but report shows error.
Also i have created the new conditions with different name and added into report. but again i getting same error while schedule the report
However reports run fine after changed the sql mode as custom sql with same sql from objects and conditions.
Could you please anyone help for this issue?
Advance Thanks
Ponnarasu

Hi SC,
Thanks for your reply . our version 12.3.6.1006. X1 3.1 was installed with SP3 .
Anyway this issue is resolved via following method.
I have created the new universe ( Create new universe and copied schema and objects from exiting universe ) and exported in to universe folder . All related reports query changed to new universe. Now reports runing fine and without error.
Thanks
Ponnarasu

How create filter in olap universe with MDX LIKE Function

Hi all
I need to create a filter in a olap universe with the LIKE MDX function.
Problem:
There is a dimension with account numbers whit 10 digits like this: 5683492703 and i need to create a filter whit all account numbers whit the number 7 in the sixth position in a olap universe.
How to do this?
Thanks all

Try like this :
<FILTER KEY="[Level Object Definition]">
     <CONDITION OPERATORCONDITION="Like">
          <CONSTANT CAPTION="_____7*"/>
     </CONDITION>
</FILTER>
Not sure if it is _ or ? to represent a single character. Try ? in place of _ if the above code doesn't work.
Regards

OLAP Universe - Filter Expression

Hello,
Can anyone help me in how to write below filter expression in OLAP universe filter expression:
(PeriodType NOT IN (0,2) or EntryPeriod=(CASE when Company in ('PH','AU') THEN '200800'
when Company in ('AE','BR') THEN '201000'
when Company ='LV' THEN '201100'
END)) and (Journalcode NOT IN ('YTI','PROD'))
and SubledgerTypeCode = 2 AND LetteringDate IS NULL
and EntryDate <= @Prompt('Please Select as on Entry Date','d',,MONO,FREE)
Your help on this will highly be appreciated.
Thanks in advance!
Regards,
Pallavi

Use Aggregate() function in place of sum for the Rolling Calculation. Eg:
<EXPRESSION>Aggregate( {[0CALMONTH].CurrentMember:[0CALMONTH].CurrentMember.lead(@Prompt('Numb
er of Months','N',,mono,free))},@Select(Measures\Amount))</EXPRESSION>
Regards,
Rohit

OLAP universe filter with pattern matching.

Hi,
I tried to create both a qaaws and a webi report which contained a filter with pattern matching on an olap universe . When I ran this it took too long to be usable. I found note 1500666 which says that pattern matching is not supported in MDX and to use BEX query variables instead.
I have created a bex query with a variable which has "Variable Represents" set to "Selection Option". I can run this query and using the search option I can do a pattern match search. I have built a universe based on this query but the filter that gets created automatically in the universe uses a "Between" operator.
Does anyone know if it is possible to change the definition of the filter in the universe so that it does a pattern match search and if so how?
The end result is that I would like to be able to do a pattern match search on the text description of a BW employee object.
Thanks
Quentin.

It would be better if you post the Filter definition here...
And why don't you do Pattern matching at BO query panel level??
Where you can find Matches pattern operator to do same stuff.
Thank You!!

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

MSAS OLAP Universe Pre Defined Filter

Similar Messages

Maybe you are looking for