One dimension level

can I just have one level in a dimension?
how can I do it?

well now I found out that I have no problem with the level.
I can delete the hierarchy when I made the dimension in editor.
But when I made the dimension manually with the editor,
I always found errors like this :
VLD-0357: All levels of STAR dimension DIMBOOKTYPE must be implemented by one and only one table or updateable view.
For Star dimension, all levels must bind to single table or updateable view.
VLD-0346: Level BOOKTYPE is not bound to a table or updateable view.
Each level should be implemented by one and only one physical table or updateable view.
VLD-0345: Level Attribute NAME is not bound to a column in a table or updateable view.
Each level attribute must be bound to a column in a table or updateable view.
I found out t hat with wizard, it create this table automatically.
so I made the a table manually too because I made the dimension manually, but it has no effect.
maybe I did it wrong.
is there anyone who can explain me how to create a table manually for the dimension?

Similar Messages

  • One Dimension with Facts at different levels

    I currently have a single dimension with 5 levels. I have two fact tables that both connect to the dimension table but at different levels.
    For example. If we have a Dimension Country -> Region -> City and then two fact tables. One that has facts at the Region level and one that has facts at the City level.
    Is there a way to be able to have an answer that contains facts from both fact tables. So if there was a fact from City and the Region level? Everything I seem to try does not work. Would I have to create an additional aggregate table that aggregates the City level data up to the Region? Or is there a way to show the data at the lowest level and show either nulls or duplicate values for the additional records.
    Any help is greatly appreciated

    This has helped a little. I am now getting values from both levels. However, because i am summing the two values. The value from the upper level is now summing duplicate values. For example.
    Value 1 on its own
    Level1 Level 2 Level 3 Value 1
    1234 10 10 13.05
    1234 20 10 70.00
    1234 20 20 70.00
    1234 30 10 105.00
    1234 30 20 105.00
    Value 2 on its own
    Level1 Level 2 Level 3 Value 2
    1234 10 10 0.50
    1234 20 10 2.00
    1234 20 20 2.00
    1234 30 10 3.00
    1234 30 20 3.00
    What I am getting
    Level1 Level 2 Level 3 Value 1 Value 2
    1234 10 10 13.05 0.50
    1234 20 10 140.00 2.00
    1234 20 20 140.00 2.00
    1234 30 10 210.00 3.00
    1234 30 20 210.00 3.00
    Desired Outcome
    Level1 Level 2 Level 3 Value 1 Value 2
    1234 10 10 13.05 0.50
    1234 20 10 70.00 2.00
    1234 20 20 70.00 2.00
    1234 30 10 105.00 3.00
    1234 30 20 105.00 3.00
    Now, the problem with this is that Value 1 is a fact at Level 2 and Value 2 is a fact at Level 3. I have one dimension table and two fact tables. The join between the fact table for Value two and the dimension table is the same as the join between the dimension table and Value 1 only it is missing the last level of detail.
    I have then set the logical table source content tabs for each fact table to the corresponding levels.
    I thought this would be enough but i still don't get the desired result. I am not sure if this is possible with one dimension table.
    Any ideas would be greatly appreciated.
    Edited by: user10800227 on Jan 11, 2010 12:43 PM

  • How to sort two different hierarchies in one dimension

    Does anyone know of a way to sort two different hierarchies in one dimension and still make drilling work correctly? We have two hierarchies in our item dimension; one called category and the other origin. Simplified, it looks like this:
    CATEGORY
    Hardware (100)
    ..PCs (100.100)
    ....PC 1
    ....PC 2
    ....PC 3
    ..Monitors (100.200)
    ....Monitor 1
    ....Monitor 2
    ....Monitor 3
    Software (200)
    ..Big (200.100)
    ....ERP package
    ....CRM package
    ..Small (200.200)
    ....Solitaire
    ....Mine Sweeper
    ORIGIN
    Vendor A (10)
    ..Site A1 (10.10)
    ....ERP package
    ..Site A2 (10.20)
    ....PC 1
    ....Monitor 3
    Vendor B (20)
    ..Site B1 (20.10)
    ....PC 2
    ....PC 3
    ....Monitor 1
    ....Monitor 2
    ....Solitaire
    ....Mine Sweeper
    ..Site B2 (20.20)
    ....CRM package
    We have numeric codes at each level above item which I represents the sort order (the number in parentheses at each level), and the items themselves should be sorted according to item number. I have implemented this (level code/item number) as an attribute in AWM making this the default sort order. However, as item is the lowest level in each hierarchy, I have only been able to list the items under the correct level in one hierarchy. As soon as I drill using the other hierarchy, the levels above item are sorted correctly, but the items appear at very odd places...
    The AWM documentation states that if default order is not selected on any attribute, hierarchies are sorted in the order they are created. Is there a way to control this order?
    Any input will be greatly appreciated!

    Hi,
    thank you for your answer. Yes, now I also find the class CL_SALV_WD_MULTI_CELL_EDITOR which could be used to set different UIE in one cell. But it is quite limited, just the following UIE could be used
    - LinkToAction 
    - LinkToURL    
    - FileDownload 
    - Button       
    - ToggleButton 
    best regards,
    Wenwen

  • One dimension used twice in a cube

    I have one dimension, but it has two meanings. How can i use the same dimension twice in the same cube as it was two separate dimension?
    Example:
    There is dimension "Region". The fact table has two keys. First key means - "region of birth", and second "region of living". So one dimension has two meanings.
    I tried put the same dimension twice with two different aliases in one cube. OEM shows such cube as valid, but querrying it through OLAP API, or building analytic workspace based on this cube is impossible (error ORA-1007).
    The only workaround i see is to build two separate but identical dimensions.The bad side of this is that i have to create two separate but identical tables of data for those dimensions (i can't create two levels from the same column).
    Raf
    i work with Oracle9iR2

    i did the same on Oracle9iR2 with OEM 9.2.0.1.0.
    Creating the cube with two aliases for one dimension was ok.
    But creating MOLAP cube from that source cube using AWM was impossible .
    Also querrying that cube (the one created in OEM) for example through Discoverer or Excel is imposible.
    I searched forums on that question, and some people had the same problem, but no answer.
    Raf

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

  • Multiple Hierarchies in one dimension - comments?

    multiple hierarchies
    Hi Experts,
    I'd like your comments on my implementation of multiple hierarchies in one dimension.- especially if this can be done in a way that:
    a) still enables users to choose the hierarchy in a dashboard prompt
    b) reduces maintenance to a minimum
    The dimension groups ages into several different groups like the example below:
    Hierarchy1 Hierarchy2
    Age......Groups........Groups.....
    0........0-2...........0-5
    1........0-2...........0-5
    2........0-2...........0-5
    3........3-5...........0-5
    4........3-5...........0-5
    75.......70-75.........70-80
    76.......76-80.........70-80
    Right now I've implemented this by defining one dimension having one hierarchy:
    Total
    ....Hierarchy
    .......Group
    .........Age
    The underlying logical table is based on several logical table sources (LTS) - one for each hierarchy as shown in the first example(Hierarchy1, Hierarchy2).Every LTS has a fragmentation definition filtering on values on 'hierarchy-level'.
    Columns in the logical table (and of course in the underlying LTS) are:
    Column               mapped to hierarchy-level
    - Hierarchy          Hierarchy               
    - Hierarchy_id          Hierarchy
    - Group          Group
    - Group-id          Group
    - Age               Age
    Advantages:
    A answers / dashboard user can select one or more hierarchies by using a dashboard prompt.
    Adding a new hierarchy (a new grouping) doesn't need changes in the dimension itself
    Disadvantages:
    A new grouping needs manual steps to implement
    - a new physical table
    - a new LTS attached to the logical table (including the fragmentation content)
    Thanks for your time and comments
    Regards
    Andy

    multiple hierarchies
    Hi Experts,
    I'd like your comments on my implementation of multiple hierarchies in one dimension.- especially if this can be done in a way that:
    a) still enables users to choose the hierarchy in a dashboard prompt
    b) reduces maintenance to a minimum
    The dimension groups ages into several different groups like the example below:
    Hierarchy1 Hierarchy2
    Age......Groups........Groups.....
    0........0-2...........0-5
    1........0-2...........0-5
    2........0-2...........0-5
    3........3-5...........0-5
    4........3-5...........0-5
    75.......70-75.........70-80
    76.......76-80.........70-80
    Right now I've implemented this by defining one dimension having one hierarchy:
    Total
    ....Hierarchy
    .......Group
    .........Age
    The underlying logical table is based on several logical table sources (LTS) - one for each hierarchy as shown in the first example(Hierarchy1, Hierarchy2).Every LTS has a fragmentation definition filtering on values on 'hierarchy-level'.
    Columns in the logical table (and of course in the underlying LTS) are:
    Column               mapped to hierarchy-level
    - Hierarchy          Hierarchy               
    - Hierarchy_id          Hierarchy
    - Group          Group
    - Group-id          Group
    - Age               Age
    Advantages:
    A answers / dashboard user can select one or more hierarchies by using a dashboard prompt.
    Adding a new hierarchy (a new grouping) doesn't need changes in the dimension itself
    Disadvantages:
    A new grouping needs manual steps to implement
    - a new physical table
    - a new LTS attached to the logical table (including the fragmentation content)
    Thanks for your time and comments
    Regards
    Andy

  • 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

  • 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

  • Joining Two facts with one dimension

    hi,
    Hello Experts,I am reporting out of 2 fact groups.
    Mailing History and Booking.
    The only common dimension between the 2 is the Person Dimension. I have created the hierarchies and defined the aggregation content in the LTS.This helps me in reporting using any column from the Facts or any one dimension from either of the fact groups. But if i select 2 or more dimensions , one or more from each fact group , then the report gives and error. A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: MailingHistory Campaign.Campaign Name. Please fix the metadata consistency warnings. (HY000)
    For Example : BookingDim--BookingFact-MailingHistoryFact (ok) MailingSourceDim--BookingFact-MailingHistoryFact works (ok) but BookingDim--BookingFact-MailingHistoryFact - MailingsourceDim (Fails ).
    When i am applying the filter from the fact 1 . i am getting this error.(which is the column in the second fact table 2).I checked all the joins in the BMM layer.
    Please help me!!!
    Thanks,
    Surya

    Surya did you set the levels properly for two fact tables and also for metrics.
    When ever you are using two fact groups with non confirmed dimensions you have to make sure all the content levels set for the fact tables and as well as for metrics.
    in your fact tables/ metrics - For related dimensions set the level to Detail. and for the non related dimension set the level to Total. This way obiee server will understand what is related dimension and whats not related..
    hope this works for you.

  • Using different logical tables in one dimension

    Hello.
    I have two fact tables and two dimension tables Country and Region. One fact table depend on one dimension table like it shown in this link - http://file.qip.ru/file/121151603/3b4ebdba/2_online.html. Table Country is received from table Region by DISTINCT.
    At the presentation I have to realize one column in Presentation Catalog for both columns Country Name (or Country Id) from Country and Region, the user won't know that one fact table depends on COUNTRY and other on REGION.
    Also I have to realize the dimention "Geography" (Country->District->Region) for fact table SALE_REGION.
    Could Oracle BI automatically choose from which table get data and if it can, how I should make the logical model?
    Thanks.
    PS.
    The best variant I realized it this - http://file.qip.ru/file/121154314/8d242b81/3_online.html where District is the shared child for second Country level, but it doesn't work properly.

    Y don't u use union request in first request details of fact1 and its related dimensions and in 2nd request fact 2 and its related dimensions.
    I guess this should work
    Thanks
    Subhash

  • Oracle Administration Tool (RPD) One Dimension linked with many fact tables

    How to connect One dimension with many table facts in the Lgical level of RPD without having an error about connection between table facts?

    It's not about "linking two catalogs". That's Siebel Marketing stuff. Forget about it. Just create your models and put them in their respective presentation catalogs.
    Whatever you fire from answers will hit that specifc presentation catalog and search its way through the metadata to contruct the query.
    Hence conforming dimensions as a technical concept are definitely the thing you want...not the rpd object type "conformed dimension links".

  • Two fact and one dimension table

    Hi folks
    i am new to this field ( 3 months ), my TL has given me one task i have to finish it up today itself, Can anyone one give me some idea how to implement
    req. The req is
    1. there are 2 fact and one dimension table is there, i have to create reports on Quaterly and monthly basis by using one dimension table.
    Can any one tell me what all are the steps in need to follow
    2.What is standalone and integrated systems?
    Regards
    Reddy

    Hi
    If u r having mapping keys for quarter level n monthly level then create a Alias for the dimension table.Use the original dim table for quarter level mapping and the alias dim for monthly level.
    Thanks
    Don

  • 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

  • Hierarchy based on one dimension.

    Hi,
    How to create a hierarchy based on one dimension. For example: we have table:
    Category
    Category_ID
    Parent_Category_ID
    I want to create hierarchy, which like as:
    Category_Level_1
    Category_Level_2
    Is it possible without create new alias of table for each level?
    Thanks

    Which version of BO are you using?
    Assuming that you are using BO XI R2 or above version.
    And Is your question - how to create custom hierarchies in Universe Designer..... for two different fields (columns) taken from a single database table?
    If so, yes you can create custom hierachy for above scenario. In Custom Hierarcies option: Add the Parent_Category_ID first and  below that add Category_ID.
    If you want to rename your hierarchy levels as Category_Level_1 & Category_Level_2, then rename their corresponding objects names in Clasess & Objects pane.
    - Anil

  • 2 date columns and one dimension hierarchy

    Hi,
    I have one question in OBIEE 10g.
    I have one dimension table with 2 date columns (insertedOn, updatedOn)
    I created insertedOnYear, insertedOnMonth and updatedOnYear, updatedOnMonth columns from my date columns.
    I have hierarchy
    Year -> Month -> Day for that dimension table
    and I would like to dril down both columns insertedOnYear and updatedOnYear
    insertedOnYear -> insertedOnMonth -> insertedOn
    updatedOnYear-> updatedOnMonth -> updatedOn
    I am able to do it only for one of these columns and not for both.
    I can place both columns to appropriate levels, but drilling doesn´t work as I want
    Can you tell me how to solve my problem?

    Oops, I was talking about 11G. Ok no problem. Do this. In the physical layer, cretea 2 alias tables. Both pointing to the table where you have these 2 fields. The put everything in your BMM. There create the 2 hierarchies using the 2 different tables (that will point to the 2 alias tables create in the physical layer). This will make them unique.

Maybe you are looking for