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.

Similar Messages

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.

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.

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

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

Do we need to give new joins in physical layer

hi all,
due to some back ground problem ,we have deleted the existing table in back end and again we have created the table having different columns names with same table name
let say ,i have deleted table A and it is having columns (no int ,name varchar,...) in the back end... again i have created table A and different columns name(sno number,sname varchar)...
like this i have created .. and whatever the content is there in old table same data i copied in to new table.
so... here my question is do we need to again import that table into physical layer and again we need to give joins... or can we make use of existing table ....???
now i am running the reports with old table .. reports are not coming up... its giving an error....
is it mandatory to import the table again .. and again i have to do all joins..
i did few calculations using that dimension ...... so... any other alternative solution for this ... instead of doing joins.. ..
i have changed the column names in back end... that's it
here can we make use of catalog manager to change the column name in the reporting side....after changing the columns name in physical layer..
i don't knw the process of catalog manager.... please can any one send me the link to change the column names in the reporting side .....using catalog manager
Thanks

Hi,
If you have deleted table in database and you have created a new table with same columns and same structure then you should not face any problem. OBIEE will still have that table intact in physical layer.In your case since you have changed the names of columns in database it is creating problems for you because OBIEE query will use names mentioned in physical layer and those columns are no more in database. SO to resolve the issue go to physical layer and change the names of the columns .That should solve the problem.
Regards,
Sandeep

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.

How to add a stand alone table from Physical layer to Business Model

Hi,
I have tables from 2 different database sources in my Physical Layer.
My Business model currently uses only tables from one database. from my second database in teh physical layer I need only one table and that will be a stand alone table, to my Presentation layer.
1. Does it have to go through my Business layer or can it be directly added to the Presentation layer. What are the steps?
2. Can I restrict the permissions on that stand alone table only to the administrator?
Thank you.

1)create a view with single column using the sql (select 1 from dual) in physical layer and join it with the table using complex join in physical layer (1=1).
Move that to BMM, set the column as key in both physical and bmm layer.
2) You can restrict the access for the table presentation layer
Double click the presentation layer table -> Permission -> there you can restrict the access by user or group
Thanks,
Vino

Physical layer design in obiee 11g

Hi,
I need a clarification regarding physical layer degin in obiee 11g,I imported Oracle Apps reports ,but could not find any keys there at table level.So should i create keys on the imported table level or at the alias level of the imported tables.
Thanks-Bhaskar

If you import a transaction table you may have keys imported in physical layer but when you going with warehouse table you may not have keys at database level, you define them using join in physical layer.
We have surrogate keys in dwh.
Hope this clear your doubt, if helps pls mark

Obiee - physical layer

Hi,
I'm new to obiee tool.
my dimension table have composite primary keys (3 keys - suppose employee id, employee ssn, phone no)
and my fact table have (2 keys - employee id, employee ssn )
then, how do we do physical join in physical layer ?
Do, we need to create 2 alias tables and join to my fact table ?
or, else can i use expression builder in the physical diagram..physical join ?

Hi,
This is why you go for alias tables ..
To set up multiple tables, each with different keys, names, or joins, when a single data source table needs to serve in different semantic roles. Setting up alias tables in this case is a way to avoid triangular or circular joins.
For example, an order date and a shipping date in a fact table may both point to the same column in the time dimension data source table, but you should alias the dimension table so that each role is presented as a separately labeled alias table with a single join. These separate roles carry over into the business model, so that "Order Date" and "Ship Date" are part of two different logical dimensions. If a single logical query contains both columns, the physical query uses aliases in the SQL statement so that it can include both of them.
You can also use aliases to enable a data source table to play the role of both a fact table, and a dimension table that joins to another fact table (often called a "fan trap").
To include best practice naming conventions for physical table names. For example, you can prefix the alias table name with the table type (such as fact, dimension, or bridge), and leave the original physical table names as-is. Some organizations alias all physical tables to enforce best practice naming conventions. In this case, all mappings and joins are based on the alias tables rather than the original tables.
Now for creating joins you can make use of expression builder to have Primary Key and Foreign Key Relationships OR you can also have Complex Joins here over nonforeign key and primary key columns. When you create a complex join in the Physical layer, you specify the expression for the join. Like
Employee.employeeID=Fact.EmployeeId
and Dim table.deptname <> 'ABC'
You, can also have case statements here...
Hope this clears your funda regarding Alias Tables & Joins. Expression Builder is just the utility for developers to select the table, columns, expressions, variables and may other functions available.

RPD Physical Layer

Hi,
I am trying to import tables from database to the physical layer. when we select objects to add to physical layer which boxes to we need to check below. I know we need to check 'Tables' and 'Keys'. Other than these two do we check any other box?

Thank you. I have one more question. When I try to do a foreign key join in Physical layer a message pops up saying ' A matching table key doesnt exist in table. Do you want to create one'. Sould I just say 'yes' to it. Any idea why this message is coming?

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.

Join in Physical Layer

Similar Messages

Maybe you are looking for