Join 2 fact tables

I have 2 fact tables and 1 dimension table, which is joined with both these tables through primary key (ID). I want to build a report, which consists of some columns from these fact tables with this condition:
FACT1.DIM_ID = FACT2.DIM_ID
AND
FACT1.DATE = FACT2.DATE
DIM_ID is FK for dimension
Should i create a bridge table?
What is the best way to do this, please? Thanks....

Actually, it seems as it's a conformed dimension you're using, so you shouldn't need bridge table for this setup. BI should pick up values from both facts. I assume Date is also a key.

Similar Messages

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.

Join fact tables with different grain without upsetting measures?

Say I am a business analyst at a university, and I have two analytical cubes available to me: an Enrollment Cube and an Admissions Cube. The Enrollment Cube has a grain of Student and Semester, whereas the Admission Cube has a grain of Student, Application and Semester (a potential student can have more than one application in a semester). Is there any way for the OLAP developer that makes these cubes to make it so that I can use both cubes' fact tables without messing up their corresponding measures, such that I can create such analyses as the following:
County
Semester
Acceptance Rate (Admission Fact)
Retention Rate (Enrollment Fact)
County A
1
30%
88%
2
60%
87%
3
42%
84%
County B
1
90%
100%

One suggestion is to create a view that joins the 2 fact tables and then create a cube with measures mapped to the view for analysis purposes. However, this would be using the measures of the new cube for the analysis.

Joining Fact tables

Hi,
In what cases can two fact tables be joined.
Can anyone explain why there is a join between promotion facts and shop facts in efashion database and that too shortcut join.
Please put some comments.
Ganesh

It shouldn't be imho. I think it's incorrect and is a result of bad analysis leading to bad table design. I went on a course years ago where we discussed this and said that you *might* consider making that a full join and creating a context with only that one join in it if you have denormalised dimensions in one of the facts but not the other. However, you'd only do that if you were certain of the granularity of the join. We agreed, though, that the model was principally flawed and it would be a lot less painful to reassess the model and rework it.

Drill across (joining facts) using Discoverer

Hi,
I've read a few books and article on DW talking about drilling across. It seems a good idea to build multiple star schemas with "conforming" dimensions and then join fact tables (drill across) when needed.
I have tried this solution, and afer a few tests, got to the conclusion that it is preferable to UNION ALL the related facts using a view or a custom folder. Of course this solution is less flexible because we need to find all the required combinations of facts.
Any comments?

OK,
I have 3 dimensions : D1, D2, D3 and 2 facts : F1, F2.
Dimensions D1, D2 are related to fact F1.
Dimensions D1, D2, D2 are related to fact F2.
I want to query on fact F2 based on values of dimensions D1 and D2, and then join F1 to get corresponding measures.
When running the query I get the following error:
Invalid combination of joins using different join keys - query cannot be resolved.
I use Oracle Discoverer 9.0.2.53.12.
What would be the best way to work around this restriction?

Join fact with another fact like a dimension

Does it work if I join fact table with another fact table as a dimention(created the dummy hierarchy and add the sum() to the measure existed in the table)?
If I pick the measure value in the fact table(which is configured like a dim), I will get the correct number? Or multiplied number?
If there is any good way of work around please let me know
Thanks
Edited by: user12077461 on Jun 29, 2011 7:39 PM

Hi,
You can create an Alias Table in the Physical Layer for the Fact table which you want to use as a Dimension Table. And start using the Dimension Table. And if you want any measure values to be used from the Fact, then you can extract that too.
This should simplify your work too.
Regards
MuRam

Modelling Time Dimension with Fact Table containing Start Date and End Date

Hi Gurus,
I have a time dimension with Year till Date. I have a fact table which consists of Start Date, End Date, Person ID, Department ID.
How do i design Time dimension with fact table the below scenario
In the dashboard i have start Month and End month as prompts.
In the report i need to display Count(Person ID) > Start Date and < End Date along the trend.
For instance, i have selected Jan-2009 as start date and Apr-2009 as End Date, then i need to display Count(Person ID) of Jan-2009, Feb2009, Mar-2009 andApr-2009.
I Can not connect Time dimension with only Start Date or only with End Date to get the trend along the months.
Please advice on the issue which i am having.

Hi,
Thanks for the response, Infact i tried using Complex join in physical layer. I have considered Time table joined with Fact table, and used >= and took and alias of the Time table and joined fact table using <=. When coming to BMM, i am not knowing how do i design this as if i merge the both the time dimensiona and its alias into single table, values will not be correct and if i make them as seperate columns. i can not show the trend as both are different columns.
Can you please let know where i am going wrong.
Thanks

Join two fact tables

Hi,
I have two fact tables F1 and F2 joined with few dimensions D1.....D9. D1,D2 and D3 are conformed dimensions.
In Physical:
F1>--D1,D2,D3,D4,D5,D6
F2>--D1,D2,D3,D7,D8,D9
In Logical:
F1>--D1,D2,D3,D4,D5,D6
F2>--D1,D2,D3,D7,D8,D9
there are some ports already using above star schemas. now I got new requirements and I need to use measures from both the fact tables and conformed and unconformed dimensions.
I did the following in logical
F1 LTS GENERAL TAB ADDED F2,D1,D2,D3,D7,D8,D9 and in content tab set logical level to unconformed dimensions at total level and for conformed dimensios at details level.
F2 LTS GENERAL TAB ADDED F1,D1,D2,D3,D7,D8,D9 and in content tab set logical level to unconformed dimensions at total level and for conformed dimensios at details level.
but I'm still getting
[nQSError: 14026] Unable to navigate requested expression:
Please fix the metadata consistency warnings. (HY000)
I cheked metadata global consistency and no errors found.
Appreciate your help
Thanks
Jay.
Edited by: Jay on Sep 27, 2011 10:14 AM
Edited by: Jay on Sep 27, 2011 10:15 AM

Let me explain my issue again
In Physical:
F1>--D1,D2,D3,D4,D5,D6
F2>--D1,D7
In Logical: Single logical fact Fact_FY_Ratio has two logical sources
LTS1: F1>--D1,D2,D3,D4,D5,D6
LTS2: F2>--D1,D7
Set the content level for each LTS in Fact_FY_Ratio:
F1 to Detail for D1,D2,D3,D4,D5,D6 and to Total for D7
F2 to Detail for D1,D7 and to Total for D2,D3,D4,D5,D6
In LTS 1 general tab added inner joins with all dimensions F1,D1,D2,D3,D4,D5,D6,D7and F2
In LTS 2 general tab added inner joins with all dimensions F2,D1,D7,D2,D3,D4,D5,D6 and F1
And I also did logical complex join for Fact_FY_Ratio with all logical dimensions D1,D2,D3,D4,D5,D6,D7
I'm able to run query using D1,D2,D3,D4,D5,D7,F1,F2 but when I include D6(time dimension) it is causing problem with F2(witth F1 it is working fine).
query success with:
F1,D1,D2,D3,D4,D5,D6
F2,D1,D7
D1,D2,D3,D4,D5,D7,F1,F2
Query failed with:
F2>--D1,D7 and D6
Please let me know anything wrong with above configuration.
Thanks
Jay...
Edited by: Jay on Oct 3, 2011 7:11 AM

How to join Dimensions and Fact Tables in OBIEE

Hi All,
I need to create report which need to get the information from two fact tables and 7 dimensions. The granularity is not same in both the fact tables. One fact table is having common keys between all the dimension tables and second fact table have only two dimension keys but with different names. My requirement is to create the report by taking the measures from both the fact tables.
I have created joins between the second fact table and two dimension tables in physical and BMM layer and also set the highest level for all other dimension tables in the LTS of second fact table. when am creating report by taking the measures from both the fact tables, data is not getting for the measure which taken from the second fact table. Please advice me how to get the data for the measure which taken from the second fact table.
Thanks in Advancec !!

You have to use the level-base measure capabilities.
http://gerardnico.com/wiki/dat/obiee/bi_server/design/fact_table/level_based_measure_calculations
For all measures of the second fact table with the lowest grain (with two dimension keys), set for all dimension where you don't have any key the logical level to the "All" or "Total".
And UNSET the highest level of the LTS for the second fact table.
Success
Nico

Date 01/01/1901 in W_DAY_D when joined to a date wid in a Fact Table

Hi
I noticed when w_day_d joined to a Fact table I am getting a CALENDER date as 10/10/1901. I have checked by joining these tables. When Fact Wid is '0',
Join is getting 01/01/1901 as date.
But I want to avoid this and display a 'NULL' value. How could I conver this date into a 'null' in Answers please.????
Thank you.

Hi,
We are using Dac Build AN 10.1.3.4.1.20090415.0146.
The start date is 01-Jan-1980 and end date 31-dec-2010.
I am interested to change the end date to 31-dec-2020.
For that I have created a custom container.
Design -> Task -> Query on SIL_DayDimension ->Parameters
Click on value, change the end_date to required value.
Save.
Setup -> Physical Datasource
Click on DataWarehouse.
Change W_DAY_D Refresh dates to null.
After running DAC W_DAY_D table is not having any record and end_date is showing as blank in paramter file
So I want to change it to original one that is as it was before.
When I de-clone it, the value for end_date is showing as Custom Format() @MM/DD/YYYY and if I add any value to it the after running dac end_date is showing as blank in paramter file and W_DAY_D table is not having any record.
Any help is greatly appreciated.
Regards,
Bhoomi

Join multiple fact tables and dimensions and use all tables in report 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.
Edited by: Jay on Feb 9, 2012 4:14 PM

So you want me to convert snowflake schema to star. does it solve my problem? individual star queries are working find but when I query multiple stars together getting inconsistency errors. I removed content tables dim level totals for unconformed dimensions in logical fact LTS and set level for measures at total level for unconformed dimensions. it is still in progress and need to test.
Thanks
Jay.

Fact table is joining with Other table having values for measures

I have one Fact table named Fact1 where i am going to create some calculation measures based on the values in Table2.
How should be the physical join between them and the logical join.
Earlier we had those VALUES in Fact1 only
Why we created table Table2 is there was bit confusion for the aggregation in Fact1.
We are bit confused on whether to make Table2 as dimension or Fact as it is having some measures and not having the foreign keys
How we have to proceed now..!! Please help us!!?

I have one Fact table named Fact1 where i am going to create some calculation measures based on the values in Table2.
How should be the physical join between them and the logical join.
Earlier we had those VALUES in Fact1 only
Why we created table Table2 is there was bit confusion for the aggregation in Fact1.
We are bit confused on whether to make Table2 as dimension or Fact as it is having some measures and not having the foreign keys
How we have to proceed now..!! Please help us!!?

Unable to join two fact tables via one common dimension in RPD(Repository)

I have created two fact tables F1 & F2 and one dimension D.
F1 is joined to D and F2 is also joined to D in Physical layer as well as in BMM layer.
I created one report in OBI Answers using these three tables.It Showed me the following error.
**Error Details**
**Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P**
**State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table dfghdfh) does not contain mapping for [Dashboard_Fact.Period_Sgt_Key]. (HY000)**
**SQL Issued: SELECT dfghdfh.Period_Sgt_Key saw_0, "Period Dim".Period_Sgt_Key saw_1, Dashboard_Fact.Period_Sgt_Key saw_2 FROM service_delivery ORDER BY saw_0, saw_1, saw_2**
How to cope up with the issue or can anyone tell me the alternate workaround for this?

That is what i have tried.
I have made a logical table TEST and dragged two fact tables f1 & f2 in source.
Now when i drag different columns from different fact tables(that are in TEST logical table) in report, it gives an error and not making any joins that you are mentioning.
ERROR MESSAGE:--
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Test) does not contain mapping for [Test.SurveyName_Id, Test.SurveyHead_Id, Test.Respondent_Id, Test.SDBusiness_Area_Id, Test.Period_Sgt_Key, Test.OBS_Id, Test.VOCBusiness_Area_Id, Test.Question_Sgt_Key]. (HY000)
The columns mentioned in the error message are all from test logical table..some are from F1 & some from F2.

OBI Joining two lookup tables. [nQSError: 14025] No fact table exists at the requested level of detail

Hello,
I basically have only fact tables that I need for my analysis. No dimensions, no hierarchies.
When add two tables in OBI Answers to start the analysis I see this error:
[nQSError: 14025] No fact table exists at the requested level of detail
I have them defined as lookup tables. How can I join lookup tables?
In order to pre-filter them using the user_name session variable.

Hi Nagireddy.
As described:
open your rpd. go to "manage" -> Variable Manager / New / Session / Variable. so to create a new session variable in the .rpd.
then you create a variable NO_FORCE_TO_DETAIL_BIN and se the default to 1.
BUT....this did actually not do the trick
I have created a logical table that is a table made up of the two that I just want to join and as soon as I create a bi answers report that contain columns from those two tables I see the error 14025.

Re Joining two fact tables.

Hi Experts,
We have a requirement for a report to display columns from two different fact table.
We have a Order Table W_ORDER_D dimension table,a Order item table W_ORDERITEM_F fact table & a INVOICE table W_INVOICE_F fact table.
The requirent is that Order attribute information such as Order Id & order number is coming from the W_ORDER_D dimension table,The Quantity requested is coming from the W_ORDERITEM_F fact table & the Quantity Invoiced is coming from the W_INVOICE_F fact table.
When we display such a report the report is displaying the OrderID,ORDERNUM,Quantity Invoiced,but the Quantity requested is coming as blank.
and the following query is getting fired at the back end.
select distinct T536200.QTY as c1,
T31759.INTEGRATION_ID as c2,
T31759.ORDER_NUM as c3
from
W_ORDER_D T31759 / Dim_W_ORDER_D */ ,*
W_INVOICE_F T536200 / Fact_W_INVOICE_F */*
where ( T31759.ROW_WID = T536200.ORDER_WID and (T31759.ORDER_NUM in ('1-10016611', '1-10017512', '1-10019361')) ) )
if you go through the query it is not picking the W_ORDERITEM_F fact table,but there are joins dified in the RPD between the W_ORDER_D & W_ORDERITEM_F table & the W_ORDER_D & W_INVOICE_F TABLE.
Kindly suggest on the same.
Thanks & Regards,

Hi Goran,
Thanks for your response I've already set the Order Logical Level to Order Detail.
Actually we have imported a new table in the repository W_INVOICE_F & defined the relationships between Various dimensions.One of the Dim is Order.
My Question is that if Order is the common dimension between both the fact table W_ORDERITEM_F & W_INVOICE_F,then the Answers Result should display columns from both the Fact table based on the Concept of confirmed dimension..right??
Please let me know if any other setting is required to define a dimension as confirmed dimension??
We are using the Core business model
Thanks & Regards,

Joining two fact tables for subject area

When I tried to use two simple fact tables joined by a dimension, I am getting the “ No fact table exists at the requested level of detail” error in the answer when I try to pull the columns from Fact 1 and Fact 2 tables. I have set the content in both the fact table to lowest granularity of dimension with CUST_ID, RAT_ID, ACT_ID keys. We have one to many relationships between dimension and both the fact tables. Any feedback is highly cherished.
Fact1: keys are: CUST_ID, RAT_ID, ACT_ID, YEAR
Fields are CUST_ID, RAT_ID, ACT_ID, YEAR , Rev1, Transaction Date
Fact2: keys are: CUST_ID, RAT_ID, ACT_ID, YEAR
Fields are CUST_ID, RAT_ID, ACT_ID, YEAR , Rev2, CreationDate
Dimension keys are CUST_ID, RAT_ID, ACT_ID
Thanks,
uday

Hi LC,
We have to add two fact tables F1 AND F2 to an existing bmm. These fact tables have history tables F11 AND F22 and we have to use partition logic for this.How you did partition ? you should be using Fragmentation logic for that any how you will add the F11/F22 tables to F1 and F2 LTS , so when you join F1 & F2 to the common dimension then it should work for the calucluated measures but dont forgot to create hierarchies and specify the content levels for the fact tables
Thanks,
Saichand

Join 2 fact tables

Similar Messages

Maybe you are looking for