3 facts and 4 dimensions

Hi,
In my RPD I have 3 facts and 4 dimensions and the joins defined are as below
Physical layer - All joins are FK and inner (1:N)
FACTA-------------- Dim1,Dim2,Dim3,Dim4
FACTB-------------- Dim1,Dim5,Dim6
FACTC-------------- Dim1,Dim7,Dim8,Dim9
BM layer - All joins are complex, inner
Question is
When i am fetching the data some records are showing blanck and some with records
i wants table to be filled with records not blanck anywhere
thanks

If you set the content level for Fact B to be TOTAL for Dim 2 the metric will be null since there is no relationship between these tables. If you want the metric to repeat for this dimension you need to set the metric content level to TOTAL for Dim 2. Try that with one of the metrics and verify the behaviour.

Similar Messages

Two fact and one dimension table

Hi folks
i am new to this field ( 3 months ), my TL has given me one task i have to finish it up today itself, Can anyone one give me some idea how to implement
req. The req is
1. there are 2 fact and one dimension table is there, i have to create reports on Quaterly and monthly basis by using one dimension table.
Can any one tell me what all are the steps in need to follow
2.What is standalone and integrated systems?
Regards
Reddy

Hi
If u r having mapping keys for quarter level n monthly level then create a Alias for the dimension table.Use the original dim table for quarter level mapping and the alias dim for monthly level.
Thanks
Don

Need to pull the information from two facts and associated dimensions

HI All, i need to pull all the columns from the two Facts and their associated dimensions, get the results.
here is the example:
Fact1 --> D1, D2, D3
FACT2--> DA, DB, DC, D1
D1 Dimension has a Join with two fact tables, as long as i'm using columns from D1 and FACT2, DA, DB, DC report works.
but my requirement is to get the results when pulling the columns from all the dimensions and two facts like Fact1, FACT2, D1, D2, D3, DA, DB, DC
how to achieve this requirement, can someone pls help me with this.
your responses are much appreciated.
Thanks
rar

Hi RAR,
I assume you have created proper dimensional hierarchies for all the dimensions in your subject area. Also, ensure that all of them have a Total Level created.
Assuming the above, since D1 is a conformed dimension, if you create a report having columns from only D1,Fact1 and Fact2, the report should show you proper results.
For creating a report having columns from all tables, ensure the following:
1. For all measure columns from Fact1 to be included in the report, set them to be calculated at the Total Level of dimensions DA, DB and DC
2. For all measure columns from Fact2 to be included in the report, set them to be calculated at the Total Level of dimensions D2 and D3
The physical sql will fire separate queries for the 2 star schemas and then join them using the conformed dimension.
Hope this helps,
Gaurav

2 facts and 1 dimension design in RPD

Hi All,
Approach 1:
I have a Fact which I am creating as a dimension and there is another fact which is joined to the same dimension.
The same process I am following in BMM layer and trying to work by setting content level.
But when I am dragging column all the 3 tables I am getting no results. Individually I am getting data.
Approach 2:
I made only one with 2 facts as a sources of that fact and tried to join with dimension in BMM layer setting the apprpriate content level.
Even in this case also I am unable to get result in the answers with all the 3 tables no results is what it is displayed.
Approach 3:
This is 3 approach I made. Like instead of creating join in the physical layer between same 2 aliases of the same table I have duplicated in the BMM layer and made a join there but still I get no results with all the 3 tables.
Any help will be appreciated on this issue. As early as possible.
Thanks
Subhash
Edited by: Subhash1111 on Jun 3, 2010 4:31 AM

See the below design guide for the WAAS:-
http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/WAASDC11.html
HTH>

Urgent - How to join multiple facts and dimensions in OBIEE rpd??

Hi,
In my RPD I have 3 facts and 4 dimensions and the joins defined are as below
Physical layer - All joins are FK and inner (1:N)
FACTA-------------- DIM_TIME, DIM_CUST,DIM_CAL
FACTB-------------- DIM_TIME, DIM_CUST,DIM_CAL
FACTC-------------- DIM_TIME, DIM_CUST,DIM_CAL, DIM_XYZ
BM layer - All joins are complex, inner
The logical table F1 pulls columns from FACTA, FACTB and FACTC . Complex join exists between all 4 dimensions DIM_TIME, DIM_CUST,DIM_CAL, DIM_XYZ to logical table F1.
Issue: I need to build a report with $ column from FACTA, FACTB and FACTC and need to add filter conditions using columns from DIM_TIME, DIM_CUST,DIM_CAL, DIM_XYZ.
However when ever I add a filter condition from DIM_XYZ the physical query generated is not generating code to access data from FACTA and FACTB. Instead it is subsituting a NULL and just pulls data frm FACTC.
My Questions: What is the best way to build the physical and BMM layer using FACTA, FACTB,FACTC, DIM_TIME, DIM_CUST,DIM_CAL and DIM_XYZ??
I need to resolve this issue ASAP so any help is appreciated. Thanks
Edited by: user11935561 on Feb 10, 2010 6:27 AM
Edited by: user11935561 on Feb 10, 2010 6:28 AM

You can find the same issue in
Logic of queries in OBIEE
or
Connection between 2 fact tables
Follow the link
http://there-n-back-again.blogspot.com/2009/04/oracle-analytics-how-to-report-over-non.html
Put 'All' or 'Total' at levels for dim_xxx for those facts you need in your report from facta and factb
Regards
Nicolae

Facts and dimensions joins

Hi,
Can we use three fact tables in rpd and not join them? We have three facts and four dimensions. All the four are common dimensions to the three fact tables. So in the physical joins can we just join the facts to the dimensions? will it be accepatble if we do not have a join between fact tables. Is it necessary that all the tables (fact and dimensions) need to be joined to some tabler? Can we leave the joins between the facts which are not necessary? Please advice.

We do not do joins between fact tables, the joins between facts will be happened through dimensions (conformed dimensions).
In your case the 4 dimension will act as an conformed one.
Is it necessary that all the tables (fact and dimensions) need to be joined to some tabler? You cannot have a table in BMM which is not joined to any other table.
Can we leave the joins between the facts which are not necessary?Yes, Dim1 - fact1 -Dim 2 in this fact 1 is connected with Dim1, Dim2 and there is no relationship for fact1 with Dim3 so we don't join it.
Dim1,Dim2,Dim3 is joined with fact2 in this case Dim 1 and Dim2 will act as conformed dimesion between fact1 and fact2, where as dim3 will be a non conformed dimesion.
Thanks,
Vino

Facts and dimension tables in BMM layer

HI Experts,
i have one doubts that is.... i have 7 Fact and 20 dimension tables in my current project ( this is mine first project ) how can i join these tables in BMM layer...
Regard's
Harish

Harish,
Just explicitly mentioning # of facts and dimensions won't fetch you any help. Extract a simple business scenario containing a fact and dimension tables.
e.g.
1. firstly, how many of the fact tables built are associated with different subject areas?
2. of the fact tables belonging to each subject areas, how many of them are aggregate tables?
3. if step 1 is not true, do they have conformed dimensions to access? <-- a caveat exists which your user MUST definitely know.
4. are there any partitions?
5. are they aggregate or summarized tables?
etc,....
based on which your modelling will start.
-bifacts :-)
http://www.obinotes.com

2 Facts with common dimensions

Hi All,
I am trying to developer an Answer
I have two Fact tables :- Budgets and Actuals
The two Fact Tables have common dimensions (Period, Cost Centre and Expense)
When I create an answer which combines these common dimensions and the two fact tables I can create a report that compares Actuals Vs Budgets and that works fine
However the Budget Fact has an additional dimension Bugdet Name (which can have values like 'Budget','Forecast','Allocation') that does not apply to Actuals
When I try to fliter or include the Budget Name I lose all my actuals
(Incidentally some actuals do not have budgets, some budgets do not have actuals and I want to see all rows)
Any ideas?
Cheers
Pete

Hi,
I try this:
I have in BMM one subject area with two fact and common dimension
SALES -> quantity_sold measure
and
SALES_TIME_ID -> select (amount_sold-100) as amount_sold, time_id from sales
and dimensions
TIMES
PRODUCTS
Both are joined to a SALES and just TIMES is joined to a SALES_TIME_ID in physical layer and in BMM complex join are propagated from facts to dimensions
Test in Answers - both queries are generated:
TIMES.CALENDAR_YEAR
SALES.QUANTITY_SOLD
SALES_TIME_ID.AMOUNT_SOLD
select T20553.CALENDAR_YEAR as c1,
sum(T20550.QUANTITY_SOLD) as c2
from
TIMES T20553,
SALES T20550
where ( T20550.TIME_ID = T20553.TIME_ID )
group by T20553.CALENDAR_YEAR
order by c1
------------------- Sending query to database named orcl (id: <<13806>>):
select T20553.CALENDAR_YEAR as c1,
sum(T35447.amount_sold) as c2
from
TIMES T20553,
(select (amount_sold-100) as amount_sold, time_id from sales) T35447
where ( T20553.TIME_ID = T35447.time_id )
group by T20553.CALENDAR_YEAR
order by c1
PRODUCTS.PROD_CATEGORY
TIMES.CALENDAR_YEAR
SALES.QUANTITY_SOLD
SALES_TIME_ID.AMOUNT_SOLD
select distinct D1.c2 as c1,
D1.c3 as c2,
D1.c1 as c3,
cast(NULL as DOUBLE PRECISION ) as c4
from
(select sum(T20550.QUANTITY_SOLD) as c1,
T20553.CALENDAR_YEAR as c2,
T21473.PROD_CATEGORY as c3
from
TIMES T20553,
PRODUCTS T21473,
SALES T20550
where ( T20550.PROD_ID = T21473.PROD_ID and T20550.TIME_ID = T20553.TIME_ID )
group by T20553.CALENDAR_YEAR, T21473.PROD_CATEGORY
) D1
order by c1, c2, c4
Amount sold is null because SALES_TIME_ID does not contain PROD_CATEGORY attribut, it's not common.

In Answers am seeing "Folder is Empty" for Logical Fact and Dimension Table

Hi All,
Am working on OBIEE Answers, on of sudden when i clicked on Logical Fact table it showed me as "folder is empty". I restarted all the services and then tried still showing same for Logical Fact and Dimension tables but am able to see all my reports in Shared Folders. I restarted the machine too but no change. Please help me out to resolve this issue.
Thanks in Advance.
Regards,
Rajkumar.

First of all, follow the forum etiquette :
http://forums.oracle.com/forums/ann.jspa?annID=939
React or mark as anwser the post that the user gave.
And for your question, you must check the log for a possible corrupt catalog :
OracleBIData_Home\web\log\sawlog0.log

Best practice when FACT and DIMENSION table are the same

Hi,
In my physical model I have some tables that are both fact and dimension table, i.e. in the BMM they are of course separated into Fact and Dim source (2 different units) and it works fine. But I can see that there will be trouble when having more fact tables and I e.g. have a Period dimension pointing to all the different fact tables (different sources).
Seems like the best solution to this is to have an alias of the fact/transaction table and have 2 "copies" of the transaction table (one for fact and one for dimension table) in the physical layer. Only bad thing is that there will then allways be 2 lookups in the same table when fetching data from the dimension and the fact table.
This is not built on a datawarehouse - so the architecture is thereby more complex. Hope this was understandable (trying to make a short story of it).
Any best practice on this? Or other suggestions.

Id recommend creation of a view in the database. if its an oracle DB, materialised views would be a huge performance benefit. you just need to make sure that the MVs are updated when the source is updated.
-Domnic

OBIEE Group By on 2 facts and concatenated columns from different dimensions

Hi
I have a different kind of problem involving 2 fact tables with different dimensional attributes.
Fact 1 has Dim Attributes ( Cust,Facility )
Measure - Gross Amount
Fact2 has Dim attributes (Cust,Facility and Risk Group )
Measure : Exposure Amount
Since we have 2 facts with different dimensions,
to exclude the 'Risk Group' dimension column from the group by for the Fact1,
we set the 'Gross Amount' measure to total level (Risk Group Dimension ) in contents tab.
So the values from both the fact tables appears in the same report correctly.
But in the same report we have another requirement where the rating column from the customer dimension has to be concatenated with the ratings column in the facility dimension.
We have to concatenate customer.rating with the facility.rating and display it in the report.
when we just pull the individual columns from the dimensions into the report it works fine.
But when we try to concatenate the 2 columns and show it in the report,
the concatenated column does not appear in the select or the group by in the SQL Fact2.( Generated by OBIEE )
The other fact1 has the concatenated column in the select as well as the group by clause ( Generated by OBIEE )
As a result the report shows the concatenated values only for the results from the Fact1. But the results from Fact2 does not have the concatenated column values.
The report should look like the below:
Custor.Name,     Customer.Id,     Facility.Name,     Facility.Id,     Customer.Rating/Facility.Rating,     Risk Group,     Gross Amount,     Exposure Amount
===========    =========      ===========     =========   ========================      =========     ===========     ===============
JPMC                123                    GROSS               123               08/10                                                  LNL                    45,000               25,000
CLAIRE               456                    NET                    456               07/10                                                  RNK                    50,000               30,000
Thanks,
Chandra

As suggested you really want to move your none-aggregated fact attributes to a logical dimension (using the same physical table as the logical fact). Map this in the BMM layer as a snowflake, Place a hierarchy on this dimension with (at minimum) Total -> Detail levels, then on the other fact table you want to include in the report, set the content level on your other fact measures to the 'Total' level for your new logical Dim and it will allow them to be present in the same report.

Using two facts of two different star schemas and conformed dimensions

Hi,
I've been working as developer and database designer for years and I'm new to Business Objects. Some people says you can not use two facts of two different star schemas in the same query because of conformed dimensions and loop problems in BO.
For example I have a CUSTOMER_SALE_fACT table containing customer_id and date_id as FK, and some other business metrics about sales. And there is another fact table CUSTOMER_CAMPAIGN_FACT which also contains customer_id and date_id as FK, and some other business metrics about customer campaigns. SO I have two stars like below:
DIM_TIME -- SALE_FACT -- DIM_CUSTOMER
DIM_TIME -- CAMPAIGN_FACT -- DIM_CUSTOMER
Business metrics are loaded into fact tables and facts can be used together along conformed dimensions . This is one of the fundamentals of the dimensional modeling. Is it really impossible to use SALE_FACT and CAMPAIGN_FACT together? If the answer is No, what is the solution?
Saying "you cannot do that because of loops" is very interesting.
Thank you..

When you join two facts together with a common dimension you have created what is called a "chasm trap" which leads to invalid results because of the way SQL is processed. The query rows are first retrieved and then aggregated. Since sales fact and campaign fact have no direct relationship, the rows coming from either side can end up as a product join.
Suppose a customer has 3 sales fact rows and 2 campaign fact rows. The result set will have six rows before any aggregation is performed. That would mean that sales measures are doubled and campaign measures are tripled.
You can report on them together, using multiple SQL passes, but you can't query them together. Does that distinction make sense?

Resolving loops in a star schema with 5 fact tables and 6 dimension tables

Hello
I have a star schema, ie 5 FACT tables and 7 dimension tables, All fact tables share the same dimension tables, some FACT tables share 3 dimesnsions, while other share 5 dimensions.
I did adopt the best practices, and as recommended in the book, I tried to resolve them using Context, as it is the recommended option to Alias in a star schema setting. The contexts are resolved, but I still have loops. I also cleared the Multiple SQL Statement for each context option, but no luck. I need to get this resoved ASAP

Hi Patil,
It is not clear what exactly is the problem. As a starting point you could set the context up so that it only covers the joins from fact to dimension.
Fact A, joins Dim 1, Dim 2, Dim 3, and Dim 4
Fact B, joins Dim 1, Dim 2, Dim 3, Dim 4 and Dim 5
Fact C, joins Dim 1, Dim 2, Dim 3, Dim 4 and Dim 6
Fact D, joins Dim 1, Dim 2, Dim 3, Dim 4 and Dim 7
Fact E, joins Dim 1, Dim 2, Dim 4 and Dim 6
If each of these are contexts are done and just cover the joins from fact to dim then you should be not get loops.
If you could lay out your joins like above then it may be possible to specify the contexts/aliases that should work.
Regards
Alan

How to design fact and dimension tables

Hi Team,
Please provide me some useful links!!
I have a Parent & Child table each has around 8 Million records (1 to many relation). These two tables need relation with many other master tables to generate any report.
I want to desing a fact and dimension(s) for this parent & Child tables.
Please help me what are the things I have to keep in mind when desingning datawarehouse fact and dimension tables?
Thanks,
Ali

Hi, any update on this?

Delete Fact and Dimension Tables

Hai All,
Small question! When deleting data from info cube, it asks whether to delete just Dimension table or both fact and Dimension tables.
What is the difference between these two?
Thank you.

Hi Visu,
The dimension table will contain the references to char value by way of SID and DIM ids, whereas the fact table will contain the number (of key figures). If you delete just the Fact table, the numbers go away, yet the DIM ids remain intact, so reload is faster. But if you are convinced that this data is not correct either, or you want a clean slate to strat reload again, then delete both Fact and Dim tables. Then when you reload, the DIM ids will be created again.
Hope this helps...

3 facts and 4 dimensions

Similar Messages

Maybe you are looking for