Logical Table source source query

In OBIEE 10g we can have multiple logical table sources and we can also add multiple tables into a single logical table source(logical table source source). I wanted to know the difference between doing so and having multiple logical table sources for each logical source.
Hope I made myself clear.
Cheers
Rem

Hi Rem,
When data is duplicated across different physical tables add them as separate LTS with column mapping pointing to most economical sources. Specifying the most economical source is about the idea that a single column exists in more than one table, based on the column mappings BI server picks up those LTS's which could satisfy the request with minimal joins.
When the data is not duplicated add them in a single LTS source. When the physical sources are added in a single LTS, you have the flexibility of using outer joins. But specifying a join as outer join makes BI Server to include this source even if its not required otherwise when the join is inner, the sources will not be included if not required to satisfy the query.
Hope this helps.
Thanks!

Similar Messages

Question on Logical table Sources

Good day!
I would like to ask for your advice on an bottleneck I am experiencing in a repository implementation in Siebel/OBIEE.
I am to create a logical table which sources comes from two different tables(Physical table A and Physical table B).
I am trying to union the contents from table A and table B so I planned to use fragmentation content.
My problem is that there is no way to distinguish the difference between the records coming from physical table A and table B.
I created two logical tables sources and specified the same condition for both but the server would automatically choose the first one and would not include the records from the second logical table source.
Is there any other way I could combine the records from table A and table B in Business Model and Mapping layer?
Please, I would like to know your thoughts.
Thanks,
Ivan

Hi Ivan,
I dont think there is other way which is equable to fragmentation content functionality.
I would suggest to try with any column is not null or most satisfied condition so that both contents present in the query.
If helps pls mark

No Fact table Exists and [nQSError: 14070] Cannot find logical table source

Hi,
I have 3 tables A(fact),B(dim) and C(dim). there are some other dims. i am getting Errors here.
A is joined with B and B is joined with C .
1) In report if i pull columns from A and B its giving data. If i include C table Columns in the report i am getting Error like
No Fact table Exists.
2) If i pull the C table columns only in the Criteria i am getting error [nQSError: 14070] Cannot find logical table source
How can i resolve this.
Thanks

In Logical table B source properties general tab ->Click on Add button and add table C and pull required columns from Physical layer table C.
If helps mark for any issues let me know.
Edited by: Srini VEERAVALLI on Feb 13, 2013 6:42 AM

Filter on the same logical table source on two logical tables is not working properly

Hi,
In the RPD, assume that I have a physical table named Employee_fact, created an Alias called D0 Employee Fact
In the BMM I've two logical tables called Employee_fact_Type1 and Employee_fact_Type2
Each of these logical tables has the same Logical table source - D0 Employee
But in each logical table source, I've a filter in where clause
such as, for Employee_fact_Type1 employee_type = 'XXX'
for Employee_fact_Type2 employee_type='YYY'
These two facts are present in the same BMM and each of them are connected to two dimensions
such as
Dept_type1 <- Employee_fact_type_1 -> Tenure_type1
Dept_type2 <- Employee_fact_type_2 -> Tenure_type2
In analysis, When I query the columns from Dept_type1 and Tenure_type1, the database query generated shows the condition employee_type='YYY' instead of employee_type='XXX' .
But, adding the columns from Dept_Type1, Employee_fact_type_1, Tenure_type1 it shows proper filter.
I checked the relationships, presentation layer for the sources of presentation tables and everything looks good.
Can anybody tell me what goes wrong here?

did you set the content level as well?

Multiple Logical Table Sources vs Single Logical Table Source

OBIEE 11g. I am totally confused. Can someone help me with the following for me.
I have seen logical table sources being used in 2 ways. I have a 2 sources tables: CUSTOMER & ADDRESS. In physical layer these 2 tables are linked by CUSTOMER _ID in a 1:M relationship. i.e. A customer can have many addresses.
Scenario # 1: In BMM the two tables form a logical table called CUSTOMER with 2 different logical table sources which are CUSTOMER & ADDRESS.
Scenario # 2: In BMM the two tables form a logical table called CUSTOMER with 1 logical table source called CUSTOMER only.
What is the difference between the above 2 scenarios and which one is better to use when creating the logical table source.
Regards.

Scenario # 1: In BMM the two tables form a logical table called CUSTOMER with 2 different logical table sources which are CUSTOMER & ADDRESS.
-->In this case; based on the columns select source is defined in the physical query
possible case would be CUSTOMER , ADDRESS, and CUSTOMER & ADDRESS
-->Used in DE-normalized scenarios
--> BI uses intelligence based on content tab settings
Scenario # 2: In BMM the two tables form a logical table called CUSTOMER with 1 logical table source called CUSTOMER only.
-->In this case; CUSTOMER properties->General tab used both CUSTOMER & ADDRESS, in your physical query both tables present irrespective of column selection
-->Used in normalized scenarios
-->Forcing BI to follow our way, since we wont set content tab settings
Hope this helps

Logical table having more than one Logical table sources

Hi ,
Is it possible a logical table has 2 logical table sources and there is no join between the underlying table of logical table sources?
What will happen if we create the request which contains one attribute from each source?
Will BI server return records with Cartesian join?
Is it mandatory if logical table is having more than one logical table sources(exp. Logical table sources are X,Y and underlying table is A,B respectively),
The underlying tables (A&B) must be joined ?
Can someone explain the logic behind the logical table sources? How does it work?
Any reference of document will be appreciable.
Thanks,Ashish

Hi Stijn,
Thanks for response.
You are saying that Oracle BI server will run a query against both tables and combine the results. But if there is no possibilty of any type of join, how BI server will combine the results from both tables.
I have a scenario like below -
Suppose i have 2 tables A and B at physical layer. Both table contains the information of any common subject area.
But there is no attribute is common between A and B so not any kind of join possible between two.
Now if i create a logical table with 2 logical table source A and B and create any request having one column from A and one from B ,
What will happen? How BI server will combine the result? Will BI server not result records after Cartesian join.
How can i model this scenario?

Confused about logical table source

Hi,
I'm confused about logical table source(LTS), there are 'General', 'Column Mapping', 'Content' tabs in
LTS, in General tab ,there are some information,like 'Map to there tables' and 'joins',
just here, we have created relationships in physical layer and BMM layer, so I would like to ask what's the use of the 'joins' here?

Hi Alpha,
Valid query, when you establish a complex join it is always between a logical fact and dimension table.Consider a scenario,
Example:w_person_dx is an extension table not directly joined to a fact but joins to a dimension w_person_d.
When you model the person_d tables in BMM, you ll have a single logical table with w_person_d as source.If you have to pull columns from both w_person_d and w_person_dx tables in a report, you add dx table as inner join to persond table in the general tab.Now when you check your physical query, you can see the inner join fired between the two dimensions.
Rgds,
Dpka

Question related to Logical table source

Hi All,
I have very basic questions -
(1) When do we create multiple logical table sources within a dimension?
(2) If a dimension has more than one logical table sources , when do we need to map the underlying table to other underlying table of logical table sources.
For exp consider these tables XLE_Entity_Profile, XLE_REgistration , AP_Invoice_ALL
AP_Invoice_All is a fact table. relationship between XLE_Entity_Profile & XLE_REgistration is (1:M).
Join info is as below -
(a) XLE_Entity_Profile.Legal_entity_id = AP_Invoice_ALL.Legal_entity_id
to get the registration of LE the where clause is as below-
(b) XLE_Entity_Profile..Legal_entity_id = XLE_REgistration.Source_id and XLE_REgistration.Source_table = 'XLE_Entity_Profile'
I have created the alias of XLE_REgistration as XLE_REgistration_LE.
With in a dimension , i have 2 logical table source - XLE_Entity_Profile & XLE_REgistration_LE.
logical table source 'XLE_REgistration_LE' has where clause 'XLE_REgistration.Source_table = 'XLE_Entity_Profile'
When i query , LE name , LE Registration Name, i get error like -
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14070] Cannot find logical table source coverage for logical columns: [LE_NAME]. Please check more detailed level keys are mapped correctly. (HY000)
Le Name is from XLE_Entity_Profile and LE Registration Name is from XLE_REgistration_LE.
But when using the properties of logical table source ' XLE_REgistration_LE' , i map it to 'XLE_Entity_Profile' ,i get the correct result.
I am not able to understand why am i getting error in first way of modeling.
Thanks , Ashish

Hi Ashish,
first about logical table sources (lts): you can create different lts for aggregation and/or fragmentation. Aggregation means that data is aggregated on another level among different physical tables. Fragmentation means that the content is different over different tables (other rows).
In your case, I think the problem is that your dimension is not denormalized, which results in a snowflake.
What I understand is that you have the following (physical diagram):
Invoice (fact table) >----- Entity (Dim) >----- Registration (Dim)
You have the following joins:
invoice.entity_id = entity.entity_id
and entity.entity_id = registration.source_id and registration.source = 'something'
First idea:
I would create the following join (in physical diagram):
Invoice (fact table) >---- Registration (Dim)
Where:
invoice.entity_id = registration.source_id and registration.source = 'something'.
Then in your Entity dimension you should create a hierarchy:
Grand Total Level
Entity
Registration.
In your dimension you should create the first lts: Entity
Set the aggregation content of this lts to Entity.
This lts contains only one physical table.
Map only the entity columns to the Entity physical table.
Then create the second lts:
Entity and Registration.
Set the aggregation content of this lts to Registration.
This lts must contain two physical tables, Entity and Registration.
Map the entity columns to the Entity physical table and the registration columns to the registration physical table.
Let me know if it works or not.
Regards,
Stijn

Financial Analytics -- Multiple logical table sources

we have two logical sources for Fact table. The two sources are Aggreates - one is at Invoice level and other one is at Supplier level. Each column in the fact is the derived column and is getting mapped to both the tables. My problem is when i use supplier name and invoice amount and other fact columns data , one of the fact column comes as Zero even though the back end query that BI server is firing is returning expected result. But some how when it comes on the report the data becomes zero. This doesnot happen when we specifically add a filter on the table at lower level of Aggregation (Invoice). This tells Bi server to fetch the data from table lower level of Aggregation .
The RPD that we are using is OOTB.

Scenario # 1: In BMM the two tables form a logical table called CUSTOMER with 2 different logical table sources which are CUSTOMER & ADDRESS.
-->In this case; based on the columns select source is defined in the physical query
possible case would be CUSTOMER , ADDRESS, and CUSTOMER & ADDRESS
-->Used in DE-normalized scenarios
--> BI uses intelligence based on content tab settings
Scenario # 2: In BMM the two tables form a logical table called CUSTOMER with 1 logical table source called CUSTOMER only.
-->In this case; CUSTOMER properties->General tab used both CUSTOMER & ADDRESS, in your physical query both tables present irrespective of column selection
-->Used in normalized scenarios
-->Forcing BI to follow our way, since we wont set content tab settings
Hope this helps

Cube Logical table source doesn't show all cube members

hi,
Please help me solve this issue.
I have a logical dimension table whcih has a source from 10 different LTS each of them is a cube and have different number of members in it
Cube 1 has 1 member say A.
Cube 2 has 1 member say A.
Cube 10 has 3 members say A,B,C.
When I bring the column of the logical dimension table into Answers, I see the output from only Cube 1 i.e. A and does not bring in from the other cubes 10 which has members A, B,C.
Same is vindicated from the MDX query.
Is there a soln for this.
Regards,
Bhavik

Alright Bhavik, the belwo soln works fine with Oracle DB and you can try this with Essbase source:
You need to set Fragmentation Content here...
1) Create a dummy logical column in the logical table and map this to all LTS with some static values for each say 'A', 'B' etc
2) Now in Fragmentation Content for each LTS set that column filter with the value given in mapping like "LTS"."CATEGORY" = 'A'
3) Check the checkbox for this source shud be combined with other sources.
Now when you will run ur report based on this it will pick from all LTS. Currently, its only picking and pointing to ur first LTS. What we will do is to force BI server to have data from all sources.
Hope this is useful

Handling Outer Join for hard coded values in the Logical Table Source

Has anyone tried to apply an outer join in the Logical Table Source Content Tab?
I have to add this APPLSYS.FND_LOOKUP_VALUES.LANGUAGE (+)= 'US' but the outer join is not allowed. I get this message.... [nQSError: 27002] Near <(>: Syntax error [nQSError: 26012] .
Could you tell me please how this should be handled? I have a lot of this cases in my project and without this being set-up affects the expected output of my report.
Thank you in advance.

hi Ap,
Pull only Dim_W_LOV_D_Acty_Src column into answers and check whether u r able to see CUST_SRC_ACT or not .Of course, you need to check sql query too
Thanks,
Saichand.v

Incorrectly defined Logical table source

Hi all,
I have two facts(F1& F2) and two confirmed dimensions(D1,D2) for the facts F1 and F2.
F1
F2:LTS1,LTS2
D1
D2
When I query columns from D1,D2,F1,F2 LTS1 result is coming
But, when I query from D1,D2,F1,F2 LTS2 it is throwing incorrectly defined logical table sources.
Please help me in understanding this error

Here's what the OP wrote:
Hi all,
I have two facts(F1& F2) and two confirmed dimensions(D1,D2) for the facts F1 and F2.
Granted, people seem to insist on saying "confirmed" instead of "conformed" (ref. http://www.kimballgroup.com/data-warehouse-business-intelligence-resources/kimball-techniques/dimensional-modeling-techn…) but he's clearly asking for a perfectly normal and standard situation of two facts with two conformed dimensions.

Repos - logical table source does not contain mapping

Hi,
I have a repository question?
I do not have a fact table in my physical layer. Do I have to have one? I thought the fact table got created in the BM.
I do have a date table in the physical layer, but it isn't joined to any other table.
I added the PK from the date_dimention to my logical fact table.
when I open the properities of my logical date table it is mapped to the physical date table.
Now in answers, I can query the date_dimension without error.
But, when I query the fact table using the date key, I get this error.
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table CRTK_FACTS) does not contain mapping for [CRTK_FACTS.MASTER_AI_ID, CRTK_FACTS.INT_DOC_ID, CRTK_FACTS.DATE_KEY]. (HY000)
SQL Issued: SELECT CRTK_FACTS.MASTER_AI_ID saw_0, CRTK_FACTS.INT_DOC_ID saw_1, CRTK_FACTS.DATE_KEY saw_2 FROM CRTK ORDER BY saw_0, saw_1, saw_2
Anyone have any suggestions on what I am missing?
thanks,
Kathy

I don't have a fact table in the physical layer. Do you mean join between the date table and other dimension tables?
or do I have to build the fact table in the physical layer?
I have not built any hierarchies yet, working on it.

Logical table source

Hello!
Can someone please explain difference between dragging and dropping a physical column from a table in Physical Layer to a Logical Table in BMM layer and ragging and dropping a physical column from a table in Physical Layer to a Logical Table Source? When to use these two options?
Thanks,
-D

Hi,
First you have to read the OBIEE Administrator concept and will clear you doubt,
OBIEE Administrator, Windows based client tool to develop and manage Metadata repository. Repository changes can be done in either online or offline mode.
Online mode is when BI Server is actively reading the repository file (when a user is logged in).
Offline is when BI Server is idle. Best practice is to develop in Offline mode.
Minor changes can be made when in online mode. Administrator uses ODBC connectivity to connect to physical data sources, uses Native Drivers for Oracle and DB2.
OBIEE defines three layers of abstraction.
Physical Layer – connections to physical data sources (OLTP, OLAP, Flat Files, Oracle, SQL*Server, Teradata, etc.).
Business Model Layer – Brings together data elements from Physical sources into a logical Star-Schema representation. This is where business rules and definitions are setup.
Presentation Layer – An abstraction from the Business Model, defines exactly how users will see tables and fields.
Connection Pool is a connection to a Physical data source. Multiple connection pools can be created to the same source to improve end-user query performance.
All tables in the Physical layer must have a Primary Key column. Column properties can be edited to set the Primary Key. Physical joins need to be established between tables, using Foreign Keys and Primary Keys. Right-click on Connection pool to create the Physical diagram joins.
A Business Model can be created by drag and drop of objects from the Physical Layer. It’s a logical Star-Schema representation of the Physical objects. Tables from different sources can be merged to form one Logical table. These sources are called Logical Table Sources.
Logical Fact tables hold Metrics; every Metric must have an aggregation rule. Hierarchies can be setup on dimensions for drilldown functionality.
It is important to join logical Facts and Dimensions together, much like the Physical Diagram. Right-click on Model, click Business Model Diagram to create joins. Use Complex joins in the Business Model.
Presentation Layer is exactly what End-Users will see in BI Answers, contains multiple Subject Areas that answer specific Business questions.
Thanks,
Balaa...

OBIEE: Incorrectly defined logical table source doesn't contain mapping

In OBIEE 10.1.3.2 I have a very simple thing but cannot get it to work. Hopefully someone can point out the mistake. I have the same schema on two different database that I want to compare data.
The schema is simple. Table (dimension) A has two columns: id and name. Table (Fact) B has two columns: id and value. Table B.id is a foreign key to A. I imported two database schema into the physical layer and for each database, I built the foreign key relationship between table A and B. In the logical layer, I have two logic tables, one to represent A (Dimension) and the other B (Fact) with a logical join. Each logical table has two data sources. For the dimension tables, both id and name columns have two sources. For the fact table, the id has two sources and for the value, I created two separate columns, one called value1 and the other value2 with one from one database's B table's value column and the other from another database's B table's value. They then were made available at presentation layer.
Now in the Anwser, I can build a query with id from dimension and value1 from fact; it displayed fine. Same with a query with id from dimension and value2 from fact, it displayed fine. However, if the query is id, value1 and value2, I got the following error
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table B) does not contain mapping for [B.value1 [ ] , B.value2 [ ] ]. (HY000)
Is there something I have to do additional to make both values appearing the same time.?
Thanks for your help
Ralph

Hi, Siddhartha P
I don't think I understand your information. I couldn't find connection pool at the business mapping layer. I only see it in the physical layer. Do you mean to do the mapping at the logical source table? That's only places I see any mappings and I don't see complex join there (only inner join, left outer, right outer and full outer) What mappings should I need to create between table B (fact table) of database 1 and table B (fact table) of database 2. I thought they don't have any relationship other than join through a dimension table which has columns that map to both table A (dimension table) of database 1 and 2. Then the logical fact table has 3 columns, one is id (to join to Dimension table) with two mappings (one to table B of database 1 and one to table B of database 2) and one column value1 which maps only to table B's value of database 1 and another column value2 maps to table B's value of database 2. That seems to be done correctly because I can pick column id and value1 or column id and value2 and have them displayed correctly but not all 3. I thought if it can display the two separately correctly, they should be able to display all 3. no?
I am not getting any inconsistency error.
There must be something I still don't understand. If you don't mind give me a little more direction, that would be great.
Thanks
Ralph

Logical Table source source query

Similar Messages

Maybe you are looking for