Dimensions joining to fact are restricted incorrectly

Hi all,
We creating a prompt with a series of fields from two dimensions (geographical values and a month). they are all in the same prompt, with the geogrphical values restricted correspondingly. The month is defaulted to the previous month (i.e. Jun 2006).
We've noticed some georgraphical values have gone "missing", we realised that if we didn't filter by the month then they reappeared. When we examine the query of that prompt in the log...we see that OBIEE is relating both dimensions across a common a fact, because this fact doesnt have any entries in June 2006 for some geophical regions, those geographical regions do not appear in the results of the query, which is the reason they dont appear in the prompts.
This would be resolved if OBIEE used a different fact to travel from one dimension to another, one which always has the required data for the geographical regions. This fact exists and works correctly...but how can we tell obiee to use that fact when joining columns from different dimensions rather than the one it is currently taking?

Zjac,
Another way to tackle this is to include a measure from the desired fact in the report and hide it. This would be useful if you have more than one report from the same subject area that display details from two dimensions but need to be joined based on different facts.
HTH.
Cheers
Aniket

Similar Messages

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.

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.

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

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

Joining 2 Facts to one Dimension.

Good Afternoon
I am currently developing a report with 2 Fact tables and only 1 Dimension (Exact Date).
How can i join the 2 Fact tables with using only the one dimension?
I know the formula is something like (FILTER USING)
Can someone please assist?
Regards
Rayno

Joining two fact tables to a dimension is a simple approach like how you join one dim and one fact. Similarly you will join second fact with the same dim.
If the fact tables are joined together and only one fact joins with dim then you can join both fact tables under one LTS in BMM layer and join that logical fact to the dim table.
OBIEE handles how to query both fact tables, as per your design.
Pls mark correct/helpful.

Join a fact to dimensions it's not directly joined to through another fact

Hello Experts,
I have a fact1 table with 2 dimensions
those 2 dimensions join to another fact2 table that is connected to 4 another dimensions.
How is possible to navigate fact1 through the other 4 dimensions?
simplification:
Fact1>----Dim1----<Fact2>----Dim2
I want to navigate through Fact1 using Dim2
is there a work around this configuration in the repository?
Thank You
Regards

Hi,
You need to create a join between a fact and dimension.If you want to navigate fact 1 through other 4 dimensions that are not joined to fact1 then you need to find out some join condition.If you have thought of a report based out of fact1 and those 4 dimension then you should be able to find out some join between these tables.
What exactly you want to do.
Can you please elaborate.
Regards,
Sandeep

Create repository from database model- snowflake facts and dimension joins

I am working on a project that has a database model similar to the image in the link below.
There are other few tables around it, but this generally represent the spine or major database model. This is not exactly a snowflake schema as there are no intrinsic hierarchy in the dimension tables. As you can see dim2 and dim4 has one to many relationship with dim3. there are joins between the fact tables as well.
From some blogs and forum threads, I found out that I can create one fact/dimension table by joining many fact/dimension tables. Is this a right approach? Any thoughts on this model please?
Thanks,
Rakesh
ps: I am using Windows XP Pro and OBIEE 10.1.4.3.1 and right now analyzing the data to create a repository.

Hi Rakesh,
As above post says you combine all fact tables into single fact table with other dimension tables so it would become a simple start schema .Go throught these blogs for further information .
http://forums.oracle.com/forums/thread.jspa?threadID=2124061&tstart=0
http://www.obinotes.com/2010/08/joins-within-logical-table-sources-in.html#comment-form
Hope it helps you.Seems your new to forum you sud follow these rules http://forums.oracle.com/forums/ann.jspa?annID=939
By,
KK

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.

Why OBIEE always joins all dimensions to the fact?

We have a fact table, which joins 10 dimensions. I have a report that gets data from the fact and only one dimension. However, when i see the physical sql, i see that OBIEE joins all dimensions to the fact, even if I am not selecting any information fro the dimension. Is there any setting to avoid this? eg Fact1, dim1, dim2, dim3. The report has data from fact1 and dim1, but the actual sql joins fact1 with dim1, dim2 and dim3 even if I am not selecting any information from dim2 and dim3 in the report

We do use star model at physical and logical layer. I wonder what change I need to make to avoid this. The fact should not always join all dimensions.

Best Practice - Outer Join between Fact and Dim table

Hi Gurus,
Need some advice on the below scenario
I have an OOTB subject area and we have around 50-60 reports based on it. The related subject area Fact and Dim1 table are having inner join.
Now I have a scenario for one report where outer join has to be implemented between Fact and Dim1. Here I am against changing the OOTB subject area join as the outer join will impact the performance of other 50-60 reports.
Can anyone provide any inputs on what is the best way to handle this scenario?
Thanks

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.

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,

Summary Report with 4 Dimensions and 5 Facts

Hello OBIEE Czars:
I have a problem.
I am trying to make a summary report with 4 Dimensions and 5 Facts.
Out of that only 2 Dimensions are Confirmed.
Now when I try to bring in all the facts, I get view display error.
I searched forum for similar issues.
So I have tried following so far.
1) Add other dimensions as source and set level to Total for those dims.
- After doing this, I dont get view display error, but I get blank rows for couple of facts.
2) I am already aggregating all the measures.
Please help me out.
This forum has been very helpful so far.
Thanks.
~Vinay

Hi
This method seems fine until you run a request that includes a filter on an unconformed dimension.
The SQL itself should be quite straightforward (see below) but the BI Server instance does not seem to be joining this data correctly after posting the 2 separate queries to the database.
SELECT
x.dim1, x.dim2
x.fact1_agg_measure
y.fact2_agg_measure
FROM
SELECT
dim1, dim2
SUM(fact1.measure) fact1_agg_measure
FROM
dim1,
dim2, --UNCONFORMED+
fact1
WHERE
.... .... join fact1 to dimensions as normal
AND dim2 = 'BUSINESS_IDENTFIER'
GROUP BY
dim1, dim2
) x,
SELECT
dim1
SUM(fact2.measure) fact2_agg_measure
FROM
dim1,
fact2
WHERE
.... .... join fact2 to dimensions as normal
GROUP BY
dim1
) y
WHERE
x.dim1 = y.dim1
The result set returned in Answers is firstly a correctly aggregated record plus ALL rows from the second query above ??
Just wondering if anyone else has come across this issue?
cheers
Tony

Can we Join 2 fact tables ?

Hi All,
We are trying to join 2 fact tables using a logical dimension. Let me explain my structure fact1 dim1 and fact2 dim2 another dim dim3 which is joined to Fact1. Other dim contains only columns for joining fact1 and fact2.
When I pick columns from fact1 and dim3,dim1,dim2 it works good. Either Fact2,dim1,dim2,dim3 works good but does not wrok when using columns for both fact1 and fact2.
Here we are using couple of materialized views both on Oracle Apps tables and some Custom tables.
Can any one have some kind of solution when using multiple fact tables.
Thanks,

Yo can join as the same joins mentioned as per your physical joins.
But you need to set dimensions hierarchy & aggregation level in BMM layer for sure.
In Reports set the aggregation rule to complex server level.
Regards,
Darwin
Edited by: Darwin S on Dec 24, 2009 1:13 PM

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

Dimensions joining to fact are restricted incorrectly

Similar Messages

Maybe you are looking for