on 04-24-2014 8:45 AM
UNX universes doesnt support OR operator in BO4.x. Is this a limitation from SAP?
In addition to what Manoj is asking for, are you talking about creating custom SQL in the UNX or in WebI?
It is supported for SQL and JOINs - but we'll need a bit more context to be able to confirm you're able to do what it is you're trying to do.
Also, the Data Access guides on http://help.sap.com may help you as well.
Thanks!
Carly
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pritesh,
I do not see such limitation in .Unx or in IDT.
What is your data source for Unx universe ?
In which scenario you find it as a limitation ?
-Manoj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Manoj/Carly,
Thanks for your response. We have both UNV and UNX universes connecting to OLAP data source (SSAS cube). Now UNX universe were created with BO4.x coming into existense. UNV universes were only created. We had BO reports created from BO3.1 which were then migrated to BO4.0. What I got information from colleagues is that UNX based universes doesn't support OR operator with report filters and hence that is the reason that we need both UNV and UNX based universes. If that is the case, then I find it as a limitation in BO4.x
I hope my question is clear.
Hi Pritesh,
Please refer to SAP Note 1687933.
Symptom
- BI 4.0 - Web Intelligence Query Panel - not possible to use "OR" operator when creating a query filters on BEX Query using BICS connection
Environment
- BI 4.0 (any SP)
- WebIntelligence Query Panel
- BW 7.x & BEx Query Designer
- Also including OLAP vendors: Microsoft Analysis Services 2008, Oracle Hyperion Essbase v11
Reproducing the Issue
- In WebIntelligence, select a BEx Query as a data provider
- Drag and Drop some Result Objects into the Query Panel
- Add a dimension into the Query Filter panel, and set a condition (e.g. Prompt)
- Create another Query filter.
- Notice the clause is joined using AND operator
- There is no way to change this to OR (as is normal with Relational source)
Cause
- Defect ADAPT01580759 was submitted to Development, however it was rejected as "By Design"
- This is because the software specification for BICS model can’t support OR operator, due to XML representation of BICS QueryView's "SelectionState"
Resolution
Workaround:
- If OR operation is for same dimension: Use operator "InList" and add all required members in same filter
- If OR operation for 2 (or N) dimensions: Use 2 (or N) Queries with a filter on each dimension in a different query
See Also
Note:
- Every OLAP source is limited to the << AND >> operator only in the query filters. This include all OLAP MDX access .UNX (MSAS and Essbase) and BICS access from DSL.
- This is because the Query Technique capability model (for these new OLAP DSL drivers) has not yet been implemented using ConnectionServer PRM files. This is a future enhancement.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.