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

Similar Messages

Deploying Factless Fact Tables in 10G

Hello - We are trying to deploy the same factless fact tables we used for OWB 9i to 10G and we are receiving validation errors saying that every cube must have a measure. We do not want to create a null column just to get around something that worked fine in a previous version of the tool, and we have quite a few factless fact tables in our model.
Are there any thoughts on this?
Thanks,
Kristi

Hi,
I already face that kind of fact table, but in the same time, i needed to count the number of intersection between dimensions or sum, so i used a one measure, that always takes 1 as value, that did the trick.
Regards

"Factless" fact table join warning

We have a physical fact table that only contains keys for a given day in order to track changes to Employment history over time. The compensation "facts" are contained in a dimension that is joined to the factless physical table in the logical layer. I use the factless fact as the table source and inner join it to the dimension to create the logical fact source. This seems to be working fine, but is creating a warning when I check consistency: "There are physical table sources mapped in Logical Table Source [...] that are not used in any column mappings or expressions." Is there a better way to model this in the logical layer that this warning is trying to alert me to?
Thanks!

Thank you,
The error does go away when I insert into the logical fact table the key from the factless physical table. The error is gone whether or not I define the physical column as the Logical fact table key. Will defining it as a logical key change anything?
I am curious as to why it would want me to include a field in the fact table that will never be used in the presentation layer. Is the warning mainly for accidental inclusion of physical tables that aren't used?
Thank you for the response. Nice blog by the way.

Bridge table or factless fact table?

Hello,
I have a model a bit different that I've worked with in OBIEE (10), and I can't make it work. I have 1 fact table and two dimensions, joined this way in the physical layer:
Fact Table >- Dim Person -< Dim Address
The join between Fact Table and Dim Person is 1:N and the join between Person and Address is also 1:N, for example one person can have many addresses.
I have searched in forum, internet, etc. how to model this in the BMM, but I can't find the same model as an example. I have found similar models solved with a bridge table, but the model is a bit different (Fact Table -< Dim Person >- Dim Address), so it won't help.
I have tried many things, but the option that I thought it's more logic, is treating Dim Address as a factless fact table. However, when I choose in a report a fact from the real Fact Table, the person ID and the address, the fact was treated as null. What I expect is that the fact table should be repeated for every address that the person has. So, if the fact is 3 for one person, and the person has 4 addresses, the result should be 4 lines with the value 3 in each of them.
Can I make Dim Address be a factless fact table in the BMM? Should I include the Dim Address in the LTS of a single logical table? Is Dim Person a bridge table??
I hope you can help me with this one, thanks!

I'm not sure how much info you need to show on the reports, but you can try creating 2 separate logic schemas with alias tables.
1) Create alias table for fact and Dim Person and join them
2) Create another alias for fact (Fact1) and Address (always thinking that the perdon ID is also in the Address table) and join them.
Try to make your report between fact1 and address (in this case you can't put detail of the person,but you can make another report showing the persona information using the first schema.
J.

Answers on factless facts

Hi,
How does OBIEE, Answers in particular, cope with factless fact tables? The related dimensions would be linked to that factless fact in the pysical and BMM tier, but the factless fact would not be shown in the subject area.
When an user selects two or more dimensions linked through this factless fact, how would BI Server generate the query?
Is it recommended to have a least a dummy measure in that fact?
Thank you!

Hy,
I have an example here :
http://gerardnico.com/wiki/dat/obiee/bi_server/design/obiee_densification_design_preservation_dimension
I don't use a factless fact table but a densification process.
The techniques used are the same as it's based on the fact vertical partitioning.
http://gerardnico.com/wiki/dat/obiee/bi_server/design/fact_table/obiee_fact-based_partitioning_outer_joins
And you can see the two queries and the full outer join issued.
Success
Nico
And thanks Stijn (I didn't know the implict fact)

Factless fact tables????

Hi gurus,
Anybody please tell me about factless fact tables? in what are all the scenarios we can use it? Can we create Infocube without key figures?
Thanks,
Karthik T

Hi Karthik,
Please go through this....
A "factless" fact table is generally one which records instances of
time-bound relationships, rather than capturing transaction amounts. The
example usually given by Kimball is a fact table which records the
instances of students, professors, and classrooms reserved for specific
classes at a college. In this case, the "key figure" is simply a binary
switch indicating the truth of a relationship expressed by the
characteristics in the dimension tables (the "zero", or false, instances
are not stored.)
Look at the delivered BW Headcount / Employee Action cube, 0PA_C01, for a
rough facsimile of the "factless fact table." To implement such a thing in
BW, you still need a key figure -- usually an integer (quantity) holding
the value 1 (at the most granular level of detail,) indicating that a
relationship expressed in the dimension characteristics is true. You can
populate a cube like this by reading information from master data tables in
your update rules, with your datasource driving off your most granular
master data table. Again, see the delivered datasources and update rules
for the 0PA_C01 cube to see how SAP does it.
Assign pts if helpfull
Thanks,
Sujeet

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.

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

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

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

Fact to Fact Relationship urgent!!!!!!!

Let us suppose there are 2 dimensions and 2 facts and every dimension is joined with every fact and there is no relation between two facts while selecting columns from both the facts with any dimension column its involving only one fact, we found one solution which is combined sql (union).
can we have any other solution?
Thanks in advance

I hope I got your question.
If you have 2 unrelated facts joined to a common dimension, and if you drag the dimension value and the measures from your fact tables, the data should show up as expected.
For e.g. we have an orders received and an orders fulfilled fact tables that are unrelated, that we can see by day (the common dimension) in a single query without any union. Of course, your measures will need to be aggregated for your fact tables to return a single row for each dimension value, otherwise it would make no sense.
HTH,
Nilanshu.

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

FACT TO FACT relation

Hi ,
I have 2 fact tables fact1 and fact 2. Fact 1 table consists of some measures where as fact 2 consists of measures and lot more non-fact columns. but i would like to create a dimensional hierarchy for fact2 table so that i can drilled down all the non-fact columns but the problem is i couldn't able to create a dimension hierarchy for fact2 table. Is there any way i can create dimensional hierarchy on fact tables?? But i found a solution not sure is it best approach or not first i created an alias for fact2 table and joined the alias and fact2 table then with alias i created a dimension. Please let me know if this is the right approach or any other solution for this.
Thanks in Advance,
chakri

Chakri,
No need to go for alias in phyical layer. In logical layer (BMM), create 2 logical table - diff names with same single physical table and just drag the non-measure columns to 1st logical table and measure cols to second logical table from physical source. Now create a simple logical join from 1st Logical Table to 2nd Logical table (1:N), in this way first will behave as Logical Dimension(will turn to white color) and second as Logical Fact(will turn to yellow color). Now go ahead and create hierarchy using cols from 1st Logical Table. This is pretty straight forward.
Hope this clears your doubt and good to start with.

Fact to Fact linkage thru a map table

Hi,
I have a situation where in two fact tables are linked thru an intermediate map table. The purpose of doing so was to facilitatie an n:n relationship between f1 and f2. So this map table essentially has 3 columns viz pk, f1 key, f2 key. f1 and f2 has it's own sets of dimension tables attached to it. Of these some dimension tables are linked to the fact tables thru corresponding map tables to facilitate n:n relationships. So there are two types of map tables >> between two facts and between a fact and a dim. The reporting requirement is like this: attributes of f1,dimensions attched to f1, attributes of f2s attached to f1, dimensions attached to f2.
The design is tricky and was done a long time ago and solutions are currently running on it. So a design change is not possible. Can somebody suggest an approach to tackle this kind of a relationship?
Many thanks

Hi,
Many thanks for the suggestion.
I'd declared the map tables that connected fact to dimension as bridge tables. When I do the same for a map table between two fact tables, the conistency check fails. I get "Internal error: Missing functional dependancy assosiation for column : Control Legal Entity.d_checker_date" Control legal entity is a dim table which is connected to the fact table thru a map table and d_checker_date is the first column in that table. If i delete this column the same error repeats for the next column.
Any thoughts on this?

Fact to fact join

HI,
I have join like this
fact1 and fact2 >>>ledger>>RPT
so ledger will be confirmed dimension
now my report look like this
column from RPT and column from fact1 filterd by fact2 column
i bought both fact column in one logical table, and went to fact1 LTS and added ledger table as inner and RPT table as left outer
ledger+fact1 =inner
ledger+fact2=innner
ledger+rpt=left outer
still i am not getting result right
when i use column from only one fact still its joing with other fact
can i know how to do join?
Edited by: 944346 on Oct 3, 2012 11:37 PM
Edited by: 944346 on Oct 3, 2012 11:37 PM

Hi,
Kindly refer the below link
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
Hope this help's
Thanks,
Satya

IMPLICIT FACT & FACTLESS FACT

Similar Messages

Maybe you are looking for