Making fact table

hi,
im having a relationship in the physical layer:
T1--< T2 --< T3 --< FactTable >-- T4
The fact table also has many to 1 relationship to another table which has its own relationships to other tables but the problematic area is here.
I wanted to change this relationship in the business model to be fact table will have many to one relationship to all the table (including T1 and T2) to resemblance a star schema, removing the relationship between T1 to T2 and T2 to T3 (the complete design is much more complicated so im trying to do some muscling to reduce the complexity).
In the business model and mapping layer, i do:
1. Created 2 new column in factTable T1key and T2 key. (obviously no T3 key column needed since fact table already contains that)
2. In the logical source table of the factTable, i added T2 and T3, making the relationship there such as:
factTable - T3: inner join
T3 - T2 : inner join
3. Navigate to the column mapping tab:
- map T1key to t1key (foreign key of T1 table that T2 table contains) in T2 table
- map T2key to t2key (foreign key of T2 table that T3 table contains) in T3 table
4. Navigate to the foreign key tab:
- adding foreign key from factTable to T2 on factTable.T2Key = T2.t2Key
- adding foreign key from factTable to T3 on factTable.T3Key = T3.t3Key
I already has the "flag allow logical foreign key join creation" checked
=> when i try to create new analysis with a column from t1,t2,t3,t4 => error: No fact table exists at the requested level of detail.
This has happened to me before when i dont create the foreign key in the physical layer and doing it on the business model layer..... Im thinking the foreign key i created at step 4 also somehow ignored by BI thus the problem... What am i missing??

I found it very difficult to understand your problem.
Based on what i understood
T1 < T2 = 1:M
T2 < T3 = 1:M
T3 < Fact = 1:M
T4< Fact = 1:M
simplest way to represent this as Star in BMM is
Create a Logical Table T3 with T3, T1 and T2 in the LTS
Create logicla table T4 and Fact
So you will have a perfect star in BMM T3< Fact> T4.
In physical layer it is still going to snowflake T1< T2< T3<Fact>T4 whatever you do.
So I think you are complicating things too much by adding T2 and T3 in Fact logical table.
Hope it helps.

Similar Messages

  • Load data in a fact table

    Hello,
    I have implemented SCD2 dimension and mapping executing works fine.
    Now I have question about loading data in a fact table.
    How do I need to use OWB (maybe JOINER operator - Join condition - between dimensions and source table) in case of:
    - update on source table
    - delete on source table
    I think the most simple is insert on source table. It is probably to_char(source_transaction_date,'dd.mm.yyyy') = to_char(sysdate,'dd.mm.yyyy'), if I load once a day..
    What is the procedure for fact table mapping to handle updates and deletes on source table?
    Regards

    Some discussions in previous forums should help you
    http://forums.sdn.sap.com/thread.jspa?threadID=2019448
    http://forums.sdn.sap.com/thread.jspa?threadID=1908902
    In the SAP tutorial, you can see a sample example of making fact tables.
    http://help.sap.com/businessobject/product_guides/boexir32SP1/en/xi321_ds_tutorial_en.pdf
    Arun

  • How to load data to dimensions and fact table is it simialr to sql server

    How to load data to dimensions and fact table in a data ware house environment, is it simialr to sql server, oracle?
    Never migrated or loaded data to datawarehouse server.
    I have an interview and am really confused if they ask anything related to the dataware house side elements.
    Coudl you please if you don't mind provide me some steps and dimension and fact table info, an example only.
    Atleast for my knowledge.
    Thank you very much for the helpful info.

    Some discussions in previous forums should help you
    http://forums.sdn.sap.com/thread.jspa?threadID=2019448
    http://forums.sdn.sap.com/thread.jspa?threadID=1908902
    In the SAP tutorial, you can see a sample example of making fact tables.
    http://help.sap.com/businessobject/product_guides/boexir32SP1/en/xi321_ds_tutorial_en.pdf
    Arun

  • Logical level in Fact tables - best practice

    Hi all,
    I am currently working on a complex OBIEE project/solution where I am going straight to the production tables, so the fact (and dimension) tables are pretty complex since I am using more sources in the logical tables to increase performance. Anyway, what I am many times struggling with is the Logical Levels (in Content tab) where the level of each dimension is to be set. In a star schema (one-to-many) this is pretty straight forward and easy to set up, but when the Business Model (and physical model) gets more complex I sometimes struggle with the aggregates - to get them work/appear with different dimensions. (Using the menu "More" - "Get levels" does not allways give the best solution......far from). I have some combinations of left- and right outer join as well, making it even more complicated for the BI server.
    For instance - I have about 10-12 different dimensions - should all of them allways be connected to each fact table? Either on Detail or Total level. I can see the use of the logical levels when using aggregate fact tables (on quarter, month etc.), but is it better just to skip the logical level setup when no aggregate tables are used? Sometimes it seems like that is the easiest approach...
    Does anyone have a best practice concerning this issue? I have googled for this but I haven't found anything good yet. Any ideas/articles are highly appreciated.

    Hi User,
    For instance - I have about 10-12 different dimensions - should all of them always be connected to each fact table? Either on Detail or Total level.It not necessary to connect to all dimensions completely based on the report that you are creating ,but as a best practice we should maintain all at Detail level only,when you are mentioning any join conditions in physical layer
    for example for the sales table if u want to report at ProductDimension.ProductnameLevel then u should use detail level else total level(at Product,employee level)
    Get Levels. (Available only for fact tables) Changes aggregation content. If joins do not exist between fact table sources and dimension table sources (for example, if the same physical table is in both sources), the aggregation content determined by the administration tool will not include the aggregation content of this dimension.
    Source admin guide(get level definition)
    thanks,
    Saichand.v

  • Creating Time Dimension from date columns in fact tables.

    I remember watching a demo from a BI Tool a couple years ago, wich I swear was OBIEE, and the presentator stated it was possible to create a Time Dimension in the admin tool, based on a date column in other table.
    Can you guys tell me if there's such functionality in OBIEE?
    If so, how could I achieve that?!
    Thanks in advance!
    Marcos

    hi,
    You are trying to make Fact table as Dim table ???
    Fact table has some dim columns??
    We can do this by making a fact table as dim table ,create a dim hierarchy on that table
    Year level :Extract(year from fact_date_column)
    Month and year  level:CAST (Extract(month from fact_date_column) As CHAR(5) ) || CAST (Extract(yearfrom fact_date_column) As CHAR(5) )
    Like this
    But,be careful while doing this make sure that all joins and content levels are good
    As per my knowledge this is not a good way,Experts can add some words lets see!!!!!! :-)
    thanks,
    saichand.v

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

  • Find the partition for the fact table

    Oracle version : Oracle 10.2
    I have one fact table with daily partitions.
    I am inserting some test data in this table for old date 20100101.
    I am able to insert this record in this table as below
    insert into fact_table values (20100101,123,456);
    However I observed that the partition for this date does not exist in the table (all_tab_partitions) morever I am not able to select the data using
    select * from facT_table partition(d_20100101)
    but I am able to extract the data using
    select * from facT_table where date_id=20100101
    could some one please let me know the way to find the partition in which this data might be inserted
    and if the partition for date 20100101 is not present then why insert for that date is working ?

    user507531 wrote:
    However I observed that the partition for this date does not exist in the table (all_tab_partitions) morever I am not able to select the data using
    select * from facT_table partition(d_20100101)Wrong approach.
    but I am able to extract the data using
    select * from facT_table where date_id=20100101Correct approach.
    could some one please let me know the way to find the partition in which this data might be inserted
    and if the partition for date 20100101 is not present then why insert for that date is working ?Who says that the date is invalid..? This is a range partition - which means that each partition covers a range. And if you bothered to read up in the SQL Reference Guide on how a range partition is defined, you will notice that each partition is defined with the end value of the range it covers. There is no start value - as the previous partition's end value is the "+border+" between this and the prior partition.
    I suggest that before you use a database feature you first familiarise yourself with it. Else incorrectly using it, and making the wrong assumptions about it, more than likely results.

  • Problem relating multiple fact tables

    I have 2 fact tables in my cube (Encounter and Visit).   Every visit has at least 1 encounter but not every encounter has a visit.  I also have a department dimension which is related to both facts, and an appointment status dimension which is
    related only to Visit Fact.  
    The users want to look at the count of encounters by department and appointment status.  At first I was having an issue with this because when using the encounter count, I would end up with the same value in each row.  So I was able to create a
    dimension from my Visit Fact table and then have Encounter Fact reference the appointment status dimension through the Visit Fact dimension.  The problem I am having now is that since not every encounter has a visit, that my count of encounters only includes
    the encounters that have visits.  What I currently have is "joining out" the encounters that don't have a visit. How do I work around this so that all of the records from Encounter Fact are in the cube regardless of whether or not they have
    a visit?
    Do I need to implement unknown members in this case?  I'm not sure where to go.
    Thanks for the help,
    Andy

    So yes, if you are going to have some nulls you want to implement unknown members either
    1. "manually" in the ETL by making yourself a custom-created unknown record in each dimension with the values your users want to see in each column (e.g. unknown record might have product_category='Misc')
    2. using the built-in analysis services stuff - convert null to unknown
    Typically in my cubes facts are related only to dimensions, not directly to each other.  So I think I am not getting a full description of the relationships in your cube so I can't comment on your overall setup.  I guess I would say if your can
    determine the appointment status of an encounter based on the visit (or null/unknown if visit is null/unknown), then you should go ahead and use that information to directly relate encounter and appointment status.  I would tend to do it in the ETL, you
    can always use a view layer over the datamart dimension tables to do this an easy way without snowflaking your actual cube with reference dimensions.

  • 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 Fact tables

    Hi,
    In what cases can two fact tables be joined.
    Can anyone explain why there is a join between promotion facts and shop facts in efashion database and that too shortcut join.
    Please put some comments.
    Ganesh

    It shouldn't be imho. I think it's incorrect and is a result of bad analysis leading to bad table design. I went on a course years ago where we discussed this and said that you *might* consider making that a full join and creating a context with only that one join in it if you have denormalised dimensions in one of the facts but not the other. However, you'd only do that if you were certain of the granularity of the join. We agreed, though, that the model was principally flawed and it would be a lot less painful to reassess the model and rework it.

  • Essbase vs. Relational Data Warehouse (Which one is the fact table in DW)?

    Guys, thanks in advance for your feedback but below is a simple question i am trying to get feedback on. I am trying to compare an Essbase cube to Relational Data Warehouse containing the same set of information:
    Essbase Dimensions
    Time, Account, Product, Scenario (making it easy)
    Relational Data Warehouse
    Time (dim), Account (dim), Product (dim), Scenario (Fact table)
    OR
    Time (dim), Product (dim), Scenario (dim), Account (Fact Table)
    Which of the relational lines is correct? Is Account the fact table? or Scenario the fact table? Account will contain your usual P&L accounts. Scenario will contain your usual Actual, Budget and Forecast scenarios.
    Thanks,

    I am so not a DW guy, it's amazing, but I've never let little more than a brush with a product stop me from posting...
    Wouldn't all of your dimensions need to be in your fact table? How else would you join from the fact table to the dimensions?
    In either layout, wouldn't you have the keys for Product, Time, Scenario, Acount, and then data in the fact table?
    Or are you talking about the last dimension in your layouts be the columns? If that were the case (and I don't know that it is), I would guess that Scenario changes less, so it would be in columns, although I can definitely see that not being efficient as you are likely to pull all or some of the Accounts for a given time, product and scenario versus all of the scenarios for a given time, product, and account.
    I'm really curious about this as I am just the consumer of star schemas, never (thankfully, and obviously, given the above insane ramblings) the designer of them.
    Regards,
    Cameron Lackpour

  • Unposted journals still in the fact tables

    Hi!
    Sometimes not very often, but from time to time we have problem with posted journals not showing in the facttables and unposted journal not being eliminated from the fact tables.
    Is someone having the same problem or knows what might cause this problem?
    Usually it´s solved by unposting and posting the journal again, but it´s tricky to know which journals is working or not.
    Regards
    Fredrik

    Hi,
       It is difficult to find an explanation without making some investigation. In order to isolate a little bit the problem, just try to check if the journal data are real into the fact tables and in which one(WB, FAC2 or FACT). Myabe it will be just enough to process the partition to see data. In my opinion is should be related to some thinks that happen in that time into the system simultaneously.
    Hope this can help you,
    Mihaela

  • Alternate Fact table in EIS

    Hi, For the financial cube we want to build an alternate fact table in EIS. I'm wondering how and where (sql, olap model, metaoutline) you build the hierarchy in the account table. Has anyone done it, where can I find more data on that. Please reply on this message or mail me at [email protected] replies are more than welcome and would be great.Thanks a million

    You can use the same table with Acount hierarchy, making a new model an metaoutline.

  • Parent member values in Fact tables

    Hello,
    I want to understand something, as far as I know, we can only send data to base level members, right ?
    Then how come we find rows of data that have parent member values in the Fact tables ? (assuming we do not play manually with the database of course), I thought that this can be due to an import with the data manager, can this be right ?

    nilanjan chatterjee wrote:
    Hi,
    >
    > The data for the parent members should be available in the SQL tables.
    > For example, 2011.TOTAL is parent member. You should not have any data for this member in your database. If it is there, it might have come somehow (may be an import). But this is not right. You might want to remove these records. But be sure that you dont delete the records for the base level members.
    >
    > Hope this helps.
    I guess you meant should not, right ?

  • Null key in fact tables

    Hi all,
    I have one role play dimension with some null key in fact table, I liked know if it's a good practice?
    thanks

    Depends on what you actually mean..
    When one dimension column contains NULL in your fact table, then it's normally a bad practice. Create a entry in your dimension table to represent this state.
    The problem is that NULL is a state, which means does missing or inapplicable information. This means that the row in the fact table is semantically meaningless. Cause your fact table is no longer additive over this dimension.

Maybe you are looking for

  • Make the Library Preview Windows Larger?

    Is there any way to make the Library Preview Window larger? When I'm working at a high screen resolution, the previews are just too small to see.

  • Safari 6.0.2 & Wordpress clash?

    Last week my Macbook Pro underwent upgrades by a reputable, indie Mac shop. They installed new HD, more RAM, LION (10.7.5), Safari 6.0.2, and iLife. I've been experiencing weird glitches since – one of the most annoying being, I can no longer see you

  • Creating two APEX_ITEMs

    Hi All, I have already created APEX_ITEM in my interactive report for dropdown, here I have to add button beside the dropdown, is it possible to include two APEX_ITEMs , and how can we do that, any idea? Thanks, Suma

  • Ifweb60.exe crash

    We have installed the fileupload bean on our Win2000 server, where we are running an Oracle 817 DB. We have not installed the full IAS, only the things that are installed during the DB installation. Our webforms run ok, but when we press the upload f

  • Duplicates when importing pictures from my camera

    Every time I import photos from my Nikon D5000 I get two of every picture. The only discussion I can find on this topic says to make sure the date and time setting on my camera are correct... they are. Any ideas how to stop this? Thanks! Dave