Fix Webi Errors based on Bex Universe

1.#UNAVAILABLE error

Scenario : I have a report wherein I have to restrict the zero values in the columns. The report is based on a SAP BW Bex query and the zero values come from a key figure. I cannot put the condition in the query filter since it doesnt allow me to pull the measure there.

If I try to put a report or a block level filter, the all the measures become #UNAVAILABLE. The report looks somewhat like the below:

Dim1| Dim2| Dim3|         M1|      M2|     M3
A     |  B    |   C    |  #UNAV|#UNAV|#UNAV

M3 is the variable I need to put a filter on for supressing Zero. I have tried with the measure(key figure) and the underlying attribute(Formatted value). The result is the same

 Cause 1:
:#UNAVAILABLE occurs when we are using smart measures and Web Intelligence cannot calculate the value based on the contexts used.
    
Solution:To Fix This modify the property of the measure object in universe:Measure object Properties-> Function to "Sum" (relevant projection too) , which was "Database Delegated" by default for OLAP universe.  

Cause 2: In case if you are forced to give exception aggregation in query, kindly inform the BO team about the reference characteristic that is used for exception aggregation. In case if they ignore the reference characteristic, they are getting the #UNAVAILABLE error.

Solution:Add the Reference Character(Sales Volume) in the block.

Example of Exception Aggregation: Counting 

The scenario below shows you how to count the results of a calculated key figure in the BEx Query Designer.

You have loaded the following data into your InfoCube:

Region	Customer	Sales Volume
		USD
NY	A	400,000
	B	200,000
	C	50,000
CA	A	800,000
	C	300,000

You want to use the query to determine the number of customers for which the sales volume is less than 1,000,000 USD. To do so, you create the calculated key figure Customer sales volume <= 1.000.000 (F1) with the following properties:

○  General tab page: Formula definition: Sales Volume <= 1.000.000

○  Aggregation tab page: Exception Aggregation: Total, Ref. Characteristic: Customer

This query would deliver the following result:

Region	Customer	Sales Volume	F1
		USD
NY	A	400,000	1
	B	200,000	1
	C	50,000	1
	Result	650,000	3
CA	A	800,000	1
	C	300,000	1
	Result	1,100,000	2
Overall result		1,750,000	2

2.Supplied XML is not Valid

The following error is common, when we tried refreshing the report in Web Intelligence based on BEx query universe. The reason for the error that the Universe created from BEx query is not up-to-date. It might happen due to the object (Characteristics / Key Figures) which was used in the BEx query is replaced / removed.

 

Resolution 

1. Open Universe Designer -> Universe Name
2. View -> Refresh Structure
3. Update OLAP Universe Wizard appear, Click Ok
4. Save and Export the universe to the repository

3.L00,L01 issue

rom an OLAP point of view a characteristic is like a dimension, that means that it contains all the members (level L01) and the All member that aggregates the characteristic members (level L00);

These metadata are provied by SAP BW when using OLAP drivers.

For a characteristic, the level L00 is not necessary unless you want to use the All member.                                                                                                                             L00 korresponds to the root node of your hierarchy and it is normally an "ALL" node (eg. ALL countries, ALL cost centers, ALL materials etc)

On the other hand, the level L00 is significant for hierarchies, hierarchy varaibles and structures because it contains members.                                         Level 00 dimension represents the aggregation of the characteristic when all members are selected (the member returned from BW is All members). The Level 01 dimension contains all members for the characteristic as a flat list of values.  Final Conclusion is:we will use L01 objects only

4.%RT, %GT, %CT, %XT, SUMRT, SUMGT, SUMXT, SUMYT and LEAF

Cause : When we  uses these Functions in BEX Query Designer we Will Get Error in BO:"error getting dimensions for cube".  these are not supported in MDX                                                                                                                                                      
Resolution:Need to Create these Functions at BO Report Level Only
%GT functions can easily be implemented in BO using Calculation Context(For Each,For All,etc..)                                                               

4.TOREFRESH: Please see the below post

http://bo-reports.blogspot.in/2016/06/torefresh-in-webi.html

5.MULTIVALUE: Please see the below post

http://bo-reports.blogspot.in/2016/06/multivalue-error.html