One fact table

Can I have only one table in "Business model"? I am trying to do this, but unsuccessful. I am getting error "Logical table ... does not join to any other logical table". Could someone explain to me why can I not have only one table?
Thanks

1. Create an alias of the table in the physical layer.
2. Add a physical join between alias and existing table on primary key.
3. Add the alias to the business model and mapping layer.
4. Add a complex join between both tables in BMM layer.
5. Use only columns of the fact table in the presentation layer.
Regards,
Stijn

Similar Messages

More than one fact tables...

Hi.
I have tried OLAP until now with only one fact table.
But now I have more than one. To start i added one more.
I am always using SOLVED LEVEL...LOWEST LEVEL.
I am always receiving the following error when creating the cube with this measures:
"exact fetch returns more than requested number of rows"
What shall I look for when dealing with more than one fact table?
Thanks.
ODDS
:: ... and still have a very poor performance ...

1.
Well ... I saw the global star schema and we have two fact tables there!!!
Do I have to build different cubes for each fact table always?
2.
I have built cubes, created a java client and a jsp client.
Performance is much better in JSP using the AppServer(sure!).
The power of the JSP client is more limited i presume.
I wonder if I can do things such setCellEditing for a crosstab in both.
3.
Some aggregation questions:
Everytime I create a cube using CWM2 and also a AW using AWM wizards with that cube I have one aggregation plan by default that processes everything online.
After that I create and deploy my own aggregation plan.
My question is: If I don't want to aggregate anything!??! I want to see, for instance, in BiBeans the lowest level values only. And everything at the top levels empty.
I am missing something 'cause I still have everything aggregated !!!
Thanks.
ODDS

Common diemsions and more then one fact table join problem

Hi,
I have 5 common dimension and 3 fact table which in the same subject area. When I want to display results from more then one fact table sending database then query more then one and I think BI server join this two different result on OBI server. But I think if obi server sending database query for exp. WITH SAWITH0 .... the results get effective.
+++002002:2ea0000:2ea000f:----2009/03/14 10:12:59
-------------------- SQL Request:
SET VARIABLE QUERY_SRC_CD='Report';SELECT "- Common Dimensions"."Year Month" saw_0, "- Subs. Tariff"."Subscriber Current Tariff Type" saw_1, "- Common Measures".Arpu saw_2, "- Common Measures"."Gross Margin" saw_3, "- Call Out"."Callout Dur" saw_4, "- Case".Case_Info_Num saw_5 FROM "CUSTOMER PROFILING" WHERE ("- Common Dimensions"."Year Month" = 200901) AND ("- Subs. Tariff"."Subscriber Current Tariff Type" = 'PREPAID') ORDER BY saw_0, saw_1
+++002002:2ea0000:2ea000f:----2009/03/14 10:12:59
-------------------- General Query Info:
Repository: Star, Subject Area: CUSTOMER PROFILING REV, Presentation: CUSTOMER PROFILING
+++002002:2ea0000:2ea000f:----2009/03/14 10:13:00
-------------------- Sending query to database named CENTRAVEA (id: <<471777>>):
select T223282.DIM_TIME_MONTH_ID as c1,
T221204.DIM_SUBS_CURRENT_TARIFF_TYPE as c2,
avg(T223490.FACT_CP_ARPU) as c3,
sum(T223490.FACT_CP_GROSS_MARGIN) as c4,
sum(T223490.FACT_CP_CO_DUR) as c5
from
DM.DIM_SUBSCRIBER T221204 /* A_DIM_SUBSCRIBER */ ,
DM.DIM_TIME_MONTH T223282 /* A_DIM_TIME_MONTH */ ,
DM.FACT_CUST_PROFILING_PART3 T223490 /* A_FACT_CUST_PROFILING_PART3 */
where ( T221204.DIM_SUBS_ID = T223490.DIM_SUBS_ID and T221204.DIM_SUBS_CURRENT_TARIFF_TYPE = 'PREPAID' and T223282.DIM_TIME_MONTH_ID = T223490.DIM_TIME_MONTH_ID and T223282.DIM_TIME_MONTH_ID = 200901 and T223490.DIM_TIME_MONTH_ID = 200901 )
group by T221204.DIM_SUBS_CURRENT_TARIFF_TYPE, T223282.DIM_TIME_MONTH_ID
order by c1, c2
+++002002:2ea0000:2ea000f:----2009/03/14 10:13:00
-------------------- Sending query to database named CENTRAVEA (id: <<471881>>):
select T223282.DIM_TIME_MONTH_ID as c1,
T221204.DIM_SUBS_CURRENT_TARIFF_TYPE as c2,
sum(T223294.FACT_CP_CASE_INFO_NO) as c3
from
DM.DIM_SUBSCRIBER T221204 /* A_DIM_SUBSCRIBER */ ,
DM.DIM_TIME_MONTH T223282 /* A_DIM_TIME_MONTH */ ,
DM.FACT_CUST_PROFILING_PART1 T223294 /* A_FACT_CUST_PROFILING_PART1 */
where ( T221204.DIM_SUBS_ID = T223294.DIM_SUBS_ID and T221204.DIM_SUBS_CURRENT_TARIFF_TYPE = 'PREPAID' and T223282.DIM_TIME_MONTH_ID = T223294.DIM_TIME_MONTH_ID and T223282.DIM_TIME_MONTH_ID = 200901 and T223294.DIM_TIME_MONTH_ID = 200901 )
group by T221204.DIM_SUBS_CURRENT_TARIFF_TYPE, T223282.DIM_TIME_MONTH_ID
order by c1, c2
I have another subject area and which defined like this subject area contain two dimension and 5 fact table. If I want to display results on this subject area I can see best sql for my database
My problem is why this two different subject areas create different queries. I think following query is the best for database.
Thanks for your help
+++002002:2ea0000:2ea0015:----2009/03/14 10:30:06
-------------------- SQL Request:
SET VARIABLE QUERY_SRC_CD='Report';SELECT "Dim - Segments"."Marketing Segment" saw_0, "Fact - Campaign Response"."Fact Campaign Award Amount" saw_1, "Fact - Customer Interaction"."Issue Response Cost" saw_2 FROM "AVEA ALL" ORDER BY saw_0
+++002002:2ea0000:2ea0015:----2009/03/14 10:30:06
-------------------- General Query Info:
Repository: Star, Subject Area: AVEA ALL, Presentation: AVEA ALL
+++002002:2ea0000:2ea0015:----2009/03/14 10:30:06
-------------------- Sending query to database named AVEA ALL (id: <<474694>>):
WITH
SAWITH0 AS (select sum(T51461.FACT_CMPGN_AWARD_AMOUNT) as c1,
T49384.DIM_MARKETING_SGMNT_DESC as c2
from
DM.DIM_MARKETING_SEGMENT T49384 /* DIM_BI_MARKETING_SEGMENT */ ,
DM.FACT_CMPGN_RESPONSE T51461 /* FACT_BI_CMPGN_RESPONSE */
where ( T49384.DIM_MARKETING_SGMNT_ID = T51461.DIM_MARKETING_SGMNT_ID )
group by T49384.DIM_MARKETING_SGMNT_DESC),
SAWITH1 AS (select sum(T51503.FACT_CUST_INT_ISSUE_RES_COST) as c1,
T49384.DIM_MARKETING_SGMNT_DESC as c2
from
DM.DIM_MARKETING_SEGMENT T49384 /* DIM_BI_MARKETING_SEGMENT */ ,
DM.FACT_CUST_INTERACTN T51503 /* FACT_BI_CUST_INTERACTN */
where ( T49384.DIM_MARKETING_SGMNT_ID = T51503.DIM_MARKETING_SGMNT_ID )
group by T49384.DIM_MARKETING_SGMNT_DESC)
select distinct case when SAWITH0.c2 is not null then SAWITH0.c2 when SAWITH1.c2 is not null then SAWITH1.c2 end as c1,
SAWITH0.c1 as c2,
SAWITH1.c1 as c3
from
SAWITH0 full outer join SAWITH1 On SAWITH0.c2 = SAWITH1.c2
order by c1

I find solution on Oracle® Business Intelligence Suite Enterprise Edition Release Notes.
If you use a version of Oracle Database 10g Release 2 prior to 10.2.0.3, then you might encounter an issue with a Full Outer Join that causes severe database performance issues and appears to hang the database when the Oracle BI Server sends to the database SQL queries that include WITH clauses.
To work around this issue when using Oracle Database 10g Release 1 or 2, upgrade to Oracle Database 10g Release 2 Patch Set 2 (for 10.2.0.3). For performance reasons, this is the preferred workaround.
To work around this issue without installing Patch Set 2, modify the Database Features table using the Administration Tool. This configuration prevents the Oracle BI Server from sending SQL constructs that expose the issue in an unpatched Oracle Database 10g.
To modify the Database Features table:
In the Administration Tool, open the properties of the Physical Database metadata object.
Navigate to the Features tab.
Ensure the values for the PERF_PREFER_MINIMAL_WITH_USAGE and PERF_PREFER_INTERNAL_STITCH_JOIN entries are selected, that is, set to True.

What is the prerequisite for creating two hierarchies from one fact table i

Hi,
what is the prerequisite for creating two hierarchies from one a single fact table.
Rgds,
Amit

create global temporary table t1 as select * from trn_ordbase on commit preserve rows;You CANNOT use this syntax.
http://download-east.oracle.com/docs/cd/B19188_01/doc/B15917/sqcmd.htm
http://download-east.oracle.com/docs/cd/B19188_01/doc/B15917/glob_tab.gif
http://download-east.oracle.com/docs/cd/B19188_01/doc/B15917/cre_tabl.gif

Multiple Date columns in one fact table

hi ,
I have a fact which related to multi date, like bid date, win date, lost date ,etc...,
I have create dimension like dim_bid_date, dim_win_date,
but if I wan to create a report , the value sum by the month (2012.01-2012.08), I don't know how to do in one report which related multi date.
I think I should have a 'common date', how to do, can anyone explain it in detail. thanks.

2 thinks here, do you want to reports based on bid date,win date, lost date etc?
if yes you need to create those many date logical tables and you need to have in Subject area (something like 'Agreement Details' subject area if you have OOB rpd)
Coming to your report requirement 'sum by the month'; I dont think this is complete report requirement, you need to know month type like bid month or win month or lost month or what!!
if user dont want do report by those mentioned dates then just use just date of type( bid,win etc) with out using day dim;
you might have some date like created date, create report based on that for sum by the month.
Hope this helps, if helps pls mark

Dimension which belongs to only one of the several fact tables

Hi,
I'm newbie in BI. I have good knowledge of DW and Administration (OCP).
Firstly could you give me, please some link expalining aspects of creating "Business Model And Mapping" better than SE Tutoarial.
Now how my problems looks like :
I have several fact tables and dimensions.
But not all dimensions are shared among all facts.
So when i try to put in Answers measurements from all facts it's ok - results are retrieved.
But when i try to add to report some Dimensions attributes which belongs to only one of the facts all facts measurements are gone except measurements for fact table to which dimension attribute is linked to.
I think i know what is the reason but i don't know how to simply solve it :
Below is session trace excerpt only with facts measurements :
RqList
Liczba Transakcji:[DAggr(Fakty - Transakcje (ZSFK).Liczba Transakcji by [ Słownik - Daty.Nr Miesiąca, Słownik - Daty.Miesiąc Rozliczenia, Słownik - Outlety.Outlet Numer (MID), Słownik - Outlety.Outlet Nazwa, Słownik - Terminale.Nr Terminala, Słownik - Daty.Rok Rozliczenia] )] as c7 GB,
Kwota Opłaty Netto:[DAggr(Fakty - Opłaty za Terminale (CBD).Kwota Opłaty Netto by [ Słownik - Daty.Nr Miesiąca, Słownik - Daty.Miesiąc Rozliczenia, Słownik - Outlety.Outlet Numer (MID), Słownik - Outlety.Outlet Nazwa, Słownik - Terminale.Nr Terminala, Słownik - Daty.Rok Rozliczenia] )] as c11 GB,
Below iis session trace excerpt with facts measurements and added dimension attribute:
RqList
Liczba Transakcji:[DAggr(Fakty - Transakcje (ZSFK).Liczba Transakcji by [ Słownik - Rodzaje Walut.KOD_WALUTY, Słownik - Daty.Nr Miesiąca, Słownik - Daty.Miesiąc Rozliczenia, Słownik - Outlety.Outlet Numer (MID), Słownik - Outlety.Outlet Nazwa, Słownik - Terminale.Nr Terminala, Słownik - Daty.Rok Rozliczenia] )] as c7 GB,
Kwota Opłaty Netto:[DAggr(Fakty - Opłaty za Terminale (CBD).Kwota Opłaty Netto by [ Słownik - Rodzaje Walut.KOD_WALUTY, Słownik - Daty.Nr Miesiąca, Słownik - Daty.Miesiąc Rozliczenia, Słownik - Outlety.Outlet Numer (MID), Słownik - Outlety.Outlet Nazwa, Słownik - Terminale.Nr Terminala, Słownik - Daty.Rok Rozliczenia] )] as c12 GB,
Second plan is the plan when report retrieves only results for one fact table and null's for others
Problem is with attribute : "Słownik - Rodzaje Walut.KOD_WALUTY" which is from dimension which belongs only to one fact table.
So other fact table are not linked to this dimension and therefore this plan cannot retrieve results for them.
It is obvious that some of the facts cannot share some dimensions with others but i would like to join them on other common attribute
and my question is how ?
Thanks's in advance Arkadiusz Masny
Edited by: Arkadiusz Masny on Dec 10, 2009 6:49 AM

It's normal behavior. How would fact measure know the value for accurate "non-fact" dimension
Workaround:
First solution is:
Add into logical source of each fact (in logical layer) tables to which belongs dimension attribute and join dimenstion to that fact.
Second you may:
Create fact table which join all needed dimensions with some useless fact ( i.e. count). Next you have to set option "Implicit Fact Column" in presentation catalog to use this fact table.
I can explain it to you in Polish by mail or phone
You bring me a next topic for my blog (in Polish) http://obiee.pl so I'll write sth about such behavior :)
Regards

How to join Dimensions and Fact Tables in OBIEE

Hi All,
I need to create report which need to get the information from two fact tables and 7 dimensions. The granularity is not same in both the fact tables. One fact table is having common keys between all the dimension tables and second fact table have only two dimension keys but with different names. My requirement is to create the report by taking the measures from both the fact tables.
I have created joins between the second fact table and two dimension tables in physical and BMM layer and also set the highest level for all other dimension tables in the LTS of second fact table. when am creating report by taking the measures from both the fact tables, data is not getting for the measure which taken from the second fact table. Please advice me how to get the data for the measure which taken from the second fact table.
Thanks in Advancec !!

You have to use the level-base measure capabilities.
http://gerardnico.com/wiki/dat/obiee/bi_server/design/fact_table/level_based_measure_calculations
For all measures of the second fact table with the lowest grain (with two dimension keys), set for all dimension where you don't have any key the logical level to the "All" or "Total".
And UNSET the highest level of the LTS for the second fact table.
Success
Nico

Multiple fact tables

Hi All,
I am using OBIEE 11g. In my requirement, I have 1 Fact table and 3 Materialized Views of fact table. Now, these 3 MV have same columns as actual fact table 1 barring a couple of additional columns in each of them. Imported these 3 MVs and 1 Fact table in Admin tool. In Physical Layer I joinedmy dimensions to each of the Fact (table and MVs). In BMM I created one Fact table with 4 LTS coming from these fact table and MV. Now, all the dimensions are conformed. Still when bring in a column from each of these facts I am getting incorrect results. e.g. when I find sales from years, the data is correct. As soon as I add another fact column from a different MV/fact table the values from first sales column gets changed.
I have check LTSs and Content levels and do not see any problems.
Does anyone have some similar experience?
Thanks,
D

Hi Dcole,
It should not be a problem,you are going in right direction but i want you to check the joins established in the physical layer once again.
But you mentioned a point above saying all the columns are same as actual fact with MV's.I suppose it is assuming as 1 column only.Can you change the column names..
Go through these links for more info
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
http://www.obinotes.com/2010/08/joins-within-logical-table-sources-in.html
hope helps you.
Cheers,
KK

How to set db schema in fact tables

Hi!
I have one mapping with one table(table1) pointing to one fact table (fact1).
This fact table has two dimensions located in two different schemas. I already deployed those dimensions and tables and its ok.
My problem is: when I open the mapping editor and ask to generate the mapping to create the package to populate the fact table,
I can see why I can not deploy it (PL/SQL: ORA-00942: table or view does not exist).
My query is: SELECT (fields) FROM schema.table1, table2 ,table3 WHERE....
I cant set the schema property from my table (table1), but I cant´t do the same with the table2 and table3 (both tables related to dimensions). i don´t have this option!
I don´t understand why this happen because both dimensions are ok. They are in two different modules and the locations are ok too.
I understand that the mapping needs the dimension keys to populated the fact table, but I really don´t know how to set this schema property. If i can´t do that,
i don´t know how to "fix" this problem. If a can´t set this schema property, how can I deploy this mapping whitout this???!!!!
I´m using the 10.2 version.
Thanks o lot!!!!!!!!!!!

This is what really happens in my example.
Look the "Generation Results" :
SELECT
/*+ ORDERED NO_MERGE("INGRP1") */
"TEMP_TABLE"."Value1" "Value1",
"TEMP_TABLE"."Value2" "Value2",
"DIMENSION1"."ID" "ID",
"DIMENSION2"."ID" "ID"
FROM
"SCHEMA"."TEMP_TABLE" "TEMP_TABLE", -> I CANT SET THIS schema
"DIMENSION1" "DIMENSION1", -> i can´t do the same here
"DIMENSION2" "DIMENSION2" -> i can´t do the same here
WHERE
( "DIMENSION1"."DIMENSION_KEY" = "DIMENSION1"."ID" ) AND
( "DIMENSION1"."ID" IS NOT NULL ) AND
( "DIMENSION2"."DIMENSION_KEY" = "DIMENSION2"."ID" ) AND
( "DIMENSION2"."ID" IS NOT NULL ) AND
( "DIMENSION1"."key" = "TEMP_TABLE"."key" ) AND
( "DIMENSION2"."key" = "TEMP_TABLE"."key" )
I already tried to use 3 DB-Modules but I have the same problem. :o(
I don´t know what to do!!!!!!!

Fact table

Hi Experts,
1.I have a question like for better performance should we use two fact tables or one fact table? ( I have two fact tables but let me know if i should use only one fact table by joining the other
Logical table source)
2. I have a detailed report to show with million records what should i do for the better performance.
PS: This report is detailed so there is nothing to Aggregate.( I am using 10.3.4.1 version)
Thanks in Advance.
chak.
Edited by: 884679 on Sep 12, 2011 9:20 AM
Edited by: 884679 on Sep 12, 2011 9:21 AM

As a best practice, create 2 Logical Table in BMM with single LTS pointing to each fact table in physical. Couple of benefits:
- when a measure is used in report, BI server easily identifies relevant Logical Table and LTS and corresponding Physical Table
- when both measures are used then each LTS from individual LT will come into picture
- for future cases you don't need to apply fragmentation to force BI server to pick one of two LTS when single LT with 2 LTS is used
- BI server will give better and optimized query
There are many used cases for this ...So, better go for 2 LT with Single LTS each.
Hope its clear

Fact Table with a metric repeated in several rows

Hi!!
I've got a little problem and I don't know how to face it.
I'm using OBIEE and I've got this case:
One fact table like this:
Order_Number - Q.Received - Supplier - Invoice_Number - Q.Inv.
1 - 10 - S1 - I1 - 2
1 - 10 - S1 - I2 - 8
2 - 10 - S1 - I3 - 10
So, for an order Number, I can have more than one Invoice Number, but the quantity Received is always 10, because is a metric refered to the Orden, not to de Invoice, but this quantity (10) I find it in two rows, not in one row. It's like having two fact tables mixed (invoices and orders).
My problem is:
If in the logical field Q.Received I don't aggregate de column, when in Answers I try to know the Quantity of units received by supplier S1, the report says 10, that is incorrect. It should be 20.
If in the logical field Q.Received I aggregate de column, when in Answers I try to know the Quantity of units received by supplier S1, the report says 30, that is incorrect too.
I've tried to separate it in two fact tables by views like this:
Fact1: Orders
Order_Number - Q.Received - Supplier
1 - 10 - S1
2 - 10 - S1
Fact2: Invoices
Order_Number - Invoice_Number - Q.Inv.
1 - I1 - 2
1 - I2 - 8
2 - I3 - 10
...and I've created a dimension with Order_Number, but the report:
Order_Number - Q.Received - Q.Inv.
...doesn't work.
-If I try without jerarquies, OBIEE goes only to the first one and if I select a field from Fact2 says that there isn't a mapping for this field.
-If I try with jerarquies for the only dimension I have, with a grand total level and a child level, selecting the lowest level for all tables, error is: "None of the fact tables are compatible with the query request "
Can anybody help me? I'm having nightmares with this issue.
Thanks a lot in advance.

Hi,
Okay. I assume you have the 2 facts:
Fact1: Orders
Order_Number - Q.Received - Supplier
1 - 10 - S1
2 - 10 - S1
Fact2: Invoices
Order_Number - Invoice_Number - Q.Inv.
1 - I1 - 2
1 - I2 - 8
2 - I3 - 10
create a business model with the following logical tables:
Order Dim,
QTY Received,
QTY Invoiced
drag/drop Order_number from Fact1 to the logical table Order Dim (this will create a logical column Order_number).
drag/drop Order_number from Fact2 to the logical COLUMN Order_number. (This will give you a second Logical Table Soruce with 1 logical table column.)
drag/drop Q.Received from Fact1 to logical table QTY Received
drag/drop Q.Inv. from Fact2 to logical table QTY Invoiced
Assign key to LT Order Dim
and draw Business Model Diagram.
This should give you the possibility to report the quantity received and invoiced per order number
Regards
Message was edited by:
wobiee1

Fact table is joining with Other table having values for measures

I have one Fact table named Fact1 where i am going to create some calculation measures based on the values in Table2.
How should be the physical join between them and the logical join.
Earlier we had those VALUES in Fact1 only
Why we created table Table2 is there was bit confusion for the aggregation in Fact1.
We are bit confused on whether to make Table2 as dimension or Fact as it is having some measures and not having the foreign keys
How we have to proceed now..!! Please help us!!?

I have one Fact table named Fact1 where i am going to create some calculation measures based on the values in Table2.
How should be the physical join between them and the logical join.
Earlier we had those VALUES in Fact1 only
Why we created table Table2 is there was bit confusion for the aggregation in Fact1.
We are bit confused on whether to make Table2 as dimension or Fact as it is having some measures and not having the foreign keys
How we have to proceed now..!! Please help us!!?

Unexpected results getting data from two fact tables through conformed dim

Hi all,
We are getting an unexpected behaviour in our OBIEE 10.1.3.3.3. We have this scenario:
We have {color:#0000ff}2 fact tables{color}{color:#000000} called F1 and F2. F1 has one measure, f1m1 and F2 has another one, f2m1.
We have {color:#0000ff}4 conformed dimensions{color}, called D1, D2, D3, Date.
When we are requesting for individual fact tables, we are getting:
date d1 d2 d3 f1m1
dt1 - x - y - z - m1
dt1 - x - y - z' - m2
date d1 d2 d3 f2m1
dt1 - x - y - z - m3
dt1 - x - y - z'' - m4
But, trying to obtain a compare scenario, we are getting
date d1 d2 d3 f1m1 f2m1
dt1 x y z m1 m4
Instead of
date d1 d2 d3 f1m1 f2m1
dt1 x y z m1 m3
Looking at query log, we have catched the reason. That's why BI Server is using to solve this request using ROW_COUNT() to join SAWITH0 and SAWITH1 in SAWITH2 result set. So, the order may not be the same in the results sets in every fact table. More or less, generated query is like:
WITH
SAWITH0 AS
(select ....
from F1),
SAWITH1 AS
(select ...
from F2),
SAWITH2 AS
select from (select ...
ROW_NUMBER() OVER PARTITION (....) c10
from SAWITH0.d1 full outer join SAWITH1.d1 ....) D1
{color:#ff0000}where (D1.c10 = 1){color}
select SAWITH2. ....
from SAWITH2
order by c1..c10
The problems seems to be that BI server is ordering the result sets SAWITH0 and SAWITH1 and getting row number to join this results sets, but this is not getting the correct result.
Any ideas?
TIA
Javier
{color}
Edited by: jirazazábal on Mar 13, 2009 2:46 PM

I have done a logical fact table with two fact table source on it.
The Sql performed against the database was this one.
-------------------- Sending query to database named PRODS_AIX (id: <<153418>>):
WITH
SAWITH0 AS (select sum(T21296.CONSUMERS_SALES_EURO) as c1,
     T21309.DIVISION_CODE as c2
from
     DIVISION T21309,
     C_CONSUMERS_SALES T21296
where ( T21296.DIVISION = T21309.DIMENSION_KEY )
group by T21309.DIVISION_CODE),
SAWITH1 AS (select sum(T21356.ORDER_VALUE) as c1,
     T21309.DIVISION_CODE as c2
from
     DIVISION T21309,
     DWH_SALES_ORDER_OVERVIEW T21356
where ( T21309.DIMENSION_KEY = T21356.DIVISION_KEY )
group by T21309.DIVISION_CODE)
select distinct case when SAWITH0.c2 is not null then SAWITH0.c2 when SAWITH1.c2 is not null then SAWITH1.c2 end as c1,
     SAWITH0.c1 as c2,
     SAWITH1.c1 as c3
from
     SAWITH0 full outer join SAWITH1 On nvl(SAWITH0.c2 , 'q') = nvl(SAWITH1.c2 , 'q') and nvl(SAWITH0.c2 , 'z') = nvl(SAWITH1.c2 , 'z')
order by c1As you can see one select (SAWITH0) for the first fact table C_CONSUMERS_SALES and one select for the second fact table DWH_SALES_ORDER_OVERVIEW (SAWITH1 ) and the two statement are joined with a full outer join.
I ask me why you have the three select (SAWITH0,SAWITH1 and SAWITH2). Can you please paste the complete SQL performed ?
Can you tell us also which SQL is performed if you select only the columns from one fact table and not for the other ?
Regards
Nico
http://gerardnico.com

No Fact Table Exists at the request level of Detail

Hi,
I'm new to BI.can anybody come across more than one fact table in BMM layer,currently i working with AP module,i am getting the error Error NO:14025 No Fact Table Exists at the request level of Detail.
Even i check with content tab where i have given detail level for confirming tables and total for non-confirming tables.
can any one have document related more than fact table in BMM layer, any body give me the right solution.
Thanks in advance !

thanks for your response,i did for the selected measures also. in Account payable model i have two fact.
F1 with dimension D1,D2,D3,D4
F2 with Dimension D5,D6,D7,D8
when i'm trying to generate reports F1 with D1,D2,D3,D4 i am getting the output,but with the non-conforming table D5,D6,D7 i am getting the error. can you give some document to work more than 1 fact table.

None of the fact tables are compatible error

Hi All,
I do see this error (none of the compatible fact table) after setting the content level aggregation on the dimension tables and the fact table. This error i get only when i try to pull the calculated item which is based on a attribute in the fact table. I have an attribute like year in the fact table i need to display like 'CY'||'2013' in a calculated logical column and when i pull this into answers i get this error -
1) joins are ok ; only one fact table and 3 dimension tables
2). content level on the fact table are specified at the detail level and also for the dimensions
any suggestions - thanks for your time

can anyone please provide some suggestions -
> i looked at the fact table LTS and specified the logical level for each dimension as the detail
> specified the LTS for each dimension table
> I have a column in my fact table which is calendar year and i want to have a derived column like rep_cal_year with 'CY'||cal_year - so when i pull this derived column in my answers i get the error - none of the fact tables are compatibile with the query;
what could be missign?

One fact table

Similar Messages

Maybe you are looking for