Creating logical levels in a dimension

Hi,
I have created a Dimension 'Group Inventory Type'. Is it possible to display two logical columns on a specific level (Parant Inv Type and Inventory Type)?
Top Level
Group Inventory type
Parant Inv Type and Inventory Type
Details
Regards Robbert
(version 11G)
Edited by: RobbertD on Dec 16, 2010 4:39 AM

I will expand on the prior example to ask another dimension related question.
ROW - 1
PRODUCT_CATEGORY - DAIRY, FARM_NAME
PRODUCT - NULL
ROW - 2
PRODUCT_CATEGORY - DAIRY, FARM_NAME
PRODUCT - 2L MILK, FAT_CONTENT
Q1: I need to join to another table on DAIRY, and to pull the FARM_NAME and the attributes from the second level (2L MILK, FAT_CONTENT). How do you guys do something like this in practical terms - check where the surrogate key for the second level is not null? One could also join on DAIRY where 2L MILK or FAT_CONTENT are not null?
Q2: The other area where I am unclear is whether to use in the mapping the dimension object or the bound table. If I try to use the dimension then OWB will not let me do this because you can not source from more than level at the same time. I guess I will have to use a join? The other option is to use the table, but witht a complex large dimension that can get messy. So ... what is the correct approach in general - use dimensions or the underlying tables in a mapping?

Similar Messages

Logical level for logical fact table sources

it is clear that for fact aggregates, we should use the Content tab of the Logical Table Source dialog to assign the correct logical level to each dimension.
question is : is it mandatory to assign even for non-aggregates fact tables the logical level for each dimension (which normally should be set to the most detailed level of each dimension) ? is it any known issue if "logical levels"in content tab are not set ?
the reason I'm asking this is a strange bug I have (I'm not going to discuss it here) and then only workaround seems to be NOT setting the logical levels (on content tab) for logical fact table sources.
thank you !

If levels are not set: By default levels are considered as lowest level
It should not matter if you set or not
Generally we set for facts explicitly when we are using Aggregate tables.
Your current issue might be a case by case; I would suggest to check implicit fact, any table mapped to the source to force a join etc
Mark if helps
Let me know how it helps
Edited by: Srini VEERAVALLI on Feb 5, 2013 8:33 AM
Any updates on this?+_
Edited by: Srini VEERAVALLI on Feb 14, 2013 9:09 AM

Use of New logical Level Key in OBIEE

Hi all,
can anybody tell me what is the use of newlogicallevel key in hierarchies(OBIEE).
why we need to set a newlogical level key for each level in hierarchies.
pls explain in detail....
regards
bharath

You may get info as below if you use Admin tool help file
Level keys. Each logical level (except the topmost level defined as a Grand Total level) needs to have one or more attributes that compose a level key. The level key defines the unique elements in each logical level. The dimension table logical key has to be associated with the lowest level of a dimension and has to be the level key for that level.
A logical level may have more than one level key. When that is the case, specify the key that is the primary key of that level. All dimension sources which have an aggregate content at a specified level need to contain the column that is the primary key of that level. Each logical level should have one level key that will be displayed when an Answers or Intelligence Dashboard user clicks to drill down. This may or may not be the primary key of the level. To set the level key to display, select the Use for drill down check box on the Level Key dialog box.
Be careful using level keys such as Month whose domain includes values January, February, and so on—values that are not unique to a particular month, repeating every year. To define Month as a level key, you also need to include an attribute from a higher level, for example, Year. To add Year, click the Add button in this dialog and select the logical column from the dialog that is presented.

Create a Total over Year Dimension

Does anybody have an idea on how to create a total over the Year dimension in Hyperion Planning (11.1.2 - Still using the Classic App since EPMA components seem tio not working properly on windows server 2008 R2 x64.)
or has an idea which of the following would be a valid approch since I cannot define aggregation to the Year Node in Planning. No addition seems to be possible possible. Background is to get the total over 5 up to 15 years for a long term capital expenditure strategy.
The following ideas came to mind:
1.) FY09 + FY10+ FY11 as a dynamic calc on the last year in the system (as a formula)
2.) Create a calculation rule that aggregates Year (but i cannot seem to be able to change the years to addition
I would appreciate your input or any additional ideas.
Best Regards
Andre

Hi,
Yes, you can't create aggregation levels in Year dimension. But you have period dimension in which you can create dynamically calculated base time periods which you can use combined with No Year.
So create a member in Period Dimension called Total of 3 Years. Place a member formula in it (IF(@ISMBR("No Year") FY09+FY10+FY11; ENDIF).
You can use this period combined with No Year.
Cheers,
Alp

Help on Setting logical Levels in Fact tables and on Dimension tables

Hi all
Can any body provide any blogs or any king of material on what exactly is levelling .
Like after creating the Dimensional hierarchies we need to set the logical levels for the LTS of fact tabels ri8 .So what is the difference between setting logical levels to fact tabels and also Setting levelling on Dimension tables .
Any kind of help is appreciated
Thanks
Xavier.
Edited by: Xavier on Aug 4, 2011 10:50 AM

I have read these blogs ,but what my question is
Setting the logical levels in LTS of Fact tables i understood .
But we can also set the logical levels for dimensions also ri8 .I didn't understand why do we set the logical levels for dimensions .Is there any reason why we go with the levelling at dimensions
Thanks
Xavier
Edited by: Xavier on Aug 4, 2011 2:03 PM
Edited by: Xavier on Aug 4, 2011 2:32 PM

Logical level Dimensions

Hi,
I am setting up a new heirarchy in Business level RPD, and in the new "Dimensions", the tab "Tables" is disabled, i tried opening it in both online as well as offline mode, same issue.
When I add a new "Logical Level" object under it, the "Add" child level key is also disabled. Please help.
Thank you.

hi,
when you create new dimension, by default the "tables" tab will be disabled because there are no tables in the dimension. and if you give right click on the new dimension it shows only logical level because there must be atleast one level to create the child and parent levels.for that you just select the columns from the dimension table and drag them into the logical level created in the dimension. and now the parent level and child level will be enabled.this is the process to create the hierarchy if you select "create new dimension" instead of this you can directly go to the dimension table in the BMM and give right click and select create dimension option. this will create the dimension hierarchy.
hope you understood...

Unable to create logical dimension in bmm layer

Hi all,
I am not able to create a logical dimension hierarchy in the bmm layer of the rpd.
when I right click on the table I am not able to find the create logical dimension option in the popup window.
could you please help me out in this?
In the logical table we have data from sql statement also.
Thanks!

Create Dimensions is only available if the selected logical table is a dimension table (defined by 1:N logical joins) and no dimension has been associated with this table.
To create a dimension automatically, the Administration Tool examines the logical
table sources and the column mappings in those sources and uses the joins between physical tables
in the logical table sources to determine logical levels and level keys.
Hope you have defined the Logical join in BMM before looking for this option. If joins are not defined, this option won't come.
Refer http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf
Page 133, Creating Dimensions Automatically
Hope its useful

How to create a custom measure for each level of a dimension

Hi all!
Can Anyone please explain me with an example, how to create a custom measure for each level for a dimension? I dont mine if you use
one or more measures.
thanks in advance
hope someone helps me.

For example:I create a dimension for product_dim witch has 4 levels:total, class, family and item:
d_aben18
n1_aben18
n2_aben18
n3_aben18
n4_aben18
herarchy:h_aben18
cube:cubo_aben18
measure:med_aben18
I create this code to fetch the data to the dimension:
TRAP ON CLEANUP
SQL DECLARE c1 CURSOR FOR SELECT-
total_product_id,1,'N1_ABEN18',total_product_dsc,-
class_id,1,'N2_ABEN18',total_product_id,class_dsc,-
family_id,1,'N3_ABEN18', class_id, family_dsc,-
item_id,1,'N4_ABEN18',family_id,item_dsc-
FROM PRODUCT_DIM
"OPEN THE CURSOR
SQL OPEN c1
"FETCH THE DATA
SQL FETCH c1 LOOP INTO-
:APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N1_aben18_LEVELDEF,:D_ABEN18_long_description,-
:APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N2_aben18_LEVELDEF,:D_ABEN18_parentrel,-
:D_ABEN18_long_description,-
:APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N3_aben18_LEVELDEF,:D_ABEN18_parentrel,-
:D_ABEN18_long_description,-
:APPEND D_ABEN18, :D_ABEN18_H_aben18_HIERDEF,:D_ABEN18_N4_aben18_LEVELDEF,:D_ABEN18_parentrel,-
:D_ABEN18_long_description,-
"SAVE THE CHANGES
UPDATE
COMMIT
CLEANUP:
SQL CLOSE c1
SHOW 'KK2'
Then I create a cube with use compression off, and in rules sum for example.
After, I create a measure and I select Override the aggregation specification for the cube, in rules I put nonadditive and I would like to create aprogram to assign distinct values to each level of the dimension. For example, I put 1, 2 3, and 4 values, but at the end I would like to put count(distinct(values)).
for that I create another program:
VRB D_RETURN DECIMAL
if D_ABEN18_N1_ABEN18_LEVELDEF eq 'N1_ABEN18'
then D_RETURN = 1
if D_ABEN18_N2_ABEN18_LEVELDEF eq 'N2_ABEN18'
then D_RETURN = 2
if D_ABEN18_N3_ABEN18_LEVELDEF eq 'N3_ABEN18'
then D_RETURN = 3
if D_ABEN18_N4_ABEN18_LEVELDEF eq 'N4_ABEN18'
then D_RETURN = 4
else d_return=26
return d_return
"SHOW D_RETURN
cubo_aben18_med_aben18_stored=d_return
but it doesnt work.I dont know how to put to assign or to see what I want.
I report the measure, or I report the program, but then how can I see the values of the measure?
thanks in advance

Creating sublevels under levels for a dimension in AWM Oracle 10g

In Analytic Workspace Manager Oracle 10g, How can I create more sublevels under a particular level in a dimension?
for eg. Year is a dimension.It has 2 levels , Quarter and Month.
Under Quarter level I want to have Qtr1 and Qtr2 as sublevels.
Under Month level I want to have Jan,Feb,Mar,Apr,May,June as sublevels.
so that Qtr1 has Jan,Feb,Mar, and Qtr2 has Apr,May,June

You need to do this in your source table.
The source table can look something like this
qtr_id, qtr_name, month_id, month_name
1 , Qtr1 , 101 , january
1 , Qtr1 , 102 , febuary
1 , Qtr1 , 103 , march
2 , Qtr2 , 104 , april
2 , Qtr2 , 105 , may
2 , Qtr2 , 106 , june
Then map it to the dimension, and maintain it.
Keep in mind that the member(id) fields need to be unique. I.E january 2007 and january 2006 cannot have the same id.
Ragnar

Why we have to create logical key at levels in Hierarchies

hi
i have one doubt that what is the use of logical key at levels in hierarchies directly we can create logical primary key and we can enable for drill down option
what is the use of creating logical key at levels (what i known is that is for unique column in the logical level)
i need small example for this
apart from that why we have to create logical key in logical tables in bmm layer so what is the need of it
Thanks
Sreedhar

hi Sreedhar,
I suggest you to go through
http://download.oracle.com/docs/cd/E12103_01/books/admintool/admintool_BusModSetup20.html#wp1005703
will clarify your doubts :-)
Thanks,
Saichand.v

Logical level in Fact tables - best practice

Hi all,
I am currently working on a complex OBIEE project/solution where I am going straight to the production tables, so the fact (and dimension) tables are pretty complex since I am using more sources in the logical tables to increase performance. Anyway, what I am many times struggling with is the Logical Levels (in Content tab) where the level of each dimension is to be set. In a star schema (one-to-many) this is pretty straight forward and easy to set up, but when the Business Model (and physical model) gets more complex I sometimes struggle with the aggregates - to get them work/appear with different dimensions. (Using the menu "More" - "Get levels" does not allways give the best solution......far from). I have some combinations of left- and right outer join as well, making it even more complicated for the BI server.
For instance - I have about 10-12 different dimensions - should all of them allways be connected to each fact table? Either on Detail or Total level. I can see the use of the logical levels when using aggregate fact tables (on quarter, month etc.), but is it better just to skip the logical level setup when no aggregate tables are used? Sometimes it seems like that is the easiest approach...
Does anyone have a best practice concerning this issue? I have googled for this but I haven't found anything good yet. Any ideas/articles are highly appreciated.

Hi User,
For instance - I have about 10-12 different dimensions - should all of them always be connected to each fact table? Either on Detail or Total level.It not necessary to connect to all dimensions completely based on the report that you are creating ,but as a best practice we should maintain all at Detail level only,when you are mentioning any join conditions in physical layer
for example for the sales table if u want to report at ProductDimension.ProductnameLevel then u should use detail level else total level(at Product,employee level)
Get Levels. (Available only for fact tables) Changes aggregation content. If joins do not exist between fact table sources and dimension table sources (for example, if the same physical table is in both sources), the aggregation content determined by the administration tool will not include the aggregation content of this dimension.
Source admin guide(get level definition)
thanks,
Saichand.v

Logical level

Hi,
I created a logical column that derived from a EVALUATE function that called a database package (returning VARCHAR(30)) in Oracle. I don't know what I should enter for the "logical level" in that logical column. I have a date hierarchy that is like Total > Year > Quarter > Month > Date.
Any suggestion?
Thanks.
Andy

Hi User,
For instance - I have about 10-12 different dimensions - should all of them always be connected to each fact table? Either on Detail or Total level.It not necessary to connect to all dimensions completely based on the report that you are creating ,but as a best practice we should maintain all at Detail level only,when you are mentioning any join conditions in physical layer
for example for the sales table if u want to report at ProductDimension.ProductnameLevel then u should use detail level else total level(at Product,employee level)
Get Levels. (Available only for fact tables) Changes aggregation content. If joins do not exist between fact table sources and dimension table sources (for example, if the same physical table is in both sources), the aggregation content determined by the administration tool will not include the aggregation content of this dimension.
Source admin guide(get level definition)
thanks,
Saichand.v

Number of elements at logical level / odbc driver

Hi everyone,
I'm new in BI area and I cannot understand one basic thing.
I study documentation about BI server, exactly chapter about "creating dimensions" and I'm confused about setting "number of elements at logical level"
It looks for me that "number of elements at logical level" is static.
What will be when someone update data in the table and number of elements will be different than number of elements in our logical level?
example:
current column with distinct values:
channel_desc:
direct sales
tele sales
catalog
internet
partners
in this case I set number of elements at logical level 5.
after a while some update data in the table and our column looks (see below)
column after update with distinct values:
channel_desc:
direct sales
tele sales
catalog
internet
partners
others (added value)
Does it mean that I have to change it to current numbers of elements?
I'm sure that this is misunderstanding in my case, but I don't know where?
Second problem which I have:
BI with oracle database is on linux
client software on windows
I can import data from database like sybase or flat files to the physical model, I can view data, but when I create whole model (physical, bussines model and mapping, presentation) and I try access data from "Answers" I have this error:
"Data source name not found and no default driver specified"
regards
Bart

Number of elements is just an indication used by the BI Server (e.g. when generating LOV's in Answers). It won't cause any problems when it doesn't hold the exact number of elements available in the dataset.

Measure Aggregated at Logical Level causes poor performance

OBIEE 11g
We've recently implemented a new measure which involves aggregating a Period expenditure figure up to the Fiscal Year level.
I've duplicated the existing Period_Expenditure rename to FY_Expenditure, and then changed the logical level for the Time dimension to Fiscal Year.
I get the figures I expected, however the OBI SQL generated wasn't what I expected.
We now have the main SQL as before but now its left outer joining to a 2nd SQL statement that does the aggregation, which is pretty expensive in terms of Logical IO. Elapsed time going from 2 seconds to 20 seconds.
I would have expected the BI server to be clever enough to apply analytics to solve this problem - has anyone else had similar issues when using aggregates like this?
Thanks in advance,
Matt

I'm going to answer my own question here as I've managed to build a simplified solution, it may help others.
Basically the Analyses this is running for is:
select measures, FY_Measure
from fact_table
where period = 'MMYYYY';
Because we don't have the full set of data within this SQL to enable coverage for the FY_Measure (ie. we're at period level granularity) OBIEE is smart enough to create a 2nd query to get the data required for the year.
If we change the analyses to be:
select measures, FY_Measure
from fact_table
where FY = '2012';
It will quite happily create analytics to satisfy the measure - fairly straightforward really.

If Logical level mappings are blank in an LTS , what does it mean?

Hi All,
I was trying to find this out in the forum but couldn't.
In my LTS, on the content tab, if i don't specify any "Aggregation, group by" information for the dims associated with my Fact table and keep it blank, then what does it mean? Would OBIEE treat this as at the detail level by default? So to test this, I created a logical fact and for its LTS, i didn't associate any logical level for dimensions. The query didn't give me any error and worked fine by using the correct join details.
Also when do we associate an LTS with the Total Level for a dim, what's the use because as I understand, this means all our measures from that LTS would be calculated for the total level of the dim and we can do this by creating level based measure and associating it with the total level of the dim.
I'll be thankful if somebody could explain me this in detail or direct me to a relevant documentation/ blog
Thanks,
Ronny

Hi,
When you have only one logical Table Source(LTS).
You don't specify the logical levels. By default it would consider the detail level of the logical levels mapped to the fact table.
When you have Multiple logical Table Source(LTS).
The concept of Multiple LTS comes into picture when you have multiple sources. The BI server picks the optimum logical source depending upon the fields (columns) selected. And also depends on the Number of element set while creating the dimension hierarchies. Refer-http://gerardnico.com/wiki/dat/obiee/level_number_element
For example- Suppose you have two logical table source Fact 1 and Fact 2 and logical levels( dimension hierarchies are created for two dimensions Dim 1 and Dim 2).
For the first Fact 1 source logical level is mapped only with Dim 1 and Fact 2 is mapped to Dim 2.
(You need to decide which fact source to hit depending upon the dimensions used in the report.)
Then in the report when you select Dim 1 (by means of column selector/filters) then Fact 1 source will be hit and same appears in the query.
Then in the report when you select Dim 2 (by means of column selector/filters) then Fact 2 source will be hit and same appears in the query.
One more situation where you have mapped Fact 1 with Dim 1 First level of aggregation and Fact 2 with Dim 1 with Detailed level. Then the BI server picks depending upon the user's request. If the request data can be pulled from the detailed level ( which tends to be optimum then picks from the second source).
So, its always better to set the logical source and check the query, if its hitting the correct sources according to the requirements.
Regards,
MuRam

Creating logical levels in a dimension

Similar Messages

Maybe you are looking for