Join two fact records

In OBI 11g, I have a report in which I show
dimRecord1 FactRecord
dim Record2 FactRecord2.
Is ther any way to construct a rpeot such that , it can be shown as
dimRecord1 FactRecordd dim Record2 FactRecord2.
in the same row
?

Hi,
Kindly refer below link
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
Two Fact tables with Different set of Dimension Tables
Thanks
Deva

Similar Messages

Joining two fact tables with different dimensions into single logical table

Hi Gurus,
I try to accomplish in Oracle Business Intelligence 11.1.1.3.0:
F1 (D1, D2 and D3)
F2 (D1 and D2 and D4)
And we want to build a report F1 F2 D1 D2 D3 D4 to have data for:
F1 that match only for D1-D2-D3
and data for
F2 that match only D1-D2-D4
all that in one row, so D3 and D4 are not common dimensions.
I can only do:
F3 (D1, D2)
F4 (D1, D2 and D4)
And report
F3 F4 D1,D2,D4 (all that in one row, and only D4 is not a common dimension)
Here is the very good example how to accomplish the scenario 1
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
But looks like it does not work in 11.1.1.3.0
I get
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 14025] No fact table exists at the requested level of detail: [,,Clients,,Day,ROI,,,,EW_Names,,,,,,,,,,,,,,,,,]. (HY000)
I am sure I set up everything correctly as advised in the blog but it works with only one not a common dimension
Is it a bug in 11.1.1.3.0 or something?
Thanks,
Kate

Thanks for all your replies.
Actually, I've tried the solutions you guys mentioned. Generally speaking, the result should be displayed. However, my scenario is a little bit tricky.
table Y's figures are not the aggregation of table X for D dimension. Instead, table Y's figures include not only D dimension total, but also others (others do not mean A, B, C dimension). For example, table Y stores all food's figure, while table X stores only drink's figure. D dimension is only about drink's detail. In my scenario, other foods' figure is not provided.
So, even if I set D dimension to all/total for table X, table X's result is still not the same as table Y.
Indeed, table Y does not have a column key to join to D dimension's key. So, if I select D dimension and table Y's measures at the same time in BI Answer, result returns no data. Hence, I can't compare table X and table Y's results with selection of D dimension.
Is there any solution to solve this problem?
Edited by: TomChan on Jun 3, 2009 9:36 AM

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

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.

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

Joining two fact tables

Hi:
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.
We have multiple dimensions D1,D2,D3, D4,D5, D6, D7, D8.
We have common dimension table D1.
F1, F2 are joined to D1 on the item Id.
F1 should be joined to F2 on the Invoice Id.
We have calculated columns in F1 based on the columns in F2.
Please let me know the best way to build a bmm in this scenario.
Thanks,
LC

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

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.

Joining two facts

Hi,
I have two facts. They have a parent child relationship. We first thought of creating a degenerate dimension with the parent fact. However, I think with degenerate dimensions 1 to N joins do not work.
Is there any other way to accomplish this, other than creating a separate dimension
Thanks
Ashvishw
Edited by: user9546253 on Mar 22, 2011 1:48 AM

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.

Error when we take the Desc column in the report when we join two facts

Hi All,
We are facing a issue when we join 2 facts via common dimension.
1) When we take the measures like revenue cost etc from both the facts after they getting aggregated on RPD as sum the report runs fine..
But once we add a desc column like Name, address from any of the facts which cant be aggregated it gives a error.
Can any one please share their knoledge over this & the fix..
Thanks,
Pankaj

Hi All,
I am very near to solve this issue. I tried doing the same.. but seems i am missing something please help me figure it out. I appreciate all your help...
-FACT1 Columns:
1) Amount
2) Transaction scr desc
-FACT2 Columns:
1) Accounted DR
2) Transaction scr desc
Note: 1) These Facts are joining over dimensions currency, period etc, whose IDs i havent mentioned in the list above. also i have created reqd dimension & set proper content level too.
2) The measure Amount & Accounted DR from both facts are aggregated as SUM.
Now when i take a report having F1.Amount, F2.Accounted DR, F1.Transaction scr desc, F2.Transaction scr desc
the query fails as I have a non aggregated columns like Transaction scr dec from both the facts.
I tried the above approach mention by you ppl, and made a 2 new logical table, one having scr from one fact from physical & the onther from other fact from physical & made these 2 new tables are dimensions to the earlier also respectively i have created the dimesnions for both 7 set the content level to detail.
I made a new report:
F1.Amount, F2.Accounted DR, F1_NEW.Transaction scr desc, F2_NEW.Transaction scr desc
Unfortunately i m facing this error: [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: tmpt.TRANSACTION_SOURCE. Please fix the metadata consistency warnings.
Thanks,
Pankaj

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,

Using two facts of two different star schemas and conformed dimensions

Hi,
I've been working as developer and database designer for years and I'm new to Business Objects. Some people says you can not use two facts of two different star schemas in the same query because of conformed dimensions and loop problems in BO.
For example I have a CUSTOMER_SALE_fACT table containing customer_id and date_id as FK, and some other business metrics about sales. And there is another fact table CUSTOMER_CAMPAIGN_FACT which also contains customer_id and date_id as FK, and some other business metrics about customer campaigns. SO I have two stars like below:
DIM_TIME -- SALE_FACT -- DIM_CUSTOMER
DIM_TIME -- CAMPAIGN_FACT -- DIM_CUSTOMER
Business metrics are loaded into fact tables and facts can be used together along conformed dimensions . This is one of the fundamentals of the dimensional modeling. Is it really impossible to use SALE_FACT and CAMPAIGN_FACT together? If the answer is No, what is the solution?
Saying "you cannot do that because of loops" is very interesting.
Thank you..

When you join two facts together with a common dimension you have created what is called a "chasm trap" which leads to invalid results because of the way SQL is processed. The query rows are first retrieved and then aggregated. Since sales fact and campaign fact have no direct relationship, the rows coming from either side can end up as a product join.
Suppose a customer has 3 sales fact rows and 2 campaign fact rows. The result set will have six rows before any aggregation is performed. That would mean that sales measures are doubled and campaign measures are tripled.
You can report on them together, using multiple SQL passes, but you can't query them together. Does that distinction make sense?

Two FACT Tables, Some Common and Non-Common Dimensions

Hello all, a question i am sure you have faced in the past but still wanted to get your feedback.
I have a few FACT tables and some dimensions that are shared (common dimensions). Rest of the dimensions are related to one or the other FACT tables.
What is the best way to present a view where users can pull information from both the FACT tables?
I am successful in pulling the shared (common) dimensions across BOTH FACT tables having the same grain but this view breaks down when i pull information from one Dimension that has not much to do with the other FACT.
What is the best way to present this? Should this be broken in three subject areas?
Subject Area 1 --> Some Dims --> FACT Table A
Subject Area 2 --> Some Dims --> FACT Table B
AND
Subject Area 3 --> ***Only Common Dims*** --> FACT Table A & FACT Table B?
Your feedback is always appreciated.
Regards,
Edited by: user10679130 on Oct 12, 2009 3:27 PM

Please check the forum first for similar threads/questions.
Joining two fact tables with different dimensions into single logical table
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
This solution keeps both fact tables in the same subject area in the single logical fact table, with common and not-common dimensions.
Regards
Goran
http://108obiee.blogspot.com

Connection between two fact tables.

I have a problem in OBIEE 10.1.3.2:
I have two fact tables A and B. Both tables have three columns - time_id, position_id and valuea (table A), time_id, position_id and valueb (table B). I have dimensions TIME (id, time) and POSITION (id, post). Facts A and B are connected to dimensions and
both queries
select TIME.time, POSITION.post, A.valuea,
select TIME.time, POSITION.post, B.valueb
work properly.
But it is definitely impossible to execute query
select TIME.time, POSITION.post, A.valueA, B.valueB.
[NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table A) does not contain mapping for [B.VALUEB]. (HY000)
Another two fact tables in the same application I can join in any query wihout any problem.
How is it possible?
Thanks for your help
Jiri

How did you joined two Fact tables. Did you use Dimension table between?

No join with fact

Hi All,
We have requirement ie... we have 2 dims and 2 facts. 1st dim has join with 2 facts but 2nd dim has join with only 2nd fact, now we want a report on both dims and facts. what should i do for that
thanks in advance

Hi,
Follow this link http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html .....you need to create a single fact of the both facts that is wat is mentioned in the blog.
Other one http://www.obinotes.com/2010/08/joins-within-logical-table-sources-in.html
Hope it helps you.Mark points.
By,
KK

Two facts with joins to all dimensions

I have two dimension tables say D1, and D2 and they are joined to two facts F1 and F2. Now I need a report from one column of d1 and other column of d2 how obiee server will perform query by only one fact or two facts if only one fact which fact it will go through.

OBI will select one fact....I think it's based on the order of the facts in the business model.
But, you can set an implicit fact columns in the presentation layer...this gives you the possibility to add implicitly the fact table that must be used when only dimension objects are selected.
Hope this answers your question.
Kr,
A

Join two fact records

Similar Messages

Maybe you are looking for