Facts at different Logical Dimension Level and Default Interaction (Drill)

I have one Geography Logical Dimension that consists of 3 physical tables snowflaked. The 3 tables are City, State and Country. I have created 3 Level Based Hierarchies.
I have 2 Facts. Fact_State is at the State grain only (Set the appropriate Content Level). Fact_City is at the City grain (Set the appropriate Content Level).
When I pull a query with Country and a metric from Fact_State, the default interaction allows me to drill down. I drill into the State values. I would assume that the Drill interaction would stop here since this metric (Fact_State) is only at this level.
What actually occurs is it allows for a drill into City and when you look at the Physical SQL it is trying to hit the other Fact Table (Fact_City) and pulls back no metrics. I then return no data.
I would ask does anyone know if this is the expected behaviour? Is there anyway to stop the drill at the State Level when metrics are only pulled from the State Fact?
Please let me know if more information is needed.

You need to have a metric sourcing from both Fact_State and Fact_City, provided both facts are as Logical sources for the logical fact table.
Make sure Fact_State got proper level and Fact_City got detail level.
When you pull Country or State with metric query should hit Fact_State, when you drill down below the state query should be from Fact_City with proper data.
Edited by: Srini VEERAVALLI on Mar 28, 2013 2:43 PM
I can look into your new post only If you update this or older posts. Still you may get responses from others ;)
Edited by: Srini VEERAVALLI on May 22, 2013 2:00 PM

Similar Messages

Join fact table with higher dimension level

how do i join fact tables with higher dimension levels with discoverer?
fact with detail at level C
measure X
dimension with
D->C->B->A
E->C
level
A B C
1------1------1
2------2------1
3------2------1
join between fact X and dimension level C
X=3*C because of sum(X) in discoverer and 3xC in dimension
is there a way to get correct values for X without creating a dimension like
D->C
E->

another way of asking this is whether you can create a summary table in Discoverer at a higher level than a dimension's fundamental grain. In other words - the summary examples in the documentation all describe leaving out one or more of your dimensions... they are either left in or completely taken out. But, some of the most effective summarization occurs when you summarize daily data to a monthly level. Assuming that I have a sales table (at a daily level, and a key value sales_date), and a table date_dim (primary key sales_date), I would like to create a summary sales_month_summary where the sales are grouped on month_year (which is a field in the sales_date table).
How is this done? I suspect that we can't use the date_dim table with the summary (due to the problems noted by the poster above). Do we have to create another table "month_dim"? Do we have to fold all of the desired date attributes (month, quarter, year) into the summary? Obviously we'd like to re-use all of the pertinent already existing date items (quarter, month, year, etc.), not recreate them over again, which would result in essentially two sets of items in the EUL. [One used for this month summary, and another used for the detail.]
I searched the forum - someone asked this same question back in 2000 - there was no answer provided.
The only other thought I have is to "snowflake" the date_dim into two tables and two folders, one at a date level, another at the month level. Then the detail tables can connect to date_dim (which is linked to month_dim), while the summary data can connect directly to month_dim.

Logical column levels and aggregation

Hi all,
In order to have reliable results, I had to specify a dimension level in a logical column properties.
As a consequence, the generated query includes this level in the query (that's great), but no aggregation is performed afterwards. Therefore, when I display this measure alone in a flat table or a ticker, I have a set of detailed value instead of an aggregated value. The only place where I can see my aggregated value is in a pivot table.
In answers, I tried to :
- replace the default aggregation by an explicit SUM, or
- add a SUM() in the measure formula
but neither solved the issue.
Does anyone know how to solve it?
Thanks in advance.
Ced.

Hi,
What is the source for AGO measures PriorDollars and PriorUnits?
AGO(CurrentUnits, '?',?)
AGO(CurrentDollars, '?',?)
Have you set up hierarchy correctly (because you said that the granularity in your fact table is at week grain) and it should be like this:
Fiscal Year > Fiscal Quarter > Fiscal Month > Fiscal Week
It depends on how did you define your TIME dimension.
Try maybe like this:
PriorYEARDollars = AGO(CurrentUnits, 'YEAR',1)
and the same for
PriorYEARUnits =AGO(CurrentDollars, 'YEAR',1)
Now, if you put in the report
YEAR
CurrentUnits
CurrentDollars
PriorYEARUnits
PriorYEARDollars
you'll get only three rows (for 3 years) with PRIOR YEAR measures.
Try it.
A good reference for understanding AGO:
http://obiee101.blogspot.com/2008/11/obiee-ago-and-todate-series.html
Also you need to set chronological key correctly for TIME dimension.
Regards
Goran
http://108obiee.blogspot.com

Dimensions, Levels and Keys

Folks,
I am trying to deploy and load a dimension table composed of the following columns:
Company Id
Company_Name
Corporation_Id
Corporation_Name
Cost_Center_Id
Cost_Center_Name
I have created three levels: Company, Corporation and Cost Center. Each Level is composed of the corresponding id and name.
I have also created a single hierarchy, composed of the three levels: Company, Corporation and Cost Center.
When I deploy the script, it creates a Unique Key constraint composed of the key at the lowest level - Cost_Center_Id.
However, it is the combination of Company_Id, Corporation_Id and Cost_Center_Id that is required to uniquley identify a row in the dimension table.
Any clue as to what I am doing wrong?
Thanks. Bruce

Hi,
I believe hierarchies in OWB are One to Many. In your example, a company can have many corporations and a corporation can have many cost centers, but a cost center can only belong to one corporation and a corporation can only belong to one company. If this was the case, then Cost_Centre_id would be the unique key. You're saying that the combination of Company_Id, Corporation_Id and Cost_Center_Id is the unique key, and this leads me to believe that you don't actually have a hierarchy (the way OWB sees it) One way to handle this is to put all the columns in a single level, and add a unique identifier for each possible combination of the three.
If you look at "best practices" I think you'll find that you should always use a single synthetic numeric value as your primary key in a dimension table. This ensures the most efficient join to the fact table. (If you have a three column key, you need all three columns in the fact table, wasting space and creating a more complex join) Also, you should try to avoid using any keys from an OLTP system as a key in your dimension.
Hope this helps,
Roald

BIEE default font size and default Interaction setting

Hi ,
my customer want us set default Interaction to NONE in column properties,
the system default in set to Drill,
any way to realize it by global?
another is they want to set default font size to 12px in dashboard,
like dimenstion values,
are there any way to setting it ??? we don't want set it one by one.
thank you!

Open Mail application
On the top menu choose Mail and then preferences
Choose *Fonts and Colors*
Opposite *Message Font* click on the Select button
A fonts menu will pop up and from there (at the top) choose the Text Color you want.
Close the open menus and you will then have the default font color for your message font.
Axel F.

BIEE default font and default interaction setting

Hi,
we have two requirements,
1. customer want to set font size to 12px in dashboard,like dimention values,
it need be set by global,not set one by one.
2. the column default interaction is Drill, customer want to set it NONE,
and we don't want to set it one by one,
any where to set it in globle? modify any configuraion file?
thank you!

Hi,
Can you please refer below thread.
https://forums.oracle.com/message/10496566
Thanks,
Satya

Use different Layouts for Summary and Details in Drill down report

Hi All,
I have a 2 level drill down report in ALV.
The summary report has certain fields and the Detail report has different fields. Now my problem is that when i use a default layout (with all fields of summary report) for the summary report, and drill down to the detail report i'm missing the fields on detail that are not in Summary. And if i save the default layout as default (with all fields of Detail) and go back to sumary, I'm missing the some other fields on summary (which are not on detail report).
Is there a way to make different default layouts for each of those summary and detail reports:
Also as the layouts are choosen by the user, i cannot hardcode any particular layout;
So if the user chooses a layout for detail; it has to stay the same layout for the detail report if he goes to summary and then back to detail; unless the user changes the layout again.
I'm using two different Layout types for each report. but i still cannot get the desired effect.
Data:
 gt_layout_s type slis_layout_alv,
 gt_layout_d type slis_layout_alv,
call function 'REUSE_ALV_GRID_DISPLAY'
 exporting
 i_callback_program = g_repid
 is_layout = gt_layout_s
 i_callback_top_of_page = g_top_of_page
 i_callback_user_command = g_user_command
 i_callback_pf_status_set = g_status
 i_save = g_save
 is_variant = gs_variant
 it_fieldcat = gt_fieldcat[]
 it_events = gt_events[]
 importing
 es_exit_caused_by_user = gs_exit_caused_by_user
 tables
 t_outtab = it_summary.
call function 'REUSE_ALV_GRID_DISPLAY'
 exporting
 i_callback_program = g_repid
 is_layout = gt_layout_d
 i_callback_top_of_page = g_top_of_page
 i_callback_user_command = g_user_command
 i_callback_pf_status_set = g_status
 i_save = g_save
 is_variant = gs_variant
 it_fieldcat = gt_fieldcat[]
 it_events = gt_events[]
 importing
 es_exit_caused_by_user = gs_exit_caused_by_user
 tables
 t_outtab = it_detail_disp.

Here is how you differentiate between the layout of two different grids. There is the parameter, IS_VARIANT in the function. You usually leave it empty or pass only the report name and username. What you need to do is to pass unique string for each grids to the HANDLE field of the parameter IS_VARIANT. You can probably hard code it as HEADER and DETAILS in your case. Once that is done, system identified that these two different layout for different grids.
Regards,
Ravi
Note : Please mark all the helpful answers

Comparing facts of different dimension levels - drilldown problem.

With our customer, we do a lot of comparisons of sales budgets vs. actual sales. The sales budgets are given per month, like this:
Sales budgets: Jan 09: 40,000 EUR, Feb 09: 45,000 EUR, Mar 09: 20,000 EUR... and so on.
There is a time dimension (year -> quarter -> month -> day). Since BI does not seem to allow binding facts to other dimension levels than the lowest one (day in my example), I used a trick and modelled these sales budgets as a fact table: (expected sales, last_day_of_month)
So I have this:
Sales budgets: 01/31/09: 40,000 EUR, 02/28/09: 45,000 EUR... and so on.
This way, I can connect both actual sales and sales budgets to the same time dimension. With this, I can create an answers report that compares the two facts easily.
The problem is now that the customer wants to drill down. This is no problem with year->quarter->month. But then, BI naturally allows to drill further to day, and in this case, BI compares the sales budget of 01/31/09 with the sales on 01/31/09, producing wrong values.
I either need a solution to prevent BI from drilling down from the month level in this special answer report, or maybe I am making an error with my modelling. Are there any ideas on how to do this better?

Hi,
I'd model the repository differently, by modeling the actual sales fact on the lowest day level, and sales budget fact on monthly level. That's how I've understood the data really is defined, right? (Lowest level physical time table you already have but for sales budget you need to create also a physical time table which is on the month level. First define the correct physical joins. Then define the logical table sources in the BM layer accordingly.) In order to be able show the sales budget together with lowest level you can create the sales budget measure as a level based measure (fix the measure to the level month in the column properties-->Level in the Administration tool).
If you just want to prevent users from drilling-down on a specific dashboard report you can go to properties of the column(s) in that report and set the interaction type for both title and values to "No interaction" in the second tab of the properties menu in the front-end.
Hope this helps!
Cheers,
Ilmari

No fact table at the requested level error.

I have one dimension
Account
Two fact tables
Threshold and Transaction
These tables are joined to the Account Dim using Account Number.
Now when I create an analysis using Account Numbers from all three tables, it says no fact table at the requested level. If I include any other fact from both the fact tables, it populates null. It works right when I create an analysis from one dimension and either of the fact tables.
Why do we get this error and how else should it be modeled.
Edited by: 979130 on Dec 29, 2012 12:52 AM

I'm not sure about your data.. I give couple of options try them out any of one should work.
Assuming both facts are at same granular: You need to create Logical Fact table in BMM add first fact as source then, open properties wizard and add other fact table.
Assuming both facts are at Different or Same granular: You need to create Logical Fact table in BMM add first fact and then add 2nd fact as 2nd logical table source and set the content tab for both facts
Using any of the option you'll be going for metrics and use them in report.
In general: You need to let BI server let know how data is spread across tables so that BI Server can respond as you expected.
Hope this helps, Appreciate if you mark as correct/helpful
Edited by: Srini VEERAVALLI on Dec 29, 2012 12:58 PM

Implementing Logical FACT & Logical dimension from 2 different data sources

Hi Gurus,
Here is my situation. We have 2 Different Data sources. One is SRMW and the other one is a different source. What we are trying to implement here is we wanted to create logical dimensions and logical facts as well in the BMM layer. For ex: w_day_d from SRMW and other time dimension from another source makes a logical table. And similarly a fact from SRMW and and another similar fact (Same data types though) will make a logical fact in the BMM.
I have done the POC of it, but the only problem is that i was able to fetch the data from only one data source not the other source.
Any suggestions ??
Thanks in Advance.

What I already mentioned is that you have to create multiple logical table sources and set the fragmentation content on each logical table source.
When you have two physical tables for the product dimension, for example DIM_PRODUCT_A and DIM_PRODUCT_B, you must add them to your logical table Products as two separate logical table sources and map all columns to the corresponding logical table columns on the Column Mapping tab.
Hereafter you should go to the Content tab of each logical table source and describe what content is in the logical table source.
For example for the logical table source of DIM_PRODUCT_A:
"BM"."Product"."Product Name" <= 'Product 2'
and for the logical table source of DIM_PRODUCT_B.
"BM"."Product"."Product Name" >= 'Product 3'
Then you must also check "This source should be combined with other sources at this level"
When you run a query in Answers only on the product table, two queries will be generated to get values from both tables.
Regards,
Stijn

One Dimension with Facts at different levels

I currently have a single dimension with 5 levels. I have two fact tables that both connect to the dimension table but at different levels.
For example. If we have a Dimension Country -> Region -> City and then two fact tables. One that has facts at the Region level and one that has facts at the City level.
Is there a way to be able to have an answer that contains facts from both fact tables. So if there was a fact from City and the Region level? Everything I seem to try does not work. Would I have to create an additional aggregate table that aggregates the City level data up to the Region? Or is there a way to show the data at the lowest level and show either nulls or duplicate values for the additional records.
Any help is greatly appreciated

This has helped a little. I am now getting values from both levels. However, because i am summing the two values. The value from the upper level is now summing duplicate values. For example.
Value 1 on its own
Level1 Level 2 Level 3 Value 1
1234 10 10 13.05
1234 20 10 70.00
1234 20 20 70.00
1234 30 10 105.00
1234 30 20 105.00
Value 2 on its own
Level1 Level 2 Level 3 Value 2
1234 10 10 0.50
1234 20 10 2.00
1234 20 20 2.00
1234 30 10 3.00
1234 30 20 3.00
What I am getting
Level1 Level 2 Level 3 Value 1 Value 2
1234 10 10 13.05 0.50
1234 20 10 140.00 2.00
1234 20 20 140.00 2.00
1234 30 10 210.00 3.00
1234 30 20 210.00 3.00
Desired Outcome
Level1 Level 2 Level 3 Value 1 Value 2
1234 10 10 13.05 0.50
1234 20 10 70.00 2.00
1234 20 20 70.00 2.00
1234 30 10 105.00 3.00
1234 30 20 105.00 3.00
Now, the problem with this is that Value 1 is a fact at Level 2 and Value 2 is a fact at Level 3. I have one dimension table and two fact tables. The join between the fact table for Value two and the dimension table is the same as the join between the dimension table and Value 1 only it is missing the last level of detail.
I have then set the logical table source content tabs for each fact table to the corresponding levels.
I thought this would be enough but i still don't get the desired result. I am not sure if this is possible with one dimension table.
Any ideas would be greatly appreciated.
Edited by: user10800227 on Jan 11, 2010 12:43 PM

2 facts with different dimensions in 1 logical table

hello,
im trying to accomplish the set up as described per blog:
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
i.e. i have 2 facts, F1: D1 ; F2: D1,D2,D3;
i followed the instructions and all seem to be working fine;
however: when i put the total on the report in Answers: D1,D2, F1, F2 then the measures from F1 that are repeated every row for D2 are being added , like regular sum on the column; this is not correct;
the only correct result i can get if manually i change the Aggregation Rule to :Server Complex Aggregate on all F1 measures;
id like to ask if this is a bug of this OBI version? 10.1.3.2
i wish not to instruct my users to change the aggregation rule; id like to have the set up via rpd such, that they dont have to manipulate the aggregation rules;
did anyone got the above working with correct totals without changing the aggregation rule?
if so, id appreciate any tips on how to achieve that
thanks
rgds

Basically, you need to :
* create your physical schema with the relationship
* drag and drop your Forecast Facts measure in the same logical table than your sales fact
* define your Forecast measure as level based measure (logical column/levels/properties) with the grain of the forecast table
Documentation
http://download.oracle.com/docs/cd/E12103_01/books/admintool/admintool_BusModSetup12.html
And you have an example in OBE series with quota in excel sheet :
http://www.oracle.com/technology/obe/obe_bi/bi_ee_1013/bi_admin/biadmin.html#t8
Success
Nico

OBIEE report from multiple facts at different levels

Currently we need to develop a report with columns from 3 different facts surrounded with conformed and non conformed dimensions at different levels.
After setting the hierarchial levels and putting the facts into single logical table with different sources OBIEE is generating 2 different queries and does a full outer join.
I would like to know how we can do a left outer join instead of full outer join between the 2 queries based on a common column?
Thanks in advance.

Hi Vinod,
The scenario provided in the link above doesnt match to my issue.
We need to develop a report from multiple fact tables at different levels with conformed & non conformed dimension columns.
I have 7 dimensions D1, D2, D3, D4, D5, D6 and D7 & two fact F1 and F2 tables.
F1 is tied to dimensions D1,D2,D3,D4,d5
F2 is tied to dimensions D3,D4,D5, D6 and D7.
In my report I have columns from D1, D2, D3, D4, D5, D6, D7, F1 and F2.
So OBIEE generates 2 queries with columns from D1,D2,D3,D4,d5 & F1 measure and another query with D3,D4,D5, D6, D7 and F2 measure.
and then does a cross fact join out of box between 2 queries.
But I need to do a left outer join between the 2 queries on a common column instead of cross fact join. I would like to know how we can achive this.
Thanks.

[39008] Logical dimension table has a source that does not join to any fact

Dear reader,
After deleting a fact table from my physical layer and deleting it from my business model I'm getting an error: [39008] Logical dimension table TABLE X has a source TABLE X that does not join to any fact source. I do have an other fact table in the same physical model and in the same business model wich is joined to TABLE X both in the physical and business model.
I cannot figure out why I'm getting this error, even after deleting all joins and rebuilding the joins I'm getting this error. When I look into the "Joins Manager" these joins both in physical as well as logical model do exist, but with consistency check it warns me about [39008] blabla. When I ignore the warning and go to answers and try to show TABLE X (not fact, but dim) it gives me the following error.
Odbc driver returned an error (SQLExecDirectW).
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 14026] Unable to navigate requested expression: TABLE X.column X Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT TABLE X.column X saw_0 FROM subject area ORDER BY saw_0
There is one *"special"* thing about this join. It is a complex join in the physical layer, because I need to do a between on dates and a smaller or equal than current date like this example dim.date between fact.date_begin and fact.date_end and dim.date <= current_date. In the business model I've got another complex join
Any help is kindly appreciated!

Hi,
Have you specified the Content level of the Fact table and mapped it with the dimension in question? Ideally this should be done by default since one of the main features of the Oracle BI is its ability to determine which source to use and specifying content level is one of the main ways to achieve this.
Another quick thing that you might try is creating a dimension (hierarchy) in case it is not already present. I had a similar issue few days back and the warning was miraculously gone by doing this.
Regards

OBIEE Facts at different levels.

Hi,
I am bringing columns from three tables: Two facts and one Dimension table to create a OBIEE Report.
The fact tables Workforce Event Fact and Employee Daily Snap Fact are at different levels, but both of them have proper joins with Dimension Employee Dim.
When i am pulling columns from D1 and any one of these two facts, i am not facing any problem in seeing results. But when i bring columns from all of these three tables, i am getting this error,
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 Workforce Event Fact) does not contain mapping for [Employee Daily Snap Fact.Exempt Indicator]. (HY000)
Is there anything i have to do in Business Model layer to avoid this error. Many people suggesting to assign an aggregation level for these two facts. But i am not having any Dimensional Hierarchy defined.
Thanks
Swami

Hi swami,
Many people suggesting to assign an aggregation level for these two factsThis is a workaround i think where you need to create aggregate tables(not levels) and then use them for your purpose.(OR) you dint define the logical source table properly either correct it.
Another work around i could suggest is,take the 2 fact tables columns needed into one alias table and make it as fact and join this fact table to dimension table and you can get all columns.
Hope it helps you.
Best Wishes,
Kranthi.

Facts at different Logical Dimension Level and Default Interaction (Drill)

Similar Messages

Maybe you are looking for