Fact to Fact join in Obiee

Hi
I am new in OBIEE, I have an scenario where in we need to join two fact tables and the condition is F1.date is between F2.valid from date & F2.valid To date
I have tried using confirm dimension. Is it possible to map such scenario in OBIEE 11g
Thanks
Sameer

Hi Venkat,
I am coming from the basics of a star schema here, so hope it helps
What is a fact?
A fact is something that has all measures which can be aggregated (Units, Dollars, # of Orders) etc with keys to different dimensions.
What is a dimension?
It is the context with which we understand/record/retrieve the measures in the fact. We understand "# of Orders" for a product/By a customer etc.
So joining a dimension and a fact helps to answer the Who/What/When kind of business questions. Ex : Who bought these products? What was the product type? When these products were sold kind of...
Now just imagine tying up fact to another fact. With this kind of model, you can never answer any business question.
I have never tried joining a fact with another fact in OBI (But do not think it will allow it though :) )
Hope I am clear.
Thank you,
Dhar

Similar Messages

  • Can we join fact to fact?

    i am new to obiee i found this question in some bi sites.
    ” If you have 3 facts and 4 dimension and you need to join would you recommend joining fact with fact? If no than what is the option? Why you won’t join fact to fact?
    i found the answer like this
    o In the BMM layer, create one logical table (fact) and add the 3 fact table as logical table source.
    but i didn't find the anser for Why you won’t join fact to fact?
    Pleae guys help me.......................
    Thans in advance.
    Rani

    You can join any two table which has some relationship but ideally you don't join Fact to Fact because its not a good practice and degrades performance..
    Get some guidance from here http://siebel.ittoolbox.com/documents/how-to-join-two-fact-tables-14090

  • Facts and dimensions joins

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

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

  • 2 fact Tables not joining to all the same dimensions

    Hi there,
    I have 2 Fact tables
    1) Errors (count)
    2) Tasks (count)
    both share the following dimension - customer
    and both have a dimension that joins only to itself
    1) Errors type (joining to errors Fact)
    2) Tasks type (joining to Tasks Fact)
    In Answers I can see customer and errors count and task count together
    When I add Errors Type, the Tasks count returns 0 (it doesn't disappear)
    When I add Tasks Type, the Errors count returns 0 (it doesn't disappears)
    customer - errors count - tasks count
    xyz 2 8
    customer - errors count - tasks count - task type
    xyz 0 8 abc
    customer - errors count - tasks count - errors type
    xyz 2 0 123
    I have seen some documentation on fact tables not joining all dimensions but any help would be appreciated
    Thanks

    The end game would be to be able to see the following:
    customer - errors type - errors count - task count - tasks type
    xyz 123 2 8 abc
    Initially I would take the either or:
    customer - errors type - errors count - task count -
    xyz 123 2 8
    customer - errors count - task count - tasks type
    xyz 2 8 abc
    I think there is something I ned to do in the Repositry?

  • Can we Join Fact to Fact obiee11g

    Can we Join Fact to Fact obiee11g?
    Regards
    kumar

    - From a physical data model point of view, yes.
    - From a logical data model point of view, not.
    To resume, you can but one of the fact must be in the business model layer of the repository designed as a dimension of the other fact table.
    Cheers
    Nico

  • How to handle monster fact and monster diamension in obiee

    Hi,
    what are ways to handle handle monster fact and monster diamension in obiee 10g.
    Thanks

    Hi,
    Thanks for your reply, I was trying things suggested, I found that the actual physical SQL (which I can get from "Manage Session" link) run in like 4-5 seconds in Query analyzer but: when I studied SQL carefully it does not contain some fiters which we I have applied in report.
    From example i have a filter in report <Measure.Present = 1 > but in Physical SQL i cannot see that filter. However, the results it gives on dashboard are correct that is after it applies the fillter.
    Any idea why is this happening?
    My guess is because above filter is not being applied at physical sql level thats why query fetches like 20000 recors in server cache and then it applies <Measure.Present = 1 >. Thats why it might be taking time ?
    Please give me your suggestions.
    Thanks !

  • Equal Join and Outer Join in OBIEE

    Hello expert,
    I think the default join in OBIEE is Outer Join. So no matter what join conditions that I specify on the physical layer, the result that I get in the presentation layer is still outer join.
    How to specify the equal join or inner join in Business and Logical layer?

    Hello,
    Thank you for your reply. However it does not work. I got the following message:
    [nQSError: 32005] The object "Fact - Fruit" bc if type 'LOGICAL TABLE SOURCE': is missing a foreign key or a complex join in the join graph.
    The situation that I have is:
    Fact table: "Fact - Fruit"
    List of value table (look up table): "dim_list_of_values"
    I am only interested in the type in the "dim_list_of_values" table where equals to "Apple". So I only want to join the "Fact - Fruit" and "dim_list_of_values" with those records with "Apple" type.
    It sounds to me that I am unable to define a freign key.

  • Incorrectly defined logical table source (for fact table Facts) does not

    Hi,
    I have two Dimensions A and B. A is joined to B by a foreign Key.
    The report works if I pull B. Column1, A.Column2.
    The report is throwing an error if i try to change the order of the columns like this. A.Column2, B. Column1.
    error : Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    File: odbcstatementimpl.cpp, Line: 186
    State: S1000. Code: 10058. [NQODBC] [SQL_STATE: S1000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table Facts) does not contain mapping for B.Column1
    I am not sure where it is going wrong.
    Thanks
    jagadeesh
    Edited by: Jagadeesh Kasu on Jun 16, 2009 4:22 PM

    did you make joins in LTS or on the physical table.
    try to make join in LTS if they are not there.

  • IMPLICIT FACT & FACTLESS FACT

    Hello Gurus
    Can anybody please explain what is implicit fact and for what is it used for .
    And also
    Can anybody please explain Fact Less Fact and for what it is used for .

    follow this,
    1. open administration tool
    2. go to help
    3. click on Search tab
    4. type Implicit Fact
    5. only one topic you'll findin the results.. plz read it and let me know your doubts on that..
    coming to your next question...
    Factless Factohhh, got these links after googling..
    http://www.geekinterview.com/question_details/31538
    http://dylanwan.wordpress.com/bi-and-olap-glossary/factless-fact-table/
    http://www.allinterview.com/showanswers/36017.html

  • Logical Facts not all joined to Dimensions in an OBIEE model

    We have a few OBIEE logical models where some of the fact rows don't have a corresponding dimension member. Essentially the FKs on the Fact don't have matching PKs in the Dimensions This has come about over time as we've made enhancements to our models and for the most part, people accept it. It causes the obvious issues when an incomplete dimension is added to a query and the fact rows drop out unexpectedly. It also causes problems where Grand Totals, which don't always include the dimension in their query, don't always match the details above.
    Is this a common approach? Is there a best practice surrounding this? Is there a list of other likely issues we will encounter?
    Thank you,
    Jim

    typically incremental fact must resolve these holes created ..wherein you have missing DIM keys . Missing keys are really bad issues as far as data integrity is concerned . unless you dont have a join on those columns , one must fix these holes . The report will be off when joined on these entities

  • Issue with Fact and Dimension join

    Hello,
    I have two Facts F1 & F2 and two Dimensions D1 & D2.
    in my schema, D1 is the common dimension between F1 & F2 and D2 is joined to F2 only.
    so when I am trying to get one record from each of D1, D2, F1 & F2 the query is not getting generated for D2 & F2. It is only creating a query like " select a1,a2, a3 from F1,D1,F2 where D1.a2=F1.a1 and D1.a2=F2.a3".
    Need some suggestion where i am wrong that OBIEE is not creating query for D2 & F2 join.
    Thanks,
    -Shub

    Discussed multiple times Business Intelligence Suite Enterprise Edition .

  • Create repository from database model- snowflake facts and dimension joins

    I am working on a project that has a database model similar to the image in the link below.
    There are other few tables around it, but this generally represent the spine or major database model. This is not exactly a snowflake schema as there are no intrinsic hierarchy in the dimension tables. As you can see dim2 and dim4 has one to many relationship with dim3. there are joins between the fact tables as well.
    From some blogs and forum threads, I found out that I can create one fact/dimension table by joining many fact/dimension tables. Is this a right approach? Any thoughts on this model please?
    Thanks,
    Rakesh
    ps: I am using Windows XP Pro and OBIEE 10.1.4.3.1 and right now analyzing the data to create a repository.

    Hi Rakesh,
    As above post says you combine all fact tables into single fact table with other dimension tables so it would become a simple start schema .Go throught these blogs for further information .
    http://forums.oracle.com/forums/thread.jspa?threadID=2124061&tstart=0
    http://www.obinotes.com/2010/08/joins-within-logical-table-sources-in.html#comment-form
    Hope it helps you.Seems your new to forum you sud follow these rules http://forums.oracle.com/forums/ann.jspa?annID=939
    By,
    KK

  • Filter on Fact columns at report level- obiee 11g

    Hello,
    The error I am getting in my report is : Incorrectly defined logical table source (for fact table SUMM) does not contain mapping for [LEDGERFACT.CD, LEDGERFACT.YEARID].
    The Model(Physical and BMM Layer) is as follows: DIM_LF_B is joined to 2 fact tables LEDGERFACT and SUMMARY
    DIM_RPT_PARAM -> DIM_LF_B -> LEDGERFACT
    DIM_RPT_PARAM -> DIM_LF_B -> SUMMARY
    Note that the aggregation is not set for any of the Fact columns. (I am aware that all measures have to be set some aggregation type , but Client restrictions as not to edit the rpd :( )
    Now on the report front, i have pulled following columns:
    >> Col name: Description ||| Forumla: DIM_RPT_PARAM.ITEM_DESC
    >> Col name: Actual Amt ||| Formula: case when SUMMARY.MONTHID=3 and SUMMARY.YEARID=2012 then sum(SUMM.AMT_1) else 0 end
    >> Col name: Plan Amt ||| Formula: case when LEDGERFACT.YEARID=2012 and LEDGERFACT.CD=300 then sum(LEDGERFACT.AMT_1) else 0 end
    I am not able to understand as to why the BI server is throwing the error.
    I tried removing the case condition and just applying the sum(as below), and the report comes up.
    Col name: Description ||| Forumla: DIM_RPT_PARAM.ITEM_DESC
    Col name: Actual Amt ||| Formula: sum(SUMM.AMT_1)
    Col name: Plan Amt ||| Formula: sum(LEDGERFACT.AMT_1) Also for the following combination the report works
    1)
    >> Col name: Description ||| Forumla: DIM_RPT_PARAM.ITEM_DESC
    >> Col name: Actual Amt ||| Formula: sum(SUMM.AMT_1)
    >> Col name: Plan Amt ||| Formula: case when LEDGERFACT.YEARID=2012 and LEDGERFACT.CD=300 then sum(LEDGERFACT.AMT_1) else 0 end
    2)
    >> Col name: Description ||| Forumla: DIM_RPT_PARAM.ITEM_DESC
    >> Col name: Actual Amt ||| Formula: case when SUMMARY.MONTHID=3 and SUMMARY.YEARID=2012 then sum(SUMM.AMT_1) else 0 end
    >> Col name: Plan Amt ||| Formula: sum(LEDGERFACT.AMT_1)
    Any help appreciated.
    Thnks,
    Shruti
    Edited by: 970002 on Mar 28, 2013 7:18 AM

    Hi Shruthi,
    To be clear you have one table 'DIM_LF_B' and its separated out as FACT and DIM in BMM layer with respective formulas ? If yes check this http://www.varanasisaichand.com/2012/04/fact-and-dimension-from-single-source.html
    let me know if it is different
    Thanks,
    Saichand

  • 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!!?

  • How do I Join Fact to Fact in the BMM

    I have a star schema in the BMM layer. Another star schema is also modelled. Now the fact table of star schema 1 has to get data from the dimension table in star schema 2.
    How do I join the fact tables of star schema 1 and star schema 2.
    They do not share a common dimension.
    Thanks for inputs.

    Just click inside the Shape and either type or paste.
    or
    select a Textbox and Shape by clicking on each with the command key held down > Menu > Arrange > Group
    Peter

Maybe you are looking for