Conformed dimension and query multiple fact tables

Hello,
Please if someone can guide me on this requirement.
Requirement - I have a conformed dimension D1 and two fact tables F1 and F2. Both fact tables have many columns so I cannot merge
the two fact tables into one logical table. Currently both these fact tables have logical tables F1 and F2 respectively.
As per design the conformed dimension is a simple logical table in the rpd and not a dimension.
Can someone guide me how should i proceed so that i'll be able to fetch information from both the fact tables?
Edited by: 930542 on Apr 26, 2012 12:28 PM

Hi,
Currently the dimension table is taken as a simple logical table in rpd as it does not have have any levels or hierarchy.
Its a flat dimension. Can you guide me how can I implement a flat dimension in OBIEE? Because this dimension is taken as simple logical table
I am not able to set appropriate level for fac tables. This dimension does not appear in the list of dimensions.

Similar Messages

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.

Multiple fact tables and dimensions

I have two fact tables actual sales and planned sales and 8 dimension tables, using a star schema. I want to query on the two fact tables with two dimensions, product and time. When I create the report in discoverer i bring in the sales from actuals and then the product_desc and month_desc. Then I bring in the measure from the second fact table and a join window pops up asking which join to use. If I choose the join to the time dimension then I get no data for the second fact table and correct data for the first fact table. If I choose the product dimension then I get correct data for the first fact table and grossly incorrect data for the second fact table.
How can I stop this from happening?
Nick

Nick,
I hope you solved your reporting issue and can share the solution with me. I am encountering the same problem. I have used Oracle Warehouse Builder 10Gr2 to design and deploy a pretty simple ROLAP data mart. We are using Discoverer Plus for OLAP as our reporting tool. We have 5 dimension tables using a star schema and have 3 fact tables, when I create the worksheet I bring in our sales measure from our sales item table and then Store_Name from my Stores Dimension and then week-ending from my time dimension, everything looks good at the stage. Then I bring in a measure from our advertising cost table and a join window pops up asking which join to use, if I choose either the Store or the Time dimension I get correct data for the first fact table (sales) and grossly incorrect data for the ad cost from the second fact table (advertsing costs)...... any help would be appreciated
monalisa

How to query on multiple fact tables ?

Hello all,
I know this is a recurring subject around here. I have read various topics and tried many thing but I couldn't reach my goal :
I want to query a BMM with 6 fact tables that all have common dimensions.
For instance, I have Invoices facts, Stocks facts, and a common SpareParts dimension.I am currently using a prewiew of my target BMM, which contains only these 2 fact tables and this single dimension. They are joined both at physical and logical level.
I'd like to build a report showing for a given spare part both stock and invoice information, but Answers replies it can't link Stocks with Invoices (even when I use the spare part dimension in the report).
* I can't afford to put both fact data in a single table as I'm most likely to report on the 4 other fact tables the same way.
* I can't either alias my dimension table, as I'd like :
- to avoid having 6 spare part dimensions for my 6 fact table (imagine the user's face in front of that)
- to have the filter on a spare part filtering on both tables at once (as I talk about the same spare part on both sides)
Unless you tell me I can create an alias and then say somewhere it's actually the same dimension...
* A colleague tried to alias the dimension and then build a 1-1 join between the dimension and its alias, but it didn't work.
* I have tried to build a hierarchy for the spare parts with all the fact data at the lowest level, but it didn't do. I guess hierarchies are not intended to be used that way.
* I have tried the bridge table to link the two fact tables but i get a circular path. Furthermore, as the fact tables then turn to dimensions, I'm pretty sure my aggregates won't work... I guess bridge tables are not intended to be used that way.
* I have tried singing, dancing, jumping and bouncing around my desktop but all I got was rain.
Can anybody catch me before I jump across the window ? I wouldn't like to get wet...
Many thanks in advance.
Ced.

Hi,
unfortunately, this purpose-built datamart was built within the company RPD. It has been deleted since then. These are the two reasons why I can't post it.
My advice is to take the time to read the help about how to build logical tables in the Administrator tool.
Here's a quick walkthrough:
- create your logical tables and join them in the business model diagram
- create dimensions (hierarchies) for all your dimension tables with at least a total level and a detail level. Thins can be done automatically by right-clicking the dimension table and selecting "Create Dimension"
- in the dimension tables, select the source table (in the source subfolder of the dimension table) and edit its properties : in the properties dialog box, select the content tab and in front of the dimension name, select the lowest (or apropriate) logical level
- in some complex BM (logical levels), it might also be necessary to apply similar settings to the fact table: This time, when you edit a fact table source, you will see the list of all dimensions available in the contents tab. There, for each dimension your fact table is related to, you will select the apropriate dimension level. if there isn't any join between you fact table and a given dimension, leave the logical level blank.
I hope this helps.
Ced.

Merging Multiple fact tables and creating a BIA target

Hi Folks
We are using Dataservices with BIA.
We want to merge mutliple fact table and create a sinvglc cube on BIA.
when we tried to do that we get a error message that we cannot merge multiple fact tables.
any pointers ?
Poonam

You could have the cubes individually on the BIA and then have a multiprovider which you can use..?
or create separate universes on the cubes and then merge the universes in BO and then you could hit the BIA for the same..?

Can a measure map to multiple fact tables

Hi Experts,
Can A Measure in an Universe map to multiple fact tables? For example, we have sales detail table by day and store and product, and have sales summary table by day and region and (product) department. We like to create a measure to map to both detail table and summary table. When I run query includes store and product, the query will automatically use the sales detail table; and query can automatically choose the summary table when it only includes region and department. Our database table could be in Teradata and Oracle. Can we achieve it and how? If a measure can't achieve this (dimension awareness), what the other option we can have and how to do it?
Thank you,
Richard

Hi Sion,
After I make the tables incompatible with the dimension objects on different levels, the measure can point to the right table if my query only include Store and Product or only include Region and Department. But in some scenario, the business could ask to include both Store and Region or Item and Department in same query. The current approach doesn't work on this further request. In our database, we have store table including Region with other higher level organization information, Product table including Department with other higher level product information, and we also have separated Region table and Department table. Could we make the objects more flexible u2013 query will be against aggregation sales table if dimension objects in query are only on higher level and will against detail sales table if some of dimension objects are on high level and some on low level?
Many thanks,
Richard

Joins with multiple fact tables

Hi Experts,
i have one doubt in joins
we have two dimensions D1 and D2,
D1 is having A1 and A2 columns
D2 is having B1 and B2 columns
two facts F1 and F2 these are joined like D1 to F1 D1 to F2 and D2 to F1, D2 to F2
D1----->F1
D1------>F2
D2-------->F1
D2-------->F2
if i selected A1 and B1 in a request from which FACT table will get the data and why can you please explain
please help me
reg,
Jell

Hi All,
I have a similar requirement where I have 4 multiple fact tables and we can't combine all those facts into one single fact table. In that case how can a query work with multiple common and uncommon dimensions and measures from multiple fact tables, if it doesn't work that way - can you please explain how can we expect a query to work with multiple fact tables.
For eg: D1– Dim
D2 – Dim
D3 – Dim
D4 – Dim
F1 –Fact
F2 – Fact
F3 – Fact
D1 -> F1
D2 -> F1,F2
D3 -> F2
D4 -> F1, F3
In this case if we want to query from D1,D2,D3, F1, F2 or D1,D2,D3,D4,F1,F2,F3. Kindly please explain how it can be modeled in BMM or what are the limitations. I have done with two fact tables in past and didn't had issues but this is kind of a vast implementation. Your help is appreciated.

Few dimension values used in FACT tables.

Hello all,
We are trying to know if somebody faced this issue earlier. We have dimension tables containing 5 million records, but the fact table uses hardly 30k of these dimension values. The fact table contains 350 million records, so is there any way to improve the performance of the query in such a scenario, where hardly 20% of dimension values are actually used by the FACT tables.
Thanks and Regards,
Upendra

nilanjan chatterjee wrote:
Hi,
>
> The data for the parent members should be available in the SQL tables.
> For example, 2011.TOTAL is parent member. You should not have any data for this member in your database. If it is there, it might have come somehow (may be an import). But this is not right. You might want to remove these records. But be sure that you dont delete the records for the base level members.
>
> Hope this helps.
I guess you meant should not, right ?

Avoiding WITH clause when querying Multiple Facts

OBIEE 10.1.3.4
We have a report which requires that we query multiple facts, which share the same Item dimension.
When we run the report, the BI Server generates a query using the WITH clause -
WITH SAWITH0 ( SELECT.............)
SAWITH1( SELECT .............)
SELECT .........
FROM SAWITH0 FULL OUTER JOIN SAWITH1
The above query errors out with ORA-918 Column Ambiguously Defined. I cannot find any issue in the query that has been generated.
The query does fail from SQL Plus with the same ORA error. But each of the select statements executed properly and the complete statement executes when I replace the FULL OUTER JOIN with INNER JOIN.
I can only assume that this is a bug in Oracle Database.
Now at times I have seen OBIEE generate separate queries when querying multiple facts and then combine the data together in memory.
Is there a way that I can force OBIEE to avoid using WITH clause and run separate SELECT statements ? How does the BI Server choose between using a WITH clause or running separate queries ?
Any help would be appreciated.

I do not have a multi-dimensional data source.
My connection pool seems fine to me, I am not sure I need to do anything with the connection pool.
Hi Turribeach,
I understand that BI Server uses WITH clause for multiple facts. But I have also seen it issue separate queries against the database.
So what I am looking to understand under what situation does it issue separate queries i.e. No WITH clause ?
Thanks

How can build BMM with multiple fact tables

HI Gurus,
I have 4 fact tables and 18 Dimension table. Dimension tables have links with multiple fact tables. i have created physical joins in Physical layer. Now my questions is how can i create Business Model with multiple fact tables.
i mean should i create 4 fact tables as logical tables and logical keys ? Then i have to move all dimension tables in to Business model?
i am new to OBIEE. i gone through tutorial it is showing with one fact and multi dimension table. Should i do follow same style with multi fact tables.
Please help me. Thanks in advance for your support.

Thanks for your response.
I had drag all tables from the phisical layer to Business Model. then i have deleted all links and recreated complex joins with default values.
now i have some revenue amont columns in fact tables.
my question is should i should i create aggregation ( like Sum..) for those columns? is it must ?
please let me know thank you very much

BMM issue for multiple fact tables

Hi All,
I have three facts F1,F2, F2 and two confirmed dimension D1,D2 in my sample rpd.
In BBM layer , I tried to do the modeling as follows instead of creating one logical fact table. There are many fact tables to come
in future.
F1<----D1--->F2<----D2--->F3
When I deploy this sample rpd and run the report from F1 andF2, I get an error No fact Table exists at requested level of detail.
I have not created any hierarchical dimension to set up the content in the fact table.
I am very much thanksful for any advices.
Thanks,
Vishal

Hi,
Please refer the below link.
http://satyaobieesolutions.blogspot.in/2012/07/implementing-multiple-fact-tables-in.html
My suggestion would be bring both the facts to the same logical table sources and have a single fact table in the BMM layer joined with multiple dimensions.
Build a dimension hierarchy for the dimensions and then in the content logical layer mapping, map the dimensions to the fact tables with detailed level/Total
Refer the below link-
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
Hope this help's
Thanks,
Satya
Edited by: Satya Ranki Reddy on Jul 26, 2012 7:34 AM

Multiple Fact Tables or Circular Joins?

I'm using OE schema to build an rpd, I'm importing foreign keys and I'm unable to decide which tables to be joined additional to the imported foreign key joins. If I'm not making any new joins I'm getting multiple fact tables and if I do make some joins I'm getting circular joins, some one please throw some light on this.

It is not a good idea to bring the OE schema tables as it is. The ideal approach would be to create a view that would represent the Fact table. For e.g this view could comprise of OE headers and OE line information and the reference id to the other dimensions. 
 
Similarly create views from customer table, item tables etc and then create a star schema surrounding the fact view with all these dimension views. 
 
-Nilesh 
Dashboard Development

Multiple fact tables using one measure

Hi Experts,
Multiple fact tables using single measure .For example Measure name is amount . This measure is using 5 fact tables. By using this info , i have to create bmm layer document . In bmm layer documents columns are like logical table name ,column name, logical sourc name . could you please help me out to draft the document ?

Hi ,
My question is five fact tables are there, day level two different fact tables , period and week fact tables are there .
Above all tables are using single measure . how to design these fact tables with measure in bmm layer ?
Please kindly give reply .
Thanks in advance.

Problem relating multiple fact tables

I have 2 fact tables in my cube (Encounter and Visit). Every visit has at least 1 encounter but not every encounter has a visit. I also have a department dimension which is related to both facts, and an appointment status dimension which is
related only to Visit Fact.
The users want to look at the count of encounters by department and appointment status. At first I was having an issue with this because when using the encounter count, I would end up with the same value in each row. So I was able to create a
dimension from my Visit Fact table and then have Encounter Fact reference the appointment status dimension through the Visit Fact dimension. The problem I am having now is that since not every encounter has a visit, that my count of encounters only includes
the encounters that have visits. What I currently have is "joining out" the encounters that don't have a visit. How do I work around this so that all of the records from Encounter Fact are in the cube regardless of whether or not they have
a visit?
Do I need to implement unknown members in this case? I'm not sure where to go.
Thanks for the help,
Andy

So yes, if you are going to have some nulls you want to implement unknown members either
1. "manually" in the ETL by making yourself a custom-created unknown record in each dimension with the values your users want to see in each column (e.g. unknown record might have product_category='Misc')
2. using the built-in analysis services stuff - convert null to unknown
Typically in my cubes facts are related only to dimensions, not directly to each other. So I think I am not getting a full description of the relationships in your cube so I can't comment on your overall setup. I guess I would say if your can
determine the appointment status of an encounter based on the visit (or null/unknown if visit is null/unknown), then you should go ahead and use that information to directly relate encounter and appointment status. I would tend to do it in the ETL, you
can always use a view layer over the datamart dimension tables to do this an easy way without snowflaking your actual cube with reference dimensions.

Get the master table value based on multiple fact tables

I have an master table which has to filter data based on multiple fact tables
In the below sample, i need to get the list of MasterTable SId in an single query for fetching data from all the fact tables with an criteria.
Can u let me know the single query to handle the below situation
Select count(1) from dbo.DimMaster where sid in
(Select Master_sid from dbo.factsales where SalesDate < '20141231')
Select count(1) from dbo.DimMaster where sid in
(Select Master_sid from dbo.factPurchase where PurchaseDate < '20141231')
Select count(1) from dbo.DimMaster where sid in
(Select Master_sid from dbo.factSalary where SalaryDate < '20141231')
Select count(1) from dbo.DimMaster where sid in
(Select Master_sid from dbo.factMarket where MarketDate < '20141231')
ShanmugaRaj

Please try below:
SELECT
(SELECT count(1)
FROM dbo.DimMaster
WHERE sid IN (
SELECT Master_sid
FROM dbo.factsales
WHERE SalesDate < '20141231'
)) as C1,
(SELECT count(1)
FROM dbo.DimMaster
WHERE sid IN (
SELECT Master_sid
FROM dbo.factPurchase
WHERE PurchaseDate < '20141231'
)) as C2,
(SELECT count(1)
FROM dbo.DimMaster
WHERE sid IN (
SELECT Master_sid
FROM dbo.factSalary
WHERE SalaryDate < '20141231'
)) as C3 ,
(SELECT count(1)
FROM dbo.DimMaster
WHERE sid IN (
SELECT Master_sid
FROM dbo.factMarket
WHERE MarketDate < '20141231'
)) as C4
-Vaibhav Chaudhari

Conformed dimension and query multiple fact tables

Similar Messages

Maybe you are looking for