BEx Structures in WEBI

Question

Hello Guys,
I am new to BO with BI as data source.
In BEx query disigner, we have one Char and KF structure (with two calculated KFs) in rows section. And Char structure with 2 chars (restrcted) in columns section. We are using cell difinition as mentioned below:
          OQT     DQT
Mat          c1     c2
CKF1          c3     c4
CKF2          c5     c6
c3 and c6 are cell references and using these reference cells in formula cells c1 and c2. CKF1 and CKF2 are hidden. When we execute this query using BEx analyzer it is displaying correct values as mentioned in below format.
     OQT     DQT
M1     20     10
We created OLAP universe on top of this BEx query. Hidden CKFs are displaying in universe level and it is displaying Structure class with one structure dimension only.
When we use that structure dimension in webi it is displaying OQT and DQT not values of it.
My question is how to create webi report to achieve above mentioned Bex report?
Is WEBI supports the cell definition/reference ?
We are using BI 7 with BO XI R3.1
Thanks in advance for your help,
Regards,
Reddy.
Edited by: pyreddy9 on Feb 17, 2012 12:11 AM

Answer 1

Hi,
It's difficult to tell exactly how you will workaround that ...
but, with MDX you have to include a Measure/KF in the webi query results
in the webi query panel, you MUST include (at minimum) the exact same objects Structure(s)/CKF combination as a baseline for your query to work reliably. ( Check this Bex layout in RSTT and see how the initial query view is designed )
generally speaking, use of multiple Characteristic Structures (like the accounting model) and Measure Hierarchies really confuses webi.  and also, can hammer the OLAP engine in BW too. (i.e. massive performance issues)
some aspects of the hardcoded layout delivered by structures (i.e. subtotals and totals, formatting indents etc)  are not understood or respected by webi.
Check out this Note here 1387793 - BEx functionality features that are not supported or integrated in WebIntelligence  
for an idea of the Bex features which are not exposed by the BW OLAP API to BObj .
as for cell references .. this is a fringe use-case for BW-BO developments, and should probably be avoided.
Ultiamtely, you should be using BEx as a simple data-delivery container, particularly for filtering,  but definitely not for presentation layout.
Regards,
H
p.s. a couple of reference notes for BW corrections in teh MDX interface:
Note 1446246 - MDX: Composite SAP Note for flattening API based on basXML
Note 1156101 - MDX: Composite SAP note for incorrect data
Note 1142664 - MDX: Composite SAP note about performance improvements