Dim & fact table sizing details

Hello Folks,
Is there any transaction which gives us direct relationship about sizing of dim and fact tables?
Thanks,
Suyog.

Hi Suyog,
Run this Program in SE38 SAP_INFOCUBE_DESIGNS .
This gives the Ratio aswell number of records.And also Dimension Mismatch.
Rgds
SVU

Similar Messages

Problem Facing while analyzing Dim/Fact Table % using RSRV

Hi All,
When we analyzing the infocube in RSRV to see percentage of Dimension tables, system is showing 0% for all the dimensions and also for Fact tables.
But data is existing in fact table of infocube and also in dimensions tables, when we see in SE11.we also executed report SAP_INFOCUBE_DESIGNS in SE38, in their also we are not able to find any entry for particular infocube.Please advice on this ASAP.
Regards
Manoj

Hi,
Check whethere the statistics for the cube is run. If not refresh the stats ans then chk in RSRV or in SAP_INFOCUBE_DESIGNS you will get the ratio betwene ur dim and fact table
Hope it helps.
Regards,
Malar B

Reason for dim fact tables ratio

Friends.
What is the exact reason for Dim tables not be greater than 20 % of Fact tables.
How does that really impact performance?

Hi,
In an extended star schema, dimension tables stores the DIM IDs and SID IDs to access the data from the actual characteristics. These dimension tables are attached with fact table with DIM IDs. Now if the size of the DIM table is as large as the size of fact table, then the cause of DIM table will not be used at all. It is as good as referring the master data for each record from fact table itself.
That's why it is ideally suggested that the ratio size of DIM table to that of fact table is 1:10.
Hope this info helps you.
Regards,
Yogesh.

Joining bridge ,dim,fact table

Hi
I have scenario where I have a bridge table,dimension table,and 2 fact tables.
The dimension table is a common table for both fact tables.
The bridge table contains the dimension tables Primary key.
The bridge is also having an other dimension table PK, but that table is not joined to any fact table.
Now I have a req where I have to get a column from bridge table and fact2 tables.
Individually when I pull those columns I am getting data.
When I pull those 2 columns together , getting " the specified criteria dint result in any data".
Tried changing joins in RPD nothing worked.please help me , this is very urgent.
In SQL developer when I joined bridge and fact or dimension and bridge I am able to get expected results.
Thanks
Sr

Hi Suyog,
Run this Program in SE38 SAP_INFOCUBE_DESIGNS .
This gives the Ratio aswell number of records.And also Dimension Mismatch.
Rgds
SVU

Dim Fact table Sizes

Hi Experts,
Could anyone please explain me stats from SAP_INFOCUBE_DESIGNS .
ZABC_C01          /BIC/DZABC_C01       rows:         17    ratio:          5 %
ZABC_C02          /BIC/DZABC_C02       rows:        311    ratio:         88 %
ZABC_C03          /BIC/DZABC_C03       rows:         15    ratio:          4 %
ZABC_C04          /BIC/DZABC_C04       rows:        346    ratio:         98 %
ZABC_C10           rows:    205,786    density:              0.0 %
ZABC_C10          /BIC/FZABC_C10      rows:    205,786    ratio:        100 %
ZABC_C10          /BIC/EZABC_C10      rows:          0    ratio:          0 %
ZABC_C10          /BIC/DZABC_C10P     rows:          2    ratio:          0 %
ZABC_C10          /BIC/DZABC_C10T     rows:        171    ratio:          0 %
Any measures to be taken ?
Appreciating your help Thanks.

Report Writer,
The ration between the each individual dimension rows and the fact table rows. OK. Say that you have 2000 rows in the fact table and 200 entries in the dimension table, that is about 10 times of the dimension size is what you have in your fact table. currently at this rate it is ok, but there are chances for this parity to grow and the ration might become more than 10% of the fact tablke in the future and it is called high cardinality, you need to find ways to minimize that. If you cannot then declare the field as 'line item dimension'. This will help better as this directly stores the sid in the cube, so the join if more efficient.
If you use LISTSCHEMA for a cube and expand the tree structue to look at each table with SE11 or SE16 you will get more idea about the cube and the join and lot more info. This will help you understand better.
Hope this helps.
Alex(Arthur Samson)

Two FACT Tables, Some Common and Non-Common Dimensions

Hello all, a question i am sure you have faced in the past but still wanted to get your feedback.
I have a few FACT tables and some dimensions that are shared (common dimensions). Rest of the dimensions are related to one or the other FACT tables.
What is the best way to present a view where users can pull information from both the FACT tables?
I am successful in pulling the shared (common) dimensions across BOTH FACT tables having the same grain but this view breaks down when i pull information from one Dimension that has not much to do with the other FACT.
What is the best way to present this? Should this be broken in three subject areas?
Subject Area 1 --> Some Dims --> FACT Table A
Subject Area 2 --> Some Dims --> FACT Table B
AND
Subject Area 3 --> ***Only Common Dims*** --> FACT Table A & FACT Table B?
Your feedback is always appreciated.
Regards,
Edited by: user10679130 on Oct 12, 2009 3:27 PM

Please check the forum first for similar threads/questions.
Joining two fact tables with different dimensions into single logical table
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
This solution keeps both fact tables in the same subject area in the single logical fact table, with common and not-common dimensions.
Regards
Goran
http://108obiee.blogspot.com

BMM issue for multiple fact tables

Hi All,
I have three facts F1,F2, F2 and two confirmed dimension D1,D2 in my sample rpd.
In BBM layer , I tried to do the modeling as follows instead of creating one logical fact table. There are many fact tables to come
in future.
F1<----D1--->F2<----D2--->F3
When I deploy this sample rpd and run the report from F1 andF2, I get an error No fact Table exists at requested level of detail.
I have not created any hierarchical dimension to set up the content in the fact table.
I am very much thanksful for any advices.
Thanks,
Vishal

Hi,
Please refer the below link.
http://satyaobieesolutions.blogspot.in/2012/07/implementing-multiple-fact-tables-in.html
My suggestion would be bring both the facts to the same logical table sources and have a single fact table in the BMM layer joined with multiple dimensions.
Build a dimension hierarchy for the dimensions and then in the content logical layer mapping, map the dimensions to the fact tables with detailed level/Total
Refer the below link-
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
Hope this help's
Thanks,
Satya
Edited by: Satya Ranki Reddy on Jul 26, 2012 7:34 AM

How to find Size of the fact table?

hello all
how do i find out the size of the fact table?
Is the size of the fact table is same as size of the cube.
pls let meknow
regards
balji

Hello Balaji,
To find out size of fact table
DB02 ->Detailed anaysis -> Fact table name
It will show you the details.
The size of cube is not exactly equal to the size of fact table, but usually as fact table is much more larger than dimension tables, fact table size will give you a fair idea about cube size.
Hope it helps.
Regards,
Praveen

OBIEE 11g: Fact table does not have a properly defined primary key

Hi,
We have two fact tables and two dimension tables.
We have joined the tables like
D1-->F1
D2-->F2
D1-->D2
We dont have any hieracies.
It is throwing error in consistency check,
[nQSError: 15001] Could not load navigation space for subject area ABC.
[nQSError: 15033] Logical table Fact1 does not have a properly defined primary key.
It is not like STAR Schema, its like snowflake schema. How to define primary key for fact table.
Thanks.

Hi,
My suggestion would be bring both the facts to the same logical table sources and have a single fact table in the BMM layer joined with multiple dimensions.
Build a dimension hierarchy for the dimensions and then in the content logical layer mapping, map the dimensions to the fact tables with detailed level/Total
Refer the below link-
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
Hope this help's
Thanks,
Satya

No fact table exists at the requested level of detail Error.

Hi Everybody,
Facing a issue on the using Fact less Fact tables.
Scenario:
========
Using two subject areas to develop a report.OBIEE 11g
Fact1 --> Compensation Plan Assignments Real Time
Fact2 --> Participant Detail Real Time"."Participant Details
On both facts we created dummy metrics on respective table id's and aggregated to ROWCOUNT.
As i said in earlier we are using the above 2 subject areas to develop reports.
Logical SQL:
===========
SELECT
0 s_0, "Incentive Compensation - Compensation Plan Assignments Real Time"."Role"."Role Name" s_1,
"Incentive Compensation - Participant Detail Real Time"."Participant Details"."Cost Center" s_2,
"Incentive Compensation - Participant Detail Real Time"."Participant Details"."Country Code" s_3,
"Incentive Compensation - Participant Detail Real Time"."Participant"."Participant First Name" s_4,
"Incentive Compensation - Participant Detail Real Time"."Participant"."Participant Last Name" s_5,
"Incentive Compensation - Participant Detail Real Time"."Participant"."Party Number" s_6
FROM "Incentive Compensation - Earnings Real Time" FETCH FIRST 65001 ROWS ONLY
Error Message:
==============
Expression 'RowCount:[DAggr(Fact - Compensation Plan Assignment.RowCount by [ Dim - Participant Details.Cost Center, Dim - Compensation Role.Role Name, Dim - Participant.Participant Name] )]' converted to NULL because [nQSError: 14020] None of the fact tables are compatible with the query request RowCount:[DAggr(Fact - Compensation Plan Assignment.RowCount by [ Dim - Participant Details.Cost Center, Dim - Compensation Role.Role Name, Dim - Participant.Participant Name] )]..
[2013-10-21T12:18:45.000-05:00] [OracleBIServerComponent] [TRACE:2] [USER-34] [] [ecid: 004uJx90aHO9lZ73VJJNB80007eh000gl_,0:2:1:9:5] [tid: 457c2940] [requestid: f2e001b] [sessionid: f2e0000] [username: [email protected]] -------------------- Query Status: [nQSError: 14025] No fact table exists at the requested level of detail:
Please share some ideas on this or any guidelines will be very much helpfull.

Govardhan,
Did u configured any Dimension Hierarchy please set the levels in that particular Fact LTS.
For more info,check the below thread
https://forums.oracle.com/thread/2134934
Thanks,

No Fact table exists at this detail level error

Hi All,
I am trying to develop an RPD and was trying to use a simple example of joining two fact tables in OBIEE through confirmed dimension.
This is my example:
Fact A: Student ID (FK)......Measure1, Measure2...
Fact B: Student ID (FK)........Measure A, Measure B
DIM 1: Student ID (PK),.....
I would like to give the users the option of joining Fact A and Fact B through Dim 1( Which is a conforming Dimension)
I tried with out level based hierarchy and got NO Fact exists at this level of detail.
Then I tried creating the level based hierarchy on Dim 1 and selected the detail level for the fact table and I am still getting the error message.
Am i doing some thing wrong here ? Or Am i missing any important setting ?
Is there a way to check whether the dimension is a conforming dimension or not in OBIEE.
Your help is much appreciated.
Thanks
Venu

Can we use between operator in physical join. We did that, its successfully checking in, but when we re-open the join, its show in RED color.
So, got doubt, can we use between?When you checkout the rpd object in online mode it would display in red, this is not an error.
"No fact table exists at the requested level of detail"; what does this error meanThis error usually happens if you have not mapped the content level correctly in the logical table source.
Rgds,
Dpka

OBIEE 11g - No fact table exists at the requested level of detail

My dimesion tables are snow-flake.
Table1 has Key, ProductName, ProductSize, Table2Key
Table2 has Key, ProductDepartment, Table3Key
Table3 has Key, ProductDivision
I have created 2 hierarchies (in same dimension Product). Note: ProductSize is in Table1.
ProductDivision > ProductDepartment > ProductName (shared level)
ProductSize > ProductName (shared level)
There are 2 fact tables
Fact1 is at ProductName level
Fact2 is at ProductDepartment level
When I create a request with columns as ProductSize and some measure; and filter it on ProductDepartment. The request fails with error "No fact table exists at the requested level of detail", but the request can ideally be answered using fact with ProductName level.
I have properly defined logical level keys in the hierarchies and logical level in the LTS (content tab)
Can anyone point me what I am doing wrong here?

Since both fact tables are at same granular level I would suggest to map each other (Signon_A maping Signon_B) in BMM layer logical fact @source.
Considering them as Fact and with fact extension.
BTW: Did you try by setting implicit fact at subject area properties?
Edited by: Srini VEERAVALLI on Feb 1, 2013 9:04 AM

[nQSError: 14025] No fact table exists at the requested level of detail:

Hi All,
I am using OBIEE 11.1.1.6.8.
I have below senario...My fact table contains 3 LTS(yearly, Monthly, Weekly) and TimeDim contains3 LTSs(yearly, Monthly, Weekly)
Fact-Weekly joins with (D1,D2,D3) & TimeDimWeekly
Fact-Monthly joins with (D1,D2,D3) & TimeDimMonthly
Fact-Yearly joins with (D1,D2,D3) & TimeDimYearly
I hv also set the Fact source content to appropriate level of TimeDIM and details level of other Dimensions.
when i build a report using only year_code or month_code_or week_code as filter the query is going to appropriate physical sources
ie. if i take week_code as filter then the query firing to FactWeek, TimeDimWeekly & other Dimensions
if i take Month_code as filter then the query firing to FactMonthk, TimeDimMonthly & other Dimensions
Problem is when I use dynamic filter its is giving [nQSError: 14025] No fact table exists at the requested level of detail: error.
My filter is something like this using presentation variable pvTime (filter is prompted)
case '@{pvTime}'
when 'Weekly' Then "Calendar"."Week - WYYYY"
when 'Monthly' Then "Calendar"."Month - MONYYYY"
when 'Yearly' Then "Calendar"."Year ID" end
Please help me if I missed any step
Thanks
Smita

Its a guess but try the below.. As you are using the CASE statement in your filter, use it in the below way.
Store the value that is prompted into a presentation Variable
YOUR WAY
case '@{pvTime}'
when 'Weekly' Then "Calendar"."Week - WYYYY"
when 'Monthly' Then "Calendar"."Month - MONYYYY"
when 'Yearly' Then "Calendar"."Year ID" end
SUGGESTED WAY
(case '@{pvTime}'='Weekly' and "Calendar"."Week - WYYYY" = '@{new PV}' THEN 1
when '@{pvTime}'='Monthly' and "Calendar"."Month - MONYYYY" = '@{new PV}' THEN 1
when '@{pvTime}'='Yearly' and "Calendar"."Year ID" = '@{new PV}' THEN 1 ELSE 0 END) =1
This might correct the way your are using your CASE statement in Filters..

No fact table exists at the requested level of detail

We have two fact tables F1,F2 and D1, D2, D3, D4, D5 dimensions.
They are connected line this.
F1 to D1, D2, D3 and self dimension D_of_F1
F2 to D2, D3 and self dimension D_of_F2
Means D2 and D3 are common dimensions between two facts.
D_of_F1
         |
         |
D1--F1--D2
         |      |
         |      |
        D3   |
        |       |
        |       |
        |-F2-|
        |
        |
        |
   D_of_F2
Hierarchies
H1 for D1
H2 for D2
H3 for D3
H_of_F1 for D_of_F1
H_of_F2 for D_of_F2
and pinned LTS of F1 --> H1 detail, H2 Detail,H3 Detail, H_of_F1 Detail
and pinned LTS of F2 --> H2 Detail,H3 Detail, H_of_F2 Detail
We are selecting these columns
D1.C1, D1.C2, D2.C1, D2.C2,D3.C1 and report works perfactly.
But when I add D_of_F2.C1 then report gives this error
Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14025] No fact table exists at the requested level of detail
Please help me to solve this error....
I m new in OBIEE concepts so not able to trubleshoot...
Thank you.

i'm try to do an analysis between two tables (that have a relatinship), we had inclued first the FACTURA.FACTURA_COD, then columns from COBRANCAS and it work's. When we inclued the FACTURA.COMISSIONISTA_ID it return the fowlling error :check the level set in content tab in fact table.it can happen that FACTURA.COMISSIONISTA_ID is at a lower level than specified in fact table.
Regards,
Sandeep

No Fact Table Exists at the request level of Detail

Hi,
I'm new to BI.can anybody come across more than one fact table in BMM layer,currently i working with AP module,i am getting the error Error NO:14025 No Fact Table Exists at the request level of Detail.
Even i check with content tab where i have given detail level for confirming tables and total for non-confirming tables.
can any one have document related more than fact table in BMM layer, any body give me the right solution.
Thanks in advance !

thanks for your response,i did for the selected measures also. in Account payable model i have two fact.
F1 with dimension D1,D2,D3,D4
F2 with Dimension D5,D6,D7,D8
when i'm trying to generate reports F1 with D1,D2,D3,D4 i am getting the output,but with the non-conforming table D5,D6,D7 i am getting the error. can you give some document to work more than 1 fact table.

Dim & fact table sizing details

Similar Messages

Maybe you are looking for