Often time you will come across scenario where in presentation catalog you have 2 or more fact tables

and couple of dimensions. And not all the fact tables are joined with all the dimensions. And when you just query the data out of dimension which is not joined to a fact table. It will give you an error like. Cannot navigate to the fact table. Matter of fact is : Whenever you query the data just from the dimension it does not just read the data from dimension but it join that dimension with the fact and then get the data from dimension. Pretty weird huh… So to resolve this what you will need an implicit column in presentation catalog so whenever you query data from dimension it goes through the table where you have defined an implicit column. In BMM layer , create a dummy logical column and called it as implicit column , map that column to any number of your choice. Please refer the below screen shot.

Once you are done creating the implicit column. Double click on the presentation catalog and select the newly created column.

1) 2) Densification Performance benefit We will discuss on them. Densification: .) Avoid performance issues by using the implicit fact constant OCTOBER 6.you will be just fine. ( Again it has to join in BMM and Physical where you have defined implicit column. 2010 LEAVE A COMMENT Implicit Fact Constant: There are two main advantages of using the implicit fact constant.Now if you query just a dimension tables.

Performance benefit In some OOB vanilla stars.Whenever a dimension attribute and a fact measure are put into a report. So the dimension attributes which have the data in the fact table appear in the report. create a new Logical Fact table source containing this fact table and the Dummy Fact column. Set this implicit fact column of the presentation catalog to point to the implicit fact constant. the implicit facts are defined on measures aggregated by function count(distinct). the requirement is to create a Cartesian join across all the dimensions (the attributes of which are pulled into the report) and make the OBI server to do conforming dimensions join using a dummy fact table and fact column. OBIEE creates a physical join between the dimension table and the fact table.. To achieve this. Using a count distinct or any other function increases the cost on the performance for each query. Hence defining the appropriate column (implicit fact constant) without defining any unwanted formula will drastically improve the performance of the reports or performance of the marketing queries . Ensure that the fact column has an aggregation. sum(count(distinct)) etc. From technical perspective. But the user may want to see all the dimension values. This is called densification in Oracle.

Sign up to vote on this title
UsefulNot useful