Universe on BEX query - Measures Question !!

Hello All,
I am building a Universe on BEx Query.
We have the following environment:
SAP BOE XI 3.1 SP2 FIX Pack 2.5
Integration KIT SP2 FIX PACK 2.5
SAP BW 701 Level 6
I see that in the BEX query the KF have technical names as "ZZRKF_Amount".
But, when this query is brought into Universe, I see the tech names as
[[4J922TWKO24NHTROOEY3WXK72]].[[4J922URARWJHKBXHBR7H15F26]]
I would like to see this as [[MEASURE]].[[ZZRKF_Amount]].
Does anyone know how to do it?
Your help & time is appreciated.
Thanks

Hi,
In the Universe Designer, select Tools ->options. In the OLAP tab, there is option to select as generate technical names as details.
I guess this may help you.
If still facing the same issue, then follow the user guide from the below link:
http://help.sap.com/
-Noor.

Similar Messages

BO Universe on BeX Query in Lumira

Hi All,
I have a requirement of accessing a BeX query in Lumira and do visualizations on it. As Lumira is not capable of accessing BeX query directly, I think, I would need to create a universe on InfoCube, for that BeX query, and then consume that universe in Lumira. Thereafter, I would need to create different datasets for different queries.
Now, I have two questions:
1. Is this approach correct? Is there any other more efficient methos than this?
2. Can I create a universe on BeX query directly? Is it possible?
When I'm following first approach (universe on InfoCube using IDT) and trying to consume that universe in Lumira, I am getting below error:
And when I'm following 2nd approach (universe on BeX query using UDT), I am not able to view that .unv in List of Available universes in Lumira.
Please help.
Thanks Much,
Purnima

Explanation on the error you faced:
The data acquisition of medium-large, large, and very large datasets from UNV or UNX universes is not supported on default installations of both SAP BusinessObjects Business Intelligence platforms 4.0 and 4.1.
It is recommended for customers that want to acquire such datasets to install a SAP BusinessObjects Business Intelligence platform (SAP BIP) server dedicated to SAP Lumira and significantly increase the value of the Maximum Character Stream Size of the Web Intelligence Processing Server on that particular server. Note that increasing this value on a running SAP BIP server can impact the memory consumption and performance of any BI clients tool running on that installation, particularly Web Intelligence. While this practice is not formally discouraged, we advise customers implementing this solution that they might face memory consumption increases and longer document data refreshes so they will need to monitor the SAP BIP server's behavior adequately to control the impacts.
Can you try to place some filters to limit the data volume retrieved?
Best regards
Antoine

Cnnection error while creating universe on Bex Query in BW

Hi
I am getting connection error while connecting to BW Bex query.
The error i am getting while creating universe is A runtime exception has occured Error getting levels for hierarchy dimension .....:Unknown error.
After this
Also while creating universe no key figures/measures are getting generated from Bex query to designer.
Also in Bex query which are created as mandatory variables comes as Prompts in webi.
But when I try to parse in Condition filter it is throwing error.
Currently that mandatory variable is From Date and To Date
Is we require to change the prompt syntax in Condition filter.
Also kindly suggest solution for Connection error as impemtation is getting affected.
Regards
Gaurav Mang

Hi
R u saying allow external acces in BEX query.This option in Bex Query designer.
Or In whether while creating universes under properties tab there is use of OLAP universes option has to be made to Yes.
This both things we have tried
Let me know any other option to be tried.
Regards
gaurav mang

Universe on Bex Query with Condition

Hi,
I'm working on creating a WebI version of a Bex Report. I've created a universe on top of the Bex Query and then a WebI report based on the Universe. The Bex Query contains 4 conditions. They allow optional filtering of two measures, Less Then or Equal and Greater Then or Equal. The conditions are applied at the employee level of the results set, so for example, if an employee's total sales is greater than 50 and the user enters 50 for the condition then none of that employee's rows of data will appear.
A single filter was created in teh Universe containing all four conditions. I had to update the syntax as they were all brought in using Equals instead of the GreaterorEqual and LessOrEqual. I also updated the filter key to use the @Select and the correct dimension.
In the WebI report, only the two using LessOrEqual are functional. The two conditions that utilize GreaterOrEqual will only remove individual rows, not the enter set of rows for that employee. I've set the aggregation to sum instead of Database Delegated for the two affected measures.
If anyone has any input on how to get the GreaterOrEqual conditions functioning properly, or a workaround that will remove all rows for an employee when their sales are not above a cert number, it would be greatly appreciated.
Thanks,
Jeff

Also here is the syntax for one of the filters that is not functioning properly.
<OPTIONAL><FILTER KEY="@Select(Total Quantity of Adjustments\Total Quantity of Adjustments)"><CONDITION OPERATORCONDITION="GreaterOrEqual"><CONSTANT CAPTION="@Prompt('Minimum Quantity of Adjustments','N',,mono,free)"/></CONDITION></FILTER></OPTIONAL>

Creating a Universe on Bex Query --- Information Design Tool 4.0

Hi,
I am creating a Universe on a BeX Query, based on my understanding from the documentation i dont have to create a data foundation layer and i can directly call the connection in the Business Layer.
when I create a business layer and select OLAP connection (BICS connection), I get an error "this connection is not supported".
I was trying to look for a solution but i haven't found anything yet. Did anyone else encounter this issue. Please Share.
Regards,
Sheikh Hassan Ayub

HI there,
I read somewhere that the support for BEx Queries are done via Relational Connection. However, the BICS connection is only available via OLAP connection.
I was able to successfully create an OLAP Connection with BEx Queries. However when I do a Business Layer with this OLAP connection it says ERROR, not supported.
I havent tested creating a relational and thus having a Data Foundation yet as I am still have issues with my installation with ports.
Anyway, let me know if you are able to create a relational connection.
I'd be interested to hear your experience.
Regards,
Iris
P.S. the connection needs to be published.
Edited by: Iris Co on Nov 2, 2011 6:18 PM

SubStr function in Universe on BEx Query

Hi SAP BO experts,
We have a universe based on SAP BEx Query with an object "WBS Element", a 24 Character field from which we need to resolve certain sections as different objects for reporting purpose. One of the objects required is first 8 chars (WBS Project No.) Following code is used in object definition.
<EXPRESSION>Substr(@Select(WBS Element\WBS Element), 1, 8)</EXPRESSION>
Parsing is OK at universe level.
Webi query without "WBS Project No" is running OK but when "WBS Project No" is used, I get an error - invalid MDX command (WIS 10901).
What is the correct syntax? Any input will be appreciated.
Thanks in advance.
Venkat

You can-not return characteristics via <EXPRESSION> tag.
In fact right now it is not possible to do substring and similar operations. You can only create objects which returns numeric
value.
Regards,
Rohit

IIF not accepting Dimensions in a OLAP Universe using Bex Query

Hi,
We have an issue with Prompted object , u2018IIFu2019 expression is not taking dimension object in u2018Thenu2019 clause, it takes only the measure object.
Below are the two expressions one with measure and other with dimension, object with measure works fine and dimension doesnu2019t.
Dimension u2013 Prompted trend (Fails with Error)
<EXPRESSION>IIF(@Prompt('Select a time period trend view','A',{'Fiscal_Year','Fiscal_Year_and_Quarter','Fiscal_Year_and_Month','Calendar_Year', 'Calendar_Year_and_Quarter','Calendar_Year_and_Month'},mono,constrained)= Fiscal_Year,@Select(Fiscal Dates\Fiscal Year),A)
</ EXPRESSION >
Measure u2013 Prompted trend (Works fine)
<EXPRESSION>IIF(@Prompt('Select a time period trend view','A',{'Fiscal_Year','Fiscal_Year_and_Quarter','Fiscal_Year_and_Month','Calendar_Year', 'Calendar_Year_and_Quarter','Calendar_Year_and_Month'},mono,constrained)= Fiscal_Year,@Select(Actuals\Actual Amt (Local)),0)
</EXPRESSION>
Has anyone tried to do this in a different way
Thanks,
Anu

Hi,
just to let you know - not overlooked - will look into this.
Ingo

Dynamic Prompts in Universe using BEx query

hi,
We have create an object in BO Universe using @prompt. the formula goes like this.
<EXPRESSION>IIF(@Prompt('Enter Currency','A',{'USD','EUR','GBP','JPY','AUD','LOCAL_CURRENCY','DOCUMENT_CURRENCY'},mono,constrained)= USD,@Select(Actuals\Actual Amt (USD)),IIF(@Prompt('Enter Currency','A',{'USD','EUR','GBP','JPY','AUD','LOCAL_CURRENCY','DOCUMENT_CURRENCY'},mono,constrained)= EUR,@Select(Actuals\Actual Amt (EUR)),IIF(@Prompt('Enter Currency','A',{'USD','EUR','GBP','JPY','AUD','LOCAL_CURRENCY','DOCUMENT_CURRENCY'},mono,constrained)= GBP,@Select(Actuals\Actual Amt (GBP)),IIF(@Prompt('Enter Currency','A',{'USD','EUR','GBP','JPY','AUD','LOCAL_CURRENCY','DOCUMENT_CURRENCY'},mono,constrained)= JPY,@Select(Actuals\Actual Amt (JPY)),IIF(@Prompt('Enter Currency','A',{'USD','EUR','GBP','JPY','AUD','LOCAL_CURRENCY','DOCUMENT_CURRENCY'},mono,constrained)= AUD,@Select(Actuals\Actual Amt (AUD)),IIF(@Prompt('Enter Currency','A',{'USD','EUR','GBP','JPY','AUD','LOCAL_CURRENCY','DOCUMENT_CURRENCY'},mono,constrained)= LOCAL_CURRENCY,@Select(Actuals\Actual Amt (Local)),IIF(@Prompt('Enter Currency','A',{'USD','EUR','GBP','JPY','AUD','LOCAL_CURRENCY','DOCUMENT_CURRENCY'},mono,constrained)= DOCUMENT_CURRENCY,@Select(Line Item Detail in Doc Currency\Line Item Doc Currency Amt),0)))))))
</EXPRESSION>
The objects Actual\Actual Amt (USD) works , but when using these objects are used in this kind of expression, its not working. It does a memory leak on the SAP BW side.
has anyone faced this issue and fixed it?
Thanks,
Anu

You can-not return characteristics via <EXPRESSION> tag.
In fact right now it is not possible to do substring and similar operations. You can only create objects which returns numeric
value.
Regards,
Rohit

Unwanted LOVs - Universe on a BEx query on top of a Multiprovider

BO XI 3.1
BW 7.01
OLAP Universe on a BEx query
BEx query on top of a Multiprovider
Multiprovider on 2 DSOs; lets say DSO1 and DSO2
BEx query has a global filter for "INFOPROVIDER = DSO1"
BEx query has a user input variable defined for "Field1" (Field1 is present in both DSOs)
In BEx, F4 on Field1 variable entry gives the values of Field1 from DSO1. (which is what we want)
Expected LOVs for the generated prompt for Field1 in the WEBI report: Values of Field1 from DSO1
Problem:
Actual LOVs returned in WEBI report: Values of Field1 from both DSO1 and DSO2
Has anyone faced this before?
Thank you

Henry Banks wrote:
> I have a suspicion the BEX property 'only values in infoprovider' isn't picked up/consumed by the BAPIs used by the MDX interface.
That is correct. The BEx properties do not carry over to the BO side. In Webi 3.1 here are the default selections for LOVs (as far as I know)
OLAP universe against BEx query on an infoprovider (Infocube, DSO, Multiprovider) - Only values in Infoprovider
OLAP universe against BEx query on an Infoset - Values in the master data table
My understanding now is
OLAP universe against BEx query on a Multiprovider - Only values in ALL Infoproviders under the Multiprovider
Henry Banks wrote:
> Yes, this is confirmed by Note 1224318 - MDX: InfoProvider restriction for the member rowset
> It's a BW limitation of the OLE DB for OLAP.
I have seen this note before and according to it you can set an RSADMIN parameter MDX_JOIN_CUBE_DIME and have more control over the LOVs.
MDX_JOIN_CUBE_DIME = "A" -> The read mode for all LOVs is Only values in master data
MDX_JOIN_CUBE_DIME = "I" -> The read mode for LOVs is either master data or infoprovider depending on the infoobject settings
Henry Banks wrote:
> It might be easier to have to 2 data providers for this document, if you don't already, for plan and actual; or 2 seperate bex queries.
Well, that would work but it would defeat the purpose of having a Multiprovider for logical partitioning, wouldn't it?

Universes over BEx - LOV questions

In old school BOBJ when we build a LOV for an object you would normally use the ID (or Key) and then add the description into the LOV so when a user selects the long description actually the ID (or Key) is passed into the SQL and therefore would be more preformat.
However, what I am seeing when you build a Universe over BEx query is that the user also is presented with the LOV but the two columns are reversed and they select the Description and that is passed into the u201Cpromptu201D. Does BEx do something clever under the hood to replace the Description with the ID when executing the query or is it doing badly performing text matching ?

Hi,
LOVs generated in universes out of BEx queries are using index awareness mechanisms.
The caption is displayed to the user but the key is sent to the database.
So there is no issue in SAP BW because the right key is sent to the server.
Regards,
Didier

Issue while importing bex query into BO

Hi EXperts,
I am using Bo xi 3.1 sp3 i am facing the issue while building the universe with bex query iam getting the following error "Error getting measures for cube (cube name(0QM_C09_Q003)),It is giving this error, i resolved this error by check cumultave property in th measures,is it right to do like this or is there any other way to resolve the issue.
Regards
Suraj

Hi Juhi,
I am facing the same issue. BW query has three input parameters i.e. Year, Month and Profit center.
I can create the service when query has only one input parameter i.e. Year. But when query has more parameter other than year, I cant create the service. Getting an error 'Association AZPROFIT_CToListOfValues: referential constraint property not found in entity ZMFIGL_ZFIGL_COST_FINAL_FIORIParameter.'
As per your last reply, if we have multiple input parameters then it does not allow to create the service from BEX query. How did you resolve this issue. Please provide some details.
Thanks in Advance.
Abhishek.

Authorisation in Business Objects Explorer Infospaces created on BEx query

Hello,
We have installed Business Objects Explorer, created Universe on BEx query and created a Explorer Infospace on that universe. everything works fine but the authorisations created for the user in BEx query are not taken into consideration when I login using SAP username "leveraging" SSO.
Is Explorer not designed to consider authorisations in BEX query?
Whats happening during Indexing of an Infospace? Will the system save the data in Business Objects repository from the source of the data?
Thanks in advance.
/Suman

Hi Suman,
You are right , Explorer is not designed to leverage Authorisations in SAP BW.
Polestar is indexing data and keeping it out side of BW. Although you can log in with SSO , it doesn't check the authorization according to BW, it shows everything indexed.
You can have a workaround if the case is simple such as;
Suppose you have 3 region , you can create 3 infospaces and give these authorizations to users from CMC.
But if you really want to use all features of authorization in BW , it is impossible for now.
Regards,
Ozan Eroglu

Calday not generated while generating universe on mdx query

Dear All,
Issue: Iam Creating a universe on Bex Query , issue is calday which is in free characteristics in not generated in
universe.Please suggest .
Thanks
suresh.p

Which version of BO and SAP BW do you use?
Regards,
Stratos

SAP BW BEx query - WEBi MDX query

Hi Experts, have we had some discussion on this?
Does MDX query send by WEBi report to BW use the same program to extract data from BW database?
One of the option for WEBi report source of data is to build Universe on top of BEx query. Could you share how this process actually happen.
I think
- WEBi query will pass parameters that is relevant for BEx query filter of the universe
- the BEx query will then extract the data (following normal process if we run BEx query independently)
- if WEBi has further filtering, it will then get the BEx result above and filter it further ..??
So, how is MDX query come into the picture?
Or is it:
- WEBi query and the BEx query will determine what MDX query will be generated, and this MDX query will then fetch the data.
But why BEx query extract data faster then MDX query?
Sorry, i am new to this. hope someone could share some light here. In the meantime i continue to real those documentation and try to get some more ideas of what is actually happening.
Thanks.

Hi Thanks a lot for pointing this out.
Did i understand it correctly that BEx query is using a different set of program (platform) to retrieve data compare to MDX query, and not MDX uses those program that is used by BEx to retrieve data from BW database and have extra steps on top of that?
Can anyone share what is actually happen WEBi MDX query is executed (how the database is hit with SQL, and what are the tools to evaluate the efficiency of the WEBi (or the used BEx). As for BEx we have RSRT to analyze it right.
And even to test the MDX query using MDXTEST and try to get the data from WEBi report, i found WEBi report still take considerably a lot longer. Why is this so? just because BO is a different system then BW?
And as it's shared the BO 4.0 is using the same platform as BEx to retrieve data from BW database, does this mean we don't need to care about MDX usage in BW anymore as far as BO data extraction concern?
Thank you very much.

Dynamic filter on time characteristics on OLAP SAP BEX query based universe

Dear all,
I'm currently working on the integration between SAP NetWeaver BI 7.0 and SAP BusinessObjects XI 3.1 FP 1.5 via integration kit.
I've built an OLAP universe on the top of a BW query based on a multiprovider that contains 10 infocubes.
Everything works fine but I need to create a filter in the OLAP universe that allows to restrict data by current date (e.g. using TIME characteristic of Infocube such as 0CALDAY or 0CALMONTH). From that filter we could start creating other conditions to compare data to different time periods.
I've already tried to use a SAP exit variable in a BW query but this kind of object would restrict query data only by current date and for example it would be impossible to browse data by previous years (to bypass this problem we could use restricted key figures with different offsets but we have too many key figures in the query and the number of restrictions
would rise exponentially).
In a relational DataBase we can do that using a "where condition" based on 'CURRENTDATE' (SQL DB2 syntax).
Now, we need to apply the same logic but translated in MDX syntax.
Is it possible to enter a dynamic filter in the OLAP universe or just fixed or promt values ?
Any advise?
Thanks in advance.
Best Regards.
M.

Hi Ingo,
1) My question is: "How can I have to manage variable in BEX queries and in the UNIVERSE in order to obtain the maximum flexibility to create reports with measures on actual day (for example) without asking the user to promt a value ?"
I want to use an unique BEX query to define an unique UNIVERSE. On this UNIVERSE I want to create many reports (actual day, previous day, and so on).
If I restrict 0CALDAY with an EXIT variable then shall I be able to create a different restrictions on the same Universe based on 0CALDAY ?
2) Another question is:
Is it possible to insert an XML / MDX filter on the OLAP Universe with dynamic derivation of the system date ?
For example:
Instead of this:
<FILTER KEY="[0FISCYEAR].[LEVEL01].[NAME]">
    <CONDITION OPERATORCONDITION="Equal">
        <CONSTANT CAPTION="Z12008"></CONSTANT>
    </CONDITION>
</FILTER>
Is it possible to insert a tag with a dynamic function to derive the system date ?
Thanks in advance.
Best Regards.

Universe on BEX query - Measures Question !!

Similar Messages

Maybe you are looking for