Physical Layer Joins

I am creating a data model from a database that is in 3rd Normal Form. My understanding in the physical layer I should make the joins based on the relation between tables. I have a CUSTOMER & ADDRESS table and I understand that my join will be 1:M here since 1 Customer can have many addresses. However I would like to get all my facts from the CUSTOMER table so since this is going to be the fact table should the Many end of the join be at the CUSTOMER table. I have been given much misinformation about this and have 2 scenarios but do not know which is correct.
Scenario #1: Model the joins in the physical layer as 1:M e.g 1 Customer has many Addresses and then reverse the joins in the BMM to make the CUSTOMER table a fact table.
Scenario #2: Model the joins in the physical layer making the M (Many) side of the join on the Customer table therefore choosing it as a fact table in the physical layer.
Thanks in advance for any answer.

So if I understand correctly then the join in the physical layer will look like this: CUSTOMER------------->ADDRESSES. Is this because the CUSTOMER table is going to be the fact table. I thought the relationship between Customer and Addresses is a 1:M i.e. 1 Customer has many addresses. Why do we not model this in the Physical Layer.

Similar Messages

Logical joins differ from Physical layer joins

Can please answer to my Question?
1.How does Logical joins differ from Physical layer joins?
2.What is NQSConfig.INI file and what does it contain?
Thanks
Chi
[email protected]

2) The NQSConfig.INI file contains configuration and tuning parameters for the Oracle BI Server. There are parameters to configure disk space for temporary storage, set sort memory buffer sizes, set cache memory buffers, set virtual table page sizes, and a number of other configuration settings that allow you to take full advantage of your hardware's capabilities.
For more information about the NQSConfig.INI file parameters, refer to Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
1) Logical joins are used in Business Model, Physical joins are used in physical layer. A key property of a logical join is cardinality. Cardinality expresses how rows in one table are related to rows in the table to which it is joined. Logical joins supports outer joins. so many else to mention... just go through RPD help file.
- Madan

Additional join in rpd physical layer.

Hi,
I created a subject area joning all the tables in physical and BMM. Now I need to existing two tables with one more key. Can I just go the physical layer joins, double click on the join and add the new join there. Can we do like this or is there any process to follow. Please advice.

user4683504 wrote:
Hi,
I created a subject area joning all the tables in physical and BMM. Now I need to existing two tables with one more key. Can I just go the physical layer joins, double click on the join and add the new join there. Can we do like this or is there any process to follow. Please advice.Yes thats it, or edit the join from the UI (right click table -> Foreign Keys)

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

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.

Multiple joins Problem in Physical Layer.

I have two tables Departments and Employees in the physical layer of admin tool. When i am trying
to create foreign keys at physical diagram its giving error.
Scenario:
Departments
===========
Department_id (PK)
Manager_id (FK)
Employees
========
Employee_id (PK)
Department_id (FK)
Manager_id (FK)
1. Manager_id of Departments table references Employee_id of Employees table
2. Department_id of Employees table references Department_id of Departments table.
3. Manager_id of Employees table references Employee_id of Employees table.
I have done 1st one. After 2nd one i have tested for consistency check, the following error is coming:
[38015] Physical tables "Oracle DB Connection".."HR"."EMPLOYEES" and "Oracle DB Connection".."HR"."DEPARTMENTS" have multiple joins.
Delete new foreign key object if it is a duplicate of existing foreign key.
How to solve this?
How to do 3rd one also?
Please clarify.
regards
chandra kanth
Edited by: Chandra kanth on 08-Dec-2011 01:47

Hi,
I have created two alias tables (E1 Employees, D1 Departments) for Employees, Departments tables.
I have created foreign key joins as follows:
D1 Departments:
EMPLOYEES.EMPLOYEE_ID = "D1 DEPARTMENTS".MANAGER_ID
E1 Employees:
EMPLOYEES.EMPLOYEE_ID = "E1 EMPLOYEES".MANAGER_ID
and it is consistent also. Please let me know whether the above approach is right or not.
regards
chandra kanth.

Joining tables across databases in OBIEE Physical Layer

I was facing this problem of joining tables across databases in Physical layer of OBIEE admin tool.
I had a requirement to combine two tables from 2 different databases A and B respectively. I had created one database object (OBIEE Object) in the physical layer and I had created two connection pools under that pointing to the required databases. I was able to view the data (right click on the table object --> popup menu option "View Data" ) though I had to go through the "Select connection Pool" window and select the required connection pool. I was able to join the tables and was able to complete the star schema in BMM and bring them up to the presentation layer. Conistency check was also successful. Everything went fine so far.
But when I started building the report, I started getting error whenever I chose the table which was supposed to be queried by using the second connection pool. The error message was something like "table or view does not exist at OCI call OCIStmtExecute". I assume that this was happening because the systm was not able to understand which connection pool to choose (because there were two pools defined under one database object) and by default the server was choosing the first one. If anybody is having a different opinion or definite information about this, kindly update with your reply.
I could resolve this problem after creating a separate database object with a separate connection pool defined under it, which points to the second database. Imported the required table under this database object. (Infact it was reverse. When I re-imported the table, OBIEE Admin tool, by default created its own database object and the connection pool separately for the imported table).
Once this was done then I went ahead as usual by joining the tables across these two different database objects and modelling was already done (ofcourse with a little more tweaking since the mapping had to be redone between BMM and Physical layers). Now I could build the report in the reporting layer without encountering any error.
Appreciate and welcome any further additions/updations/corrections regarding this issue(?).
-MMishra.
Edited by: user13483341 on Nov 29, 2011 8:20 AM
Edited by: user13483341 on Nov 29, 2011 8:20 AM
Edited by: user13483341 on Nov 29, 2011 8:24 AM

Hi Deepak, Thanks for your reply.
Appreciate if you can help me with another thread "possibility of multi-currency in OBIA 7.9.6.2 financial anlytics".
- MMishra.

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

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

Defining Keys/Joins in the physical layer

When the keys and the join conditions are defined manually using a table's Properties dialog box in the Physical layer, do these keys or joins also get defined in the database automatically? My understanding is that it does not get created in the database. So what I am trying to understand is - once the joins are defined in the RPD physical layer, do I have to then define the indexes/constraints in the database as well?
Thanks,

803309 wrote:
When the keys and the join conditions are defined manually using a table's Properties dialog box in the Physical layer, do these keys or joins also get defined in the database automatically? No
My understanding is that it does not get created in the database. So what I am trying to understand is - once the joins are defined in the RPD physical layer, do I have to then define the indexes/constraints in the database as well?
Not required. Indexes can be created in DB on joining col for performance purpose only.
Hope this helps
Edited by: Deepak Gupta on Aug 15, 2011 10:07 AM

Joins in the physical layer

Hi,
I have a small doubt:
Is it possible to to give the Outer joins in the physical layer+ of the RPD.i.e.,left outer join,right outer join and full outer join.
If yes can you pls provide me any links related to that.
Thanks,
Chinna

Hi,
No we cannot have outer joins in Physicla layer.
We can outer joins in BMM layer.
In BMM layer - complex join can be full inner join or full outer join or whatever your criteria was,but in physical layer - physical join is always an inner join.
Check this....http://nerdsofobiee.wordpress.com/2010/07/06/obiee-interview-questions/
http://gerardnico.com/wiki/dat/obiee/physical_layer
Regards,
Srikanth
Edited by: Srikanth Mandadi on Oct 15, 2010 1:29 AM

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

Physical Layer Joins

Similar Messages

Maybe you are looking for