Multiple Facts and Join Paths

If you have multiple fact sharing the same dimensions is there a way to force the default Fact join path when pulling in only Dimensions? For instance pulling in Dashboard Prompts and using the Constrain - I pull in a few Dimensions and it obviously has to use the Fact table for the constaint, however, it is not using the one I am utilizing in the report. Thanks!

Yes, this functionality is called "Implicit fact", which means that this fact measure always be used when you run the query.
How to do this:
1) Create a measure on the fact table you want to create the join on.
2) In the presentation layer, go to the subject area and add this measure as the implicit fact.
3) Test it. Go to answers create a "dimension-only" report. Run the report and check the SQL to see whether the fact table is used.
Regards,
Stijn

Similar Messages

  • Join multiple facts and dimensions for reporting issue

    Hi,
    I have a report requirements and need to use multiple fact tables and unconformed dimensions as described below
    Fact table: F1,F2,F3
    Dimensions tables: D1.....D9
    F1:(joined to) D1,D2,D3,D4
    F2::(joined to)D1,D2,D5,D6
    F3::(joined to)D1,D2,D7,D8
    D7::(joined to)D9,D8 (dimension D7 joined to two other dimensions D9 and D8
    I'm trying to use columns from almost all the fact and dimension tables but getting "Unable to navigate requested expression. Please fix the metadata consistency warnings."
    Repository is consistent and no errors and warnings.
    How can I configure the repository to develop reports using all fact tables and dimensions?
    Appreciate for your help.
    Thanks
    Jay.

    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

  • 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

  • Multiple facts and dimensions

    Hi Guys,
    If you help me for this question that would be really great.
    dim1, dim 2
    fact1, fact2 and fact 3
    dim 1 having join with fact 1
    dim 2 having joing with all facts
    so, i want to have a report on dim1, fact2 and fact 3.
    Please let me know how I can track using these dimensions and fact tables. If i would create one logical table and include all dim1, dim 2 and 3 facts then is it work right.
    Regards,
    Shaik

    You are trying to build a report with out joins between DIM & FACT. Overall you would like to know approach how to generate reports with multiple facts & dimensions.
    Let take your scenario D1 -> F1, D2->F1,F2,F3
    Now I want to generate report D1,D2,F1,F2,F3. Here D1,D2 are joined to the fact then there is no pblm. But F2,F3 are not joined to the D1.So we need to exclude D1 JOIN WITH F2 & F3 during runtime. To do that
    1. Create hierarchies for D1,D2
    2. In the contenct tab for set level for F2,F3 as TOTAL FOR D1 which eliminates the join between them during runtime

  • Inserting in multiple tables and joining data

    I am using DW8, PHP and MySQL.
    I've created a database for software inventory. One table is
    a list of software products and the other is the licensing
    information. I set it up this way because we have a product such as
    Windows XP that will have different licenses. But the end result
    will be someone clicking on Windows XP and seeing all licenses for
    that product.
    I've created a page to insert into the software table and one
    for the licensing information. Now I need to make a third page so
    that the user can select the product from a dropdown menu and then
    enter the licensing information. I have join setup between the
    tables in the MySQL backend. How do I tell Dreamweaver that the
    license being entered is related to the correct product?
    Thanks!

    Nevermind, I figured out how to do this.

  • Multiple fact - outer join

    Hi all,
    let's say that I created two facts
    1) ALL_RELATIONS_FACTS: two dimensions
          d1: START_POINT
          d2: END_POINT
    START_POINT  END_POINT
    1            2
    3            4
    1            3
    A row in this fact means that the relationship exists, not all relationships will be measured
    2) ALL_MEASURE_FACTS: three dimensions
          d1: START_POINT
          d2: END_POINT
          d3: DATE
          MEASURE1
          MEASURE2
    START_POINT  END_POINT  DATE       MEASURE1    MEASURE2
    1            2          20121023   100         200
    3            4          20121023   300         400
    A row in fact gives us measures on a certain date for a certain relationship.Now I would like to merge these two facts (with an OUTER JOIN).
    START_POINT  END_POINT  DATE       MEASURE1    MEASURE2
    1            2          20121023   100         200
    3            4          20121023   300         400
    1            3          20121023Could someone point me to a standard solution?
    Riccardo

    I don't get why you are telling me "ONE" confirmed dimension.
    My current BMM is
      ALL_RELATIONS_FACTS
        |           |
    start_point   end_point
        |           |
        D1         D2
        |           |
    start_point   end_point
        |           |
      ALL_MEASURE_FACTS -------- DATE

  • How do I resize multiple shapes and their paths?

    I can only ever resize the shapes one frame at a time, will I have to remove the keyframes and do them again?

    Tweens are designed to animate a variety of properties, scale being one of many. If you click on the symbol and resize it, then go several frames and resize it again, you'd expect Flash to animate the resize, right? That's just Flash doing what it's supposed to.
    If you go inside the symbol and resize the contents it will do what you want.

  • Avoiding WITH clause when querying Multiple Facts

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

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

  • How can we differ which is a fact and which is a dimension?

    Hi All,
    I'm a new bee to OBIEE...
    If any one can help me out or provide me a link...
    if we have multiple facts and dimensions? How can we differ which is a fact and which is a dimension?
    Thnkx in Advance.

    Hi ,
    You can identify the facts and Dimension based on the data.
    You have to analyze.
    Generaly the Table with measure column (Max column in the table) we will consider as Fact.
    Table with attribute as Dimensions.
    For the Facts we can apply the aggregate rules.
    Thanks,
    Ananth

  • Join multiple fact tables and dimensions and use all tables in report issue

    Hi,
    I have a report requirements and need to use multiple fact tables and unconformed dimensions as described below
    Fact table: F1,F2,F3
    Dimensions tables: D1.....D9
    F1:(joined to) D1,D2,D3,D4
    F2::(joined to)D1,D2,D5,D6
    F3::(joined to)D1,D2,D7,D8
    D7::(joined to)D9,D8 (dimension D7 joined to two other dimensions D9 and D8
    I'm trying to use columns from almost all the fact and dimension tables but getting "Unable to navigate requested expression. Please fix the metadata consistency warnings."
    Repository is consistent and no errors and warnings.
    How can I configure the repository to develop reports using all fact tables and dimensions?
    Appreciate for your help.
    Thanks
    Jay.
    Edited by: Jay on Feb 9, 2012 4:14 PM

    So you want me to convert snowflake schema to star. does it solve my problem? individual star queries are working find but when I query multiple stars together getting inconsistency errors. I removed content tables dim level totals for unconformed dimensions in logical fact LTS and set level for measures at total level for unconformed dimensions. it is still in progress and need to test.
    Thanks
    Jay.

  • Multiple Fact Tables and Dimension Tables

    I have been having some problems trying to model the data from Oracle E-Business Suite maintenance. I will try to give the best description of how the data is held in the tables. The structure is such that a work order can have multiple operations and an operation can have multiple resources as well. I believe the problem comes in the fact that an operation doesn't necessarily need to have a resource. I could not attach an image so I have written out an example below. I am not saying this is right or that it works, but just to give you an idea of what I am thinking. The full dimension would be Organization -> WorkOrder -> Operation -> Resource. Now, the fact tables all hold factual data for the three different levels, with the facts being at each corresponding level. This causes an obvious problem in combining the tables into one large fact table through the ETL process.
    Can anyone tell me if they think this can be done? Am I way off? I am sure that there is a solution as there always is but I have been killing myself trying to figure this one out. I currently have the entire solution in different Business Models. I would like however to be able to compare facts from multiple areas such as the Work Order level and the Resource level.
    Any help is greatly appreciated. I realize that the solution may also require additional work on the ETL side so I am open to any and all suggestions.
    Thank you in advance for anyones time. :)
    Dimension Tables
    WorkOrder_D
    Operation_D
    Resource_D
    Organization_D
    Fact Tables
    WorkOrder_F
    Operation_F
    Resource_F
    Joins
    WorkOrder_D -> Operation_D
    Operation_D -> Resource_D
    WorkOrder_D -> WorkOrder_F
    Operation_D -> Operation_F
    Resource_D -> Resource_F
    Organization_D -> WorkOrder_D
    Organization_D -> Operation_D
    Organization_D -> Resource_D

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

  • Joins with multiple fact tables

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

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

  • Multiple Fact Tables or Circular Joins?

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

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

  • Joining Multiple facts to the multiple Dimension tables

    Hi All,
    We have multiple fact tables which are Joined to common Dimension tables. We join them in physical layer and maintain Left outer join in the BMM. I do not get any consistency errors. But when I run report I get error.
    "could not find level detailed enough for group by clause" any suggestion on the same.
    The join Strucutre is as follows.
    Facts - F1, F2, F3
    Dim - D1, D2, D3
    F1 --> D1, D2, D3
    F2--> D1, D2,
    F3--> D1, D2, D3
    We cannot combine F2, F3 into F1 using multiple Logical Table Source.
    What is the best way to achieve the above mentioned functionality.
    Please advice.
    Regards,
    Narendra Shetty.

    Check this
    OBI Error While Running Query
    Update us back with solution, if helps pls mark
    Edited by: Srini VEERAVALLI on Dec 20, 2012 7:13 AM

  • Error: There are multiple join paths between these folders

    I occasionally see this multiple join path error message when collapsing a field in a cross-tab report. The strange thing is that this error only occurs when collapsing on detail of the field, but does not happen when collapsing on the field title. For example, if the column is the department field, there is no error when collapsing on the department title at the top of the column. However, when collapsing on a single department (e.g. president_office) then the error occurs. The second odd thing, when reviewing the SQL there is only one join to the department table.
    Does anyone have an explanation, solution, or a suggestion on how to debug this error? Sometimes I found that by rearranging the layout of the fields fixes the problem, but this is not an option in every report.
    thanks

    Since it's using the "Firstname lastname" to reference the user when I use add-distributiongroupmember, I suspect that referencing the smtp address would return different results.
    Does Add-DistributionGroupMember reference AD objects, even if they don't have an associated mailbox? I ran into the same error when giving myself full permissions on a mailbox; I have only one Exchange object (a mailbox) but I have a second
    AD object (user object with dom admin rights). I then went and found that the user I had trouble adding to the DG has an
    AD object with no associated mailbox. (We frequently create AD users for business partners to access published remote applications.)
    My suspicion is that Add-DistributionGroupMember references AD objects, and not just valid Exchange recipients. This would make sense if you're using security enabled groups and having them pull double duty - which we don't do at this company.
    If my suspicion is correct, it should be documented on the technet article. http://technet.microsoft.com/en-us/library/aa995970(v=exchg.141).aspx

Maybe you are looking for