Value based dimension hierarchy in OBIEE 10G

Hi,
I am a user of OBIEE10G. I have to create a value based dimension hierarchy in my RPD. My hierarchy should be such that when I click on any VP Name, the respective employees working under him/her should be shown. But my columns of VP Name and Employee_Name are present in separate dimensions. Hence when I drag the column of VP Name to Employee dimension and then create the dimension hierarchy, I get an error of illegal cross join .
Is value based hierarchy possible in 10G?
Pls reply.
Thanks
Ankita
Edited by: 848789 on Sep 28, 2011 8:40 PM

Hi Ankita,
As per my Understanding the VP column did't map to any LTS .
When ever u have multiple LTS in Dim Admin tool won't create Dimension Hierarchy manually we need to create that.
Follow these steps to resolve your Problem...
1) give the simple join in physical layer for that two tables.
2) Create one Dim table in to BMM layer drag all columns in 2 tables in to BMM Dim table so u can able to see all the columns is mapped in to their respective LTS.
3) Now u can create hierarchy manually step by step.Like Grand total Parent ----> Child level .
4) If u have any fact table joined with these dimension in physical layer give the logical joins in BMM layer and set the content levels properly.
Let me know need any detail clarification.
Thanks,
Satya

Similar Messages

Pre-compute for Value based dimensions in AWM 10g

hi,
I created a compressed partitioned MOLAP cube in OWB 10.2.0.3 based on some value based dimensions.
I selected the hierarchy in value based dimensions for pre-compute, but it did display the hierarchy in OWB.
I deployed the cube into Analytical workspace AWM 10g(10.2.0.3A).It created PRECOMPUTE(NA) in the relation statement for the value based dimensions.
Is it that value based dimensions cannot be pre-computed (at the heirarchy) in AWM 10g ?
Regards
Chakri

For reference, I believe this error was due to the deletion and recreation of a standard form AW formula without full restoration of the formula's PROPERTY values. AWXML (and hence 10g OWB/AWM) will not work correctly if you remove PROPERTY values from objects.

Can we precompute a value based dimension ?

Hi,
I do not know how to precompute/summarize a value based dimension in AWM 10g.
One of my value based dimension in AWM 10 g (10.2.0.3A) showed pre-compute already done , but the aggmap of the cube did not show any precompute clause in relation statement for this dimension.
1) Is AWM 10.2.0.3 A taking care of this internally ? How can i verify this ?
2) If not, how can i set pre-compute for a value based dimension by hand ?
(provided the precompute clause remains even after cube is maintained).
Regards
Chakri

Hi All,
Thanks for your replies.
Let me give you a background . Iam creating a cube over some value based dimensions in OWB (10.2.0.3) and then deploying them to AW .Iam loading the cube and dimensions using OWB mappings.
Any other changes or objects not possible through OWB are done directly in AWM (10.2.0.3A)
Stuart,
Yes this a duplicate thread i posted for almost the same problem statement.
David,
1st option - precompute valueset is defaulting to all members.
a) Are you talking about the valueset <DIMENSION>_PARENTREL(<VSET>)
I did an rpr on <VSET> , it just returned the hierarchy name. This vset would be there for any dimension ( even without precompute) and would just return the default heirarchy
b) or Are you referring to PRECOMPUTE(<VSET>).
As mentioned, this VSET is not coming up in the aggmap.
2nd option - Modify the XML template with the PreComputeClause to say Expressiontype="INCLUDE" instead of "EXCLUDE". You can then delete the cube and recreate it from your XML.
The Model view of AWM (10.2.0.3A) was showing the 'All' box as checked for this value based dimension, but the aggmap did not show any PRECOMPUTE clause. Also, when i checked the XML of the cube (in which the dimension is used), there was no pre-compute clause for only this dimension. This might be due to my AWM version iam using.What is your AWM version ?
How do i check if pre-compute is working ?
Here is the info about my cube :
Dimensions : TIME (Levels: Year,Quarter,Month) ,LOB,CUST and FIN
All dimension except TIME are value based.
Settings : compressed, partitioned along TIME.MONTH
I want to fully precompute TIME and LOB .
CUST and FIN should not be precomputed.
Thanks
Chakri

DimensionmemberList with value-based dimension

Hi,
I'm unable to use a DimensionMemberList with a value-based dimension. It works fine with level-based, however when I select a value-based dimension and hierarchy in the wizard and click on "Next" an Error pop-up appears with no message and I have to click on "Cancel" to get out of the wizard.
Has anyone encountered this behavior?

Hi Ankita,
As per my Understanding the VP column did't map to any LTS .
When ever u have multiple LTS in Dim Admin tool won't create Dimension Hierarchy manually we need to create that.
Follow these steps to resolve your Problem...
1) give the simple join in physical layer for that two tables.
2) Create one Dim table in to BMM layer drag all columns in 2 tables in to BMM Dim table so u can able to see all the columns is mapped in to their respective LTS.
3) Now u can create hierarchy manually step by step.Like Grand total Parent ----> Child level .
4) If u have any fact table joined with these dimension in physical layer give the logical joins in BMM layer and set the content levels properly.
Let me know need any detail clarification.
Thanks,
Satya

Parent child Hierarchy in OBIEE 10G

Hi,
I want to implement the parent child hierarchy in OBIEE 10g where I need to show people working under manager directly and indirectly.
Please let me know as users doesn't want to drill the report but by selecting the option from the drop down Direct/Indirect they should see the results.
Thanks

I guess it will update when the structure changes,Let see the response from other gurus.
Thanks,

Has anyone setup BIEE with OLAP 10g using value-based dimension hierarchies

I just wanted to know if it is possible to setup BIEE with 10g using multple dimensions containing multiple value-based hierarchies?
I know this involves using the OLAP Cube View Generator to create an sql view of the cube data.
I have been able to get this to work with nine dimensions all containing a single value-based hierarchy bar one which had four value-based hierarchies. But as soon as i have multiple hierarchies in multiple dimensions it seems to go haywire and i cannot get the sql view to return correct data.
I thought i would post on the BI side to see if anyone has been successful in creating a BIEE setup like this?

The simple answer to your question,
how robust is the 11g materialised views with multiple value-based hierarchies...?is that materialized views are not supported on top of value-based hierarchies in 11g. The reason is that it is not possible to write a reasonable SQL statement that aggregates a fact over a value-based hierarchy. Such a SQL statement is necessary if we want to create a rewritable MV on top of the cube.
But I suspect this is not what you are really asking. If you are trying to set up OBIEE on top of the cube in 10g using the view generator, then you will probably want to use the "ET VIEWS" that are generated automatically in 11g. These are generated whether or not you enable materialized views on top of your cube. I am not aware of any issues with the generated value-based hierarchy view support in 11g. Members may be shared between value hierarchies and you will not need to generate or modify limit maps.

Dashboard prompt on a Dimension Hierarchy in Obiee 11g

Hi All,
I have created a hierarchy (parent-child) on a dimension 'A'. I am able to create a dashboard prompt for the dimension hierarchy. However I am not sure how to create a report that is to be filtered on this dashboard prompt. I tried using the attribute name that the hierarchy uses but that does not work. Can some one please let me know how i can filter a report by a hierarchy dimension prompt.
Thanks,
Nikita
Edited by: user12438396 on May 8, 2011 1:16 PM

Hi Nikita,
For your requirement, you need to go for Selection steps pane in the analysis(report). Click on steps link and then add the hierarchy column that you want to use and expand the hierarchy to the lowest level. Now select all these and all the attributes will now appear in the other side.
If you dont expand the hierarchy to the lowest level, then only the highest level values will appear in your selection at prompt.
Also make sure to check the 'override' checkbox in the bottom, this helps in filtering the values.
Hope this answers your question.
Cheers,
Obul

Filter value based on Date in OBIEE 11g, Reporting Issue

Hi,
I have following tables
Dim_Item
Dim_Loc
Fact_Price-Item_Key,Loc_Key,Date_Key,Reason_Code,Amount,Load_date
Reason Code is the code which discribes the reson behind price change
Amount- price of Item at particular location (Note: one item can have different price at different location)
Load Date - When ever there is price change for a particular item at particular location new record is inserted in the fact load date represents the date on which the data is updated
Item_key Loc_key Date_key Reason_Code Amount Load_Date
1                  1        20131113                  0          1400    13/11/2013
1                  1        20131115                  6          1100    15/11/2013
2                  1        20131112                  0          900      12/11/2013
2                  2        20131112                  0          1200    12/11/2013
2                  2        20131113                  3          325      13/11/2013
My report requirement is
Report should show only the Item & location for which there is price change
Report should be like
Item Loc Orignal_Amt Changed_Amt
1       1         1400           1100
2       2         1200            325
I have tried to calculate Orignal_Amt by taking Min(Load_Date) & Changed_Amt by taking Max(Load_Date) but result is not correct
I need to min(Load_Date) or max(load_date) for an Item at particular location
i.e it should be like min(load_date by item_key,loc_key)
max(load_date by item_key,loc_key)
then I can filter out Amount based on this min & max value.
How can I achive this, is there any other approach to achive this
Thanks
Sameer

Hi,
Does this approach with comparing prices in the first and last date of the period actually indicates the price change?
What about the sample data below - is considered to be a price change or not?
Item_key Loc_key Date_key Reason_Code Amount Load_Date
2                  2        20131110                  0          325     12/11/2013
2                  2        20131111                  0          1100    12/11/2013
2                  2        20131112                  0          1200    12/11/2013
2                  2        20131113                  3          325      13/11/2013
Option #1:
Use 2 requests:
Req1 selects surrogate key for the first and last record by load date for each location and product. Surrogate key is just a concatenated expression of Item_Key, Loc_Key and Load_Date fields (use separators between them).
For this request you need to filter out all other dates but first and last - use Rank function with BY clause. It will be 2 calculated fields: RANK(Date_Load BY Item_Key, Loc_Key) = last date, RANK(-Date_Load BY Item_Key, Loc_Key) = first date. Select records having any of these ranks=1.
In result this request should return up to 2 records for each product-location combination with surrogate key, something like this for my example:
Item_key Loc_key Date_key Reason_Code Amount Load_Date          KEY
2                  2        20131110                  0          325     12/11/2013      LOC:2;ITM:2;DT:20131110
2                  2        20131113                  3          325      13/11/2013     LOC:2;ITM:2;DT:20131113
In fact, it could be more than 2 records in case there are more than 1 change in a day for the price and no time stored on date field. This is up to you how to eliminate duplicates.
Now you have another request, resulting one, which is filtered by Req1 using the same surrogate key expression. Orignal_Amt =Min(Amount), Change_Amt = Max(Amount). Apply a filter to find records with different values between them.
In result, if product price is the same in the beginning and end of period (or it is single record) - these records will be filtered out, otherwise you get them in the report.
Option #2:
Play around with logical SQL under Advanced tab, it allows you to write requests with joins (as regular SQL does).
This is sort of desperate option as such an analysis is hard to maintain (make modifications to it).

Value Based Dimension causing Aggrega tion problems

I am new to building cubes in Oracle Olap, and am having trouble with a particular cube. (I hope I get all the terminology accurate enough to describe the problem I am having). Our organization structure is hierarchical. For example, org 0001is at the top of the "tree" and has 5 children: 1000, 2000, 3000, 40000, A000. Each of those 5 orgs have children that rollup to them. The problem is that the org "tree" is uneven. For example, Org 4000 has children that go down 4 more levels where the 3000 org only has children that go to level 3. We have about 1500 total orgs in the company. The dimension table we have shows the org_number and its Parent_org. Thus, I created an org dimension in AWM and then a value_based hierarchy. I can maintain and view the dimension in AWM and it all looks fine. I can then map the org dimension in the cube and maintain it (the cube that is). The problem is that the totals for my measures (actual costs) in the cube are way too high. Any advice as to what the problem is? I have verified that every org is in the table only once and that each org only rolls up to one parent org. I should mention that costs can be incurred by any org in the structure, no matter what level the org is at. Thanks for your help.
Edited by: rybarrus on Jun 15, 2010 1:56 PM

Thanks for your reply. That was a helpful suggestion. I found what seems to be the problem,but don't know why it is happening. When I look at a particular leg of the Org in the cube (in AWM) I see the following totals (indented to show parent child relationship):
ORG--------------------Total
1000...................602.42
-------1030............557.48
--------------1034.....557.48
-------1060............ 44.94
--------------1063..... 44.94
When I Query the fact table I see the following totals:
1000................... 0.00
1030................... 159.05
1034................... 557.48
1060...................7,800.00
1063................... 44.94
To me, it looks like the total amount of the child is REPLACING the total of the parent. For example, the total in the cube for org 1060 should be 7,844.94 (7,800 + 44.94). Any reason why it doesn't sum correctly?
Also, the total for org 1030 should be 716.53 (557.48 + 159.05).
If you look back at my first post, I said that the overall total in the cube at the top level is way over the total in the table. That is still the case. This example that I have shown happens to be the opposite. The total I get when I query the fact table is greater than the total in the cube at this level. I hope that is not confusing.
Edited by: rybarrus on Jun 15, 2010 4:37 PM

Passing filter values from column formula in OBIEE 10g

Hi,
I am trying to pass filter value from the column LY Spend YTD columns where we have a filter option and passing the year filter 2013 as below.
FILTER("Fact - Purchasing - Invoice"."LY Spend YTD" USING (Time."Year" = '2013'))
My goal behind doing this is, we have a filter already present for the whole criteria on the year which is 2012.
But specifically for this column i dont want to pass the year 2012 to it, Instead I want to pass 2013 to it. But I am not succeding the result is blank.
Please suggest and let me know if further understanding is needed.

Hi Srini
Thanks for you reply.
I cannot do that way because some measures are satisfying with year 2012 and displaying the data and other measure are satisfying with 2013.
I am working on LY Spend YTD, LY spend YTD - 1, Spend YTD and Year ago spend.
So thats the reason I have thought that way of passing the filter in column formula irrespective of criteria filter.
Please suggest.

Security for value based hierarchy + OLAP

Hi,
I am using row-level security mechanism described here: http://www.rittmanmead.com/2012/03/obiee-11g-security-week-row-level-security/
It works well for level based hierarchies... but is there a way to apply it to value based OLAP hierarchy in OBIEE 11.1.1.6?
My case is:
- I have parent-child value based hierarchy representing management structure with various depth.
- of course facts are always linked to leaf members of hierarchy
- I need to apply security at different levels. E.g. Office manager should have access to one/multiple offices information (basically all employees he manage currently + his previous office before he was moved)
- In report I display presentation hierarchy that starts at country level and then manager drill to his offices
- At country level, manager should see a measure aggregate only for his offices (not whole country)
In relational database there is no problem:
- I follow rittman blog
- create session variable that store list of all leaf members of hierarchy (employees) managed by manager
- with OBIEE "Manage"->"Identity" I apply filter on fact table and get right measure aggregates at all levels of hierarchy
Issue for OLAP:
- with OBIEE "Manage"->"Identity" I apply filter on OLAP value based hierarchy
- in case of filter "MY_BMM"."Org Str"."Org Str Key" = VALUEOF(NQ_SESSION."LEAFS_LIST") -> when manager include hierarchy column to report there are no results because hierarchy starts at country level and he have no access to country data
- to workaround it I tried: "MY_BMM"."Org Str"."Org Str Key" = VALUEOF(NQ_SESSION."LEAFS_LIST_AND_ALL_ANCESTORS") -> manager can see all aggregates at country level because he have access to country, and OLAP just use country level aggregate
- IsDescendant("MY_BMM"."Org Str" , VALUEOF(NQ_SESSION."OFFICE_ID")) will work only for single office as we can not use row wise variables here
One solution I can imagine is to create additional level based dimension that have only 2 levels: "All"->"Org Str Leaf". Then apply filter on this "artifitial" dimension. It is not perfect solution to duplicate dimensions only for security purposes... that's why I ask you for advice if you know better way?
Regards,
mudi

Here is an example, how to set security in OBIEE 11.1.1.5 (or future versions) against Oracle OLAP dimensions.
*(1). Create the Oracle OLAP Hierarchy Descendant View against Value-based hierarchy*
These views return a row for each ancestor-descendent relationship in the hierarchy. As you can see how easy it is.
CREATE OR REPLACE VIEW DEPT_DESCENDANTS
AS
SELECT 'DEPT' "DIMENSION", 'DEPTHIER' "HIER", ancestor, descendant
FROM TABLE(OLAP_TABLE('BAWOLAP.BNSOLAP DURATION QUERY', null, 'LIMIT DEPT_HIERLIST TO 'DEPTHIER''',
'DMNS DESCENDANT AS VARCHAR2(60) FROM DEPT
DMNS GID_VAL AS NUMBER FROM ___AW_GID_DIMENSION
MSR ANCESTOR AS VARCHAR2(60) FROM DEPT_FAMILYRELVAL'
where ancestor is not null
*(2). Create the User ACL Tables and Populate with Data*
Create an Access Control list test table by user and Dept. Later this will be populated with production data.
create table user_dept_acls
username varchar2(30),
dept varchar2(60)
insert into user_dept_acls(username, dept) values ('user1', 'GWM');
insert into user_dept_acls(username, dept) values ('user1', 'GT');
insert into user_dept_acls(username, dept) values ('user1', 'SC');
insert into user_dept_acls(username, dept) values ('user2', 'GWM');
insert into user_dept_acls(username, dept) values ('user2', 'GT');
insert into user_dept_acls(username, dept) values ('user3', 'SC');
commit;
*(3). Create an Init Block Connection Pool*
Oracle BI EE requires a separate Connect Pool for Init blocks. It does not allow the default query connection pool to be reused for init blocks. So, we need to create a new init block.
*(4). Create the ACL Session Variables*
These session variables hold the list of all members that the user may access.
Example Session Variable: DEPT_ACL
Init Block: "Init DEPT_ACL"
SQL:
select 'DEPT_ACL', account from user_DEPT_acls where username = ':USER'
union all
select 'DEPT_ACL', descendant
from DEPT_descendants
where ancestor in (select account from user_DEPT_acls where username = ':USER')
union all
select 'DEPT_ACL', ancestor
from DEPT_descendants
where descendant in (select account from user_DEPT_acls where username = ':USER')
The first query block of the init block SQL just selects the members explicitly entered into the ACL table. The second block selects all the descendants of those members from the descendants view. The third block selects all the ancestors to ensure that the user has access to all the members in the drill path starting from the root member.
Make sure that row-wise initialization is checked in the Variable Target section of the init block.
*(5). Add the Data Filters*
In our test case we assigned the data filters to the BIAuthor role, but the filters should be added to whatever role makes the most sense.
Data filter on "BNSGL"."Department":
"BNSGL"."Department"."Dept" = VALUEOF(NQ_SESSION."DEPT_ACL")
*(6). Log in as a Normal User and Query the Hierarchy*
The user can only see to the members to which they are granted access in the ACL table plus all ancestors and descendants of those members.
Drill down to the bottom of the hierarchy.
*(7). Look at the Query Log*
In the nqquery.log we see that the session variable is expanded into an IN list in the physical SQL query. The BI Server breaks the IN list into two IN lists to avoid the Oracle SQL limit of 1,000 items per IN list.
Edited by: Nasar Ali-Khan on Jul 2, 2012 8:14 AM

OBIEE and Oracle OLAP Value Based Hierarchies

Hi there...
I have a value based dimension built on Oracle OLAP and want to map it on OBIEE Administration tool.
I've been using the above link as reference:
http://www.oracle.com/technology/obe/olap_biee/CreateBIEEMetadata.htm
There's no option to import from Oracle Multi-dimensional Database. Either to import/configure the view created by OLAP as an Unballanced or Ragged Dimension.
I also checked this example, but it uses ESSBASE as the multi-dimensional source....
http://www.rittmanmead.com/2008/08/27/ragged-hierarchy-handling-in-obiee/
How to map this Ragged Dimension created in OLAP workspace in OBIEE? Any suggestions or directions will be highly appreciated...
Thanks in advance
Marcos

Mark and others,
You can create OLAP_TABLE views with level columns on top of value-based hierarchies. BI Beans used to do that too behind the scenes in Discoverer Plus OLAP. If you trace the Discoverer session, where you are querying data from Value-based hierarchies, you will see that it also generates OLAP_TABLE views with level columns in it.
So the question is how to do it. Internally, even for Value-based hierarchies Oracle OLAP keeps track of the "depth" of each value by using a structure called GID_DIMENSION (i.e., Grouping Dimension). Here is an example of a view on top of a value-based hierarchy (CFC_ACCT_GAPP) for RPT_ACCOUNT dimension. You have to know how "deep" your value-based hierarchy is.
Similar kind of a thing is done by OLAP View Generator application, which I never use - since I always prefer to define my own OLAP_TABLE views.
This kind of a view can then be used in the RPD of OBIEE.
select *
FROM table(OLAP_TABLE ('AW duration session',
*'DIMENSION RPT_ACCT_ID FROM RPT_ACCOUNT WITH*
HIERARCHY RPT_ACCOUNT_GAAP_PARENT   FROM RPT_ACCOUNT_PARENTREL(RPT_ACCOUNT_HIERLIST ''CFC_ACCT_GAAP'') INHIERARCHY RPT_ACCOUNT_INHIER
HATTRIBUTE RPT_ACCOUNT_GAAP_LVL_NUM FROM RPT_ACCOUNT_DEPTHVAL
FAMILYREL RPT_ACCOUNT_GAAP_LVL1,
RPT_ACCOUNT_GAAP_LVL2,
RPT_ACCOUNT_GAAP_LVL3,
RPT_ACCOUNT_GAAP_LVL4,
RPT_ACCOUNT_GAAP_LVL5,
RPT_ACCOUNT_GAAP_LVL6,
RPT_ACCOUNT_GAAP_LVL7,
RPT_ACCOUNT_GAAP_LVL8
FROM RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 127),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 63),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 31),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 15),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 7),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 3),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 1),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0)
FAMILYREL RPT_ACCOUNT_GAAP_LVL1_DSC,
RPT_ACCOUNT_GAAP_LVL2_DSC,
RPT_ACCOUNT_GAAP_LVL3_DSC,
RPT_ACCOUNT_GAAP_LVL4_DSC,
RPT_ACCOUNT_GAAP_LVL5_DSC,
RPT_ACCOUNT_GAAP_LVL6_DSC,
RPT_ACCOUNT_GAAP_LVL7_DSC,
RPT_ACCOUNT_GAAP_LVL8_DSC
FROM RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 127),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 63),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 31),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 15),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 7),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 3),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 1),
RPT_ACCOUNT_FAMILYRELVAL(GID_DIMENSION 0)
LABEL RPT_ACCOUNT_LONG_DESCRIPTION
ATTRIBUTE ACCOUNT_LDSC    FROM RPT_ACCOUNT_LONG_DESCRIPTION
ATTRIBUTE ACCOUNT_SDSC    FROM RPT_ACCOUNT_SHORT_DESCRIPTION
ATTRIBUTE ACCOUNT_TYPE    FROM RPT_ACCOUNT_TYPE
ATTRIBUTE SOURCE_LEVEL    FROM RPT_ACCOUNT_LEVEL
ATTRIBUTE CALCULATION     FROM RPT_ACCOUNT_CALCULATION
ATTRIBUTE CALC_DATA       FROM RPT_ACCOUNT_CALC_DATA
ATTRIBUTE GAAP_SORT_ORDER FROM RPT_ACCOUNT_GAAP_SORT_ORDER
ATTRIBUTE RATIO           FROM RPT_ACCOUNT_RATIO
ATTRIBUTE ACCOUNT_LEVEL   FROM RPT_ACCOUNT_LEVELREL'))

Aggregation On Value Based Hierarchy

Hi
I am having a problem with aggregation on value based hierarchy
Well I have a table which will serve as my fact and dimension table
It is as follows
ID     Name     MID     Salary
0     All
1     A     0     10000
2     B     1     9000
3     C     1     9000
4     D     1     9000
5     E     2     8000
6     F     2     8000
I created a value based dimension named EMPLOYEE , with child as ID and parent as MID
I created a cube EMP_SALARY with a measure salary mapped to the Salary column in Employee
My expectation here is to see the total salary at every level including the salary at that level
So let us take employee B as an example. He is the manager for employees E and F
So what I would like to see at level B is sal of B + sal of E + Sal of F = 9000 + 8000 + 8000 = 25000
But what I get from the cube is 9000. Now is the above possible ? If so please so provide me suggestions
I can achieve the same by using the following sql query
select e1.id,rpad('*',2*level,'*') || e1.name,e1.sal,
select sum(e2.sal)
from test_emp e2
start WITH e2.id = e1.id
CONNECT by PRIOR e2.id = e2.mid
) sum_sal
from test_emp e1
start with e1.mid is null
CONNECT by prior e1.id = e1.mid;

The same basic problem, along with a solution, was discussed in the following thread.
Re: Value Based Dimension causing Aggrega                         tion problems

Customize Font in Pivot Table OBIEE 10g

Hi All,
I have the Pivot table like this:
Item                Value
A                     1
B                     2
C                     3
Total A-C         6
D                     1
E                     2
F                     3
Total D-F          6
How to bold the Total A-C and its value?My version is OBIEE 10g
Thank you before
Regards
JOE

Hi Joe
In 10g
1st change the View from Compound Layout to "Tabular View"
2nd.. as you told the A-C total is needed, in the tabular view at Answers......navigate to that field/column & find Sigma (Summation Symbol) ..
3rd, by clicking on it..you will get the Totals in Bold Letters
Please mark Correct if this helps you
Regards

Preaggregation across value based hierarchy dimension in 11g

Hi All,
I have created a cube with 6 dimensions in olap 11g. One of those six dimensions has only one hierarchy which is value based hierarchy. I have chosen level based aggregation as I know at what levels exactly users are going to query. When I was going through the dimensions to choose levels to preaggregate I noticed there were no options available for my value based hierarchy dimension ( I could see "all" option for the same case in 10g) then I tried to look for definitions of underlying objects just to make sure it will preaggregate data across my value based hierarchy dimension.
I found value set corresponding to my value based hierarchy dimension in <CUBE NAME>SOLVEAGGMAP object , which AWM uses to decide which dimension values to preaggregate but if I do rpr on that value set (rp r<CUBE NAME>SOLVE<DIMENSION NAME>_PVSET) it shows NA so my question is can I pre aggregate across value based hierarchy dimension in olap 11g?
Olap Version: 11.2.0.1
AWM version: 11.2.0.1
Thanks

Even if you know exactly which levels your users will query, percent based precompute (e.g. 30%) may still be faster in practice because queries are returned using 'sparse looping' instead of 'dense looping'. This was the single biggest performance advantage of 11g over 10g.
But if you still want to use level based precompute, then you should look at the XML template for the cube (as saved by AWM, for example). In it you should find something called PrecomputeCondition. This defines the set of members that are precomputed. Here is an example I just created using the GLOBAL schema
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT LEVELS (PRODUCT.CLASS, PRODUCT.FAMILY, PRODUCT.ITEM)]]>
</PrecomputeCondition>The PrecomputeCondition is also visible through the USER_CUBES view.
SELECT PRECOMPUTE_CONDITION
FROM USER_CUBES
WHERE CUBE_NAME = 'MY_CUBE';You can hand modify this condition in the XML to specify an alternative 'non level based' precompute condition for any dimension. For example, if you define an attribute named 'SHOULD_PRECOMPUTE' on your PRODUCT dimension that is 1 for members to be precomputed and 0 for all others, then you can change the condition as follows.
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
</PrecomputeCondition>If you recreate the cube from the XML with this condition, then the PVSET valueset you discovered should contain all dimension members for which the attribute value is 1.   This gives you complete control over what is precomputed.   Note that AWM doesn't support this form of condition, so it won't show up if you go to the Precompute tab, but it is valid for the server. The PL/SQL below will modify the PrecomputeCondition (for the cube named MYCUBE) without going through AWM.
begin
dbms_cube.import_xml(q'!
<Metadata
Version="1.3"
MinimumDatabaseVersion="11.2.0.2">
<Cube Name="MY_CUBE">
    <Organization>
      <AWCubeOrganization>
        <PrecomputeCondition>
          <![CDATA[
           "TIME" LEVELS ("TIME"."MONTH","TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
           CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL,CHANNEL.CHANNEL),
           CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT,CUSTOMER.REGION,CUSTOMER.SHIP_TO),
           PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
        </PrecomputeCondition>
      </AWCubeOrganization>
    </Organization>
</Cube>
</Metadata>
end;
/

Value based dimension hierarchy in OBIEE 10G

Similar Messages

Maybe you are looking for