Keys in a Dimension Level

Hi,
I am creating a Dimension with two levels.
As every level must have two identifiers: a surrogate identifier and a business identifier.
when I create the dimension, i can define surrogate key for the first level as well as business identifier. But for the second level I am able only to define the business identifier and am not getting the option of surrogate identifier.
Please, guide me.
I am using OWB 11G on windows XP.
thanks in advance

You may have more luck getting an answer to this question on the Warehouse Builder forum. I am not aware of any difference in the handling of levels at the AW level. You could also consider using AWM to define your AW, since this would let you take advantage of the new features in 11g. (I believe OWB support is currently limited to 10g style AWs in an 11g instance.)
Link: Warehouse Builder

Similar Messages

  • 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

  • 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.

  • Security at a dimension level in a Planning Application (ver 9.3.1)

    Hi,
    I'm dealing with the Assign Access process in the Dimensions pane.
    Is it possible set access at dimension level?
    How can I set the member Account (root of Account Dimension) visible for only a subset of user?
    Thanks in advance.
    Stefano

    Hi Stefano,
    I'm currently using Hyperion Planning version 4.0.2. I tried using the ImportSecurity.exe file to update the security for the top member in Entities dimension (ie the dimension name itself) but it kept giving me this error:
    Record not processed -Finance,Entities,READ,MEMBER- Invalid Member name.
    All lines in Import Security file were successfully parsed.
    No records inserted into the database.
    1 Lines were not processed by the application due to errors.
    My secfile.txt file looks like this:
    Finance,Entities,READ,MEMBER
    Am I doing anything wrongly?
    Thanks for your help!
    Michelle

  • 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/

  • 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

  • Loading Parent Keys in Customer Dimension

    I have a question about how to setup my mapping for my Customer Dimension. A subset of the dimension attributes is below:
    Customer_Key (Surrogate Key)
    Customer_Number
    Parent_Key
    Bill_To_Key
    My source table has the following fields:
    Customer_Number
    Bill_to_Customer_number
    Parent_Customer_number
    I am having difficulty in visualizing this because I can see where the current record may be for customer 10 and its parent is customer 20. Since I have not loaded the record for customer 20, I cannot use a lookup to get the surrogate key for customer 20 as it does not exist. So, my only thought was to load the dimension without the parent and bill_to keys and then run a post-mapping process to update the missing fields. This works, but takes an extremely long time (4 hours) as there are over 300,000 records that it has to update. Maybe my post-mapping process was just inefficient, I am not sure. What I am doing is running an update command on my dimension and looking up the customer-numbers from my staging table, then looking up the surrogate key in my dimension.
    Is there a better, more efficient, way to do this?
    Thanks,
    Jason

    I did a little more work with this and have developed at procedure in the post-mapping process that updates the necessary fields in about 3-4 seconds.
    Sorry for taking up extra room in the OWB forum with a sql efficiency issue.
    Thanks,
    Jason

  • How to implement Dimension Level Security on Tabular?

    Not possible on SQL Server 2014 SSAS Tabular? How to work around?
    Kenny_I

    Hi Kenny_l,
    According to your description, you want to implement dimension security in SSAS 2014 tabular. Right?
    In Analysis Services Tabular mode, dimension level security (based on role permission) is not supported. This security can only used in Multi-dimension mode. In tabular mode, we can only use row-level security based on role permission.
    Please refer to links below:
    Implement Dynamic Security by Using Row Filters
    Reference:
    Comparing Tabular and Multidimensional Solutions (SSAS)
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou
    TechNet Community Support

  • Comparing facts of different dimension levels - drilldown problem.

    With our customer, we do a lot of comparisons of sales budgets vs. actual sales. The sales budgets are given per month, like this:
    Sales budgets: Jan 09: 40,000 EUR, Feb 09: 45,000 EUR, Mar 09: 20,000 EUR... and so on.
    There is a time dimension (year -> quarter -> month -> day). Since BI does not seem to allow binding facts to other dimension levels than the lowest one (day in my example), I used a trick and modelled these sales budgets as a fact table: (expected sales, last_day_of_month)
    So I have this:
    Sales budgets: 01/31/09: 40,000 EUR, 02/28/09: 45,000 EUR... and so on.
    This way, I can connect both actual sales and sales budgets to the same time dimension. With this, I can create an answers report that compares the two facts easily.
    The problem is now that the customer wants to drill down. This is no problem with year->quarter->month. But then, BI naturally allows to drill further to day, and in this case, BI compares the sales budget of 01/31/09 with the sales on 01/31/09, producing wrong values.
    I either need a solution to prevent BI from drilling down from the month level in this special answer report, or maybe I am making an error with my modelling. Are there any ideas on how to do this better?

    Hi,
    I'd model the repository differently, by modeling the actual sales fact on the lowest day level, and sales budget fact on monthly level. That's how I've understood the data really is defined, right? (Lowest level physical time table you already have but for sales budget you need to create also a physical time table which is on the month level. First define the correct physical joins. Then define the logical table sources in the BM layer accordingly.) In order to be able show the sales budget together with lowest level you can create the sales budget measure as a level based measure (fix the measure to the level month in the column properties-->Level in the Administration tool).
    If you just want to prevent users from drilling-down on a specific dashboard report you can go to properties of the column(s) in that report and set the interaction type for both title and values to "No interaction" in the second tab of the properties menu in the front-end.
    Hope this helps!
    Cheers,
    Ilmari

  • Overhead keys at Work center Level

    Hi Experts,
    Our client needs to assign the Overhead keys at work center level.
    But what we know is, it possible only in Materail throghu overkead group. In simillar way is it possible to build a link to Workcenter.
    Regards
    Sham

    Hi Shyam,
          Ask abaper to insert a filed in document header which retrieves the data at work center level.
    Regards,
    Srinivas Muthyala

  • How we use Surrogate Keys for snowflake dimension

    Hi All,
    my question is - How we use  Surrogate Keys for  snowflake dimension
    i heard from some body Surrogate Keys only work with star schema.
    please correct me if i wrong.
    Regards,
    Manish

    Hi manishcal16PPS,
    According to your description, you can only create natural key in your dimension. But it's not working when using surrogate key. Right?
    In Analysis Services, the snowflake schema of the dimensions are represented by more than one dimension table in other words its takes multiple dimension tables to define a dimension. Surrogate key are just some extra, redundant, unique key based on the
    natural key. So there's no direct relationship or some limitations between surrogate keys and snowflake schema.
    In this scenario, since there's relationship between the two dimensions, you should create natural key. For using natural key or surrogate key. Please refer to an article below:
    Surrogate Key vs. Natural Key
    For understanding star/snowflake schema, please see:
    Understanding Star and Snowflake Schemas 
    Regards,
    Simon Hou
    TechNet Community Support

  • Dimension level Security

    Hi All,
    Can anyone help me in providing Dimension level security for some members in a dimension? I have given planning application access as "Interactive User" and Reporting Level as "Explorer and Viewer".
    I am using Hyperion 11.1.1.3.
    Thanks in advance

    No the roles in Shared Services are not for defining member access in the planning application, if you want more information on the planning roles in shared services have a look at http://docs.oracle.com/cd/E12825_01/epm.111/epm_security/apas07.html
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Logical Key for Degenerate Dimension

    Hi Gurus,
    Need some help on the degenerate dimensions in the BMM layer.
    I have one fact table with dimension attributes and I would like to move the attributes into separate logical table and treat it as dimension.
    Now my newly created dimension has the Fact LTS and I would like to assign a logical key to the newly created table and then create the logical dimension.
    Can anyone provide some inputs on we can assign the logical key to the column?
    Thanks

    Hi Srini,
    Since my main logical fact table consists of two LTS and the dimension being created from this table will also have 2 LTS, the content level will be set to all levels on which the fact is joined.
    So I would like to create a logical dimension based out of my dimension and then assign the content level at the detail level.
    Please let me know if I am not clear.
    Thanks

  • Need information on Dimension levels

    Hello everyone specially Igor,
    Last time i asked about filling of Dimension and fact. And Mr. Igor explained well to me. Now i want to know that how many level must be in a hierarcy like Mr. Igor gave me an example that in a Customer dimension the cust_id level will be the last level in the hierarchy and cust_type_id level will be that last level in the other hierarchy and one level can have more columns (attributs)other then id e.g cust_name, address, age etc etc., so now i want to ask that if we put all these columns (attributs) in one level of a hierarchy then what will bethe other columns (attributes).
    For example i have a Loan module of a bank to make then how many dimensions will be there like i made seperate dimensions for customer personal informaton, customer address, customer contact informtaion, loan details, loan types etc. If i follow the above instructions then i will put Customer personal information, customer address, customer contact infotmaion in one dimension with three seperate hierarchies with this inforamtion and other dimension named loan right. Which means i will have two to thre dimendsions in my whole loam modules.
    Please tell me with example about the levels in hierarchy and hierarcies in a dimension.
    Here i also want to specify that i dont have anyresource to learn OWB in my whole area.
    Thanks you and wating for you repaly.
    Mustafa Ali Qizilbash
    [email protected]

    Mustafa,
    As per your brief description, you would have at least 3 dimensions: Customer, Loan and Time (time is almost always there). The customer personal information, customer address and customer contact infotmaion would not go to separate hierarchies, but to the same hierarchy and possibly to the same level (the lowest one - customer) of the customer hierarchy, because they belong to a single customer. Therefore, you would have a customet key (customer_id) and customer_name, customer_address and cust_contact_info on the first level of the customer hierarchy as attributes. What levels you would have above the customer level in your hierarchy depends on how you want to classify your customer data. For example, if you want to classify customers by geographical area (and don't want to have a separate geography dimension), you could have a geography hierarchy within the customer dimension with levels like cust_city (with cust_city_id key and attributes like city_name, city_population ...), cust_region etc. up to the highest level of the hierarchy that would probably be cust_total. From the reporting tool you will then be able to navigate data from the customer total, down to regions, cities and finally to a single customer. You could have multiple hierarchies in the customer dimension if you decide to classify customers in more that one way. For example, apart from classifying the customers geographically, you might also want to classify the customers by income level. You would then have an income hierarchy which would again start from the customer level (common to the income and geography hierarchies), and then continue up with levels like income_class etc. up to customer total (which would again be common to the two hierarchies).
    Similarly (depending on your business requirements) for your loan dimension, you would have one or more hierarchies, each with several levels.
    For the time dimension, OWB provides an out of the box dimension (see in the directory <owb_home>\owb\misc\time) with a hierarchy that goes from days to months to quarters to years.
    Regards:
    Igor

  • Define logical Key on Logical Dimension Table

    It's recommended to define a logical key for any logical dimension table - in 10g there was a function on the right mouse button, as far as I remember - but in 11g there is no such functionality ? the foreign key can be added by "green plus" button, but not the primary key ?? you have to type in the name of the key, then you can choose the column and then you select as primary key ... funny.
    bug or undocumented feature?

    Hi Srini,
    Since my main logical fact table consists of two LTS and the dimension being created from this table will also have 2 LTS, the content level will be set to all levels on which the fact is joined.
    So I would like to create a logical dimension based out of my dimension and then assign the content level at the detail level.
    Please let me know if I am not clear.
    Thanks

Maybe you are looking for