Logical table source in BMM

Hello,
I am using obiee 11g.
I have few doubts In RPD with respect to logical table Source.
Consider i have tableA,tableB,tableC in PL.
Now in my BMM i dragged tableA now i want one column from the tableB.
So which method is correct?
1>
Go to the logical table source properties of tableA->then there + sign click and then add tableB left outer join with tableA.
Here in the logical table source we see only one table tableA.
2> Drag the tableB column so that we have 2 logical table source.
Now what i am more interested is which method is selected on what basis?
Any help?
Thanks

Thanks a lot for the reply
Second case can u just elaborate more.
First case i think i understood.
My main confusion is ok ill explain my situation.
I have tableA,TableB,TableC all are connected.
Now i have one fact table.In that fact table i would like to create 10 measures.5 From tableA,3 from tableB and 2 from tableC.
So
First i created 5 measures from tableA.
Second i created 3 measures from tableB.
Third i created 2 measures from tableC.
Till now i have 3 logical table source sources in one LTS.
Now in my report when i combine columns from tableA and tableB , tableB column shows no data.
When i see in the sql i see tableB col is not taken itself.
Then i need to go to tableB,then go to General tab and then click + sign add tableA and then go to column mapping and map atleast one col of tableA here.
So on what basis here i should do mapping.
Since i have 3 logical table source sources in one LTS.Each time i click on sources->tableB->i could see even the
tableA columns but not mapped?
Is that every column from tableA should be mapped to tableB and tableB to tableC and tableC to tableA?I mean in the column mapping
This is something which i am feeling very difficult to understand?
Pls help me out?
Thanks

Similar Messages

Multiple Logical Table Sources In BMM Under 1 Logical Table In OBIEE 11g

I have a question and even after doing a lot of search on google i could not find any article so through to ask you :-
I want to create a Logical Dimension table
This logical dimension has columns coming from 2 different physical tables, TableA and TableB. The relationship between TableA to TableB is 1 to zero.
There are 2 ways to create the logical dimension :-
1) Go to the logical table source properties of TableA-->then there + sign click and then add TableB right outer join with tableA.
Here in the logical table source we see only one table tableA.
2) Drag the tableB column so that we have 2 logical table source.
Please try this to explain without using the concept of fragmentation and without considering the fact tables. I have this question for simple logical dimension tables only.
I wanted to know which is the right way and what requirement/factor decides what to do ?

Check this post
Business Model - Logical Table Source
Let me know for Qs.
If helps mark as correct :)

Union of more than 2 fragments/Logical Table Sources in BMM Layer

Hi,
I have come across many blogs which explain how to union two fragments/physical tables in a logical table source.
Currently, i have a requirement where i have to combine/union 4 fragments/physical tables in a logical table source, say T1, T2, T3, T4 dimension tables.
All have the same table structure, but differ in data.
The requirement is to define dashboard prompt on the union of these tables and populate the values from all the tables.
I am able to union two of the tables using a '>' and a '<' condition on a key column.
But, am not able to union the other two tables.
If i try to put more than 2 LTS, then the union fails.
Please share your thoughts.
thanks,
Varun

Hi Varun,
What do you mean by the Union fails?
You can have a logical table source in your business layer with 4 different tables as a source.
Import the tables in the physical layer and create your joins.
Then create a logical table in the Business layer and go in the table properties you will see that you can add as much tables as you want into the source (Map to these tables).there you can add all of your 4 tables and specify what type of join you want to have between them (inner, outer...)
Regards
Adil

Dragging the columns to existing logical table source.....

Hi,
I am just learning OBIEE 11g and I am using a turorial from oracle it is
"Creating a Repository Using the Oracle BI 11g Administration Tool" for practice purpose.
In this tutorial it is saying that drag that columns from phscial layer to Logica Table Source
in BMM Layer to avoid creating a second logical table source.. But when I am trying to drag the columns to
existing logical source it is disabling I mean which it is not allowing .. is there any other technique to
do it... or Am i wrongly approaching.. .The below is brief description in the
tutorial.
"Drag all six columns from D50 Sales Rep in the Physical layer to D5 Sales Rep in the BMM layer. This action
creates logical columns and adds a D50 Sales Rep logical table source to D5 Sales Rep.
Rename the D50 Sales Rep logical table source to LTS1 Sales Rep.
In the Physical layer, expand D52 Sales Rep Position.
Drag POSTN_DESC and POSTN_LEVEL from D52 Sales Rep Position to LTS1 Sales Rep. Note that you are
dragging the columns to the logical table source, not the logical table. Dragging to the logical table would create a
second logical table source.
Drag DISTANCE from D51 Sales Rep Parent Child to LTS1 Sales Rep. Again, you drag the column to the logical
table source, not the logical table."
help would be appreciated.
Thanks and Regards,
Sri_Oracle.

Hi Sri,
When you are dragging a physical column onto an existing Logical table source and if it does not let you do so, then it means that there is no physical join between the existing physical table(which the logical source is pointing to already) and new physical table (from which you are dragging the column now). So, please make sure, you have the join in place.
Hope this helps.
Thank you,
Dhar

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?

Dynamically change the Priority Group of Logical Table Sources in OBIEE 11g

Hi All,
I have 2 Logical Table Sources(LTS 1 and LTS 2 for a Logical Table in BMM Layer).
Example: Logical Table : Sample
LTS Source 1 : Sample 1(Priority Group Set to 1)
LTS Source 2 : Sample 2(Priority Group Set to 0)
I have set the Priority Group of Sample 1 LTS Source to 1 and Priority Group of Sample 2 LTS Source to 0.
I need to dynamically change the Priority Group of Sample 1 LTS Source to 0 if my role is DEVELOPER where role is a column in database.
If my role is not equal to DEVELOPER then the Priority Group of Sample 1 LTS Source will remain same(1).
Please suggest how can i achieve this.
Thanks,
Soukath Ali

hello Soukath Ali,
didi you find a way to dinamically changing Priority Group?
thanks,
Maria Teresa Marchetti

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

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

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

Code:10058. Incorrectly defined logical table source

Hi experts
I need to create Business model for which i have two fact tables in physical layer and both are connected to each other and one time dimension which is shared by both fact tables in physical layer and one dimension which is connected to fact2 that contain hierarchy. i want to create one fact table in BMM layer which should contain measures from both fact table......
How to achieve this, any help on this..
thanks & regards
Edited by: ObieeUser on 06-May-2010 02:58
Edited by: ObieeUser on 06-May-2010 03:00

hi
Go through this forum thread
OBIEE: Incorrectly defined logical table source doesn't contain mapping
try this steps
Goto Business Model and Mapping Layer. There Fact table is present expend that fact table. You will find Sources option expend that sources option. In that option you will find sone table name that is present in Physical layer.Get the property of first table and there you can see in General tab in downward ADD option is there. click on ADD option new window is open and there three part is . right down contains some table select table from that table which we are joining and then click on select option. Now that table will added. you can change join type also. By default it is inner join. now refresh you page.
i hope this will help you
thanks & regards

NQSError: 10058 Incorrectly defined logical table source

Hi All,
i am trying to join two facts using a dimension. If i run report having one column from dimension & one from fact it works. But when i run a report having 1 column from first fact & 2nd column from second fact i get the below error.
I am sure this has something to do with the content tab under sources in BMM later.
But can anyone me what exactly i need to do.
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 DWH_PA_MBR_PA_TMP_NEW) does not contain mapping for [DWH_PA_MBR_PA_TMPT_NEW.PERIOD_CODE]. (HY000)
SQL Issued: SELECT DWH_PA_MBR_PA_TMPT_NEW.PERIOD_CODE saw_0, DWH_PA_MBR_PA_TMP_NEW.CURRENCY_ID saw_1 FROM DWH ORDER BY saw_0, saw_1
Thanks,
Pankaj

yes i have the following
Facts
1) DWH_PA_MBR_PA_TMP_NEW
2) DWH_PA_MBR_PA_TMPT_NEW
Dim
1) PA_PERIODS_ALL
Join 1) PA_PERIODS_ALL.PERIOD_NAME = DWH_PA_MBR_PA_TMPT_NEW.PERIOD_NAME
Join 2) PA_PERIODS_ALL.PERIOD_NAME = DWH_PA_MBR_PA_TMP_NEW.PERIOD_NAME
When i run report with columns from Fact 1 & Fact 2 i get the error.
else if i run report with column from Fact 1 & Dim it works fine.
Note: here Period Name is the key.
I guess we need to define the LTS, colmn mappings.
Thanks,
Pankaj

Incorrectly defined logical table source in rpd

Hi
I'm very new to rpd building and started with the below model
F1 >----D1------<F2
Fact 1 is joined to Dim 1 and the same Dim 1 is joined to Fact 2. With this model in physical & BMM Layer I built rpd and deployed.
In answers I picked 1 column from each of these three tables and getting the below 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 FACT_SALES) does not contain mapping for [DIM_LOCATION.LOC_NAME]. (HY000)
Seems, I'm missing some basic rule in building rpd, any help will be great.

Hi,
Just check the mapping between the fact_sales and Dimension table.
the error explaining about the mapping error only.
Just check the datatype compability too.
Regards
VG

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...

Business Model - Logical Table Source

Can someone give me clarification on exactly when you would follow scenario 1 when modelling a logical table and exactly when you would follow scenario 2, and what the key difference in behaviour between the two is. It would help if someone could illustrate with sql table joins equivalent.
Scenario 1
You drag a second physical table's column onto the logical table. This causes an additional field to appear in that logical tables list of columns sourced from a different table to the original and causes a second table to appear under the original table in the source folder.
Scenario 2
You drag a second physical table onto the existing logical table source of a logical table. The physical table source appears on the surface the same as before, but when you examine its properties you see that the second table has been joined to it.
Thanks for your input,
Robert.

Hi Robert,
This is quite an interesting question, I would say :). As per me, here is why
As you know already, BI Server generates intelligent queries based on our logical mappings in the BMM layer and there is only one primary goal for our BI Server Engine, generating an optimistic physical query.
Scenario 1 : Two logical sources created.
Two logical sources mean, there are two different ways the logical table(or same logical column) could be arrived at.
Ex 1:
You have a model, where you have Sales numbers and 4 levels of product hierarchy (lowest P4 -> P3-> P2-> P1) with sales at productlevel4.
And, You have created aggregated tables for sales numbers at level2 of product dimension also.
So, in this case the same product dimension would have two logical table sources, just because Level 1 Product can be derived from Aggregated product dimension source at level2 or detailed product dimension source at level4. And, it is the BI Server which would determine from where it has to pick (Of course there are some other criteria to control it).
Ex2:
Here even sales numbers are available at different granularities viz product level2, product level4. So for sales logical fact, we end up creating two sources just because there are two completely different sources with different granularity.
Scenario 2 : Two columns created, but only one logical source with a join in it.
Say, in the above example you have a snowflake product manager dimension to the product dimension. So, when you pull Product Manager into your product dimension (collapsing snowflakes), you end up creating just one logical table source with an inner join of ProductManager dimension and product dimension because product manager could be arrived only by going through products.
So, if you have report on sales by product manager, you would see query with an inner join of sales fact to product and inner join(this is based on the join type you set in this logical source) of product to product manager.
Hope I was clear enough and this helps.
Thank you,
Dhar

How would multi Logical Table Source work?

Hi All,
I am facing a problem about multi Logical Table Source. Can I build a Business Model with a Logical Fact Table that have two Sources? Taking the below description as an example:
Table Name
Columns
Description
Fact
TIMECD(2013Q101, which join to Time.TIMECE), DATA
Fact_Aggr
TIMECD(2013Q1, which join to Time.PERQUARTER), DATA
Aggregate table for Fact and sum Monthly data to Quarterly
Time
TIMECD, YEAR, PERYEAR, QUARTER, PERQUARTER, MONTH, PERMONTH
I tried to create a BMM that contains two Fact Table in the same Logical Fact Table. But BIEE shows the DATA from Fact even if I drag PERQUARTER into the report.
The following is my question:
1. Can I have a Logical Fact Table that contains Fact and Fact_Aggr?
2. How will BIEE determine which DATA should be used?
Best Regards,
Martin

The basic rule for one LTS vs two is: If you use table A AND Table B together, then one LTS. If you use table A OR Table B, then 2 LTSs.
So when you have an aggregate fact table, you use either the Agg or the base fact, meaning you should have 2 LTSs. OBI understands how to use one or the other through a variety of rules, but the main piece of config you need to have is proper levels defined on each and every LTS's Content tab. In your example, you will need to make sure the grains of your aggregate and base fact table match the time dimension properly; thus normally you have a day table and a month table in the time dimension, each joining to the appropriate Fact LTS. If you join a month level aggregate to a day time table your results will be incorrect. OBI knows that month is higher in the hierarchy than day, so it will prefer to use the set of Month LTSs when it can.
Jeff M.

Logical table source in BMM

Similar Messages

Maybe you are looking for