Dimension table greater than Fact table

Hello,
By analysing infocubes with SAP report , i encounter a situation where I have more records in a dimension table than in the cube :
ABI_C0101          /BIC/DABI_C01011    rows:         22    ratio:          0 %
ABI_C0101          /BIC/DABI_C01012    rows:         27    ratio:          0 %
ABI_C0101          /BIC/DABI_C01013    rows: 3.558.433    ratio:        229 %
ABI_C0101          /BIC/DABI_C01014    rows:          1    ratio:          0 %
ABI_C0101          /BIC/DABI_C01015    rows:     66.440    ratio:          4 %
ABI_C0101          /BIC/DABI_C01016    rows:     15.383    ratio:          1 %
ABI_C0101          /BIC/DABI_C01017    rows:      2.533    ratio:          0 %
ABI_C0101          /BIC/DABI_C01018    rows:          1    ratio:          0 %
ABI_C0101          /BIC/DABI_C0101P    rows:          2    ratio:          0 %
ABI_C0101          /BIC/DABI_C0101T    rows:        122    ratio:          0 %
ABI_C0101          /BIC/EABI_C0101     rows:          0    ratio:          0 %
ABI_C0101          /BIC/FABI_C0101     rows: 1.551.333    ratio:        100 %
As the contents of the cube AND dimension are deleted before reload, I'm wondering how this can happen.
Can somebody help me here ?
Thanks.
Fred.

Hi,
As I said yesterday, I'vz got the same feeling and test it by manually delete cube and dimensions before load and dimension is now only 17% of the cube. This is well what I expected.
I will give also a feeback on the report SAP_INFOCUBE_DESIGNS. When I ran it after manual delation of the cube, the number of rows in this report doesn't change ! So, I suppose that thsi program read some statistics but it does'nt read directly tables for sure.
So, conclusion is well that the variant doesn't work correctly. I will check OSS and open a note if required.
Thanks all for you ideas.
Fred.

Similar Messages

How can we know that size of dimension is more than fact table?

how can we know that size of dimension is more than fact table?
this was the question asked for me in interview

Hi Reddy,
This is common way finding the size of cube or dimensions or KF.
Each keyfiure occupies 10 Bytes of memory
Each Char occupies 6 Bytes of memory
So in an Infocube the maximum number of fields are 256 out of which 233 keyfigure, 16 Dimesions and 6 special char.
So The maximum capacity of a cube
= 233(Key figure)10 + 16(Characteristics)6 + 6(Sp.Char)*6
In general InfoCube size should not exceed 100 GB of data
Hope it answer your question.
Regards,
Varun

Dimension Table Larger Than Fact Table

Hi,
I need a solution to deal with a situation in my project. The master data for the Business Partner is close to 20 Mil and growing. The overall records in the fact table is only 1.5 to 2 Mil.
I am looking for suggestions that can help me in designing a optimal data model which does not hinder the reporting performance. Reporting with 20 Mil records in Dimension and 10 times less data in the fact table is not common occurance. I guess this is a scenario that the retail Industries would have experinced due to the huge customer base.
P.S: Segregation of the dimension is something that will not help. And its currently a line item dimension. So any thoughts apart from these will be highly appreciative.
Thanks!
Sajan R

Hi Sajan Rajagopal ,
I think u need to just go through the dimensions u had created so trat u can delete unnecessary infoobjects assigned to tat dimension and can build a dimension whcih has only those of master data.
For Ex...for the material master when we checked we had huge amount of data more than ur's so we had made diffenet dimenons for material and batch and then we had tried to load the data for tat dimensions and it was working fine and also data loads also getting loaded fine..
Please check ur dimensions once so tat required ones are defined correctly in the dimensions

Few dimension values used in FACT tables.

Hello all,
We are trying to know if somebody faced this issue earlier. We have dimension tables containing 5 million records, but the fact table uses hardly 30k of these dimension values. The fact table contains 350 million records, so is there any way to improve the performance of the query in such a scenario, where hardly 20% of dimension values are actually used by the FACT tables.
Thanks and Regards,
Upendra

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 ?

Dimension and fact table with a fact table between them

Hello all,
Here is my problem. As seen in the image, I have a fact table linked to the two dimensions.
I would have the number of Id from Cube_Requirements by variant including 'unknown" variant if no linked variant.
How is it possible ? How to create the dimension ? As my fact table has two fields, if i want to use reference as dimension usage, it doesn't work.
Thanks for your help.

Hi, this looks a many to many relationship scenario, follow these steps:
- drag extractid from cube_applicability onto measures area, so this table becomes a fact
- you will have count of Extractid measure after you perform above step
- Assuming Variant is already a dimension, go into dimension usage tab, link variant dimension with cube_requirement fact using many to many relationship and selecting cube_applicability
process cube, you should be able to get count of id by dragging and dropiping id from variant dimension..
Regards
Rakesh

Conformed dimension and query multiple fact tables

Hello,
Please if someone can guide me on this requirement.
Requirement - I have a conformed dimension D1 and two fact tables F1 and F2. Both fact tables have many columns so I cannot merge
the two fact tables into one logical table. Currently both these fact tables have logical tables F1 and F2 respectively.
As per design the conformed dimension is a simple logical table in the rpd and not a dimension.
Can someone guide me how should i proceed so that i'll be able to fetch information from both the fact tables?
Edited by: 930542 on Apr 26, 2012 12:28 PM

Hi,
Currently the dimension table is taken as a simple logical table in rpd as it does not have have any levels or hierarchy.
Its a flat dimension. Can you guide me how can I implement a flat dimension in OBIEE? Because this dimension is taken as simple logical table
I am not able to set appropriate level for fac tables. This dimension does not appear in the list of dimensions.

Same dimension in two different fact tables

Hi,
I have one same dimension in two different fact tables. I would like to know how BI server choose the fact table when I do a request in this dimension.
I know that is always using the same fact table, but I would like to know why choose this table and not the other.
Thanks

Sorry,
But it doesn't seem to me.
I reorded the tables in the BMM layer and it continues to use the same table, regardless this table is in last.
After, I droped that table in the BMM layer and it continued to use the same.
Thanks for your reply

Incorrectly defined logical table source (for fact table X

Hi!
Imagine the following Physical Diagram:
- Dim A
- Dim B
- Fact A
- Fact B
Joins:
- Dim A is parent of Dim B
- Fact B has a FK to Dim B
- Fact A has a FK to Dim A
Business Layer:
- Logical Table Dim A
- Logical Table Dim B
- Logical Table Fact A
- Logical Table Fact B
Joins:
- same joins (not FK Joins) that Physical Layer
When we build a report that only has one column of Dim A and one column of Dim B (A is parent of B), the following error appears:
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 "Fact A") does not contain mapping for [Dim A.col1, Dim B.col1]. (HY000)
What is wrong?
Help!
Thanks.

Hi,
The joins of dimensions go via a fact table. In your case there is no common fact table.
You can solve this by drag/drop a field from the physical table Dim B on the displayed logical table source of the logical table Dim A.
Now the BI Server knows that Dim A and B have a physical relationship.
Regards

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.

What type of table is E Fact table

Hi Experts,
please let me know What type of table is E Fact table??
Thanks
Mark

Hi Mark,
A cube has 2 fact tables - E and F. When the requests are loaded in the cube the data exists in the F fact table This table contains the Request ID. and when the requests are compressed the data lies in the E fact table.
When the requests are compressed all the request ids are lost(set to NULL) and you would not be able to select/delete the data by request id. The data in the E fact table is compressed and occupies lesser space than F fact table.
assign points if this helps,
Thanks,
Sudhakar

Adding Dimension field ($) in measures (fact) table in logical layer

Hi,
I have a field (amount) in the dimension table. I would like to add this field in the fact table at the logical layer. Dimension table and fact table had physical joins. Can I add into fact table and still do aggregation on that field based on the other dimensions linked to fact table. I working on Siebel Analytics version 7.8. Any help would be greatly appreciated.
Thanks in advance,
RK

Check here : How to create a measure from data that is stored in a dimension table
http://gerardnico.com/wiki/dat/obiee/bi_server/design/fact_table/obiee_measures_dimension
Cheers
Nico

Two Filter on Two dimensions without constraining the fact table

Hi All,
does anybody know how to avoid the fact constraint when creating a report with two filters on different dimensions?
I have a big fact table with more than 10 Million rows. In the starmodel the is the dimension customer and products. I create a filter on the customer atrribute "Status" and choose the value "Active". Now I add the column "Product Type" from the dimension "Product" to the filter section. When I want to choose a value OBIEE executes a select statement within the fact table. So I have to wait very long to select a value. Is there any way to say OBIEE only to select the dimension table without joining the fact table?
Thank you very much in Advance.
Regards,
Stefan

Hi Stefan,
Generally queries on the dimensions (across dimesions also) always go through a fact. In case, you would like the queries not be through fact table, but just the dimension tables right away, you can set up a separate subject area for them.
You can create a separate subject area based on a dummy fact table to get these prompt values.
Please refer to http://gerardnico.com/wiki/dat/obiee/presentation_service/obiee_parameter_prompt_subject_area for more details on this setup.
Hope this helps.
Thank you,
Dhar

Distinct count of dimension business key in fact table

In my cube I have a fact table which joins to a patient dimension. The patient dimension is a type 2. What I would like to do is get a distinct count of patients who have records in the fact table. The business key in the patient dimension
is the PrimaryMrn. So a SQL query would look like this.
SELECT count(distinct PrimaryMrn)
FROM EncounterFact e
INNER JOIN PatientDim p
on e.PatientKey = p.PatientKey
Is it possible to do this via MDX?
Thanks for the help.

If you have to distinct count an attribute in a SCD 2, you might choose between:
Denormalizing that attribute in the fact table, and the create a classical DISTINCT COUNT measure
Use a many-to-many approach - see the "Distinct Count" scenario in the Many-to-Many White paper here:
http://www.sqlbi.com/articles/many2many (for both Multidimensional and Tabular
If you use Tabular, you might want to read also this pattern:
http://www.daxpatterns.com/distinct-count/
Marco Russo http://www.sqlbi.com http://www.powerpivotworkshop.com http://sqlblog.com/blogs/marco_russo

Dimension key in a fact table should be repetitive?

Hi All,
We do have one to one relationship between a FACT table and Dimension table? Is it correct to have this kind of dimensional model.

You may find this link of some help.
How to Model Fact table having 1:1 relationship with key Dimension attributes

Multiple Joins from one Dimension Table to single Fact table

Hi all,
I have a single fact table with attributes as such:
Action_ID
Action_Type
Date_Started
Date_Completed
and a Time Dimension to connect to the fact table. Currently the 2 Date columns in my fact table are in the format of 20090101 (which is the same as my key in the time dimension), if it means anything. I've tried to create multiple joins but have been getting error messages. What is the easiest way to link the time dimension with the two date columns in my fact table? Thanks.

hi..
it seems to be, you need to use between operator to join time dimension with fact (i.e. Non-equi join)
If it's then you should create complex join in physical layer by connecting dimension with your fact.
select columns and operators in such a way that it resembles something like the below.
timeDimension.timeKey BETWEEN FactTable.Date_Started AND FactTable.Date_Completed

Dimension table greater than Fact table

Similar Messages

Maybe you are looking for