BIEE Answers: Problem with logical table source

Hi,
I am creating a detail report in answers. This report does not use any column from the fact table in the logical model, but uses other dimension tables.
In the logical model fact table, I use 3-4 times the same physical table as logical table source in order to filter results or not.
The problem is that my report filters results by using one of the logical table sources. Is there a way to specify in answers or administration which should be my "default" logical table source for the specific physical table joins?
Another workaround is to add as a filter on the report one of the columns from the fact table that do use the desired logical table source, but this is not always a workaround..
Can you please advise?
Thanks in advance,
Nadia

Remember to set the # Elements in your hierarchy to the appropriate ratio between levels, actual numbers not so important but the ratio needs to be correct for the BI Server to make the best guess if using more than one LTS.

Similar Messages

Problem: 1 physical table -- multiple logical table sources

Hi,
I'm quite new to BIEE and setting up my repository.
So I have a question, if the following scenario is possible:
Physical Layer: TABLE_A: COL_A, COL_B, COL_C
TABLE_B: COL_D, COL_E, COL_F
Join TABLE_A.COL_A = TABLE_B.COL_D
In Business Model I have a Dimension Table with TABLE_A as datasource with fields DIM1 (COL_B).
The Fact Table (MEASURE) would have twice TABLE_B as data source with different where-clauses on COL_F and logical table columns (ATT1 and ATT2) of value COL_E.
So far I have created everything and the consistency check shows no errors or warnings, but I get an error in Answer: Incorrectly defined logical table source (for fact table MEASURE) does not contain mapping for [MEASURE.ATT1, MEASURE.ATT2], when I creating an report showing DIM1, ATT1, ATT2.
Isn't it possible to have one physical column used as multiple data source?
I know it 's working, when I create the physical table twice ... but maybe there's a solution for business model.
Thanks
chrissy

Hi mengesh,
that's what I also tried, but it's always returning me the same error.
I know it would work, when I import the physical table twice or more, but that's not what I want to do, because at the end I have 10 or more fields based on this one physical table. There's one field indicating what value is contained in the record, this means:
COL_F | COL_E
1 | customer name
2 | customer number
3 | customer branche
4 | salesman
5 | date
6 | report number
etc.
I don't think it's usefull to import the physical table as often as I need this field. So I want to divide it in business model.
thanks
chrissy

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.

Max number of logical table sources

Hi,
I have one logical table based (a fact table) on 8 logical table sources. This is done to simulate some partitioning as my customer does not have an partition set up on data base level.
Anyway my challenge is that a request fired in answers does not seem to take all logical table sources into account when building the physical SQL.
The missing logical table source (the one not being part of the physical SQL) does not differ from the other logical table sources.
Is there a limit of how many logical table sources BIEE can handle under one logical table?
BIEE version: 10.1.3.4

Alastair,
thanks for replying.
The logical tables sources partition the data by year. The aggregation level is the same for all LTS, the check for using this with other sources at this level is set and I've tried to force a result from every LTS (not combined but each LTS for itself). Forcing the results is done by using a dashboard prompt in answers filtering on year.
The whole 'LTS-setup' works in combination with Oracle Warehouse Builder. What I mean by this is the following: In OWB I split the data from one table into 8 different tables, each containing 3 years of data (except for the oldest data where the number of years and amount of data will grow over time).
This is done by comparing values of a year column with the actual year. E.g. the most actual table would contain data for the years 2010 - 2008, the next would contain data for 2007 - 2005, and so on.
Now as the years in the different tables will change, I decided to establish an equaly changing counterpart in BIEE. Basically I defined some repository variables: actaul_year, three_years_ago, six_years_ago, 9_years_ago, etc.
The fragmentation content of the different LTS is defined like this:
most actual data: MyModel.Year.Year >= VALUEOF("3_years_ago")d
next table: VALUEOF("3_years_ago") > MyModel.Year.Year AND MyModel.Year.Year >= VALUEOF("6_years_ago")
next table: VALUEOF("6_years_ago") > MyModel.Year.Year AND MyModel.Year.Year >= VALUEOF("9_years_ago")
etc.
The funny thing is that the missing table is the one containing years 13 - 15. All the other tables (e.g. 16 - 18 years and 19 - 21 years) are represented in the physical SQL. This particular table is not even represented in the physical SQL.
I haven't yet tried to take one of the 'working' tables out to see if this helps (getting an idea if there is a limit on number of LTS per logical table).
Any idea?
Thanks
regards
Andy

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

How to "think" use of multiple logical table sources

Hi everybody,
i'm new to OBIEE and its paradigm. I'm trying to build a prototype with multiple physical sources: ERD and a Data Mart; I need OBIEE to go to the Data Mart model at the need of aggregated info and to go to the relational model at the need of transactional info. I need to do that working with dimensions, assigning different sources to each logical level of the dimension.
My problem begins when thinking how to actually do that. Here is my question:
- Should I add the relational source in the data mart logical table source folders, mapping the same information with joins? If so, how does dimensions work from that point? (drill down)
thanks in advance!

I'm a little confused
Is the problem
1 - You want to Access a table in an existing 9i database from a different 10g database
or
2 - You have a new 10g database as a copy of a 9i one, and a table called system has gone missing?

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

Logical table source error

I am having a union report.
I have a strange problem. The report executes successfully normally but when I am ordering the columns as per the customer requirement its throwing an error "
A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Fact - tablename does not contain mapping for [case when Dim - Account. Number in (some values)]
none of the report is using any column from the fact table so I don't think that join should exist between fact-dim in this case.
Any other solution one can suggest?

Try to redo the same report with requested order. that would be the simplest way to handle it unless you have hidden hills in your development.
If helps mark
Thanks,
http://cool-bi.com

Calc problem with fact table measure used as part of bridge table model

Hi all,
I'm experiencing problems with the calculation of a fact table measure ever since I've used it as part of a calculation in a bridge table relationship.
In a fact table, PROJECT_FACT, I had a column (PROJECT_COST) whose default aggregate was SUM. Whenever PROJECT_COST was used with any dimension, the proper aggregation was done at the proper levels. But, not any longer. One of the relationships PROJECT_FACT has is with a dimension, called PROJECT.
PROJECT_FACT contains details of employees and each day they worked on a PROJECT_ID. So for a particular day, employee, Joe, might have a PROJECT_COST of $80 for PROJECT_ID 123, on the next day, Joe might have $40 in PROJECT_COST for the same project.
Dimension table, PROJECT, contains details of the project.
A new feature was added to the software - multiple customers can now be charged for a PROJECT, where as before, only one customer was charged.
This percentage charge break-down is in a new table - PROJECT_BRIDGE. PROJECT_BRIDGE has the PROJECT_ID, CUSTOMER_ID, BILL_PCT. BILL_PCT will always add up to 1.
So, the bridge table might look like...
PROJECT_ID CUSTOMER_ID BILL_PCT
123          100     .20
123          200     .30
123          300     .50
456 400 1.00
678 400 1.00
Where for project 123, is a breakdown for multiple customers (.20, .30. .50).
Let's say in PROJECT_FACT, if you were to sum up all PROJECT_COST for PROJECT_ID = 123, you get $1000.
Here are the steps I followed:
- In the Physical layer, PROJECT_FACT has a 1:M with PROJECT_BRIDGE as does PROJECT to PROJECT_BRIDGE (a 1:M).
PROJECT_FACT ===> PROJECT_BRIDGE <=== PROJECT
- In the Logical layer, PROJECT has a 1:M with PROJECT_FACT.
PROJECT ===> PROJECT_FACT
- The fact logical table source is mapped to the bridge table, PROJECT_BRIDGE, so now it has multiple tables it maps to (PROJECT_FACT & PROJECT_BRIDGE). They are set for an INNER join.
- I created a calculation measure, MULT_CUST_COST, using physical columns, that calculates the sum of the PROJECT_COST X the percentage amount in the bridge table. It looks like: SUM(PROJECT_FACT.PROJECT_COST * PROJECT_BRIDGE.BILL_PCT)
- I brought MULT_CUST_COST into the Presentation layer.
We still want the old PROJECT_COST around until it get's phased out, so it's in the Presentation layer as well.
Let's say I had a request with only PROJECT_ID, MULT_CUST_COST (the new calculation), and PROJECT_COST (the original). I'd expect:
PROJECT_ID MULT_CUST_COST PROJECT_COST
123          $1000     $1000
I am getting this for MULT_CUST_COST, however, for PROJECT_COST, it's tripling the value (possibly because there are 3 percent amounts?)...
PROJECT_ID MULT_CUST_COST PROJECT_COST
123          $1000 (correct)      $3000 (incorrect, it's been tripled)
If I were to look at the SQL, it would have:
          SELECT SUM(PROJECT_COST),
SUM(PROJECT_FACT.PROJECT_COST * PROJECT_BRIDGE.BILL_PCT),
               PROJECT_ID
          FROM ...
          GROUP BY PROJECT_ID
PROJECT_COST used to work correctly before modeling a bridge table.
Any ideas on what I did wrong?
Thanks!

Hi
Phew, what a long question!
If I understand correctly I think the problem lies with your old cost measure, or rather combining that with you new one in the same request. If you think about it, your query as explained above will bring back 3 rows from the database which is why your old cost measure is being multiplied. I suspect that if you took it out of the query, your bridge table would be working properly for the new measure alone?
I would consider migrating your historic data into the bridge table model so that you have a single type of query. For the historic data each would have a single row in the bridge with a 1.0 BILL_PCT.
Best of luck,
Paul
http://total-bi.com

Problems with a table in PDF`S footer

Dear sirs,
We are having problems when trying to run a PDF with Adobe LiveCycle Designer tool.
We are working with a PDF which is composed of a header, the main body and a footer. We have created a table (table1) at the footer and
another one at the main body (table2). This last table (table2) may overflow therefore it will genarate two pages for our PDF.
On both pages appear the header and the footer correctly but in the last page it does not write the data from the table included in the footer (table1).
We have no problems with the table included in the main body
In the attachments, I send you the screenshots of both pages in which I have marked in red the part where we have error.
May you help us to solve our problem?
Thanks in advance your help.
Edited by: emgaitan on Mar 16, 2010 2:18 PM

Wardell,
Check the data in RSA3 for the extractor that you use to bring data .
You must be using the data source 0CO_OM_CCA_09. Check the data and reconcile and you will get it.
Let me know if you need anything else.
Thanks
Ravi Thothadri
[email protected]

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!

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 :)

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?

BIEE Answers: Problem with logical table source

Similar Messages

Maybe you are looking for