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".

Similar Messages

  • 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

  • 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.

  • 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

  • Joining two fact tables for subject area

    When I tried to use two simple fact tables joined by a dimension, I am getting the “ No fact table exists at the requested level of detail” error in the answer when I try to pull the columns from Fact 1 and Fact 2 tables. I have set the content in both the fact table to lowest granularity of dimension with CUST_ID, RAT_ID, ACT_ID keys. We have one to many relationships between dimension and both the fact tables. Any feedback is highly cherished.
    Fact1: keys are: CUST_ID, RAT_ID, ACT_ID, YEAR
    Fields are CUST_ID, RAT_ID, ACT_ID, YEAR , Rev1, Transaction Date
    Fact2: keys are: CUST_ID, RAT_ID, ACT_ID, YEAR
    Fields are CUST_ID, RAT_ID, ACT_ID, YEAR , Rev2, CreationDate
    Dimension keys are CUST_ID, RAT_ID, ACT_ID
    Thanks,
    uday

    Hi LC,
    We have to add two fact tables F1 AND F2 to an existing bmm. These fact tables have history tables F11 AND F22 and we have to use partition logic for this.How you did partition ? you should be using Fragmentation logic for that any how you will add the F11/F22 tables to F1 and F2 LTS , so when you join F1 & F2 to the common dimension then it should work for the calucluated measures but dont forgot to create hierarchies and specify the content levels for the fact tables
    Thanks,
    Saichand

  • 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

  • Proper use of one table in different business areas

    Hi
    We will be using certain DB tables in several business areas and we are more than one person to define them.
    If a table is loaded from the database for each of the business areas it will be numbered 'table 1, 2...' which does't seem very desirable. Also I'd rather define hiearchies only once and for all.
    If a table is loaded only once and used for all the business areas all the joins which are necessary in the different business areas are shown. This will be confusing. If one of us considers a certain join unnecessary he might accidentially delete the wrong one belonging to a different business area.
    Exporting the business areas including the joins regularly is probably not a great help if afterwards new joins for other business areas were added.(?)
    Am I misunderstanding the concept of Discoverer?
    How do you handle such a situation?
    Advice appreciated
    Franziska

    Hi Michael, et al,
    I'm just planning my EUL and your comments in the last post seem relevant.
    My general plan is as follows:
    (1) Create a BaseMaster BA which is used to bring and tables/views from the database into disco. The folders in here will be created with "New Folder from database" and be fairly straightforward, with only very simple calculations and no aggregations in calculations. The joins will echo the joins in the underlying database. This is not shared with Users.
    (2) Create a CustomMaster BA which contains Custom Folders which consist of various SQL views of the database. The SQL in these may use have some more complex calculations and these calculations may include aggregation. This will not be shared with users.
    (3) Create a CentralMaster BA which contains Complex Folders which are assembled from items from the BaseMaster BA and the CustomMaster BA. These folders may include more complex calculations and the calculations may include aggregated items.
    (4) Create a number of User BA's. Using Manage Folders, share the relevant Folders from the Central Master.
    I've got a few questions relating to this.
    (a) Custom Folders based on Folders
    It would seem nice to me if it were possible to create Custom Folders which were based on other Folders, rather than Database Views. Then, even if you need a view and a complex transformation of that view in your business area, you still only have one place where the EUL brings that view into disco. My understanding is that this is not possible. Am I right? I suppose there could be an argument that complex transformations should be pushed back to the DBA but it seems reasonable to me that sometimes this sort of thing could be within the remit of the disco admin?
    (b) SQL Efficiency
    Am I right in thinking that generally a complex folder is usually not much less efficient than using a base folder because the SQL interpreter ends up optimising the SQL?
    And a last question which has turned out rather complex - by all means ignore it if you like - it's me getting to grips with the process.
    (c) Nested Complex Folders
    I presume that if a transformation is needed which would in a normal database environment would need a mainquery and a subquery, then this could be done in a
    number of ways (adhering to the above methodology) by:
    (i) Get the DBA to write a view which does both mainquery and subquery and then bring into the BaseMaster and then straight into the CentralMaster folder.
    (ii) Get the DBA to write the subquery, bring this into the BaseMaster and then implement the mainquery in the CentralMaster.
    (iii) Create a Folder in CustomMaster which implements both mainquery and subquery and then bring this into the CentralMaster folder.
    (iv) Create a Folder in the CustomMaster which implements just the subquery and then implement the main query in the Central Master.
    If you've got this far - thankyou for baring with me.
    Perhaps there's something written about this sort of thing or maybe it's just a matter of practice!
    Any thoughts on all this would be much appreciated.
    Kind regards
    Suhada

  • Problem querying over two fact tables

    The business requirement is that we want to be able to see sales for two different periods of times, over different brands, different Items' years and seasons per periods.
    So for the different dimensions I created alias having two tables in the physical layer
    for Brands, Shops and Items (tables) [These are the tables where I query for different brand, Item's year and different season]. The Business Model Schema looks like this:
    Items-----> SALES <------Brands Items 2-----> SALES 2 <------------Brands 2
    ^ ^
    TIMES TIMES 2 (TIMES JOINED WITH SALES AND TIMES 2 WITH SALES 2)
    and VENDORS connected to both SALES & SALES 2 left outer joined
    The need is that I need to query over two indepedent periods of time with independed dimensions but for a common dimension (Vendors).
    The presentation data simplified looks like this:
    Answers
    Vendor Sales Qty Sales 2 Qty
    1092 234 123
    The problem is that when a vendor doesn't exist in one period it doesn't come and in the other although there are sales. So when I query with the same filters (same period of time, Brands, Items' years and seasons) over these two fact tables I get the same sales and correct data. When there are different criteria then I lose data.
    The Query fired in the database is the following:
    select distinct case when D2.c4 is not null then D2.c4 when D1.c4 is not null then D1.c4 end as c1,
    D1.c3 as c4,
    D1.c1 as c5,
    D1.c2 as c6,
    cast(D1.c2 / nullif( D1.c1, 0) * 100 as DOUBLE PRECISION ) as c7,
    D2.c3 as c8,
    D2.c1 as c9,
    D2.c2 as c10,
    cast(D2.c2 / nullif( D2.c1, 0) * 100 as DOUBLE PRECISION ) as c11
    from
    (select sum(T43161.amnt_1) as c1,
    sum(T43161.mk_1) as c2,
    sum(T43161.qty_1) as c3,
    T7120.VE_NAME as c4
    from
    VE04_TBL T7120,
    GE04_COMPANY_TBL T43802,
    EI04_TBL T6931,
    Salesmcost T43161
    where ( T6931.EI_CODE = T43161.ei_code and T6931.VE_CODE = T7120.VE_CODE and T6931.GE_COMPANY_CODE = '1' and T6931.EI_SEASON_CODE = 'Χ' and T6931.EI_YEAR = '2009' and T7120.GE_COMPANY_CODE = '1' and T7120.VE_CODE = T43161.ve_code and T43161.ge_company_code = T43802.GE_COMPANY_CODE and T43802.GE_COMPANY_NAME = '*** Φ. & Κ. ΛΕΜΟΝΗΣ ΑΕΒΕ ****' and T43802.LIST_ITEM_IND = '1' and T43161.trans_date >= ADD_MONTHS(TO_DATE('2010-05-12' , 'YYYY-MM-DD'), -7 * 12 ) and T43161.trans_date between TO_DATE('2009-01-01' , 'YYYY-MM-DD') and TO_DATE('2009-01-31' , 'YYYY-MM-DD') )
    group by T7120.VE_NAME
    ) D1,
    (select sum(T44099.amnt_1) as c1,
    sum(T44099.mk_1) as c2,
    sum(T44099.qty_1) as c3,
    T7120.VE_NAME as c4
    from
    EI04_TBL T44615 /* EI04_TBL 2 */ ,
    VE04_TBL T7120,
    GE04_COMPANY_TBL T43802,
    Salesmcost T44099 /* Salesmcost_2 */
    where ( T7120.VE_CODE = T44099.ve_code and T7120.VE_CODE = T44615.VE_CODE and T7120.GE_COMPANY_CODE = '1' and T43802.GE_COMPANY_CODE = T44099.ge_company_code and T43802.GE_COMPANY_NAME = '*** Φ. & Κ. ΛΕΜΟΝΗΣ ΑΕΒΕ ****' and T43802.LIST_ITEM_IND = '1' and T44099.ei_code = T44615.EI_CODE and T44615.GE_COMPANY_CODE = '1' and T44615.EI_SEASON_CODE = 'Χ' and T44615.EI_YEAR = '2008' and T44099.trans_date between TO_DATE('2008-01-01' , 'YYYY-MM-DD') and TO_DATE('2008-01-31' , 'YYYY-MM-DD') )
    group by T7120.VE_NAME
    ) D2
    where ( D1.c4 = D2.c4 ) /*<------- I think that this join creates the problem*/
    order by c1
    Edited by: user1198434 on 12 Μαϊ 2010 5:14 πμ
    Edited by: user1198434 on 12 Μαϊ 2010 5:41 πμ

    Hi,
    go through this
    http://obiee101.blogspot.com/search/label/OUTER%20JOIN
    I think you are new to the forum. try searching through some of the famous obiee forums. Gurus have already covered most of the issues. few are,
    http://obiee101.blogspot.com
    http://oraclebizint.wordpress.com/
    http://gerardnico.com/weblog/
    http://108obiee.blogspot.com/
    thanks,
    karthick

  • Joining two fact tables with different dimensions into single logical table

    Hi Gurus,
    I try to accomplish in Oracle Business Intelligence 11.1.1.3.0:
    F1 (D1, D2 and D3)
    F2 (D1 and D2 and D4)
    And we want to build a report F1 F2 D1 D2 D3 D4 to have data for:
    F1 that match only for D1-D2-D3
    and data for
    F2 that match only D1-D2-D4
    all that in one row, so D3 and D4 are not common dimensions.
    I can only do:
    F3 (D1, D2)
    F4 (D1, D2 and D4)
    And report
    F3 F4 D1,D2,D4 (all that in one row, and only D4 is not a common dimension)
    Here is the very good example how to accomplish the scenario 1
    http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
    But looks like it does not work in 11.1.1.3.0
    I get
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 14025] No fact table exists at the requested level of detail: [,,Clients,,Day,ROI,,,,EW_Names,,,,,,,,,,,,,,,,,]. (HY000)
    I am sure I set up everything correctly as advised in the blog but it works with only one not a common dimension
    Is it a bug in 11.1.1.3.0 or something?
    Thanks,
    Kate

    Thanks for all your replies.
    Actually, I've tried the solutions you guys mentioned. Generally speaking, the result should be displayed. However, my scenario is a little bit tricky.
    table Y's figures are not the aggregation of table X for D dimension. Instead, table Y's figures include not only D dimension total, but also others (others do not mean A, B, C dimension). For example, table Y stores all food's figure, while table X stores only drink's figure. D dimension is only about drink's detail. In my scenario, other foods' figure is not provided.
    So, even if I set D dimension to all/total for table X, table X's result is still not the same as table Y.
    Indeed, table Y does not have a column key to join to D dimension's key. So, if I select D dimension and table Y's measures at the same time in BI Answer, result returns no data. Hence, I can't compare table X and table Y's results with selection of D dimension.
    Is there any solution to solve this problem?
    Edited by: TomChan on Jun 3, 2009 9:36 AM

  • Mutiple fact tables for one report?

    HI
    I have two fact tables like Shipment and Sales. They each have their own star schema but most of the dimension tables are very similar. In one report I have to combine the two fact tables. so my report would have something like date, product Shiptment and Sales.
    What is the best way to set this up as shipment and sales have their own fact tables but the dimension tables that are being used in this report are common?
    Do i do this in the Physical layer of the rpd and how?

    you need to work in BMM layer for this..
    In one of your business models where there is Sales Fact Table... bring the shipment Fact Table from the physical layer onto this buisness model , and do a complex join to the Time dimension (common dim)...
    Now Bring this Shipment Fact Table from that buisness model to the Presentation Layer under the same Subject Area ( ie now a single Subject Area must have both the Fact Tables under it...
    Bounce back ur servers...
    Now you are good to go...

  • Problems working with different types of aggregation in two facts table

    Hello every Body!! Greetings from Brazil..
    At fisrt I'd like to say that I've tried to find some thead with the same problem, but I've foud no answere. That is why I'm typing this new post.
    Here we go ...
    I've a Fact table with one metric and two degenerate dimensions..
    For exemple:
    Invoice_number
    Puschase_Date
    Purchase_Value$
    When I model it at Business Model Mapping, I used the Aggregation's type below:
    Invoice_number - None
    Puschase_Date - None
    Purchase_Value - Sum
    So far it works fine at Answeres area.. Since I use only values from this Fact..
    But... if I try to join values from two different Facts Table (both of them sharing the same Dimensions) and the Second Fact has an aggregated value, it does'nt work... I get 'null' as values (metrics) of the second Fact Table...
    I think that it is caused because I'm working whith different types of aggregation, but I don't know the solution.
    By the wat, the second Fact I've told has only one metric, aggregated whith 'SUM'.
    Is there a solution? Any hint?
    Tks.
    Vettore

    int x = (int)(7 + 3.0 / 4.0 * 2); //the variable will do the math bracket first. then the va type will still be an int because int was never changed.
    Following the standard order of operations, 3.0/4.0 will result in a double, then 2 will be converted to a double before being multiplied to the result, then 7 is converted to a double before being added to the result, and then the (int) cast will force a conversion
    back to an int.
    Console.WriteLine((1 + 1) / 2 * 3); // 1 + 1 will be done first then 1 / 2 then * by 3
    Correct.
    I THINK THATS ALL WRONG ^ =/ like the comments
    Why?

  • How to create a ROLAP Cube that has two fact tables.

    I want to know if it is possible to create a ROLAP Cube with two fact tables.
    Suppose that I have these two star schemas:
    The first star schema has only a measure and a time dimension. The time dimension has three levels (Year -> Month -> Day)
    The second star schema has the same measure of the first schema and a time dimension. In this schema the time dimension has only two levels (Year -> Month). The values of the measure of this schema come from the first schema, this is, the value of the measure for a defined year and month results of the sum of all fact values of the first schema, that have the same year and month.
    I want to know if is possible to create a ROLAP cube that can get the information of the two star schemas, according to the level that the user are consulting.
    For example, if the user consults the cube with "OracleBI Spreadsheet Add-In", and if the user is consulting the first two levels (Year and Month), then the ROLAP cube would get the information of the second star schema.
    But if the user does a drill down in a month to get information of the days, then the ROLAP cube would get the information of the first star schema.
    Is it possible to do this?
    Regards,
    Rui Torres

    I'm not exactly sure what you want to do. Sorry if I get this wrong.
    You have two fact tables, one with data values at the day, month and year levels and a second fact table with data values at just the month and year levels. If this is the case, in the CWM2 APIs or OWB Paris, you would create a view that joins the two tables together and then map this view to the ROLAP cube.
    For CWM2 details, please refer to the Oracle OLAP Reference.

  • 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

  • Bridge Table between two fact tables

    Hello everybody,
    From what I have read on the BI Administration tool help and on this forum, bridge tables are used to define many-to-many relations between dimension sand fact tables. Is it possible to have a bridge table defining a many-to-many relation between two fact tables?
    Here is my senario:
    1. We have a fact table called fact_Orders describing orders for some products.
    2. We have a fact table called fact_Sales describing sales og these products.
    3. We have a table describing the transformation from order lines to sales lines which is a many-to-many relation, because it is possible to transform an order in more than two steps.
    I was thinking of connecting the two fact tables with a bridge table.
    If bridge tables are inappropriate for this case, what could be a better model for my senario?
    Thanks for your time.

    Hi,
    Well a conformed dimension is a bridge table between two facts, so not sure why you need anything else. If there is a one to many from D1 to F1 and a one to many from D1 to F2 then effectively there is a many to many join from F1 to F2 through the D1 dimension.
    Sounds to me like all you need is an order dimension table, rows in the orders fact table will join to this dimension and so will rows in the sales fact table. You can then do calculations like number of sales per order, total sales revenue per order, # of order items per order etc etc.
    Regards,
    Matt

  • 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

Maybe you are looking for