Fact and Dimension Linking

Hi,
Is it possible to link Fact and Dimension tables with two conditions using OR.
I have one dimension table for Customer Sites where Site_Use_ID (Pk).
But in my Fact table, Bill_To_Site_Use_ID and Ship_To_Site_Use_ID
SITE_USE_ID = BILL_TO_SITE_USE_ID OR
SITE_USE_ID = SHIP_TO_SITE_USE_ID
So, I need to join Customer sites Dimension with Fact and it is possible with OR condition. How can I specify these two condition while linking..
Thanks in Advance,
-Vency

Hi Daan Bakboord,
I tried those things.
I have already tried to create complex join in Physical Layer but unfortunately it is saying that "The column 'SITE_USE_ID" is used more than once". So, I am unable to create complex join.
Coming to creating Alias Table.. If I create Alias for that table then I need to show both the tables to the user (in Presentation Layer) so that he/she can select BILL_TO from one and SHIP_TO from another table.
But I am trying to get it with only one Table.
Thanks for giving reply,
-Vency

Similar Messages

  • How to design fact and dimension tables

    Hi Team,
    Please provide me some useful links!!
    I have a Parent & Child table each has around 8 Million records (1 to many relation).  These two tables need relation with many other master tables to generate any report. 
    I want to desing a fact and dimension(s) for this parent & Child tables.  
    Please help me what are the things I have to keep in mind when desingning datawarehouse fact and dimension tables?
    Thanks,
    Ali

    Hi, any update on this?

  • Join multiple facts and dimensions for reporting issue

    Hi,
    I have a report requirements and need to use multiple fact tables and unconformed dimensions as described below
    Fact table: F1,F2,F3
    Dimensions tables: D1.....D9
    F1:(joined to) D1,D2,D3,D4
    F2::(joined to)D1,D2,D5,D6
    F3::(joined to)D1,D2,D7,D8
    D7::(joined to)D9,D8 (dimension D7 joined to two other dimensions D9 and D8
    I'm trying to use columns from almost all the fact and dimension tables but getting "Unable to navigate requested expression. Please fix the metadata consistency warnings."
    Repository is consistent and no errors and warnings.
    How can I configure the repository to develop reports using all fact tables and dimensions?
    Appreciate for your help.
    Thanks
    Jay.

    You can find the same issue in
    Logic of queries in OBIEE
    or
    Connection between 2 fact tables
    Follow the link
    http://there-n-back-again.blogspot.com/2009/04/oracle-analytics-how-to-report-over-non.html
    Put 'All' or 'Total' at levels for dim_xxx for those facts you need in your report from facta and factb
    Regards
    Nicolae

  • Table as fact and dimension

    Hi,
    Can one table act as a fact in one subject area and act as a dimension in another subject area? Thanks.

    Hi
    I confirm Stijn Gabriels' post.
    You don't have to do an alias in your physical table, otherwise the request will generate an alias in SQL for nothing ! However, in your logical layer, you will create 2 logical table : one for the fact, one for dimension. Both of them will have the same source : your unique physical table.
    Let's take an example : suppose you have only 2 table in your datawarehouse : 1 fact table with degenerate dimension attributes (so a table with fact and dimension data), we'll call it "revenue", and 1 dimension table for... "Time", for example. We'll call it"Time"
    Your conceptual (on paper) is a star schema with 1 fact table (revenue_fact), and 2 dimension table (time, and revenue_carac).
    In your OBIEE physical layer :
    - you import the 2 tables "revenue" and "time" from your database.
    - you link "revenue" with "time"
    In your OBIEE logical layer :
    - you create a logical table called "Dim Time", based on the "Time" physical table and you do what you want with it (hierarchy...)
    - you create a logical table called "Dim Revenue Carac", based on the "revenue" physical table, and you do what you want with attributes
    - you create a logical table called "Fact revenue", based on the "revenue" physical table, and you do you what you want with measures and aggregation
    - you link the 2 logical dimension table with the logical fact table
    And that's all. Now, let's see which kind of SQL OBIEE will generate if you want to display the measure "revenue" with the attribute "revenue_carac" and the attribute "year".
    Select Sum(R.revenue_measure) , R.revenue_carac , T.year
    From revenue R , time T
    Where R.time_id = T.id
    Group by R.revenue_carac , T.year
    If you set alias in your physical layer, the request will be that (and you don't want it) :
    Select Sum(R1.revenue_measure) , R2.revenue_carac , T.year
    From revenue R1, revenue R2 , time T
    Where R1.time_id = T.id
    And R1.id = R2.id
    Group by R2.revenue_carac , T.year
    same results, but useless join between the same physical table

  • In Answers am seeing "Folder is Empty" for Logical Fact and Dimension Table

    Hi All,
    Am working on OBIEE Answers, on of sudden when i clicked on Logical Fact table it showed me as "folder is empty". I restarted all the services and then tried still showing same for Logical Fact and Dimension tables but am able to see all my reports in Shared Folders. I restarted the machine too but no change. Please help me out to resolve this issue.
    Thanks in Advance.
    Regards,
    Rajkumar.

    First of all, follow the forum etiquette :
    http://forums.oracle.com/forums/ann.jspa?annID=939
    React or mark as anwser the post that the user gave.
    And for your question, you must check the log for a possible corrupt catalog :
    OracleBIData_Home\web\log\sawlog0.log

  • Best practice when FACT and DIMENSION table are the same

    Hi,
    In my physical model I have some tables that are both fact and dimension table, i.e. in the BMM they are of course separated into Fact and Dim source (2 different units) and it works fine. But I can see that there will be trouble when having more fact tables and I e.g. have a Period dimension pointing to all the different fact tables (different sources).
    Seems like the best solution to this is to have an alias of the fact/transaction table and have 2 "copies" of the transaction table (one for fact and one for dimension table) in the physical layer. Only bad thing is that there will then allways be 2 lookups in the same table when fetching data from the dimension and the fact table.
    This is not built on a datawarehouse - so the architecture is thereby more complex. Hope this was understandable (trying to make a short story of it).
    Any best practice on this? Or other suggestions.

    Id recommend creation of a view in the database. if its an oracle DB, materialised views would be a huge performance benefit. you just need to make sure that the MVs are updated when the source is updated.
    -Domnic

  • Delete Fact and Dimension Tables

    Hai All,
              Small question! When deleting data from info cube, it asks whether to delete just Dimension table or both fact and Dimension tables.
    What is the difference between these two?
    Thank you.

    Hi Visu,
    The dimension table will contain the references to char value by way of SID and DIM ids, whereas the fact table will contain the number (of key figures). If you delete just the Fact table, the numbers go away, yet the DIM ids remain intact, so reload is faster. But if you are convinced that this data is not correct either, or you want a clean slate to strat reload again, then delete both Fact and Dim tables. Then when you reload, the DIM ids will be created again.
    Hope this helps...

  • Unable to Create Fact and Dimension tables from the Tools menu in EIS conso

    Hi All,
    In the EIS console, I am unable to create the fact table and the dimension tables to produce my OLAP model from the TOOLS menu whereas I am able to create them by dragging from the left panel where the tables are displayed. I am geeting the below error message:
    "An exception occured while retrieving OLAP model metadata. Please verify you are connected to the catalog and try again"
    Any help appreciated.
    Thanks,
    Raja

    I have fact and dimension tables in one server and i moved those stuff to another server.If I do that what happen to essbase and about totale EPM System.I want to know how to do this and what I can expect?
    Please reply

  • How to have fact and dimension which are not joined in same report

    Hi All,
    suppose we have 2 dimensions and 1 of them is joined to fact but we want to pull both these dimensions along with fact and fact column shows null but we dont want that .how can we have 2nd dimension which is not joined to fact in the same report .Actually i have a column called equipment schedueled time and it can be shown only with equipment dimension but I want to pull both equipment,geography and equipment scheduled time in report if I do it now it shows equipment scheduled time as null because its not joined with geography dimension.I want even if the geography dimension exists it should show the value of equipment scheduled time .
    Can someone please help me.
    Thanks in Advance

    Hi ,
    Can you please tell me what are fact and dimension tables of your requirement.If you want display the data from 2 dims and a fact table ,you have to establish the joins between facts and dimensions.
    mark if helpful/correct...
    thanks,
    prassu

  • Facts and dimensions joins

    Hi,
    Can we use three fact tables in rpd and not join them? We have three facts and four dimensions. All the four are common dimensions to the three fact tables. So in the physical joins can we just join the facts to the dimensions? will it be accepatble if we do not have a join between fact tables. Is it necessary that all the tables (fact and dimensions) need to be joined to some tabler? Can we leave the joins between the facts which are not necessary? Please advice.

    We do not do joins between fact tables, the joins between facts will be happened through dimensions (conformed dimensions).
    In your case the 4 dimension will act as an conformed one.
    Is it necessary that all the tables (fact and dimensions) need to be joined to some tabler? You cannot have a table in BMM which is not joined to any other table.
    Can we leave the joins between the facts which are not necessary?Yes, Dim1 - fact1 -Dim 2 in this fact 1 is connected with Dim1, Dim2 and there is no relationship for fact1 with Dim3 so we don't join it.
    Dim1,Dim2,Dim3 is joined with fact2 in this case Dim 1 and Dim2 will act as conformed dimesion between fact1 and fact2, where as dim3 will be a non conformed dimesion.
    Thanks,
    Vino

  • How to design many to many relationship in the fact and dimension

    There is a problem in my project what is the subject.And i wanna know how to implement in owb.I use the warehouse builder 10. Thanks.

    You may design and load whatever db model you want to.
    But If you set a unique key, you may find some integrity issues. I wouldn't do a many to many relationship between facts and dimensions. This could cause you lots of headaches when users start to submit queries using this tables. You'll probably face performance issues.
    Regards,
    Marcos

  • DWH: how do you analyze fact and dimension tables

    Hi,
    I was wondering how you analyze your fact and dimension tables.
    Our fact table is partitioned per month. Each partition contains 4M rows and is 270 MB large. We are using 9 dimensions, 6 have about 50'000 rows (2MB), 1 about 1M rows (50MB) and 2 about 3M rows (200MB). All tables are compressed. The version of Oracle we are using is 9.2.0.5.
    What I was wondering is how you would, using dbms_stats, analyze the fact and dimension tables. Which percentage would you analyze? On which column would you build histograms?

    nope, but i could copy-paste the URL or I could copy-paste the entire thread from the other forum. Id did the one that made more sense to me.

  • What I should do If I move fact and dimension tables from one server to other server

    Hi
    I have question like
    what all changes need to be done  in EPM System if we move the Fact and Dimension tables to a different server.
               Reply me asap and thanks in advance

    I have fact and dimension tables in one server and i moved those stuff to another server.If I do that what happen to essbase and about totale EPM System.I want to know how to do this and what I can expect?
    Please reply

  • Left outer join on Fact and dimension table.

    Hi all, I have a fact F with account number and few measures as columns.
    I also have a dimension D with account number, account name columns.
    Few account numbers from Fact doesnt exist in Dimension D , but they need to show up in the report though.
    How do I left join Fact and Dimension D in RPD?
    I have this report where I need to show Account Number, Account name, measures.
    If D doesnt have certain account numbers, I need to convert that account number from F as string and show it in the report in account name column.
    Can you pls help.

    Ok. I tried this:
    Driving table : Fact, Left outer join -- didnt work.
    Driving table: Dimension D left outer join -- didnt work either
    In either the case, I see physical query as D left outer Join on Fact F. and omitting the rows.
    And then I tried this -
    Driving table: Fact, RIght outer join.
    Now, this is giving me error:
    Sybase][ODBC Driver]Internal Error. [nQSError: 16001] ODBC error state: 00000 code: 30128 message: [Sybase][ODBC Driver]Data overflow. Increase specified column size or buffer size. [nQSError: 16011] ODBC error occurred while executing SQLExtendedFetch to retrieve the results of a SQL statement. (HY000)
    I checked all columns, everything matched with database table type and size.
    I am pulling Fact.account number, Dimension.account name, Fact.Measures. I am seeing this error each time I pull Fact.Account number.

  • Fact and Dimension tables

    Hi all,
    Please let me know the relation between the fact and dimension table(s).
    regards
    chandra kanth.

    Hi Chandra, it would be useful if you read a little bit about BI before start working with a BI tool.
    Anyway, I'll try to help you.
    A dimension is a structure that will be join to the fact table to so that users can analyze data from different point of views and levels. The fact table will most probably (not always) have data at the lowest possible level. So, let's suppose you have SALES data for different cities in a country (USA). Your fact table will be:
    CITY --- SalesValue
    Miami --- 100
    NYC --- 145
    Los Angeles --- 135 (because Arnold is not managing the State very well ;-) )
    You will then can have a Dimension table with the "Country" structure. This is, a table containing the different cities along with their states, counties, and finally the country. So your dimension table would look like:
    NATION --- STATE --- COUNTY --- CITY
    USA --- Florida --- Miami --- Miami
    USA --- NY ---- NY --- NYC
    USA --- Los Angeles --- LA --- Los Angeles
    This dimension will allow you to aggregate the data at dffirent lavels. This is, the user will not only be able to see data at the lowest level, but also at the County, State and Country level.
    You will join your fact table (field CITY) with your dimension table (field CITY). The tool will then help you with the aggregation of the values.
    Ihope this helps.
    J.-

Maybe you are looking for