Dimensions, Levels and Keys

Folks,
I am trying to deploy and load a dimension table composed of the following columns:
Company Id
Company_Name
Corporation_Id
Corporation_Name
Cost_Center_Id
Cost_Center_Name
I have created three levels: Company, Corporation and Cost Center. Each Level is composed of the corresponding id and name.
I have also created a single hierarchy, composed of the three levels: Company, Corporation and Cost Center.
When I deploy the script, it creates a Unique Key constraint composed of the key at the lowest level - Cost_Center_Id.
However, it is the combination of Company_Id, Corporation_Id and Cost_Center_Id that is required to uniquley identify a row in the dimension table.
Any clue as to what I am doing wrong?
Thanks. Bruce

Hi,
I believe hierarchies in OWB are One to Many. In your example, a company can have many corporations and a corporation can have many cost centers, but a cost center can only belong to one corporation and a corporation can only belong to one company. If this was the case, then Cost_Centre_id would be the unique key. You're saying that the combination of Company_Id, Corporation_Id and Cost_Center_Id is the unique key, and this leads me to believe that you don't actually have a hierarchy (the way OWB sees it) One way to handle this is to put all the columns in a single level, and add a unique identifier for each possible combination of the three.
If you look at "best practices" I think you'll find that you should always use a single synthetic numeric value as your primary key in a dimension table. This ensures the most efficient join to the fact table. (If you have a three column key, you need all three columns in the fact table, wasting space and creating a more complex join) Also, you should try to avoid using any keys from an OLTP system as a key in your dimension.
Hope this helps,
Roald

Similar Messages

Facts at different Logical Dimension Level and Default Interaction (Drill)

I have one Geography Logical Dimension that consists of 3 physical tables snowflaked. The 3 tables are City, State and Country. I have created 3 Level Based Hierarchies.
I have 2 Facts. Fact_State is at the State grain only (Set the appropriate Content Level). Fact_City is at the City grain (Set the appropriate Content Level).
When I pull a query with Country and a metric from Fact_State, the default interaction allows me to drill down. I drill into the State values. I would assume that the Drill interaction would stop here since this metric (Fact_State) is only at this level.
What actually occurs is it allows for a drill into City and when you look at the Physical SQL it is trying to hit the other Fact Table (Fact_City) and pulls back no metrics. I then return no data.
I would ask does anyone know if this is the expected behaviour? Is there anyway to stop the drill at the State Level when metrics are only pulled from the State Fact?
Please let me know if more information is needed.

You need to have a metric sourcing from both Fact_State and Fact_City, provided both facts are as Logical sources for the logical fact table.
Make sure Fact_State got proper level and Fact_City got detail level.
When you pull Country or State with metric query should hit Fact_State, when you drill down below the state query should be from Fact_City with proper data.
Edited by: Srini VEERAVALLI on Mar 28, 2013 2:43 PM
I can look into your new post only If you update this or older posts. Still you may get responses from others ;)
Edited by: Srini VEERAVALLI on May 22, 2013 2:00 PM

Difference between Dimension Id and Dimension Key

I am reading the third chapter of Rittman's OBIEE book on design of Repository.
It says while building the BMM, don't drag the dimension Id columns from physical layer to logical layer as the BI Server takes care of the join for you but make sure you drag across the dimension key columns as you will need these later on to create your logical table keys.
Can someone enlighten me on what is the difference between a dimension id and dimension key (may be with an example).
Thanks.

Besides the theory says that a fact table can reference any level of a dimension, I couldn't do it with OWB. I don't know if there is a specific way to do that, but I only could assign a dimension detail level to a fact table.
The ID's can have different values when I use a hierarchy in a dimension. OWB generates automatically negative ID's for the more summarized levels.
For example, a product dimension with 2 levels: category and detail. If the product has 4 categories and 20 products (detail level), the table has 4 rows for categories with negative id's. Each row has a category and the fields specific for detail level are empty. The table will have other 20 rows for the detail level, with all fields filled, and all id's positive. The table will have 24 rows in the end.

My battery life at a full 100% charge is about 2 hours 22 minutes (backlight and key lights at lowest level). Should I go complaining to Apple or do I just need different software?

My battery life at a full 100% charge is about 2 hours 22 minutes (backlight and key lights at lowest level). Should I go complaining to Apple or do I just need different software? I've only had my mac book since August 2011. The battery dies in 2 to 3 hours with some web surfing (little video play) and photo editing etc. I really don't feel like taking my computer all the way to the apple store to wait there for 5 hours to hear that I need to call someone blah blah blah. Any advice? (BTW Safari hasn't been working since I last updated my mac, WHYYYY?)

emsavage1127 wrote:
Should I go complaining to Apple or do I just need different software?
emsavage1127 wrote:
I really don't feel like taking my computer all the way to the apple store to wait there for 5 hours to hear that I need to call someone blah blah blah.
Make an appointment at the genius bar, that way, you wont have to wait. http://www.apple.com/retail/geniusbar/

Creating dimension in OMB script with only 1 level and no hierarchy

Hi all,
I have created some dimensions in the OWB client, that map straight 1-on-1 to a table. Those dimensions have only 1 level 'TOTAL' and no hierarchies.
I am trying to create those dimensions using an OMB script, but it seems that when I bind the dimension level to a table, it =expects= me also to bind hierarchy levels to the table! However I have (dont want/need) a hierarchy?!
The error message is:
OMB00001: Encountered DIMENSION_KEY at line: 1, column: 2309. Was expecting one of: <EOF>
The OMB code I have is:
IMPLEMENTED BY SYSTEM STAR \
DIMENSION_KEY BOUND TO COLUMN 'DIM_CAUSE_KEY' \
LEVEL 'TOTAL' BOUND TO TABLE 'DIM_CAUSE' \
LEVEL_ATTRIBUTE 'DIM_CAUSE_KEY' OF LEVEL 'TOTAL' BOUND TO COLUMN 'DIM_CAUSE_KEY' \
LEVEL_ATTRIBUTE ...
LEVEL_ATTRIBUTE ...
After the LEVEL_ATTRIBUTEs the statement ends, so I say nothing about any hierarchies.
If anybody could give me a hint, that would be much appreciated!!
Ed

It is finally solved...
The keyword "SYSTEM" in "IMPLEMENTED BY SYSTEM STAR" shoudn't be there...
Unfortunately I was overlooking that in the oh-so-clear syntax diagram in the OWB API and Scripting Reference..... )-;
Let's move on.
Cheers,
Ed

High level overview and key features - Urgent

Dear all Hi,
Please suggest me some points a i have to prepere one single slide PPT indicating the PP's high level overview and key features.
Please help
thanks in advance.

You coverthe overall general cyle involved in PP like
1 Receipt of sale order
2 MRP
3 Production Planning
4 Shop Floor Control(Planned order to prod order,Capacity planning,GI,Confirmation,GR,Settlement)
Key Features
1 Highlight the features of MRP
2 Capacity Evaluvation/Planning
3 Reports etc
Hope this is useful
Revert back if you have any further queries
Reward points if useful
Regards,
SVP

ECO number with revision level and release key

Hi All,
I have a requirement from client with regards to Engineering change manangement.
The scenario is that we are maintaining BOM for materials.Whenever a change is required for BOM a ECO number is created with release key.
Once the BOM is changed against ECO number is created a workflow is triggered for approval.
Then it goes through a series of approvals in the heirarchy.In each level the reviewer will propose a new value for the changed line item.
All these changes have to be maintained in record.At the end the final approver reviews all the proposed changes and release the ECO number with the appropriate change.
I had a thought of implementing the above scenario with ECO with revision level and release key.
But I am unable to replicate the scenario due the fact that,when I select the ECO number with release key,I cannot select the material in Object type.
Its disabled.Its available when I create a ECR with release key.
Please suggest a way to create ECO number with release key and revision level for BOM.
Regards
Richie

Hi,
You create the revision level against the material (via MM02, basic data tab)) not against the serial. The serial number, by definition, would be unique to the combination of material and revision.
Regards

The table name or tcode to count the number of Dimensions and Key Figures

Hi all,
Do you have an idea about the table name or tcode to count the number of Dimensions and Key Figures of an Infocube WITHOUT installing the cube from Business Content?
Thanks in adv.
Ajay

Hi,
You can't do that because there's no active table in the system for the Business Content since it hasn't been installed yet...
One thing you could do is go to the Business Content Tab, select "Infoproviders by InfoArea" on the left side, look for the Cube or DSO you want to check, right click on it and select "Display Description".
On the window that opens you'll have a list of all InfoObjects and Key Figures. You also have the option to Display it as Start Schema, where you can see the Dimensions, etc.
Hope this helps.
Luis

Join fact table with higher dimension level

how do i join fact tables with higher dimension levels with discoverer?
fact with detail at level C
measure X
dimension with
D->C->B->A
E->C
level
A B C
1------1------1
2------2------1
3------2------1
join between fact X and dimension level C
X=3*C because of sum(X) in discoverer and 3xC in dimension
is there a way to get correct values for X without creating a dimension like
D->C
E->

another way of asking this is whether you can create a summary table in Discoverer at a higher level than a dimension's fundamental grain. In other words - the summary examples in the documentation all describe leaving out one or more of your dimensions... they are either left in or completely taken out. But, some of the most effective summarization occurs when you summarize daily data to a monthly level. Assuming that I have a sales table (at a daily level, and a key value sales_date), and a table date_dim (primary key sales_date), I would like to create a summary sales_month_summary where the sales are grouped on month_year (which is a field in the sales_date table).
How is this done? I suspect that we can't use the date_dim table with the summary (due to the problems noted by the poster above). Do we have to create another table "month_dim"? Do we have to fold all of the desired date attributes (month, quarter, year) into the summary? Obviously we'd like to re-use all of the pertinent already existing date items (quarter, month, year, etc.), not recreate them over again, which would result in essentially two sets of items in the EUL. [One used for this month summary, and another used for the detail.]
I searched the forum - someone asked this same question back in 2000 - there was no answer provided.
The only other thought I have is to "snowflake" the date_dim into two tables and two folders, one at a date level, another at the month level. Then the detail tables can connect to date_dim (which is linked to month_dim), while the summary data can connect directly to month_dim.

Logical column levels and aggregation

Hi all,
In order to have reliable results, I had to specify a dimension level in a logical column properties.
As a consequence, the generated query includes this level in the query (that's great), but no aggregation is performed afterwards. Therefore, when I display this measure alone in a flat table or a ticker, I have a set of detailed value instead of an aggregated value. The only place where I can see my aggregated value is in a pivot table.
In answers, I tried to :
- replace the default aggregation by an explicit SUM, or
- add a SUM() in the measure formula
but neither solved the issue.
Does anyone know how to solve it?
Thanks in advance.
Ced.

Hi,
What is the source for AGO measures PriorDollars and PriorUnits?
AGO(CurrentUnits, '?',?)
AGO(CurrentDollars, '?',?)
Have you set up hierarchy correctly (because you said that the granularity in your fact table is at week grain) and it should be like this:
Fiscal Year > Fiscal Quarter > Fiscal Month > Fiscal Week
It depends on how did you define your TIME dimension.
Try maybe like this:
PriorYEARDollars = AGO(CurrentUnits, 'YEAR',1)
and the same for
PriorYEARUnits =AGO(CurrentDollars, 'YEAR',1)
Now, if you put in the report
YEAR
CurrentUnits
CurrentDollars
PriorYEARUnits
PriorYEARDollars
you'll get only three rows (for 3 years) with PRIOR YEAR measures.
Try it.
A good reference for understanding AGO:
http://obiee101.blogspot.com/2008/11/obiee-ago-and-todate-series.html
Also you need to set chronological key correctly for TIME dimension.
Regards
Goran
http://108obiee.blogspot.com

How to map a cube to a non-leaf dimension level?

Hi,
I'm using AWM 11.2.0.1.0 and Oracle 11.2.0.2.0 on a CentOS 5.4 64-bit system.
I have a time dimension with levels Year, Month, Day, Hour, Half-Hour and several cubes mapping to the Half-Hour level. Now I'm trying to populate a cube using a time hierarchy Year/Month/Day, i.e., the mapping should be done at the Day level, not Half-Hour.
When adding the time dimension, although I specify that aggregation should be done only on the Year/Month/Day hierarchy, I still see all the levels in the mapping view. And when I try to map the Day level to the fact table, I get the following error:
The transaction is not committable: "Invalid Metadata Objects:
Invalid Object "OLAPIN.SSD_BALANCE.MAP1.DATETIME": "XOQ-01930: The cube dimensionality map has no mapped dimension."What is strange is that this used to work on version 11.1.0.7.0 (I have an example of it right in front of me). Am I supposed to do things differently with the new 11.2 version?
Thanks for your help!
Chris

My guess is that this is a result of
BUG 8264467 - REGRESSION FROM 10G : CANNOT LOAD CUBE DATA AT MULTIPLE LEVELS
This was fixed in 11.2.0.1 on the server and may appear to have nothing to do with your problem. Unfortunately there was a bug in the corresponding change in 11.2.0.1 AWM that can cause the symptoms you are having. It may be related to the following AWM bug.
BUG 8889693 - SUMMARY LEVEL MAPPING DOES NOT WORK IF USING DIMENSIONS WITH SURROGATE KEYS
There is an AWM "A Patch" for 11.2.0.1 (Patch 9672534: AWM 11.2.0.1A) that fixed the above bug and several other mapping related problems. You could try this to see if it fixes your problem.

How to improve the query performance in to report level and designer level

How to improve the query performance in to report level and designer level......?
Plz let me know the detail view......

first its all based on the design of the database, universe and the report.
at the universe Level, you have to check your Contexts very well to get the optimal performance of the universe and also your joins, keep your joins with key fields, will give you the best performance.
at the report level, try to make the reports dynamic as much as you can, (Parameters) and so on.
and when you create a paremeter try to get it match with the key fields in the database.
good luck
Amr

Max no. of Characteristics and key figures stored in infocube

Hi All,
What is the maximum number of characteristics and key figures that can be stored in the infocube?
Best Regards,
Chandan Dubey

Alright,
Now what I know about that is max 255 chars and 255 key figures can be stored. Here I am talking about the individual planning levels (like product, product group, customer, location and so on) and not the "DATA". I know data storage can not be defined in numbers and no significance too.
I hope my question is clearer now !!
Best Regards,
Chandan Dubey

How to know on which time dimension level we are ?

Hello,
I would like to know is there a variable or a mean to know dynamically on which time dimension level we are in order to use that in a CASE WHEN clause ?
By using a sort of aggregation tables in which one of the column contains the name of the level, I could know on which level I am but I can't use that for drill down. What I mean :
Tab1 :
'Year' as typelevel, year
Tab2 :
'Month' as typelevel, year, month
In BMM, I have made one logical table with as Source tab1 and tab2 and as columns typelevel, year and month.
tab1 has in content column the year level
tab2 has in content column the month level.
So when in Answers I retrieve
typelevel, year
the result is : 'Year', 2008
and when I request : typelevel, year, month
the result is : 'Month', 2008, 1
But if I want to drill from year to month in order to have :
'Year', 2008
and then after drill
'Month', 2008, 1
it is impossible as a filter on typelevel='Year' is added on the month level, so it retrieves 0 columns.
If someone has an idea on how to do that it would be very great.
Thanks in advance for your help.

Hi Supriya,
OOTB I think you can use SharePoint designer, but I would suggest custom code to iterate to all pages, and get the lists that are associated with these pages.
http://stackoverflow.com/questions/633633/sharepoint-how-can-i-find-all-the-pages-that-host-a-particular-web-part
another one would be if those lists were never used and you can check for list with empty data.
I would use Get-SPLists to get all of the lists to check for zero items.
http://blogs.technet.com/b/heyscriptingguy/archive/2010/09/15/use-windows-powershell-to-manage-lists-in-sharepoint-2010.aspx
http://sharepointrelated.com/2011/11/28/get-all-sharepoint-lists-by-using-powershell/
Hope this helps!
Ram - SharePoint Architect
Blog - SharePointDeveloper.in
Please vote or mark your question answered, if my reply helps you

Dimension 2300 and Solaris 10

Hi guys....
I just installed Solaris 10 (Dec 8, 2004) on a Dell Dimension 2300 and it doesn't seem that I can start the graphics interface. Right now it's sitting at level 3 (text only) and I'd love more than anything to bring it to level 5.
I'm brand new to Solaris and dont know yet where to go get patches and/or drivers to support the monitor and graphics card... can someone help?
The video card for this machine is Intel 845. I did run the xorgconfig tool (according to another thread in this forum) and changed the video card to Intel 810 (They dont have 845 in the list). Still not able to start the xserver.
Will keep looking while waiting for an answer... Thanks all! Have a nice day...
Kevin

Seems like you're used to Linux. In Solaris run-level 5 is shutdown+poweroff.
Try to configure the graphics adapter by using the "kdmconfig" command. Choose "Xsun" and pick the following driver:
XF86-I830 Intel integrated graphics chipsets: 830, 845, 852, 855, 86
After you're finished with kdmconfig start X-Windows using the following command:
/etc/init.d/dtlogin start
Regards,
Martin Andersson

Dimensions, Levels and Keys

Similar Messages

Maybe you are looking for