Fact joins in Physical ayer

Hello All,
I recently joined in a project, I was going through the RPD and I can see there are Fact to Fact joins in Physical layer..however there are no Fact joins in BMM layer.
I'm trying to understand why these joins are created and how it will impact in BI query's. Thanks...

It is Fact to Fact Extension they have joined i guess.
http://satyaobieesolutions.blogspot.com/2012/07/implementing-multiple-fact-tables-in.html
Mark if helps.

Similar Messages

What is the different between Logical complex join and Physical join?

hi,
Do somebody know what is the function different between logical complex join in BMM layer and physical join in physical layer?
Thanks.

Thank you very much1
I understand their differentiation:
In the BMM Complex join (intelligent), means OBI picks the best way from possibly many different ways to join using physical join. FK join forces the same join always, which limits flexibility.

Can we create a multiple joins in physical layer

Hi,
I have a requirement that i want to create a multiple joins in physical layer.
Ex:
Table a (custid,name,sal) and tableb (custid,ced_id, loc)
i had requirement that cust id is joining with custid and cedid from table b
i.e a.custid=b.custid AND
a.custid=b.ced_id (Note data types are same across all the joins here).
When am trying to handle it form physical joins, getting an issue that The column'cusid' is used twice.
Regards,
Malli

As Daan said use complex join in physical layer that should work. Just in case its not working then go with 1 join condition physical layer and create foreign key join in BMM layer, this would override join in physical layer.

Join in Physical Layer

hi all,
is it possible to give right outer join in physical layer? if so how can we do that? actually Type options is not visible in physical diagram.
thanks

No, outer joins are created in the bmm layer.

How can we achieve the outer join in physical layer

Hi,
Can any one can suggest ,how do we handle the outerjoin criteria in obiee.
thanks
B.kumar

Its not advisable as such to use complex join in physical layer......Use physical primary-foreign key relationship join on the tables.
But looking at your where condition
where tab1.date between tab2.start_date and tab2.end_dateIt is not possible because you are taking table1 date and giving the table 2 dates for evaluation.
it should be this way if its primary key relation ship.
where tab1.date between tab1.start_date and tab1.end_dateIf it is equi-join then you need to write what you have mentioned in your query.
Cheers,
KK

Outer Joins in physical layer

Hello BI people - I'm new in this issue and I need help.
I'd like to do sth like outer join in physical layer between two tables and I can't :(
For example
Table CUSTOMERS and table REGIONS for customers. Table CUSTOMERS has colum: POSTAL_CODE and in table REGIONS I have primary key:POSTAL_CODES. till now everything looks simply PK to FK 1:n relation but sometimes happens that in table customers there are nulls or mistakes in this field (reason: bad written application, dirty data etc)
and when I don't use OUTER JOIN I'll lose some records about customers - I would like to see that records even with cleared region informations. How to do it in BI -use VIEWS ? Can I join two physical tables with outer join?
Thanks for help

Ok. You have to resolve this in the logical layer as wel.
When you click on custumers and then on sources.
What do you see there?
Do you only see one source or 2 sources?
If you see 2 sources, then just delete one and double click on the source that is left over. In here you can join with the other table and choose outer join.
Good luck ;)

Complex join in physical layer

Hi Experts,
In which scenarios we will use complex join in physical layer i saw in many blogs that when we are using expressions and other than equality.
For better under standing can any one post few scenarios on this.
Regards,
Rafi

Hi,
Always use “Foreign Key” joins, not “Complex Joins” on the Physical Layer
Refer-http://obiee101.blogspot.com/2011/10/obiee11g-golden-rules-rpd-physical.html
If your join looks like D_DATE = TRUNC(S_DATETIME) try add a extra column S_DATE in your DWH. Any matching processing done by the BI-server costs time and you often loose the advantage of an index in your DWH.
For all others relationships other than a Primary Key-Foreign Key Relationships (expression other than equal to perform an equi join), you have to use a complex join otherwise you have to use a foreign key

Use of complex join in BMM and Physical Join in Physical layer ?

Hi All ,
Why we need to use complex join in BMM layer not the Physical Join ?
Why we need to use Physical Join in Physical layer not Complex join ?
thanks in advance

Hi,
A physical join is at the physical layer and defines the join between two physical tables.
Logical joins live at the BMM (logical) layer and define a join between two logical tables.
The important differentiation is that at the BMM layer you do not tell the OBIEE server how to do the join,
you just tell it that there is a relationship between these two logical entities.
when the server comes to this logical join it will use the information in the physical joins and decides how the two logical tables are joined together.
thanks,
pramod.

Diff bw complex join and physical join

hi all
Can sumbody explain me the all the differences between complex join and physical join in the admin tool
Thanks
Shobhit

Hi,
Suggest you to go through this link. It may be helpful in detail.
http://st-urriculum.oracle.com/obe/fmw/bi/biee/r1013/bi_admin/biadmin.html
Thanks,
Vengatesh.

OBIEE 11g - complex join in physical layer

Hi, I need to create a complex join in the physical layer with join criteria like the following:
fact.fiscal_year = dim.fiscal_year and fact.accounting_period <= dim.accounting_period
Every time I try to do this, I get the nQSError: 37005 Transaction Update Failed message. Any ideas what is going on?
Thanks,
Scott

Actually, I (finally) got it to work - wow logical joins are a big pain in the butt in 11g. First off, I had to edit the RPD offline, couldn't get it to work (at all) online.
Next I had to delete the existing joins...there appears to be no way to change an existing FK join into a logical join.
Next created the logical joins as stated in my original post - but had to fiddle with it for about 15 minutes to get it to work. You can NOT click the two columns on the dim side, two columns on the fact side, and then just edit the default formula (which defaults to have = sign between the expressions) - because it creates a FK join, and then you start getting errors. Instead, I had to build the expression from scratch.
All in all, 11g has gotten much less flexible and easy to use in this regard.
Scott

RPD: Wrong Fact join when utilizing Level Based Measures (TOTAL Level)

I have 2 Facts and 3 Dimensions (Customer, Customer Emails, Time) being used in the RPD. The Dimensions are all set with TOTAL and DETAIL hierarchies.
Physical Layer:
Fact 1 joined to all 3 Dimensions
Fact 2 joined to all 3 Dimensions
Business Layer:
Fact 1 joined to all 3 Dimensions and Content Level set to DETAIL for all 3 Dimensions
Fact 2 joined to all 3 Dimensions and Content Level set to DETAIL for all 3 Dimensions
Metrics:
Fact 1 Metric: SUM set to TOTAL Level for Customer Emails Dimension
Fact 2 Metric: SUM set to TOTAL Level for Customer Emails Dimension
Issue:
I run a query pulling the metric from Fact 1 along with Dimension columns Email Address and Customer Name (2 Dimension Tables).
2 Physical queries are generated one against Fact 1 to get the Metric total by Customer. The 2nd query to get the Customer and Email Address that hits the Fact 2 table.
Expectation:
I would expect both queries from above to hit the SAME fact table (Fact 1). I understand the 2nd query would NOT contain the metric (Due to it set to TOTAL), but a relationship exists between the Fact 1 table and the Email Dimension, since the metric is pulled from this table I'd expect the Dimension value to be pulled from this table as well.
I look forward to any thoughts.

Merging Customer and Customer Email will not work as a Customer can have multiple Email Addresses and changes the grain of that Dimension (Customer Level).
Implicit fact would make no sense here, since each Fact has different sets of data.
The basic issue here is that we have a Customer Email table that is NOT at the grain of the Fact or even the Customer Dimension. I would have loved to snowflake off the Customer Email from the Customer Dim but then the metrics get inflated when returned and total on.
Hence we built the Email dimensions to join off the Fact and set all the metrics in each Fact (That joins to Customer) to TOTAL. So the metrics do not get inflated, the metrics repeat (Customer request) for each email per Customer.
I hope that clarifies.

How to define join in physical layer between cube and relational table

Hi
I have a aggregated data in essbase cube. I want to supplement the information in the cube with data from relational source.
I read article http://community.altiusconsulting.com/blogs/altiustechblog/archive/2008/10/24/are-essbase-and-oracle-bi-enterprise-edition-obiee-a-match-made-in-heaven.aspx which describes how to do it.
From this article I gather that I have to define a complex join between the cube imported from essbase to my relational table in physical layer.
But when I use Join Manager I am only able to define jooin between tables from relation source but not with the imported cube.
In My case I am trying to join risk dimension in the cube based on risk_type_code (Gen3 member) with risk_type_code in relation table dt_risk_type.
How can I create this join?
Regards
Dhwaj

Hi
This has worked the BI server has joined the member from the oracle database to cube. So Now for risk type id defined in the cube I can view the risk type code and risk type name from the relational db.
But now if I want to find aggregated risk amount against a risk type id it brings back nothing. If I remove the join in the logical model then I get correct values. Is there a way by which I can combine phsical cube with relational model and still get the aggregated values in the cube?
I have changed the column risk amount to be sum in place of aggr_external both in logical and phsical model.
Regards,
Dhwaj

Fact - dimension and Fact Join

Hi ,
I have a issue in OBIEE 11g here ,
I am trying to query two columns from 2 different fact tables F1 and F2
the join between these tables is F1 - D - F2 , where D is the confirmed dimension.
so when i am querying for
f1.c1 , d.c1 , f2.c1 , its throwing me up with error
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14020] None of the fact tables are compatible with the query request
Can you please help me with this issue , am i doing the correct join ??, can we query two columns from two diff fact tables?
Thanks in advance.

Hi All,
Thanks for your responses , I have tried creating hierarchy dimension and assgned levels to the fact sources but i still see the error
and
Combining 2 facts will resolve the issue but its not the case here as each fact table has about 25 dimensions connected to it , but there are only 2 confirmed dimensions between both facts and the problem here is user wants to see both the fact tables in the same subject area
I have been trying but unable to get the solution.
Can you guys please suggested any other way of achiving this task
Thanks a lot

Fact to Fact join in Obiee

Hi
I am new in OBIEE, I have an scenario where in we need to join two fact tables and the condition is F1.date is between F2.valid from date & F2.valid To date
I have tried using confirm dimension. Is it possible to map such scenario in OBIEE 11g
Thanks
Sameer

Hi Venkat,
I am coming from the basics of a star schema here, so hope it helps
What is a fact?
A fact is something that has all measures which can be aggregated (Units, Dollars, # of Orders) etc with keys to different dimensions.
What is a dimension?
It is the context with which we understand/record/retrieve the measures in the fact. We understand "# of Orders" for a product/By a customer etc.
So joining a dimension and a fact helps to answer the Who/What/When kind of business questions. Ex : Who bought these products? What was the product type? When these products were sold kind of...
Now just imagine tying up fact to another fact. With this kind of model, you can never answer any business question.
I have never tried joining a fact with another fact in OBI (But do not think it will allow it though :) )
Hope I am clear.
Thank you,
Dhar

2 Dimensions and a Fact - Join Paths

I have a scenario and I have been racking my brains out as to if what I am looking for could be set up. I have two dimenisions - Region and System - each System belongs to a Region. So the System Dimenison contains a Region_Key.
I have a Fact table that contains both the Region_Key and the System_Key allowing each dimension above to be joined directly to the Fact table.
Is there any way of creating a model where I could set it up where if someone pulls a column from just the System and Region it only pulls from these two tables (The join doesn't go through the Fact Table). And when a metric is pulled that it uses the direct joins to the Fact table for each table.
I'd appreciate any feedback, thanks alot!

If I am understanding what you are saying, you are saying to duplicate the Region Dim in the Business Layer then join this newly created Logical Table off of the System Dim? So snowflaking it out. But how would that allow me to present the Region column as one column in the Presentation layer? If the user just selected the Region column and a Fact I was hoping the path would just go between that direct join. If they selected only Region and System just have it utilize the dimensional join. Thanks for your response by the way!

Fact joins in Physical ayer

Similar Messages

Maybe you are looking for