About the implicit fact table

Hi all,
Can any one has any idea about the implicit fact table, where it is used. Any doc or screenshot with example will be helpful for me.
Thanks once again.

I forgot the definition that you can find here :
http://download.oracle.com/docs/cd/E12096_01/books/admintool/admintool_PresentationSetup4.html
If you set an implicit fact column this column will be added to a query when it contains columns from two or more dimension tables and no measures. The column is not visible in the results. It is used to specify a default join path between dimension tables when there are several possible alternatives.
Cheers
Nico

Similar Messages

  • Alternate fact table without disturbing the existing fact table in EIS

    I have a question in EIS, how to load or work with alternate fact table, without disturbing the existing fact table, pls provide me with some procedure and steps
    thank u in advance
    sunil

    Yes you can have multiple models and metaoutlines load one cube. I've done it before. The trick is you ahve one "master" metaoutline that you put all the measures in (even if they are manually added. You use that to build the cube. Then you can have multiple metaoutlines build different measures within the cube. The idea is you have to have them update different intersections or the last one in will be what you get. I have a client that gets sales info from one source, shipment info from a different relational source . in all I have 10 differnt models and metaoutlines that build one cube. you just lump the load statements into one CBS file. It works great (or as great as EIS works). The biggest issue is timing to make sure all the sources are available when the load is going to be doe. Of course you could build different parts at different times.

  • Mix source data with different granularity into the same fact table?

    I have two transaction tables "Incident (157 columns)" and "Unit (70 Colums)". For every "Incident" that happens there could be one or more records in the "Unit" table.
    As part of my data mart design, I have merged both the tables into a single Fact "Incident Fact (227 Columns)" and inserted the records from both the tables with a join condition between them [incident.IN_NUM = Unit.IN_NUM].
    Is this correct, is my question? or am I mixing source data with different granularity in the same fact table. Appreciate your help.
    Best Regards
    Bees

    Bees,
    Are the measures from 'Incident' , repeated for a given incident where it has more than one record in the Unit table ? If so, then the sum(indicent.measure) will give an incorrect result, no ?
    What requirement is there to physically merge the tables together outside of OBIEE? With OBIEE you could have one logical 'fact' table to present to report users, which sourced from seperate Incidents and Units tables and would stop the incorrect aggregations occuring. A common modelling piece in the same way would be Order Headers and Order Lines, quite common in OBIEE to have a logical 'Orders' fact which contained both Order header measures and Order line measures, this translates to your Incidents -> Units relationship.
    To do what I've mentioned, is relatively straight forward, you need a 'Dim - Incident' with two levels, Incident and Unit, mapp the unique identifiers in as the level keys and then use these levels to set the content levels correctly in your 2 logical tables sources for logical 'Fact' , ie Incidents LTS at incident level, Units LTS as units level.
    Hope this helps, let us know if you get stuck.
    Cheers
    Alastair

  • Cubes with different dimensions based on the same fact table

    I have a fact table (f_a) with three dimensions (dim_a, dim_b, dim_c) and a one measure (m_a).
    Is it possible to create cube with only one dimension (dim_a)?
    Data for other two dimensions (dim_b, dim_c) should be aggreagated together.
    Of course i can create second fact table with only one dimension, and then creating that cube would be no problem.
    But is it possible doing this directly from the primary fact table (without creating second fact table)?
    Raf
    PS:i use AWM 9.2 to create target cubes. Source cubes i create with OEM 9.2

    At the beginning i was confused by the numberous kind of cubes...
    for example when i created cube in MS i just designed cube, picked fact table, and that's all. In Oracle firstly i create project of cube (first cube) in OWB. Then i export it to the OLAP Catalog (second cube). That cube in OLAP catalog is a source cube for the AW cube (third cube). Then i need to enable AW cube for OLAPI by creating another cube in OLAP Catalog (i use 9iR2, so OLAPI doesn't have direct access to AW cubes).
    I spent much time until i could see my first sample cube in Discoverer or Excel as a final user should see it. :-)
    Now i'm facing another problem - when you redesign cube (for example add another dimension), you can't just "refresh" it as it was in MS. You have to delete old cube and create new one. And deleting cube isn't so simple (i'm not sure which elements i should delete).
    For testing and learning purposes i just create every cube in seperate AW. deleting whole AW is much simplier that deleting one cube.
    Raf

  • Dimension which belongs to only one of the several fact tables

    Hi,
    I'm newbie in BI. I have good knowledge of DW and Administration (OCP).
    Firstly could you give me, please some link expalining aspects of creating "Business Model And Mapping" better than SE Tutoarial.
    Now how my problems looks like :
    I have several fact tables and dimensions.
    But not all dimensions are shared among all facts.
    So when i try to put in Answers measurements from all facts it's ok - results are retrieved.
    But when i try to add to report some Dimensions attributes which belongs to only one of the facts all facts measurements are gone except measurements for fact table to which dimension attribute is linked to.
    I think i know what is the reason but i don't know how to simply solve it :
    Below is session trace excerpt only with facts measurements :
    RqList
    Liczba Transakcji:[DAggr(Fakty - Transakcje (ZSFK).Liczba Transakcji by [ Słownik - Daty.Nr Miesiąca, Słownik - Daty.Miesiąc Rozliczenia, Słownik - Outlety.Outlet Numer (MID), Słownik - Outlety.Outlet Nazwa, Słownik - Terminale.Nr Terminala, Słownik - Daty.Rok Rozliczenia] )] as c7 GB,
    Kwota Opłaty Netto:[DAggr(Fakty - Opłaty za Terminale (CBD).Kwota Opłaty Netto by [ Słownik - Daty.Nr Miesiąca, Słownik - Daty.Miesiąc Rozliczenia, Słownik - Outlety.Outlet Numer (MID), Słownik - Outlety.Outlet Nazwa, Słownik - Terminale.Nr Terminala, Słownik - Daty.Rok Rozliczenia] )] as c11 GB,
    Below iis session trace excerpt with facts measurements and added dimension attribute:
    RqList
    Liczba Transakcji:[DAggr(Fakty - Transakcje (ZSFK).Liczba Transakcji by [ Słownik - Rodzaje Walut.KOD_WALUTY, Słownik - Daty.Nr Miesiąca, Słownik - Daty.Miesiąc Rozliczenia, Słownik - Outlety.Outlet Numer (MID), Słownik - Outlety.Outlet Nazwa, Słownik - Terminale.Nr Terminala, Słownik - Daty.Rok Rozliczenia] )] as c7 GB,
    Kwota Opłaty Netto:[DAggr(Fakty - Opłaty za Terminale (CBD).Kwota Opłaty Netto by [ Słownik - Rodzaje Walut.KOD_WALUTY, Słownik - Daty.Nr Miesiąca, Słownik - Daty.Miesiąc Rozliczenia, Słownik - Outlety.Outlet Numer (MID), Słownik - Outlety.Outlet Nazwa, Słownik - Terminale.Nr Terminala, Słownik - Daty.Rok Rozliczenia] )] as c12 GB,
    Second plan is the plan when report retrieves only results for one fact table and null's for others
    Problem is with attribute : "Słownik - Rodzaje Walut.KOD_WALUTY" which is from dimension which belongs only to one fact table.
    So other fact table are not linked to this dimension and therefore this plan cannot retrieve results for them.
    It is obvious that some of the facts cannot share some dimensions with others but i would like to join them on other common attribute
    and my question is how ?
    Thanks's in advance Arkadiusz Masny
    Edited by: Arkadiusz Masny on Dec 10, 2009 6:49 AM

    It's normal behavior. How would fact measure know the value for accurate "non-fact" dimension
    Workaround:
    First solution is:
    Add into logical source of each fact (in logical layer) tables to which belongs dimension attribute and join dimenstion to that fact.
    Second you may:
    Create fact table which join all needed dimensions with some useless fact ( i.e. count). Next you have to set option "Implicit Fact Column" in presentation catalog to use this fact table.
    I can explain it to you in Polish by mail or phone
    You bring me a next topic for my blog (in Polish) http://obiee.pl so I'll write sth about such behavior :)
    Regards

  • About the FPGA utilization table

    Hi all,
    I would want to know how to interpret the unit in terms of which the usage of the resources of the FPGA is given in that table. I've read carefully the FPGA utilization tutorial, but I guess that nothing is said about that there.  In few words: ¿What does it mean , for instance, that the Quotient & Remainder function takes "138,56" when placed outside a SCTL and using I8/U8 data types? ¿What is a 95% of the usage of that unit?
    Thanks for your attention
    Jose

    I forgot the definition that you can find here :
    http://download.oracle.com/docs/cd/E12096_01/books/admintool/admintool_PresentationSetup4.html
    If you set an implicit fact column this column will be added to a query when it contains columns from two or more dimension tables and no measures. The column is not visible in the results. It is used to specify a default join path between dimension tables when there are several possible alternatives.
    Cheers
    Nico

  • OBIEE Query not hitting the other fact table

    Hi All,
    I am trying to create report based on two fact column and one dimension. Dimension is connected with these two facts table. When i create report using one column from dimension and one column from respective facts so i get two scenerio...
    For example let say..
    D1 is dimension and F1 and F2 are two fact tables.
    First i used a column which have aggregation rule from one fact and one column from other fact which also have aggregate column.
    That is report like...
    D1.c1,Agg(F1.c2),Agg(F2.c3)
    When i run the report I get the data from dimension and only from first fact table. When i check the query, Query contain only one fact table and it doesnt hit the other one.
    Now in second scenerio i used one column from dimension, one column from first fact which have aggregation rule and one column from second fact which doesnt have any aggregation rule.
    like...
    D1.c1,Agg(F1.c2),F2.c3
    When i run the report i got the error. It says
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: F1 -C2 . Please fix the metadata consistency warnings. (HY000).
    But there is no warning in RPD.
    I am amazed that it is not taking both the fact columns even the dimension is confirmed dimension and have joined with both the fact tables.
    As i am just started to learn OBIEE, So i am find it bit difficult that how OBIEE select the tables and formed physical query.
    Waiting for your help.
    Regards
    Suhail

    Aadi-Wasi,
    Thumb rule, OBIEE BMM layer must contain a simple star schema.
    Did your BMM layer suffice the above condition? If hope, Not.
    My prediction of your BMM layer structure contains 3 logical tables, i.e. dimension & 2 logical facts...which is not a simple star.
    Thus to make it a simple star collapse 2 logical fact tables into 1 logical fact table. As you mentioned dimension is linked to both facts, collapsing 2 logical fact tables into 1 logical fact table will provide the result for your query1.
    regarding your second error:
    All aggregations must be contained within Fact tables with few exceptions.
    Let us know If I did resolve your issue
    mark posts promptly...
    J
    -bifacts
    http://www.obinotes.com

  • Selecting The Correct Fact Table

    I have an environment that has multiple dimension tables and multiple fact tables.
    I have multiple Presentation Catalogues to organise these.
    In PCat1 I have multiple dimensions and two Facts; F1 & F2.
    In answers I have build a filter to restrict the dashboard to show only selected data from two dimensions; D1 & D2. The filter is built using PCat1.
    The facts F1 and F2 do both have relationships defined to D1 and D2.
    When I check the SQL generated by the filter (as the results do not look correct) I can see that the SQL is referencing a fact table F3 that is NOT in PCat1.
    F3 does contain valid joins to D1 and D2 but F3 is not in PCat1 so I do not know why it is being used.
    How do I FORCE BIEE to generate SQL that is sourced ONLY from the presentation catalogue that was selected when I created the filter in answers.
    I am using version 10.1.3.3

    Excellent, that seems to have done the trick.
    Right click on the presentation catalogue select properties and selected my fact table.
    Need to test ALL my reports now.
    Thanks for your help<br>
    Ross

  • How to refer to fact table to update the same fact table

    Here is my scenario. Fact table is having measures basic_sal, Tax, net_sal with dimension key to employee dimension.
    I neet to update the net_sal = basic_sal - tax in fact table.
    I tried to do a map with fact_table as source and also target. but after deploying the map, it's not updating the net_sal to the existing rows. It's inserting the new rows with dimension key and net_sal columns. so now fact table is having the double the existing rows.
    Thanks,
    Srini.

    Ola Srini,
    We have some experience that updating a table while using that same table as source often takes a lot of time... Specially when the table contains a lot of data (which is mostly the case with fact tables).
    You can use two solutions. Expand the mapping u use to fill the fact table... The calculations looks not that complex to me... But I could be wrong.
    Other solution is to create a temp table where you store all sal types. You could load the fact table from this temp table. Disadvantage of this solution is maintenance of the temp table...
    Regards,
    Moscowic

  • A question about the multiple source table for the logical table

    Hi All,
    I am to test, having two physical sources for an logical table, but it is failing as it is always getting data from only one table rather than two tables.
    !http://picasaweb.google.com/KSivaUS/OracleForumQuestions#5433761212378087346!
    Any suggestion or inputs would be appreciated.
    Thanks
    Siva

    your 2 measure columns are in the same unique - low level??
    your connections look good.
    which is the result if you bring only the sales column at your report??is it the sum of the 2 datasources??
    try to repass again all your bussiness model.or make an other one.
    fisrt pass your fact with 2 sources and then your dimensions....
    as i can see you have customer_dim,do both of your columns have the appropriate key to this dimension??try to make a physical connection from both fact sources to this dimension as well as for time...
    if you do it in this way ,there is no possibility not to work
    hope i helped...
    http://greekoraclebi.blogspot.com/

  • About the data of table control in tab strip control

    hi experts:
           I use screen 0001 include one tab strip control,and its include two subscreens,one of it is table control(subscreen is 0003).
    I input data in the table control,when I click the button of tab strip control to change to another subscreen 0002.I found that the data I input into table control have not append to internal table.how can I solve this problem?
           appreciate your reply.thanks a lot.

    Hi,
    in the Main Screen
    In PAI
    call subscreen sub. ---> here it calls the subscreen where the tablecontrol is placed
    then call module user_command
    In the subscreen where you have your table control
    in PAI
    Loop at itab.
    module modify_tab.
    endloop.
    module modify_tab,
    descirbe table itab lines tc-lilnes.
    if tc-lines <= tc-current_line.
    modify itab index tc-current_lilne.
    else.
    append itab.
    endmodule.
    next you call the module user_command on the main screen
    module user_command
    case sy-ucomm
    WHEN 'TAB1'
    TS-ACTIVE_TAB = 'TAB1'
    when tab2.
    ts-active_tab = 'TAB2'.
    endmodule
    further you can take the help of CONTROL EXAMPLES in DWDM tcode
    Regards
    Ramchander Rao.K

  • About the access of table

    hi, friends, there are three tables which need some modifications, however thess tables are so important to the system that no access to them is intolerable.
    how can i make them read only for others and at the same time which can be modified by and only by my session ?
    thanks in advance

    If it is indeed "so important" (to quote you) then use Oracle's very handy, very reliable syntax of security suggested to you already. THEN connect to the database as a user who starts any/every session with the privileges you desire.

  • Implicit fact column...

    Hi Friends,
    I created a repository named vision, in that i imported six tables from database. Since from the six table none of the table resemebled to me as a fact table as all the table is of, not a measure based. So i went to the concept of " IMPLICIT FACT TABLE"(wat i understood about the implicit fact table is, the table that contains all primary key column of all the dimension table which is in the physical layer).
    As per my concept i want to add all the primary key column from the dimension table to the implicit fact table.
    How i need to copy the primary key column's from the dimension table to the fact table in the physical layer.........
    Regards,
    Harry.....

    Hi Nag,
    Since i want to create a BI report (i.e.)
    "Nationality count in department wise manner"
    For this Im using the following tables
    *) per_all_people_f -----> this table contains the column 'Nationality'...
    *) per_all_assignments_f ----> Im not taking any column from this table, but im using this table for the join condition....
    *) hr_all_organization_units ----> this table contains the column 'Departments'...
    As per my concern the result that want to display to me should be like this manner,
    COLUMN----------->COUNT------------->NATIONALITY
    1 ROW ------------> 2 --------------->INDIAN
    2 ROW-------------> 5 ---------------->AMERICANS
    The above is the example for my report, as i dont want to show the column "department" for the display, but i need the report in department wise only.........
    since all the three tables is not a measure based. so it is dimension table.........
    So for dimension table inorder to give join with fact table, i need to have a fact table.....so how to create a fact table????
    For the fact table creation, Whether can i create "Factless Fact table"for this report.....
    Since i need to get " Nationality count in department wise manner", whether can i create a factless fact table for this report...........
    If so, means guide me for the steps of creating "FACTLESS FACT TABLE"..........
    Thanks,
    Harry.........
    Edited by: HariPrasad on Sep 28, 2010 11:37 AM
    Edited by: HariPrasad on Sep 28, 2010 9:44 PM

  • Dimension Table Attributes giving No Fact Table Exists Error

    Hi Experts,
    My OBIEE version is 11.1.1.6.10. There is a presentation table which has columns coming from multiple logical tables. I'm dragging 2 columns into the report which are coming from 2 logical tables.
    The result is displaying. When I checked the query, a fact table is also coming and results are getting effected because of this.
    Could anybody let me know if any idea.

    Hi SriramKarthik,
    Aj (bi007) already gave you the answer on how you can change the implicit fact table, the one you are seeing in your physical query.
    I'm just not sure of what is your question: are you surprised to see a fact table is used in the physical SQL and look for a way to avoid it because, as you say, results are impacted by that implicit fact table? You can't get rid of that table, you can only choose it (the implicit one).
    OBIEE must join in a way or another your 2 dimensions, and in your BMM these dimensions are joined by a fact table, that's why you see it in your query.

  • Implicit Fact Column - am I thinking about this the right way?

    My exploration of the Implicit Fact Column is below. Let me know if you think this is the intended usage.
    When the BI Server sees a request where one Dimension is being constrained by another, it has to pick a fact table that contains references to these two dimensions. The "Implicit Fact Column", which is set in the Presentation Layer of the RPD is used to guide the BI Server towards one or more Fact tables that can be used to satisfy the request. In the absence of the Implicit Fact Column, I noticed that the BI Server was choosing random fact tables so I went exploring how this feature worked. I set the Implicit Fact column in my Presentation layer and then went looking to see how the queries were generated.
    For my example, my two dimensions are Program and Channel. I want to see the list of Channels available for a Program. Without the Implicit Fact Column, the queries are of the form:
    select distinct T289.CHANNEL_NAME as c1,
    T36001.PROGRAM_NAME as c2
    from
    DIM_PROGRAMS T36001,
    DIM_CHANNELS T289,
    SomeRandomFactTable T41210
    where ( T289.DIM_CHANNEL_KEY = T41210.DIM_CHANNEL_KEY and T36001.DIM_PROGRAM_KEY = T41210.DIM_PROGRAM_KEY )
    order by c1, c2
    The nice part about this is that there is only one set of Program / Channel combinations returned. The downside is that the Fact table that is chosen to resolve the combinations can be any Fact table under the purview of the BI Server. It doesn't even have to be in the same subject area where the Program and Channel were chosen. When I set the Implicit Fact Column, the queries are of the form:
    select distinct T289.CHANNEL_NAME as c1,
    T36001.PROGRAM_NAME as c2,
    T35832.DIM_SITE_KEY /* this is the implicit fact column */
    from
    DIM_PROGRAMS T36001,
    DIM_CHANNELS T289,
    AFactTableMappedToFactColumn T35832
    where ( T289.DIM_CHANNEL_KEY = T35832.DIM_CHANNEL_KEY and T35832.DIM_PROGRAM_KEY = T36001.DIM_PROGRAM_KEY )
    order by c1, c2
    I was happy that I could predict what Fact table was being used, but now the results are wrong as I get a duplicate set of records for every DIM_SITE_KEY / Channel / Program combination. I decided to play a little Algebra trick. Knowing that the DIM_SITE_KEY was a numeric value, I defined the Implicit fact column as DIM_SITE_KEY / DIM_SITE_KEY which will always result in a value of 1. Now I get queries that look like:
    select distinct T289.CHANNEL_NAME as c1,
    T36001.PROGRAM_NAME as c2,
    T35832.DIM_SITE_KEY / nullif( T35832.DIM_SITE_KEY, 0) as c3
    from
    DIM_PROGRAMS T36001,
    DIM_CHANNELS T289,
    AFactTableMappedToFactColumn T35832
    where ( T289.DIM_CHANNEL_KEY = T35832.DIM_CHANNEL_KEY and T35832.DIM_PROGRAM_KEY = T36001.DIM_PROGRAM_KEY )
    order by c1, c2
    Since DIM_SITE_KEY / DIM_SITE_KEY is always equal to 1, I only get one set of Program / Channel combinations. I get the added bonus of knowing which set of Fact tables are going to be used to satisfy the request.

    Perfect Analysis, But one important note is when using implicit fact table, Always select measure( Which has some aggregation) as a implicit fact column. So that will allows the query will eliminate duplicate rows by doing a group by operation.
    Other note is make sure performance is good. When we don't have a good model for fact tables, when the tables contains large set of data, make sure performance is good by doing indexes or caching to load the prompts.
    - Madan

Maybe you are looking for