Problem: two fact tables and one conformed dimension

Hi everyone!
I need to solve this situation:
I have two fact tables, let's say F1 and F2, that are both linked to D1, my conformed dimension
I just need to select fields from D1 but I know that, when querying, OBIEE links it to a fact table anyway..how does it choose the fact table? That is, if I only want fields from D1, does the system queries also from F1 or F2? Is it a random choice?
Is there a way to "force" this choice, telling the system for example to choose only from F1?
Is there a workaround to solve this situation? Remember, I only need fields from D1.
Thanks!!

The solution of your problem is "Implict Fact Column"
Go to presentation layer and double click on your subject area. then you will see Implict fact column option. click on set. give corresponding fact column there( in your case give F1 fact column)
references: http://oracle-bi.siebelunleashed.com/articles/implicit-fact-column/
Thanks
GSR
Edited by: GSR on Mar 20, 2012 3:22 PM

Similar Messages

Best way to connect two fact tables when no conformed dimension exists

Can anyone please elaborate how would I connect two fact table without any conformed dimension. Let say FACTA, FACTB. FACTB is related to a dimension "StatusDim". I want to select the count of all FACTA item which are related to FACTB items with
a particular status. I have found the following article but just wondering whether it is the best practise to connect two fact tables directly.
http://bifuture.blogspot.com/2011/11/ssas-selecting-facts-with-reference.html
Thank you

Hi Ahsan,
After read the blog you posted, I think it's a pretty good solution to create a view in the relational database or a named query in the Data Source View containing as the the columns in FACTA and FACTB. Then build a dimension from it, setting the "Null processing"
property (you have to click the "plus" two times for the "Key Columns" property of the attribute in BIDS to access this property) to "UnknownMember". And then use this dimension for the many-to-many relationship. Dimensions from FactA can benefit of the reference
relationship between FactA and FactB and therefore a powerful solution it is.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Querying against two fact tables with non conformed dimension

I have two fact tables and I have this set up in RPD :
Fact1 joined to DimA and DimB
Fact2 joined to DimA
On Front end I build two analysis:
Analysis 1:
DimA.A, Fact1.1, Fact2.2
Analysis 2 :
DimA.A, DimB.B, Fact1.1, Fact2.2
In the results of Analysis 1 , I am seeing correct values for Fact2.2
In the results of Analysis 2, I am seeing Fact2.2 as empty column. I think the reason is that Fact2 is not joined to DIMB.
Is it possible that I should be able to report against both dimension tables (DIMA and DIMB) columns for FACT1 and FACT2 measures.... Even though I don't have join between DIMB and FACT2.
Any response would be helpful!!!
Regards,
Annu

Hi,
Go to the LTS-- Content Level of the fact which does not have join with Dimension and put Total level for that Dimension and total level on Column(Measure also)(Double click --Levels)(Assume Dim Hierarchy is already set up)
Pull everything(D1,D2,F1,F2) You will see results.
Update Me
Thanks
NK
Edited by: DNK on Mar 20, 2013 1:35 PM

Unable to join two fact tables via one common dimension in RPD(Repository)

I have created two fact tables F1 & F2 and one dimension D.
F1 is joined to D and F2 is also joined to D in Physical layer as well as in BMM layer.
I created one report in OBI Answers using these three tables.It Showed me the following error.
**Error Details**
**Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P**
**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 dfghdfh) does not contain mapping for [Dashboard_Fact.Period_Sgt_Key]. (HY000)**
**SQL Issued: SELECT dfghdfh.Period_Sgt_Key saw_0, "Period Dim".Period_Sgt_Key saw_1, Dashboard_Fact.Period_Sgt_Key saw_2 FROM service_delivery ORDER BY saw_0, saw_1, saw_2**
How to cope up with the issue or can anyone tell me the alternate workaround for this?

That is what i have tried.
I have made a logical table TEST and dragged two fact tables f1 & f2 in source.
Now when i drag different columns from different fact tables(that are in TEST logical table) in report, it gives an error and not making any joins that you are mentioning.
ERROR MESSAGE:--
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 Test) does not contain mapping for [Test.SurveyName_Id, Test.SurveyHead_Id, Test.Respondent_Id, Test.SDBusiness_Area_Id, Test.Period_Sgt_Key, Test.OBS_Id, Test.VOCBusiness_Area_Id, Test.Question_Sgt_Key]. (HY000)
The columns mentioned in the error message are all from test logical table..some are from F1 & some from F2.

Multiple 'logical joins' between a fact table and one dimension table

It appears that one cannot create multiple ‘logical joins’ between a fact table and one dimension table in OBIEE using the Oracle BI Administration Tool. For example, considering a Business Model with a dimension table TIMES and a fact table FACT containing START_TIME and END_TIME, we would like to create separate logical joins from FACT to TIMES for the START_TIMEs and END_TIMEs? Obviously, the underlying foreign keys can be created, but as far as I can tell the Oracle BI Administration Tool doesn’t support this. The workaround would be to replicate the TIMES table, but that’s ugly.
I seek an alternative approach.

Try this. Create an two aliases for the TIMES dimension (Start & End) in the Physical Layer and then remove foreign key to the "Parent" Times dimension. Create the Foreign Key in the Physical Layer to the new aliases and then create the complex joins in the BMM Layer to the new aliases as well. This will allow you to present both dates within the same table in the Presentation Layer. Not the most elegant solution but it works.

Something about two fact table in one subject

Hi all,
when I using two fact table in one subject, it can't make sense as expected.
The problem is describled as follows:
1.about the RPD:
In the presentation layer of Admin Tool, there is a mesure names "A", which is equal to B*C, come from table t1 and table t2 in logical layer respectively.
2. In biee Answeers, I created an answeer which includes some dimesions and the mesure A, another mesuare m1.
but in the the result pane, i saw there is no data in the the colume of mesure A, all other performs well.
3. so, I went for the NQquery for the phisical SQL, and found that,
in Where clause, table t2 is lost.
why? and how can I make it?

This sounds interesting. What would I join there? The dimension keys of the two fact tables?
Unfortunately this Logical Table Source stuff looks quite different in Admintool 11g. What would I need to create there?
Thanks,
Knut

Again: two facts and one conformed dimension

Dear all,
I know this has been asked quite often but I haven't found a solution for my problem here. Believe me I have done a lot of searching across the net ..
What I want to do is the following:
I have two fact tables with a number of common dimensions. A report should show the two facts across these common dimensions.
To keep it simple I start with only one common dimension.
Here's what get's to the db from OBIEE:
*SELECT Revenue."Date (YYYYMMDD)" saw_0, Sales."Day Day Code" saw_1, Revenue."TPV (Total Payment Volume in Millicent [€])" saw_2, Sales.DEBIT_AMOUNT saw_3 FROM "Company KPIs" ORDER BY saw_0, saw_1, saw_3*
Note that *Revenue."Date (YYYYMMDD)"* and *Sales."Day Day Code"* are the same field from the common time dimension. I just put them in different presentation tables for the end users.
TPV and DEBIT_AMOUNT are facts from the two different cubes.
Everything fine, right?
Now I look at the nqquery.log:
RqList
Dim Time.Day Day Code as c1 GB,
Dim Time.Day Day Code as c2 GB,
*Tpv:[DAggr(Cube Revenue.Tpv by [ Dim Time.Day Day Code, Dim Time.Day Id, CUBE_SALES.DEBIT_AMOUNT] )] as c3 GB,*
CUBE_SALES.DEBIT_AMOUNT as c4 GB,
Dim Time.Day Id as c5 GB
OrderBy: c1 asc, c2 asc, c4 asc
now the bold thing looks odd to me. Is he trying to aggregate one cube based on the other? Could be the problem, but where to influence this?
And finally this translates into this query:
WITH
SAWITH0 AS (select distinct T4110.DEBIT_AMOUNT as c1,
T281.DAY_DAY_CODE as c2,
T281.DAY_ID as c3
from
DIM_TIME T281,
CUBE_SALES T4110
where ( T281.DIMENSION_KEY = T4110.DIM_TIME ) ),
SAWITH1 AS (select distinct SAWITH0.c2 as c1,
SAWITH0.c2 as c2,
*cast(NULL as DOUBLE PRECISION ) as c3,*
SAWITH0.c1 as c4,
SAWITH0.c3 as c5
from
SAWITH0)
select SAWITH1.c1 as c1,
SAWITH1.c2 as c2,
SAWITH1.c3 as c3,
SAWITH1.c4 as c4
from
SAWITH1
order by c1, c2, c4
As you see, the tpy ist gone and a NULL appears. That's what I see in the report. TPV is always NULL.
So where did I miss a configuration ???
Thanks, Knut

You only need to set the content levels on the measures themselves when you want non-conformed dimensions in the report, as your working with fully conformed dims just make sure your levels are set on the content tab for each Logical Table source in the Logical fact table. Leave the non-conformed dim hierarchies as blank.
Remember - You should put a hierarchy on each logical dim , even if there is no real hierarchy, just have a total -> Detail.
You should always always always set your content levels for logical table sources, both in Dimensions and Logical fact LTS's.
If they are greyed out, make sure your not in read only, have checked the object out if on-line mode, failing that, perform the changes off-line then re-start your BI Server.

Two fact tables in one business area

Hi,
Would there be problem if two fact tables, one flat, one with hierarchy, in one business area. Both fact tables are joined to same set of dimension tables except one: region_1 to fact_1, region_2 to fact_2. The consistency check is fine. But I get error in Answers. I don't have the exact error with me, but it is complains about fact_1 is not linked region_2.
Any suggestions ?
Thanks.

Thank you, Stijn, Ced for your kind reply.
I did not explain it clearly.
The fact_1 (flat) table has data in all levels (detailed and aggregated). For example, it has % sales to planned from city, state to national (we were not provided with numberator and demoninator to aggregate the detailed data). The fact_2 table has only city level data and have a dimension region_2 with city, state and national hierarchy. For data in Fact_1 table, we simply want to show them in reports. For data in Fact_2 table, reports can drill-down.
In Answers, the error is "Incorrectly defined logical table source ( for fact table Fact_1) does not contain mapping for region_2.state_id".

Modelling 2 Fact Tables with Non-Conforming Dimension in OBIEE 11g

Hi all,
I have two fact tables (Fact 1 and Fact 2) and two dimension tables (Product and Rule). The Product dimension table is a conforming dimension and is used in both fact tables, but the Rule dimension is a non-conforming dimension which is used only one fact table. I'm using OBIEE 11g (11.1.1.6.0).
====
Fact 1
====
Sales ID | Product ID | Quantity | Sales Description | Sales Status
S001 | P001 | 100 | bla bla bla bla bla | N
S001 | P002 | 200 | bla bla bla bla bla | N
S002 | P001 | 200 | lab lab lab lab lab | Y
S002 | P003 | 250 | lab lab lab lab lab | Y
Notes for Fact 1:
- One Sales ID can have multiple Product IDs
- Sales Description and Sales Status are the same for one Sales ID (repeating Sales Description and Sales Status for the same Sales ID)
====
Fact 2
====
Sales ID | Product ID | Rule ID | Score
S001 | P001 | R001 | 2
S001 | P001 | R002 | 3
S001 | P002 | R003 | 1
S002 | P001 | R003 | 1
S002 | P003 | R002 | 2
S002 | P003 | R004 | 5
Notes for Fact 2:
- One combination of Sales ID and Product ID can have multiple Rule ID
I'm wondering how best to model these tables so that I can create this report (number of the dimension and fact tables created in the business model, level mapping, aggregation rule, etc)? Any suggestion/advice on how to achieve this?
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID | Score
S001 | P001 | 100 | bla bla bla bla bla | N | R001 | 2
S001 | P001 | 100 | bla bla bla bla bla | N | R002 | 3
S001 | P002 | 200 | bla bla bla bla bla | N | R003 | 1
S002 | P001 | 200 | lab lab lab lab lab | Y | R003 | 1
S002 | P003 | 250 | lab lab lab lab lab | Y | R002 | 2
S002 | P003 | 250 | lab lab lab lab lab | Y | R004 | 5
Thank you very much!

Hi Dhar, thanks for the suggestions.
I tested what you suggested, but the result is not as per my expectation mentioned above. Here's what I did:
1. In physical layer:
- I joined Fact 1 table with Product dimension table only
- I joined Fact 2 table with Product and Rule dimension tables
2. In business model layer:
- I created 3 logical tables: Fact, Product, and Rule
- The Product table contains the Product ID and Product Name from the Product dimension table in the physical layer
- I created the hierarchy (logical dimension) for Product with only ProductTotal level (as the grand total level) and ProductDetail level that contains Product ID and Product Name
- The Rule table contains the Rule ID and Rule Name from the Rule dimension table in the physical layer
- I created the hierarchy (logical dimension) for Rule with only RuleTotal level (as the grand total level) and RuleDetail level that contains Rule ID and Rule Name
- The Fact table contains 2 logical tables sources: Fact 1 (which logical level in the Content tab is mapped to ProductDetail and RuleTotal) and Fact 2 (which logical level in the Content tab is mapped to ProductDetail and RuleDetail)
- The Fact table contains Sales ID logical column (mapped to both Fact 1 and Fact 2 logical table sources)
- The Fact table also contains Sales Description and Sales Status logical columns (mapped to only Fact 1), which aggregation rule is the default to None
- The Fact table also contains Quantity logical column (mapped to only Fact 1), which aggregation rule is set to Sum
- The Fact table also contains Score logical column (mapped to only Fact 2), which aggregation rule is set to Sum
OBIEE returns the expected result when I retrieve the report:
Sales ID | Product ID | Quantity | Sales Description | Sales Status
However, OBIEE returns an error when I retrieve the reports:
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID
or
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID | Score
The error is:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14020] None of the fact tables are compatible with the query request FACT.SALES_STATUS. (HY000)
And the Score column is blank when I retrieved this report:
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Score
Any suggestion anyone? Please help. Thanks a lot!
Edited by: stewartlife on Nov 29, 2012 4:01 PM

Confirmed Dimensions. OBIEE Not able to pull data from two fact tables.

Hi Experts,
I have a very simple set up of Star Schema with two fact tables and 1 dimension. Both fact tables joined to the dimension at the same level.
When i pull a column from both fact tables and the dimension table in OBIEE, it has to create simple SQL like below:
select FACT1.column1,
Fact2.Column1,
Dim.Column1
from FACT1, FACT2, DIM
where FACT1.ID = DIM.ID and FACT2.ID = DIM.ID
but instead it creating a query in a very complex way:
select case when D1.c2 is not null then D1.c2 when D2.c2 is not null then D2.c2 end as c2,
     D1.c1 as c3,
     D2.c1 as c4
from
     (select FACT1.Column1 as c1,
               DIM.Column1 as c2
          from
               DIM T1287863,
               FACT1 T1287945
   where (DIM.ID = FACT1.ID)
       ) D1 full outer join (
        select FACT2.Column1 as c1,
               DIM.Column1 as c2
          from
               DIM,
               FACT2
          where ( DIM.ID = FACT2.ID)
     ) D2 On isnull(D1.c2 , '1') = isnull(D2.c2 , '1') and isnull(D1.c2 , '2') = isnull(D2.c2 , '2')
I even tried setting the levels for both the fact tables and it still creates the query in avove way. Any thoughts on this will be vary helpful.

Subramanian,
see below the code we're using for the RFM.
on the ct_containers table i'm passing a line, and its getting updated after the call.
on the ct_errors table i just want to receive the errors and i only receive the line, we add manually there ('Serious error with validation code').
kr, achim
FUNCTION zbapi_ra_validations .
*"*"Local Interface:
*" IMPORTING
*"     VALUE(IS_RA_SCREEN) TYPE ZBAPI_S_RA_SCREEN
*" CHANGING
*"     VALUE(CT_ERRORS) TYPE ZRA_T_ERRORS
*"     VALUE(CT_CONTAINERS) TYPE ZRA_T_CONT_IP
DATA:
    lo_badi_handle TYPE REF TO zra_validation_rule,
    ls_error       TYPE zra_s_error.
GET BADI lo_badi_handle.
TRY.
      CALL BADI lo_badi_handle->validate_rules
        EXPORTING
          is_screen_flds = is_ra_screen
        CHANGING
          ct_containers = ct_containers
          ct_errors      = ct_errors.
    CATCH zcx_ra.
      ls_error-message = 'Serious error with validation code'.
      APPEND ls_error TO ct_errors.
ENDTRY.
ENDFUNCTION.
if i call this rfm in SE37 the ct_errors table is populated with all errors and the manually created line.
Message was edited by: Achim Hauck

Filter and non-conforming dimensions

I have a model design which includes three fact tables with non-conforming dimensions. This causes BI to create multiple queries for a report and finally bring the results together using a full outer join at the end. When I attempt to filter on a field from one of the non-conforming dimensions, that filter is not applied at the full outer join step but during an earlier step related to the chosen filter field. This results in more data returning then desired. I need to move the filter to the full outer join step. Here are two sub-optimal methods that I have found to work around the issue.
1. Build the logical query in answers. Then, wrap that query with an outer query and apply the filter to the outer query.
2. Build a minus query in answers that removes the records you don't want to see.
I have seen this issue discussed in other threads, but I haven't found a good solution. Does anyone have any recommendations?
Thank you,
Edited by: user10715047 on May 21, 2010 7:13 AM
Here is a decent description of the problem
http://siebel.ittoolbox.com/groups/technical-functional/siebel-analytics-l/two-fact-tables-and-nonconforming-dimensions-3297052
and this is a better solution than the two I stated above. However, even this solution is not going to be very intuitive for the users
http://siebel.ittoolbox.com/groups/technical-functional/siebel-analytics-l/two-fact-tables-and-nonconforming-dimensions-3298529

i know this is a bit old thread but thought it might be helpful to someone who came across the same issue...
when using Degener@teDimen$ion ( this is !nner joned to FACT tables in BMM) and if any of the dimensions {other than theDegener@teDimen$ion (Let us say Dim X) } have an ()uter join to any of the fact tables, and you were doing your analysis using Degener@teDimen$ion, Dim X, Measure value you will face the following issues.
when filtering the analysis on the ()uter join dimension ( Dim X), the IN filter will not work. Reason is that the filter is getting applied to both the Dimension and FACT tables and the values that exist in Dimension Dim X but not in FACT table wont show up.
The above issue can be fixed by changing the join between the fact and Degener@teDimen$ion from inner to outer.
Please mark if you found this helpful.

How to combine multiple fact tables and dimensions in one worksheet?

Hello Forum,
I am encountering a reporting problem when trying to create a worksheet that uses more than one cube/fact table and common dimensions. 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 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 day from my time dimension, everything looks good at the stage, we're just trying to get a sum of all sales for that store on that day. 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 measure from the second fact table (advertsing costs)...... any help would be appreciated

You have encountered one of the key limitations of Discoverer... which I complained about to the Discoverer product manager at OpenWorld in 2001....
Anyhow, to get around this, you are going to have to deal with it either in the database, (views, materialized views, tables), or within the admin tool by creating a custom folder.
Discoverer also calls this the "fan trap", but never really had a solution to the problem. [The solution only worked is you joined to one and only one dimension!]
What you want (using Sales_Fact and Inventory_Fact as an example) is to join Sales to Time, Store, and Product, and save that result. Then join Inventory to Time, Store, and Product, save that result, then do a double outer join between the two intermediate temporary tables in order to calculate something useful like inventory turns by store and product line.
This is also known a "multipass SQL", and is supported by some (but not many) other tools.
So, to accomplish this with Discoverer, you'll either need to create a view, or table, or materialized view that has already put Sales and Inventory into a single (virtual?) fact table. Alternatively you can write the SQL for how to do this linkage (don't forget to handle missing data), and use the Discoverer admin tool to create a custom folder that uses your SQL.
Hope this helps!

One DIMENSION, Two FACT Tables - One WEEKLY grain, one DAILY grain

All the OBIEE gurus, thanks for checking out this post.
Background: We have a common DIMENSION referencing two FACT tables having different granularity.
DIM = Customer Dim
FACT = Forecasting (Weekly granularity)
FACT = Sales (Daily granularity)
There is a need to report from the Customer Dimension table AND access the Forecasting FACT (weekly grain) & Sales FACT (daily grain).
Example of query is listed below:
Give me customer = 'ABC' and the forecast and sales for a specific time period.
What will be the best way to handle something like this? I have seen examples of handing multi-fact table access in OBIEE but the granularity of both the FACT tables is different (weekly vs. daily).
Any help with an example is greatly appreciated.
Thanks,
Sunshine

Hi.
This one:
Joining different level aggregation measures together into a single logical fact table
http://108obiee.blogspot.com/2009/07/joining-different-level-aggregation.html
Regards
Goran
http://108obiee.blogspot.com

Two FACT Tables, Some Common and Non-Common Dimensions

Hello all, a question i am sure you have faced in the past but still wanted to get your feedback.
I have a few FACT tables and some dimensions that are shared (common dimensions). Rest of the dimensions are related to one or the other FACT tables.
What is the best way to present a view where users can pull information from both the FACT tables?
I am successful in pulling the shared (common) dimensions across BOTH FACT tables having the same grain but this view breaks down when i pull information from one Dimension that has not much to do with the other FACT.
What is the best way to present this? Should this be broken in three subject areas?
Subject Area 1 --> Some Dims --> FACT Table A
Subject Area 2 --> Some Dims --> FACT Table B
AND
Subject Area 3 --> ***Only Common Dims*** --> FACT Table A & FACT Table B?
Your feedback is always appreciated.
Regards,
Edited by: user10679130 on Oct 12, 2009 3:27 PM

Please check the forum first for similar threads/questions.
Joining two fact tables with different dimensions into single logical table
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
This solution keeps both fact tables in the same subject area in the single logical fact table, with common and not-common dimensions.
Regards
Goran
http://108obiee.blogspot.com

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

Problem: two fact tables and one conformed dimension

Similar Messages

Maybe you are looking for