Joins in LTS??

Hi all,
can any one help me what is the difference between joins at LTS(general tab) and type of joins when we creating complex join between two tables??
thanks in advance.

Hi,
In addition to the above, in the general tab, when you click on the add button. Then you can see all the tables which you have joined in the physical layer.
And after you add it in the general tab, it appears in the 'Joins' below.
Supposing you have a fact table and you have joined with dimension in the physical layer, then in the fact source when you add, dimension table will be showcased to you.
Select the dimension, and you see the joins with the fact and the dimension appearing by default in the 'Joins' section. And default of 'inner joins'.
This indicates that whenever you are pulling columns from the fact table then the joins with the dimension and fact appears (if you have enabled the 'tick' mark in the 'Joins' sections.
So, if you think you need default joins to happen when the fact columns is pulled then you can enable the joins in the 'Joins' section with fact and dimension. (For example, security purpose, user will always want the joins to appear with a particular fact and dimension).
Or else it will make the join only when the dimension is applied to the fact(joins will be taken according to the physical layer).
Different Joins are
1.Inner
2.Left Outer
3.Right Outer
4.Full Outer
And these joins is fully dependent on the requirement. By default its, inner join.
Hope this clarified all your doubts.
Regards
MuRam

Similar Messages

Forced inner join in LTS

Hi All,
can u plz explain the concept of forced inner join,like why it is used?,in which context it is usefull?
Thanks in Advnc
Aravind

And also it's useful to model snow flake schemas. Business Model and Mapping Layer must be a star schema, so, we use LTS to transform the real snow flake schema to star schema of BMML. For example, imagine you have an dimensions tables about customers information that are all togheter the customer dimension. When you build the BMML, you need to group all that tables in one, because the model must be a star schema. Then , you must use inner join in LTS to group in one all tables of real (physical) snow-flake schema.
Regards.

Defining Joins in LTS

I am working on a Snowflake Schema. I imported the tables and defined fk joins as per the underlying database. In the BMM layer, I created a logical dimension table that have 3 LTSs. I double click on 1st LTS and define join as inner join with the 2nd LTS, for 2nd LTS I defined inner join with the 3rd LTS.
When I try to create a report that have columns from 2nd/3rd LTS, I am not getting any result. I use the query from querylog and run in toad without any results either.
I am not able to understand the problem. Am I defining the joins correctly?
thanks,
ashish

Asish,
Yes you defined joins appropriately. Check if there is any matching data existing between the tables through TOAD.
mark answers promptly.
J
-bifacts
http://www.obinotes.com
Edited by: bifacts on Nov 15, 2010 9:30 AM

2 table sources in LTS but only 1 in query?

Hi,
I am using obiee 10g.
I have one DIM_A table with some data. DIM_A table is 'SELECT' type on physical layer and data in this table are filtered. I am using ValueOf(NQ_SESSION.USER) variable to filter data in this DIM_A table. Every user can see different data in this table.
In FACT_A table are data for every user so I need to always filter data in FACT_A using values in DIM_A table.
I have properly join in physical layer.
In BMM I have both tables. Every with only one logical table source. I added DIM_A as second "mandatory" source to existing FACT_A table source. So I can see 2 records at general tab of FACT_A table source and also inner join between them.
But when I make query only on FACT_A without dimension, or with some other dimension, DIM_A is not present in generated select so user can see data which are not for him.
I need to make MANDATORY join between FACT_A and DIM_A everytime.
Can you tell me how to simulate mandatory join between these two tables?

I am able to make "mandatory" join between DIM_A and FACT_A table using mentoned filter in security.
So I don't need to add username to BMM tables and I don't want to complicate it...
Thank you.
I would like to ask you on my second question...
"I thought that multiple sources in LTS should have same effect. I saw it somewhere... Now I need to make join as part of mentioned security filter, but I think that inner join in LTS shoul also work..."
Here is explained what I want:
Multiple Sources in BMM Layer
When you add multiple physical tables to one logical source then all these tables will be called when the OBIEE server creates the SQL to send to the database. For instance let's say you have one logical table called "Dim - Account" with one logical source "Dim_W_ORG_D" and this logical source is made up of the physical tables W_ORG_D and W_ORG_DX. When you create a report using this dimension the SQL will always join the two tables together and select from them both. If you have two seperate logical tables for W_ORG_D and W_ORG_DX then these tables will only be included in the SQL when you select a columns from each of those two tables.
I have multiple physical sources for one logical source. Physical sources are joined together. I can see join also in logical table source. But If i make query from this logical table in generated select is only one physical table which is not joined to another one.

Re: Working with Confirmed and Non Confirmed Dimensions

I want to make a report with columns from Lot_D, Lot_Grade_D dimensions and measures from Lot_Quantity_F and Stock_F facts, did the following steps but unable to get the required result
- two facts Stock_F and Lot_Quantity_F, Lot_D dimension is conformed whereas Lot_Grade_D is connected with Lot_Quantity_F only.
- made the joins on physical layer between Stock_F and Lot_D and than among Lot_Quantity_F, Lot_D and Lot_Grade_D.
- dragged all the four objects in BMM (now four BMM objects with relevant source in physical)
- created level-based hierarchies for Lot_D and Lot_Grade_D in BMM
- set the Stock_F measure column under Levels tab to Total level for Lot_Grade_D dimension
- set the Logical Level in the Content tab of Stock_F to Detail level for Lot_D dimension
- set the Logical Level in the Content tab of Lot_Quantity_F to Detail level for Lot_D and Lot_Grade_D dimensions
- dragged all the BMM objects in presentation layer
created the report based on flat dimensions (not Hierarchical dimensions)
Looking for a quick response
regards
Farooq

Follow The Below Steps
1) Add the Stcok_F and LOT_Q_F as LTS in BMM .
2) Join this LTS to both the dimensnons Lot_d and Lot_Grade_D
3)Open the Stock_F in LTS and go to Content tab.Set the Lot_Grade_d to total and Lot_d to Detail
4)Open the LOT_Q_F LTS and set the levels to detail.
5)Open the Individual columns coming from Stock_F and set the level for lot_grade_d to Detail.

Incorrectly defined logical table source (for fact table Facts) does not

Hi,
I have two Dimensions A and B. A is joined to B by a foreign Key.
The report works if I pull B. Column1, A.Column2.
The report is throwing an error if i try to change the order of the columns like this. A.Column2, B. Column1.
error : Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
File: odbcstatementimpl.cpp, Line: 186
State: S1000. Code: 10058. [NQODBC] [SQL_STATE: S1000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Facts) does not contain mapping for B.Column1
I am not sure where it is going wrong.
Thanks
jagadeesh
Edited by: Jagadeesh Kasu on Jun 16, 2009 4:22 PM

did you make joins in LTS or on the physical table.
try to make join in LTS if they are not there.

Outer Join with Where Clause in LTS

HI all,
I have a requirement like this in ANSI SQL:
select p1.product_id, p1.product_name, p2.product_group
from product p1 left outer join product_group p2 on p1.product_id = p2.product_id
and p2.product_group = 'NEW'
In Regular SQL:
select p1.product_id, p1.product_name, p2.product_group
from product p1, product_group p2
WHERE p1.product_id *= p2.product_id and p2.product_group = 'NEW'
In OBIEE, I am using a left outer join between these two in Logical table Source, and also, Gave
p2.product_group = 'NEW' in WHERE clause of LTS.
This doesn't seem to solve purpose.
Do you have any idea how to convert WHERE clause in physical query that OBIEE is generating to something like
product p1 left outer join product_group p2 on p1.product_id = p2.product_id AND p2.product_group = 'NEW'
I am using Version 10.1.3.4.1
Creating an Opaque view would be my last option though.

Hello
I have read your post and the responses as well. and I understand that you have issues with the Outer Join with where Clause in LTS.
Try this solution which worked for me (using your example ) -
1. In the Physical Layer created a Complex join between PRODUCT and PRODUCT_GROUP tables and use this join relationship :
PRODUCT.PROD_ID = PRODUCT_GROUP.PROD_ID AND PRODUCT_GROUP.GROUP_NAME = 'MECHANICAL'
2. In the General Tab of PRODUCT table LTS add PRODUCT_GROUP table and select Join Type as Left Outer Join.
3. Check Consistency and make sure there are no errors .
when you run a request you should see the following query generated -
select distinct T26908.PROD_ID as c1,
     T26908.PROD_NAME as c2,
     T26912.GROUP_NAME as c3
from
     PRODUCT T26908 left outer join PRODUCT_GROUP T26912 On T26908.PROD_ID = T26912.PROD_ID and T26912.GROUP_NAME = 'MECHANICAL'
order by c1, c2, c3
Hope this works for you. If it does please mark this response as 'Correct' .
Good Luck.

Difference between joins that we mention in LTS and the one in Business dia

Hi Gurus,
Can anyone please share the exact difference between the joins in the LTS of logical table and the one that we use in business diagram.
Let me put this clearly.
1.we can map a logical table source with other physical tables and mention the type of join to be used. when this approach should be used.
2.We can also mention the type of join between the 2 logical tables while defining a join between 2 logical tables. when this should be used.
Thanks in advance.........

Hi,
1.we can map a logical table source with other physical tables and mention the type of join to be used. when this approach should be used.
--Whenever you need to take the joins with the physical layer tables along with the logical table that is hit, we add the physical tables that is joined in the physical layer and make inner or other joins accordingly. Default the tick will be there, but when you are overriding the physical layer joins of the tables in the content tab 'where clause' then you need to remove the tick and allow it to take the joins/conditions specified in the 'where clause'.
2.We can also mention the type of join between the 2 logical tables while defining a join between 2 logical tables. when this should be used.
--These joins tells the OBI server to make the optimum joins while requesting for the request and tells about the cardinalities to join.
Hope this solves your problems
Regards
MuRam

Join two fact tables

Hi,
I have two fact tables F1 and F2 joined with few dimensions D1.....D9. D1,D2 and D3 are conformed dimensions.
In Physical:
F1>--D1,D2,D3,D4,D5,D6
F2>--D1,D2,D3,D7,D8,D9
In Logical:
F1>--D1,D2,D3,D4,D5,D6
F2>--D1,D2,D3,D7,D8,D9
there are some ports already using above star schemas. now I got new requirements and I need to use measures from both the fact tables and conformed and unconformed dimensions.
I did the following in logical
F1 LTS GENERAL TAB ADDED F2,D1,D2,D3,D7,D8,D9 and in content tab set logical level to unconformed dimensions at total level and for conformed dimensios at details level.
F2 LTS GENERAL TAB ADDED F1,D1,D2,D3,D7,D8,D9 and in content tab set logical level to unconformed dimensions at total level and for conformed dimensios at details level.
but I'm still getting
[nQSError: 14026] Unable to navigate requested expression:
Please fix the metadata consistency warnings. (HY000)
I cheked metadata global consistency and no errors found.
Appreciate your help
Thanks
Jay.
Edited by: Jay on Sep 27, 2011 10:14 AM
Edited by: Jay on Sep 27, 2011 10:15 AM

Let me explain my issue again
In Physical:
F1>--D1,D2,D3,D4,D5,D6
F2>--D1,D7
In Logical: Single logical fact Fact_FY_Ratio has two logical sources
LTS1: F1>--D1,D2,D3,D4,D5,D6
LTS2: F2>--D1,D7
Set the content level for each LTS in Fact_FY_Ratio:
F1 to Detail for D1,D2,D3,D4,D5,D6 and to Total for D7
F2 to Detail for D1,D7 and to Total for D2,D3,D4,D5,D6
In LTS 1 general tab added inner joins with all dimensions F1,D1,D2,D3,D4,D5,D6,D7and F2
In LTS 2 general tab added inner joins with all dimensions F2,D1,D7,D2,D3,D4,D5,D6 and F1
And I also did logical complex join for Fact_FY_Ratio with all logical dimensions D1,D2,D3,D4,D5,D6,D7
I'm able to run query using D1,D2,D3,D4,D5,D7,F1,F2 but when I include D6(time dimension) it is causing problem with F2(witth F1 it is working fine).
query success with:
F1,D1,D2,D3,D4,D5,D6
F2,D1,D7
D1,D2,D3,D4,D5,D7,F1,F2
Query failed with:
F2>--D1,D7 and D6
Please let me know anything wrong with above configuration.
Thanks
Jay...
Edited by: Jay on Oct 3, 2011 7:11 AM

How to join Dimensions and Fact Tables in OBIEE

Hi All,
I need to create report which need to get the information from two fact tables and 7 dimensions. The granularity is not same in both the fact tables. One fact table is having common keys between all the dimension tables and second fact table have only two dimension keys but with different names. My requirement is to create the report by taking the measures from both the fact tables.
I have created joins between the second fact table and two dimension tables in physical and BMM layer and also set the highest level for all other dimension tables in the LTS of second fact table. when am creating report by taking the measures from both the fact tables, data is not getting for the measure which taken from the second fact table. Please advice me how to get the data for the measure which taken from the second fact table.
Thanks in Advancec !!

You have to use the level-base measure capabilities.
http://gerardnico.com/wiki/dat/obiee/bi_server/design/fact_table/level_based_measure_calculations
For all measures of the second fact table with the lowest grain (with two dimension keys), set for all dimension where you don't have any key the logical level to the "All" or "Total".
And UNSET the highest level of the LTS for the second fact table.
Success
Nico

BMM - Decision criteria on how to define LTS for a multi-source object

I am curious to know what others use as their decision criteria when determining how to setup a BMM logical table that has multiple sources that map to multiple columns in the logical table.
For example,
If you have defined logical table Dim - Customer in the BMM that has 4 fields:
Dim - Customer
Customer Id
Customer Name
Customer Address
Customer Phone
The sources for this logical table from the physical layer are:
CUSTOMER (all customers exist here)
CUSTOMER_ADDRESS (A customer may or may not have an address, but can have only one address to simplify this conversation)
CUSTOMER_PHONE (A customer may or may not have a phone, but can have only one phone to simplify this conversation)
Field Mappings from Logical Table to Physical Table are:
Dim - Customer
Customer Id - CUSTOMER
Customer Name - CUSTOMER
Customer Address - CUSTOMER_ADDRESS
Customer Phone - CUSTOMER_PHONE
How would you setup the logical table and LTS's for this object in the BMM knowing the following requirements?:
1. The Address and Phone tables should only be joined in when fields from those tables are used in a report/query.
2. Since a customer may or may not have an address or phone, the BMM table needs to be setup such that adding those fields into a query will not filter all customers that dont have data for those fields, i.e. display null if it does not exist.
My initial approach for resolving this would be to set it up as follows:
A single Logical Table Source: LTS_CUSTOMER
Three Tables added to the LTS:
CUSTOMER, CUSTOMER_ADDRESS, CUSTOMER_PHONE
Two joins defined for the three tables:
CUSTOMER - CUSTOMER_ADDRESS (LEFT OUTER JOIN)
CUSTOMER - CUSTOMER_PHONE (LEFT OUTER JOIN)
Issues/Questions:
- The problem I have run into is that any query that uses Customer Id or Customer Name still causes a join to the CUSTOMER_ADDRESS and CUSTOMER_PHONE table even though I didn't use a field from those tables. I assume this is because OBIEE things that any query to that Logical Table using that LTS has to query it as the LTS is defined (so all three tables are joined in)
- Is there a way around this? If so, is it to specify separate LTS tables for the Logical Table Dim - Customer? If you do this, then there is no way to specify a LEFT OUTER JOIN and the query will just default to what is specified in the Physical Layer as an inner join.
- Curious as to what peoples thoughts are in general for how to decide whether to specifiy multiple sources in a single LTS or just add multiple sources to the Logical Table and the decision criteria for going either way.
Thanks in advance.
K
Edited by: user_K on Jun 3, 2010 11:09 AM
Edited by: user_K on Jun 3, 2010 11:10 AM

Thanks a lot for the example, that fixed the problem.
I've been reading the NSAPI programmers guide several times now and I was under the impression that you should either use <object> or <client>, never thought about this approach. Now when I re-read it is makes sense, but wasn't very clear at first.
I think I'll e-mail Sun to suggest an addition of the <Object> tag in their <Client> tag example (http://docs.sun.com/source/817-6252/npgobjcn.html#wp1045056) to make things a little more clear.
Thanks again, now I can finally implement the final configuration settings and plan for the actual switch later this evening.

Issue with Multiple LTS for a fact table and filters

Hello,
I am facing an issue with obiee 10g.
In my model, I have a huge FACT table F1 (partitioned and indexed). The average response time for the queries, which targeted it, was ~30-60 seconds, which was not really convincing our end user.
So, we decided to create a materialized view, which removes some dimensions that are not used by default, but might be used if the end user adds some filters. I added the Materialized view in the Physical Layer and in the corresponding Logical Table Source.
I then tried to see if it works, but I was a bit surprised by the result. Indeed,
-> If the report does not reference a truncated dimension, it targets the materialized view. -> Perfect
-> If the report does reference a truncated dimension in the columns, it targets the Fact Table. -> Perfect
-> If the report does reference a truncated dimension in the Filters, it targets the materialized view. For this reason, the filter is never resolved and no join on the dimension table is applied, whereas it exists in logical SQL generated. -> Ko.
A suggestion could be to add the filters into the columns, but I am not satisfied by this response because it will never use the materialized view in that case.
An other suggestion could be to use query rewrite, but I 'd like to have the full control on the generation of the queries.
Does someone know if the filters are not evaluated to determine which LTS to use? How can I force this evaluation?
Regards,

Hi,
If I understand your description correctly, then your materialized view skips some dimensions (infrequent ones). However, when you reference these skipped dimensions in filters, the queries are hitting the materialized view and failing as these values do not exist. In this case, you could resolve it as follows
1. Create dimensional hierarchies for all dimensions.
2. In the fact table's logical sources set the content tabs properly. (Yes, I think this is it).
When you skipped some dimensions, the grain of the new fact source (the materialized view in this case) is changed. For example:
Say a fact is available with the keys for Product, Customer, Promotion dimensions. The grain for this is Product * Customer * Promotion
Say another fact is available with the keys for Product, Customer. The grain for this is Product * Customer (In fact, I would say it is Product * Customer * Promotion Total).
So in the second case, the grain of the table is changed. So setting appropriate content levels for these sources would automatically switch the sources.
So, I request you to try these settings and let me know if it works.
Thank you,
Dhar

How to use OUTER JOIN in Oracle Answers Filters?

Hi, I need to have a filter on an 'Oracle Answers' report.
The query from the NQQuery.log appears as below. (I have simplified the SELECT clause here for easy reading)
SELECT t692.enquiry_business_route AS c1,
t692.enquiry_id AS c11, t913.YEAR AS c12,
t913.full_date AS c13, t666.surname AS c14,
t666.post_code AS c15, t855.company_name AS c16,
t983.notes AS c30
FROM
mkt_dw_enev_enhi_dim t983,
mkt_dw_key_partner_dim t855,
mkt_dw_event_type_dim t821,
mkt_dw_customer_dim t666,
mkt_dw_time_dim t913,
mkt_dw_enquiry_event_fact t692
WHERE (
t692.enquiry_id = t983.enqu_id
AND t666.customer_dim_key = t692.customer_dim_key
AND t692.event_date_time_key = t913.time_dim_key
AND TRUNC(t983.event_date)= t913.FULL_DATE
AND t692.event_type = t821.event_type_dim_key
AND t692.key_partner_dim_key = t855.key_partner_dim_key
AND t821.event_type_category = 'RECEIVE_FEE'
AND t913.YEAR = 2009
and t692.enquiry_id = 535986
For the following two lines I would like to have the OUTER JOIN.
AND t692.event_type = t821.event_type_dim_key(+)
AND t821.event_type_category(+) = 'RECEIVE_FEE' (THIS IS THE FILTER CONDITION, AT THE MOMENT IT DOESN'T WORK WITH OUTER JOIN SYMBOL)
Please could you let me know the best way of achieving the above.
Thanks
Srikanth

In the BMM layer in the join condition you will be able to specify the join to be (left, right or full outer join).
You can even add the required table in the LTS(logical table source) and also specify a left, right or full outer join there as well.
There is an interesting work around as mentioned in the below blog to get to the Outer join results with out changing anything in rpd but in Answers.
http://obiee101.blogspot.com/2008/11/obiee-outerjoin-workaround.html
Hope it helps
Thanks
prash

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.

If Logical level mappings are blank in an LTS , what does it mean?

Hi All,
I was trying to find this out in the forum but couldn't.
In my LTS, on the content tab, if i don't specify any "Aggregation, group by" information for the dims associated with my Fact table and keep it blank, then what does it mean? Would OBIEE treat this as at the detail level by default? So to test this, I created a logical fact and for its LTS, i didn't associate any logical level for dimensions. The query didn't give me any error and worked fine by using the correct join details.
Also when do we associate an LTS with the Total Level for a dim, what's the use because as I understand, this means all our measures from that LTS would be calculated for the total level of the dim and we can do this by creating level based measure and associating it with the total level of the dim.
I'll be thankful if somebody could explain me this in detail or direct me to a relevant documentation/ blog
Thanks,
Ronny

Hi,
When you have only one logical Table Source(LTS).
You don't specify the logical levels. By default it would consider the detail level of the logical levels mapped to the fact table.
When you have Multiple logical Table Source(LTS).
The concept of Multiple LTS comes into picture when you have multiple sources. The BI server picks the optimum logical source depending upon the fields (columns) selected. And also depends on the Number of element set while creating the dimension hierarchies. Refer-http://gerardnico.com/wiki/dat/obiee/level_number_element
For example- Suppose you have two logical table source Fact 1 and Fact 2 and logical levels( dimension hierarchies are created for two dimensions Dim 1 and Dim 2).
For the first Fact 1 source logical level is mapped only with Dim 1 and Fact 2 is mapped to Dim 2.
(You need to decide which fact source to hit depending upon the dimensions used in the report.)
Then in the report when you select Dim 1 (by means of column selector/filters) then Fact 1 source will be hit and same appears in the query.
Then in the report when you select Dim 2 (by means of column selector/filters) then Fact 2 source will be hit and same appears in the query.
One more situation where you have mapped Fact 1 with Dim 1 First level of aggregation and Fact 2 with Dim 1 with Detailed level. Then the BI server picks depending upon the user's request. If the request data can be pulled from the detailed level ( which tends to be optimum then picks from the second source).
So, its always better to set the logical source and check the query, if its hitting the correct sources according to the requirements.
Regards,
MuRam

Joins in LTS??

Similar Messages

Maybe you are looking for