LTS of fact table in obiee 10g

Hi
In LTS for the fact table, I want to set the level to the lowest level of the dimension
How to achieve this.
Please suggest.

Hi,
To set the LTS level first you need to have the dimension hierarchy for that table, after that double click the LTS >> click on Content Tab >> there in level drop down you can select which level you want assign. so now select the lowest level from the drop down and save.
Mark if Helpful/correct.
Thanks

Similar Messages

Unable to join 3 fact tables in obiee data model.

Hi,
I am unable to join the 3 fact tables in obiee rpd. If I join with 2 fact tables I got the data in repors, Once I add the one more fact table and join with related dimensions, I am getting nodata error. I am following all joins keys as per datamodel, I am able to see the data in database. anyone pls give me the solution. Thanks in advance.
Edited by: 1007582 on May 23, 2013 2:17 AM

Can you please give some more detail as in what you have model in RPD;
For example, if There are 3 Fact table F1, F2, F3 and two Dimesion Confirmed_D1, Non_Conf_D2. Confirmed_D1 is joined to all three fact tables and Non_Conf_D2 is joined to F2.
Now to implement this model we have to set the logical content level in BMM layer for Non_Conf_D2 in F1 & F2 to Total*. After this only we can report on Confirmed_D1, Non_Conf_D2, F1, F2, F3 whithout any error.
Sometime join with multiple table can also result in No Data, since the join conditions filters out the result data.
Please mark helpful or correct.
Regards,
Kashinath

Why not to Join Fatc to fact tables in OBIEE... What is the Logical Reason

Why not to Join Fatc to fact tables in OBIEE... What is the Logical Reason
Thanks in advance
V

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

How to join Dimensions and Fact Tables in OBIEE

Hi All,
I need to create report which need to get the information from two fact tables and 7 dimensions. The granularity is not same in both the fact tables. One fact table is having common keys between all the dimension tables and second fact table have only two dimension keys but with different names. My requirement is to create the report by taking the measures from both the fact tables.
I have created joins between the second fact table and two dimension tables in physical and BMM layer and also set the highest level for all other dimension tables in the LTS of second fact table. when am creating report by taking the measures from both the fact tables, data is not getting for the measure which taken from the second fact table. Please advice me how to get the data for the measure which taken from the second fact table.
Thanks in Advancec !!

You have to use the level-base measure capabilities.
http://gerardnico.com/wiki/dat/obiee/bi_server/design/fact_table/level_based_measure_calculations
For all measures of the second fact table with the lowest grain (with two dimension keys), set for all dimension where you don't have any key the logical level to the "All" or "Total".
And UNSET the highest level of the LTS for the second fact table.
Success
Nico

Self join with fact table in Obie 10G

I am a newbie to obiee.I have a development requirement as follows-
I need to find supervisors designation with the existing star RPD design. explanation is below
                                                    DIM_Designation(Desig_Wid)
                                                  |(Row_wid)
                                                  |
DIM_EMPLOYEE--------WORKER_FACT------------DIM_Supervisor
(Row_Wid)-----------------(Employee_Wid)
                                  (Supervisor_Wid)------------(Row_Wid)
3 dimension is joined to fact to get employee, his supervisor and designation of employee. now i want to get the supervisor's designation? how is it possible? already employee and supervisor dimension is same W_employee_d table joined with fact as alias DIM_EMPLOYEE and DIM_SUPERVISOR. how to do self join with fact to get supervisor's designation. i do not have any supervisor_desig_wid in fact table. any help is deeply appreciated.

Yes,Duplicate the fact table create a primary key on the newly fact table alias dimension table.So you can ur data modelling as usual.

How map to my particular table to the fact table in obiee 11g...

Hi friends,
I did this simple report in obiee 11g(i.e)
"NATIONALITY COUNT IN DEPARTMENT WISE"
For that i used the following tables:
per_all_assignments_f----->fact table
hr_all_organization_units----->dim table(containing departments)
per_all_people_f---------------->dim table(containing nationality)
I made all the mappings in the physical diagram, as also viewed my report in BI answers
It shows the following results like
NATIONALITY---------------------------------------------------------------------COUNT(NATIONALITY)
AUS------------------------------------------------------------------------------------------------24
AFR------------------------------------------------------------------------------------------------25
PHQ_VB-------------------------------------------------------------------------------------------40
SH_VT----------------------------------------------------------------------------------------------4
The problem is for me it is showing the above results, but the nationality column is of various codes of the country.
Since i doesnt want the code of the nationalitian to display in the results..i need the meaning of each and every nationality..
like,
AUS------------------------Australian
AFR-------------------------African
PHQ_VB----------------------Germanian(assigned)
Since i know that the meaning for the nationalitian is available in "FND_LOOKUP_VALUES"...okay..
I can import "FND_LOOKUP_VALUES" table to the physical layer...but how i can able to give the mapping to the fact table in my physical diagram...
In my report the fact table is "per_all_assignments_f"
As my fact table doesnt contains any matching column corresponding to the dimension table "FND_LOOKUP_VALUES".....
Then how i can give mappings to the fact column???? for viewing the full meaning of the nationalitian in my report.....Help me friends...
Regards,
Harry...

Hi bifact,
I followed the step that U asked me to go but im stuck with later.....
*) I saved the query that i executed in toad with the columns showing country codes and country meaning to the excel sheet...
This is the query that i executed in toad and copied data s in excel sheet..
select z.lookup_code, z.meaning
from per_all_people_f e, per_all_assignments_f f, hr_all_organization_units h, fnd_lookup_values z where
e.person_id = f.person_id and f.organization_id = h.organization_id and e.business_group_id = f.business_group_id
and f.business_group_id = h.business_group_id and f.location_id = h.location_id
AND z.lookup_type(+) = 'NATIONALITY'AND z.lookup_code(+) = e.nationality and sysdate between
e.effective_start_date and e.effective_end_date and e.nationality is not null
*) After that i created a system DSN for the excel drive..
*) After that when i tried to import metadata of the excel data that is saved, it showed me connection failed...
For importing this excel data
what connection details i need to give:--------------------
as well as user name and also password...
Soon after importing this excel you said that to give key connection only to fnd_lookup_tables(dim) and that excel data..
if so, again im not giving key connection to my fact table..
I think again the same error will occur that no logical mapping is not made to fact so again repository is inconsistent...
Hi bifact sorry to ask you, but can you see the steps that i followed is correct and after that wat more steps i need to proceed..Can you tell me in breif manner...Thanks for your help...
Regards,
Harry...

How to link two fact table in OBIEE

i experts
1. I have one fact table EXCHANGE_FACT(Contains the exchange rate for each curruncy on each day) .
2. I Have anothe fact Table ACCOUNT_FACT(Contains Amount for each currency on each day).
Now i have to link these two table on bace of currency_key and time_key in OBIEE. so i have can i achieve it in OBIEE.
Regards
Frnds

Hi Frnds,
You should create two common dimensions (currency en time) and join each fact table seperately to these dimension. Create a demnsion (hierarchy) for each dimension.
Good Luck,
Daan Bakboord
Scamander Solutions

User Profile Table in OBIEE 10g

Hi,
In obiee 10g do we have any table at database level or system level which contains the details of user profile information?
We have 100+ users and I want the detail of all users (name, mail id etc.).
Please suggest.
Thanks.

Hi,
You can use SA System Subject Area to do this. Here is a sample description:
http://oraclebizint.wordpress.com/2008/04/25/oracle-bi-ee-101332-sa-system-subject-area-autoloading-profiles-and-bursting/
Hope it's helpful

Help on Setting logical Levels in Fact tables and on Dimension tables

Hi all
Can any body provide any blogs or any king of material on what exactly is levelling .
Like after creating the Dimensional hierarchies we need to set the logical levels for the LTS of fact tabels ri8 .So what is the difference between setting logical levels to fact tabels and also Setting levelling on Dimension tables .
Any kind of help is appreciated
Thanks
Xavier.
Edited by: Xavier on Aug 4, 2011 10:50 AM

I have read these blogs ,but what my question is
Setting the logical levels in LTS of Fact tables i understood .
But we can also set the logical levels for dimensions also ri8 .I didn't understand why do we set the logical levels for dimensions .Is there any reason why we go with the levelling at dimensions
Thanks
Xavier
Edited by: Xavier on Aug 4, 2011 2:03 PM
Edited by: Xavier on Aug 4, 2011 2:32 PM

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 10g: Problem on fact table mapping

Hi to everyone,
i have this situation:
1) i have 2 fact tables in phisical model (FHRCTR and HCTOT) this two table is the same in the FK columns.
2) the structure is: FHRCTR[month_fk, transaction_type, measure A], HCTOT[month_fk, measure B]. 'transaction_type' is an attribute of the table not dimension.
3) i have created a logical fact table with this two tables for source.
4) each field of logical table is mapped on the corrispetive field on the both phisical table, except for 'transaction_type' column having as source only FHRCTR table.
5) i've created a report with follow colums: month_fk, transaction_type, measure_A, measure_B
The problem is: if i create the report with the columns in point 5, the measure_B returns null values and the measure_A have a correct value.
Insteed if i create a report without 'transaction_type' column the value of Measure_B and Measure_A are correct.
I remind you that: 'transaction_type' in the logical fact table is mapped only on the FHRCTR table because on HCTOT it doesn't exist.
Can you help me to solve this issue?
Thanks

832596 wrote:
Can you help me to solve this issue?
ThanksI guess when you set some aggregation rule for 'transaction_type' in a repository then all will be ok (for examplу - min). But you'll get results that you don't expect.

Issue with Multiple LTS for a fact table and filters

Hello,
I am facing an issue with obiee 10g.
In my model, I have a huge FACT table F1 (partitioned and indexed). The average response time for the queries, which targeted it, was ~30-60 seconds, which was not really convincing our end user.
So, we decided to create a materialized view, which removes some dimensions that are not used by default, but might be used if the end user adds some filters. I added the Materialized view in the Physical Layer and in the corresponding Logical Table Source.
I then tried to see if it works, but I was a bit surprised by the result. Indeed,
-> If the report does not reference a truncated dimension, it targets the materialized view. -> Perfect
-> If the report does reference a truncated dimension in the columns, it targets the Fact Table. -> Perfect
-> If the report does reference a truncated dimension in the Filters, it targets the materialized view. For this reason, the filter is never resolved and no join on the dimension table is applied, whereas it exists in logical SQL generated. -> Ko.
A suggestion could be to add the filters into the columns, but I am not satisfied by this response because it will never use the materialized view in that case.
An other suggestion could be to use query rewrite, but I 'd like to have the full control on the generation of the queries.
Does someone know if the filters are not evaluated to determine which LTS to use? How can I force this evaluation?
Regards,

Hi,
If I understand your description correctly, then your materialized view skips some dimensions (infrequent ones). However, when you reference these skipped dimensions in filters, the queries are hitting the materialized view and failing as these values do not exist. In this case, you could resolve it as follows
1. Create dimensional hierarchies for all dimensions.
2. In the fact table's logical sources set the content tabs properly. (Yes, I think this is it).
When you skipped some dimensions, the grain of the new fact source (the materialized view in this case) is changed. For example:
Say a fact is available with the keys for Product, Customer, Promotion dimensions. The grain for this is Product * Customer * Promotion
Say another fact is available with the keys for Product, Customer. The grain for this is Product * Customer (In fact, I would say it is Product * Customer * Promotion Total).
So in the second case, the grain of the table is changed. So setting appropriate content levels for these sources would automatically switch the sources.
So, I request you to try these settings and let me know if it works.
Thank you,
Dhar

NQS ERROR:14025 NO FACT TABLE EXISTS -after migrating from 10g to 11g

NQS ERROR:14025 NO FACT TABLE EXISTS AT THE REQUESTED LEVEL OF DETAIL in all the reports after migrating from 10g to 11g ...
then we applied the patch (One-off Patch for Bug: 11850704) for the error <<NQS ERROR:14025 NO FACT TABLE EXISTS AT THE REQUESTED LEVEL OF DETAIL>>
But after applying the above the above patch we are still getting the same error.
but in the above patch instructions file - Post deployment instructions to create the Variable
Post Install Instructions:
- To revert to the 10g navigator behavior for handling conforming dimensions,
you must set the following session variable via an init block in the RPD:
NO_FORCE_TO_DETAIL_BIN=1
The default value for the above variable is 0.
- Restart all servers (Admin Server and all Managed Server(s))
but we didn’t find the process to create the specified variable and Initialization block in the RPD
Can you please suggest us how to go further.
Our questions are:

Hi
Refer the below thread.
obiee 11g non-conforming dimensions and nQSError 14025
Might be help you/
Thanks,
satya

How to prioritise obiee to select logical fact out of 2 logical fact tables

Hi All,
I have a scenario where in I have 2 Logical Fact tables F1 and F2 and 2 Logical Dim tables D1 and D2.
Both Logical Dim tables are joined to F1 and F2 i.e.(D1-F1-D2) and (D1-F2-D2). When a user selects columns from D1 and D2 it always select F1.
I would like OBIEE to select F2 instead of F1. Is this possible?
With Regards
Prads

You need to mention the levels in content tab of LTSs depends on the joins to dimensions.
It automatically picks the right LTS based on the dimensions selected in criteria & levels in the content tab of your LTSs.
Anyways, if you want to make f2 as main LTSs put that in first position under Sources folder.

Bridge Table check box in OBIEE 10G

Hi,
In BMM layer of OBIEE 10G, we see a Bridge Table check box when we double click on each table.
What is the difference it makes if we check that VS don't check that. Is it mandatory to check it?
There are 2 ways to model many-to-many relationships.
1. Perform Fact-->Bridge and Bridge-->Dimension join in physical layer. In BMM layer, bring Fact and Dimension tables. Do an inner join between Bridge-->Dimension and join the Dimension to the Fact.
Question:- In this case do we need to check the Bridge Table check box on the Dimension table?
2. Perform Fact-->Bridge and Bridge-->Dimension join in physical layer. In BMM layer, bring Fact, Bridge and Dimension tables. Fact-->Bridge and Bridge-->Dimension.
Question:- In this case do we need to check the Bridge Table check box on the Bridge table?
Thanks,
Anilesh

Hi,
My question is -->What is the difference it makes if we check that VS don't check that. Is it mandatory to check it?
And we are following the first approach out of the 2 approaches listed below.
There are 2 ways to model many-to-many relationships.
1. Perform Fact-->Bridge and Bridge-->Dimension join in physical layer. In BMM layer, bring Fact and Dimension tables. Do an inner join between Bridge-->Dimension and join the Dimension to the Fact.
Question:- In this case do we need to check the Bridge Table check box on the Dimension table?
2. Perform Fact-->Bridge and Bridge-->Dimension join in physical layer. In BMM layer, bring Fact, Bridge and Dimension tables. Fact-->Bridge and Bridge-->Dimension.
Question:- In this case do we need to check the Bridge Table check box on the Bridge table?
Thanks,
Anilesh

LTS of fact table in obiee 10g

Similar Messages

Maybe you are looking for