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.

Similar Messages

Creating Time Dimension from date columns in fact tables.

I remember watching a demo from a BI Tool a couple years ago, wich I swear was OBIEE, and the presentator stated it was possible to create a Time Dimension in the admin tool, based on a date column in other table.
Can you guys tell me if there's such functionality in OBIEE?
If so, how could I achieve that?!
Thanks in advance!
Marcos

hi,
You are trying to make Fact table as Dim table ???
Fact table has some dim columns??
We can do this by making a fact table as dim table ,create a dim hierarchy on that table
Year level :Extract(year from fact_date_column)
Month and year level:CAST (Extract(month from fact_date_column) As CHAR(5) ) || CAST (Extract(yearfrom fact_date_column) As CHAR(5) )
Like this
But,be careful while doing this make sure that all joins and content levels are good
As per my knowledge this is not a good way,Experts can add some words lets see!!!!!! :-)
thanks,
saichand.v

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

Non dimensional attributes in a fact table

i would like to add 2 fields into my fact tables - LOAD ID (populated by a sequence during each load) and LOAD DATE.
as these fields are not related to any reporting dimensions, it is still possible to add them in OWB ? the fact wizard always ask for a foreign key to a dimension ...

i would like to add 2 fields into my fact tables - LOAD ID (populated by a sequence during each load) and LOAD DATE.
as these fields are not related to any reporting dimensions, it is still possible to add them in OWB ? the fact wizard always ask for a foreign key to a dimension ...
Duncan,
If you want to add non dimensional attributes to a fact by using OWB, you can create additional measures to it and use them as attributes.
Igor

Dimension ids are 0 in fact table of infocube

Hi ,
We have cube in which we have have dimension A which has two chars stocktype (non masterdata).
and stock category(non masterdata).
When I checked the fact table of the same cube I could see that the DIM ID for A is maintained as 0 for all values.
In this case how does the DIM IDs get linked to the fact table.
Please explain.
Thanks.
Ramesh

Hello Ramesh
DIM ids are combination of SIDs. Please check whether those two InfoObject have "Attribute Only" option checked in InfoObject maintenance.
If that is the case , then there will be no SID table generated for these two InfoObjects and if no SID is there, there can not be any DIM id.
But I was wondering why this if these are Attribute Only then why did system allow you to add them in dimension.
Another possibility, you did not get any data for these two field in this cube , so it did not check SIDs and generated DIM ids.
Do you have value for these two fields in the cube?
Regards
Anindya

Dimension table is added as Fact table

OBIEE 11.1.1.5
I have a table that I am importing into the BMM as a dimesion table. Each time I try and join the existing fact to this dimension table in the BMM it recognizes the dimension as a fact table. How can I add this table as a dimension.

Hi,
Define a primary key in dimension table and establish the join between fact and dimension table in both physical and BMM layer.Better to use physical join in both the layers.
mark if helpful/correct...
thanks,
prassu

OBIEE-can we link two dimension tables belonging to different fact tables?

Hi ,
I have just started with OBIEE concepts....need your views on this issue:
Fact 1 -> Dim 1, Dim2,Dim3 and so on..
Fact 2 -> Dim a, Dim b,Dimc and so on...
If I link Dim1 and Dim a with a valid key ,would that distort the star schemas to slowflake in BMM layer?
Thanks in advance!
Neha

I don't see this that would make it snowflake more like what I think as conforming dimensions. You need to make sure the grain of the measures is at what level , the they are same grain then you should be good however if they are different then you would start seeing null values.
Fact Measures use the same, conformed dimensions like Dim1 and Dim a if you trying to generate from multiple facts, the BI server was able to automatically stitch them together into a single result set. If they came from the same fact table that's easy as its only one single table, but if you are pulling from different fact tables, the conformed dimensions would allow them to be stitched into the same report
Conformance means that these sources can be mapped to a common structure – the same levels – and also the same data members.
Mark if helps.
Thanks,
SVS

Where we can find the dimension exceeds 20% of the fact table

hi all,
we have dimension in cube if i want to make the dimension as the line item dimension. before doing that we need to find the dimension is exceeds the 20% of the fact table.
where we can find this option?
please let me know ....
thanks

hi mallikarjun,
please follow the steps:
1.Go to t-code RSRV
2.Choose "All Elementary Tests" - "Database."
3 Double-click the line "Database Information about InfoProvider Tables
4.In the window on the right, choose "Database Information about InfoProvider Tables
5.Enter the InfoCube name and choose "Execute Tests
6.. After the analysis finishes, choose "Display Messages" and open the analysis tree with the correct time stamp.
Hope this will help you
REGARDS
AMAR.

How do I use Derived Table to dynamically choose fact table

How do I use the Derived Table functionality to dynamically choose a fact table?
I am using BO XI R2 querying against Genesys Datamart kept in Oracle 10g. The datamart contains aggregated fact tables at different levels (no_agg, hour, day, week, etc...) I would like to build my universe so that if the end user chooses a parameter to view reports at daily granularity, then the daily fact table is used; choose hourly granularity, then hourly fact table is used, etc....
I tried using dynamic SQL in Oracle Syntax, but Business Obljects Universe didn't like that type of coding.
The tables look something like this:
O_LOB1_NO_AGG o
inner join V_LOB1_NO_AGG v on o.object_id = v.object_id
inner join T_LOB1_NO_AGG t on v.timekey = t.timekey
Likewise, in the 'hour', 'day', 'week', etc... fact tables, the Primary Key to Foreign Key names and relationships are the same. And the columns in each O_, V_, T_ fact table is the same, or very similar (just aggregated at different levels of time).
I was thinking of going a different route and using aggregate aware; but there are many Lines of Business (20+) and multiple time dimensions (7) and I believe aggregate aware would require me to place all relevant tables in the Universe as separate objects, which would create a large Universe with multiple table objects, and not be maintenance-friendly. I also was going to dynamically choose Line of Business (LOB) in the derived tables, based on the end user choosing a parameter for LOB, but that is out-of-scope for my current question. But that information sort of points you down the train of thought I am travelling. Thanks for any help you can provide!

You can create a derived table containing a union like the following:
select a,b,c from DailyFacts where (@prompt('View'....) = 'Daily' and (<rest of your where conditions here if necessary>)
union
(select a,b,c from MonthlyFacts where (@prompt('View'....) = 'Monthly' and (<rest of your where conditions here if necessary>))
union
(select a,b,c from YearlyFacts where (@prompt('View'....) = 'Yearly' and (<rest of your where conditions here if necessary>))
I assume that you are familiar with the @prompt syntax
Regards,
Stratos

Incorrect defined log. table source- 2 differen fact tables but same source

Hi Guys,
I have been struggling with this error for a while and searching this forum led me to a few posts but people seem to have a different setup such
as with Dimension tables or joining multiple facts).
My issue is that I can not even select two column from one and the same fact table.
[[screen print of issue]|www.metallon.org/test/Incorrect_source.jpg]
Thanks,
metalray
note: Total is just a calulated/derived logical colum such as A+3

Total is calculated and the calculation takes values from a DIFFERENT fact tables BUT those fact tables have the same PHYSICAL source.
so yes, there is no link between the facts but they are the same physical source anyway.....hm

How to force BI Server to pick from the Agg table and not the Fact table?

Hi All,
I have 3 tables as the Sources in the Key measures. 2 are fact tables and the other one is the agg table.
E.g.
Fact 1 at A,B,C,D and E level
Fact 2 at A,B,C level
Agg at A,B,C level which contains the measures from the Fact1 and Fact2
So when I select the measures from the Agg which are coming from Fact1 the Agg table get fired and when I select measures from Agg which are coming from Fact2, the Fact2 table gets fired in the SQL Query.
Now my question here is there anyway to tell BI Server that when I select Fact2 measures fire the Agg table and not the Fact2 table. The reason being the Agg and Fact2 tables are at the same level.
But I need to keep the Agg table as it is one level higher than the Fact1 tables.
Any pointers would be helpful.

hi,
you explain us your situation really good.but you forgot to tell us the most import,the measures in aggregate table and the aggregated dimensions.
meaning,you have 7 measures aggregated in some levels of your dimensions tables?if yes,there is no possibility Bi goes anywhere else..(by choosing only these measures and the defined levels at your dimensions..)
One more thing,if you choose a combination of your 2 fact data sources,bi goes?where???
hope i helped...
http://greekoraclebi.blogspot.com/

Rptcurrency in WB table, fac2 tabke and fact table

I loaded a data by using a transformation file with the following logic for reptcurrency
RPTCURRENCY= *newcol(LC)
The data was successfully loaded, then I check the WB table, fac2 table and fact table respectively, I notice the following:
In WB table,          rptcurreny    ....     signeddata
                               LC                         5000
In Fac2 table     rptcurreny    ....     signeddata
                             USD                         5000
                             EURO                     5000
In fact table          rptcurreny    ....     signeddata
                             USD                        5000
                             EURO                     5000
                             LC                          5000
I have USD,EURO and LC in the rptcurrency,USD and EURO's reporting property value as 'Y'. looks like when the system load the LC data, it copy the LC data to USD and EURO, but for me it not make scence the same value with different currency.
Anybody can explain this?

JW,
Please check your default.LGF formula at Admin console.
Default.LGF is called 'DEFAULT' which means it will be called whenever user posts their data to server.
If default.LGF includes baisc currency translation statement, it will convert value behind the scene
Of course, user can execute it again through Data manager later.
Thanks
James Lim.

Issue using one 2 Fact tables with one dimension Table.

Hi,
I have 1 Dimension table X and 2 Fact tables A and B
X is joined to Both A and B for Loan Amount ( with A) and for colleatral amount (with B) when I am selecting the X.Product_Name, A.Loan_Amt, B.Collateral Amount, it is giving an error message
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 EIP Collateral FACT) does not contain mapping for [EIP Reporting FACT.PD ID]. (HY000)
Any clues???
Is there a Inner or Outer join which needs to be created or set in the RPD to get the desired results???

Ok..
I have one table which is Porfolio Details which has Portfolio name, Product Category , Product Name, Product ID, Product sources code.- This is my Dimension table.
I have another 2 set of fact tables : EIP Reporting FACT and EIP Collateral FACT..
These two tables are joined to Portfolio Details table.
EIP Reprting FACT gives portfolio wise Loan Amount
and EIP Collateral FACT gives Portfolio wise Collateral Amount details for same set of customer..
Now, I am selecting Portfolio Name, Product Category, Product Name,SUM( EIP Reporting FACT.LOAN_AMOUNT), SUM(EIP Collaetral FACT.Collateral_Amt) in a report
Now, on selecting these columns I am getting that error message which is related to mapping.
If I take any column from Portfolio details table and any column from EIP Reporting FACT- It works.
If I take any column from Portfolio details table and any column from EIP Colletral FACT- It works.
But if I take any column from portfolio table and columns from both FACT tables it gives mapping error...
Hope I am able to explain the issue in a better way now..
Edited by: help-required on Mar 11, 2010 6:53 PM
Edited by: help-required on Mar 11, 2010 6:53 PM

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

Reg: Fact table and Dimension table in Data Warehousing -

Hi Experts,
I'm not exactly getting the difference between the criteria which decide how to create a Fact table and Dimension table.
This link http://stackoverflow.com/questions/9362854/database-fact-table-and-dimension-table states :
Fact table contains data that can be aggregate.
Measures are aggregated data expressions (e. Sum of costs, Count of calls, ...)
Dimension contains data that is use to generate groups and filters.
This's fine but how does one decide which columns to consider for Fact table and which columns for Dimension table?
Any help is much appreciated.
Pardon me if this's not the correct place for this question. My first question in the new forum.
Thanks and Regards,
Ranit Biswas

ranitB wrote:
But my main doubt was - what is the criteria to differentiate between columns for Fact tables and Dimension tables? How can one decide upon the design?
Columns of a fact table will often be 'scalar' attributes of the 'fact' data item. A dimension table will often be 'compound' attributes of a 'fact'.
Consider employee information. The EMPLOYEE table can be a fact table. It might have scalar attribute columns such as: DATE_HIRED, STATUS, EMPLOYEE_ID, and so on.
Other related information that can't be specified as a single attribute value would often be stored in a 'dimension' table: ADDRESS, PHONE_NUMBER.
Each address requires several columns to define it: ADDRESS1, ADDRESS2, CITY, STATE, ZIP, COUNTRY. And an employee might have several addresses: WORK_ADDRESS, HOME_ADDRESS. That address info would be stored in a 'dimension' table and only the primary key value of the address record would be stored in the EMPLOYEE 'fact' table.
Same with PHONE_NUMBER. Several columns are required to define a phone number and each employee might have several of them. The dimension tables are used to help 'normalize' the data in the employee 'fact' table.
And that EMPLOYEE table might also be a DIMENSION table for other FACT tables. A DEVELOPER table might have an EMPLOYEE_ID column with a value that points to a 'dimension' row in the EMPLOYEE dimension table.

Dimension Table Attributes giving No Fact Table Exists Error

Similar Messages

Maybe you are looking for