Joins in BI Administration layer

Hi,
I have created few dimension in Owb, along with a cube. now i imported them in BI administrations physical layer. is it necessary to join them both on physical and business model an mapping layer or its enough to join them on physical layer.
secondly, can we use complex join in place of logical foreign key joins.........??
regards,
imran

Thanks for ur response.......
I did the same but when i completed business model and mapping layer and then drage it to the presentation layer but consistancy check gives me error that shows there is some relationship error. i think some joins are still missing.... should i join on presentation layer as well .......... if not why ???? as i am joining tables in first two layers.....
Secondly tell me something about Chronological key in time dimension. what is its usage.......
thanks
imran
Edited by: user596732 on Feb 18, 2009 10:39 AM

Similar Messages

Join issue OBIEE (BMM Layer)

Hi All -
1. I have following tables:
D1 - Dimension Table
D2 - Dimension Table
D3 - Dimension Table
F1 - Fact Table
We have join between - D1 - F1, D2, F1 & D3 - F1
2. We have some more tables :
D4 - dimension Table
F2 - Fact Table
We have join between - D4 - F2
3. We have some more tables :
D5 - Dimension Table
F3 - Fact Table
We have join between - D5 - F3
Now the scenario is we need to enable joins between all these tables in the logical layer. i created dimensional hierarchies and assigned at the total level for the fact tables. but it is not working.
can anybody please lookinto this issue?
Thanks

I noticed that if you create the FK in the physical layer BEFORE moving the columns into the Business Model layer it will keep them when you bring them over, but if you create the columns in the BM layer then made the physical joins you have to go back and join in the BM layer.
Unfortunately if you'll lose anything in the Presentation or Business Model layer if you remove it from the BM and want to re-join.

Why do we need to Join in the BMM Layer

Hi,
Somebody asked me the following questions
*"If the joins are already defined in the Physical Layer and ultimately the query will pass thru Physical Layer to the Database and will take the joins defined in the Physical Layer then why do the joins in the BMM layer". This can be a Complex join or a Foriegn Key Join*
Under what conditions do we use Foreign Key Joins in BMM layer ?
How do we use Stored Procedure in OBIEE?
Any answers.
Rgds,
Amit
Edited by: amitsharma73 on May 20, 2010 5:51 PM
Edited by: amitsharma73 on May 20, 2010 5:52 PM
Edited by: amitsharma73 on May 20, 2010 5:52 PM
Edited by: amitsharma73 on May 20, 2010 5:53 PM

This is most likely because the copy's licence has not been verified, and to verify it you need to log in so it can check that you account contains the license.
It's just to prevent torrenting and piracy.

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

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

Table joins, templates, null-checks, layer confusion and localization

Hello everyone, this is my first post on this network.
I am designing a website that does several things, one of which is to display latest news items on the home page.
The news items are stored in the database as a table with a basic structure: id, poster_id, postDate, subject, body
where id is the primary key, poster_id is a foreign key to the users table, postDate is the date at which posted and the rest is obvious.
I want to display these items with a basic template:
subject by author at postDate
body
<hr />
When a user changes his/her username, the updated username will be shown on the news listing. This is the reason why I'm using a foreign key.
I've defined poster_id such that it can be set as NULL, meaning it was not created by a registered user, but a guest. Don't ask me why I'd want a guest to post a news item :P
When it comes to getting the news posts from the database and resolving the poster_id to a username i just use a join. However, when poster_id is NULL i obviously don't get a username for that post but a NULL. The word "Guest" has to come in when the poster_id is null. So in my template you'd think i could just put a null check as I can't do it in sql (as far as i know anyway).
Now, I'm using localization on the site and the word "Guest" is different depending on the locale. So you'd think i could just use a null check and a locale->get('guest_username') and that will return the word "Guest" in the right language.
If I want to view news on different pages, and more importantly, in different forms such as just author: subject, I come across a problem. I want to avoid having to repeat that null check code on every template that views news posts. Complicating things, I want anywhere that display a username to do the null check and return the locale'd guest username if it is a null.
Where do I put this null check? The locale object is part of the model layer, because other model objects use it.
Is this the presentation or the model layer's responsibility? I am relatively new to this design patterns thing, but I'm getting there :) I've thought about using wrapping classes but I'm just not sure at this point and I need smart people's opinion :)
I hope I was able to explain my problem properly and I thank anyone in advance for taking the time to read and give their insight on such a problem. Thank you :)

antirealm wrote:
Hello everyone, this is my first post on this network.
I am designing a website that does several things, one of which is to display latest news items on the home page.
The news items are stored in the database as a table with a basic structure: id, poster_id, postDate, subject, body
where id is the primary key, poster_id is a foreign key to the users table, postDate is the date at which posted and the rest is obvious.
I want to display these items with a basic template:
subject by author at postDate
body
<hr />
When a user changes his/her username, the updated username will be shown on the news listing. This is the reason why I'm using a foreign key.
I've defined poster_id such that it can be set as NULL, meaning it was not created by a registered user, but a guest. Don't ask me why I'd want a guest to post a news item :PI think this is a fundamental mistake. A better design, IMO, would be to have an explicit GUEST or anonymous poster ID, but not null.
When it comes to getting the news posts from the database and resolving the poster_id to a username i just use a join. However, when poster_id is NULL i obviously don't get a username for that post but a NULL. The word "Guest" has to come in when the poster_id is null. So in my template you'd think i could just put a null check as I can't do it in sql (as far as i know anyway).See above.
Now, I'm using localization on the site and the word "Guest" is different depending on the locale. So you'd think i could just use a null check and a locale->get('guest_username') and that will return the word "Guest" in the right language.Localization should be a UI issue. It should be all sorted out by the time you get to the persistence layer.
If I want to view news on different pages, and more importantly, in different forms such as just author: subject, I come across a problem. I want to avoid having to repeat that null check code on every template that views news posts. Complicating things, I want anywhere that display a username to do the null check and return the locale'd guest username if it is a null.If it's hard to do, it's worth re-thinking. Don't use null when there are sensible non-null alternatives.
Where do I put this null check? The locale object is part of the model layer, because other model objects use it.
Is this the presentation or the model layer's responsibility? I am relatively new to this design patterns thing, but I'm getting there :) I've thought about using wrapping classes but I'm just not sure at this point and I need smart people's opinion :)L10N and I18N issues should be the responsibility of the presentation layer, IMO.
%

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.

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

Keys and Join description at physical layer does not reflect in BI Answer?

Hi All ,
While creating a RPD , the description about keys and join information using
description and hint property which we define at physical layer, those informations do not reflect BI Answer when i query to metadata dictionary.
Any ideas in this regard?
-- Ashish

Hi All ,
Here i give little bit more description what i did.
(1) I created a RPD and gave some description about Foreign Keys and using hint a gave some description about Physical joins.
(2) After then using utilities I generated the Metadata Dictionary.
(3) Now after restarting of services when i query to Metadata Dictionary using BI Answer , i am not able to see those descriptions. Rest of the information like table level and column level descriptions i am able to see.
Is there any way to get these descriptions or metadata dictionary does not keep descriptions for keys and joins?
Any ideas in this regard??
--Ashish

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)

Left outer join usage in obiee BMM layer

Hi All,
We lately started using left outer join in our bmm layer , to meet the requirement expectation .
problem : We have two tables Fact A , Dim B . There is an join int_id column to join them . Problem is... in table Dim B , we have 3 millions rows of Int_id and in fact table it is loaded for only data available(1 million rows).
Due to this we are dropping rows in the report ..as it is only getting data where fact.int_id = dim.int_id. So we used left outer join to solve to one particular report .(we know we can do ETl to load dummy int_id and make it null , but it is huge effort ..so we did left outer join)
These days , same kind of reports are in requirement . if i keep on doing same left outer join to meet the requirement in BMM layer ? is there any disadvantages due to this ? any performance degrade due to this ? please throw few lines on left outer join and its usage ?
Thanks,
Sri

Remodel your tables that might be a partition or any other way and follow in BI as per your new model.
Simply: Go for ETL kind of solution

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.

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

Link Join Concept In Physical and Business Model Layer

Hi,
As we know that we could make join relationship in physical layer and also business model layer in obiee 10g. This is what makes me confuse.
First of all, I tried to follow the tutorial in the oracle learning library center with schema SH as an example.
In the beginning, it is stated that we must make join relationship first in physical layer for all imported tables which are consist of dimension tables and fact tables.
Then, in the business model layer, the tutorial said that we must also make join relationship for the logical dimension table and logical fact table.
So, what's the purpose actually we must make join relationship in business model layer ?
All objects in business model layer are actually mapped from physical layer. So automatically the relationship in business model layer should be available automatically as they are mapped from physical layer.
Maybe for you guys who know the concept well about this difference of relationship, could tell me so I could get the idea of what it is actually about.
Thanks

Physical layer does represent datamodel joins as is in almost all cases.
Federated queries are a best example why joins are implemented in both (Physical & BMM layer) places.
Business model mapping layer is modelled according to your business requirements.
This is where your model MUST be a simple star schema, also where you model your hierarchies based on logical tables in bmm layer, & do appropriate aggregate navigation.
Hope the view points presented will put you in right direction.
mark answers promptly.
-bifacts
http://www.obinotes.com
J
Edited by: bifacts on Dec 16, 2010 9:19 PM

Left Outer Join in BMM layer

Hi All,
while building the RPD we have to use the join as Left outer join for two tables , we added join condition in BMM layer like evey table we have three tabs like General,Column Maooing and Content.
In General tab we have to sections like map to these tabls and Joins right. In the Join Scetion we add join conditions for two tables as left outer join.
Now i need to move the first table as second table and wise versa , how i can?? move these two tables
Thanks for your help.

Hi User,
You will have to remove and add the table as there is no option to reorder the tables.
Rgds,
Dpka

Joins in BI Administration layer

Similar Messages

Maybe you are looking for