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.

Similar Messages

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.

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

Relating facts to different levels of a dimention

Dear All,
I need to relate a fact to optionally different levels of a hierarchy in a dimension
that's sales plan may be put on the level of a salesman or a distributor or a channel and so on ...
I think that it could be implemented by adding a dummy record in a each level that represent the parent .. but i don't konw how to add this dummy record in owb ...
can you help ..
Regards,
Shaimaa

Hi Shaimaa,
this is actually a very difficult business question. Technically, it's straightforward.
The easy part is to create one fact table per dimension level where you have a plan. So, you would have a SalesPersonPlanFact, a SalesManagerPlanFact, and so on. That will work technically . . .
But it won't really work. :-(
The reason is that the way these plans are created. Typically, the Boss and his guys work out a master plan. Then it gets broken into bits, and each department does their own sub-plan. All the way down, until it gets to individual sales plans. And at every step of the way, the plan gets tweaked, modified, 'special cases' put in.
The result is that they never add up. How you resolve that is a business issue, not a technical one.
Me? What I do is tell people that they won't add up, and then say that it doesn't matter anyway. The reason I give is that the purpose of the plan is to measure actual sales performance against plan, and that we can do. Sales take place at the most atomic level for which there is a plan, and these we can match and consolidate plan against actuals. The consolidated results are then MVed and thus present a high-performance single picture of 'the truth'.
Realistically, you're building a second-level snapshot (could be aggregated, could be periodic, could be both), and that's your reporting structure.
I suspect you may need to go and have a re-think about your value chain, and do much communication with your sponsors so that they understand what's achievable and of real worth to the business. After all, your business as a data warehouse architect is to ensure you're publishing the right data.
Cheers,
Donna

Essbase cubes with different levels of detail - OBIEE 10.1.3.4.1 on LINUX

Hi all,
I have BSO and ASO cubes which contain broadly the same information, but with the ASO cube at much higher detail. For simplicity sake, they only have 1 dimension, and 1 fact. The dimension a date and is structured like:
Gen2 = year
Gen3 = year & quarter
Gen4 = year & month
Gen5 = year, month & day
Only the ASO cube has Gen5. the BSO cube only has the information to Gen4 level.
I've imported them both into the RPD and dragged the ASO cube across into the BMM. and then taken the fact column from the BSO cube and dropped it onto the BMM, selected its new source ( the BSO cube ) and set the
Content tab and set the logical level as Gen4.
I then dragged the key items from the BSO date hierachy onto the date dimension in the BMM.
I purposely had a slightly different date hierachy and data content in the 2 cubes so I could tell where it was getting the data from.
If I select the year only...it gets the value from the BSO, and if I drill down to quarter and month it also gets the dates from the BSO cube.
If I select the data fact, it will switch to the ASO cube and retrieve the value from there.
Same applies if I select just the year - data comes in from the ASO cube.
So my question is this, how do I get it to select the data facts from the less detailed cube when the details is not required and only switch to the ASO cube when the extra detail is needed?
Thanks in advance for any assistance

Anyone have any thoughts on this?
Data fact with 2 sources, where source 1 & 2 have differing levels of detail, it always seems to take the data from the more detailed source

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

Joining Facts with Different Grains

Hello
We have a requirement where we have two facts with different grains
DEPT_FACT - Contains (Dept_Id, Dept_Name, Revenue)
EMP_FACT - Contains (Emp_Id, Dept_Name, Is_Current_Employee)
Here is some sample data
DEPT_FACT
========
1 Sales_Dept 100,000
2 Manufacturing_Dept 200,000
EMP_FACT
========
100 Sales_Dept Y
200 Sales_Dept Y
300 Sales_Dept N
400 Manufacturing_Dept N
500 Manufacturing_Dept Y
600 Manufacturing_Dept N
Our requirement is to create an OBIEE report that shows the *"Revenue/ Number of current employees in department BY Department"*
The above example must show
Sales_Dept => $50,000 (100,000 / 2 current employees)
Sales_Dept => $200,000 (200,000 / 1 current employee)
Any suggestions on how this can be done ?

For me,
DEPT_FACT is not a fact. It's a dimension table because you have a one-to-many relationship and you have a measure in the dimension table (it's an aggregated measure).
And EMP_FACT is also not a fact because you don't have any measure on it.
But if we say that EMP_FACT is a fact. DEPT_FACT is an aggregated table from EMP_FACT.
I will :
* create a logical dimension for the employee with three levels (all, departement and detail)
* create a logical fact table with :
- one logical column for the revenue in the level all departement
- one logical column for the employee
and two physical source :
* DEPT_FACT with the departement level
* EMP_FACT with the level to detail
Success
Nico

Substract as an aggregation rule for different level in a DIM ?!

Hi there..
I'm building a BI model based on financial transactions (incomes, expenses, etc..)
and my main problem is how to substract a measure, where the aggregation rule is set to SUM, for different levels in the "Account" dimension?
Example:
I have the "Account" dimension with the following hierarchy:
Account_ID / Account_name / Account_type / Account_total
And, lets say, 2 rows in it:
1.row in the "Account" dimension:
account_ID : 100
account_name : "Marketing expense"
account_type : "Variable expenses"
account_total : "Total profit" (total income - total Expenses)
2. row in the "Account" dimension:
account_ID : 200
account_name : "Financial incomes"
account_type : "Total incomes"
account_total : "Total profit" (total income - total Expenses)
"Total profit"
"Tot. incomes" "Tot. Expenses"
"Finan. incomes" "Market. expenses"
The fact table has just one measure: "Amount" and, of course, some foreign keys:
Account_ID -> "Account" dim
Organization_ID -> "Organization" dim
Date -> "Date" dim
Amount
The measure "Amount" in the fact table is positive both for expenses and incomes.
Now, what I'm trying to do is to sum up that measure on my top level in the "Account" dim.
At that level my report in Answers should substract "Total expenses" from "Total incomes"!
How can I do that?
thanks..
Ivan

Sorry to pop the obvious question, but can't you model that nicely and put it into distinct columns?
If not, you can create derived measures on you fact using "case when" statements. One for the incomes with amount > 0 (or >=0 ...depends on where you want to have the 0's) and one for the expenses with amount < 0.
HTH,
Chris

WHAT IS THE CONDION TO BUILT DIFFERENT LEVELS IN ONE HIRERCHY

WHAT IS THE CONDION TO BUILT DIFFERENT LEVELS IN ONE HIRERCHY..
Can any one Help me Plese,
Urgent

hi Ashok,
Go through the link this may answer all your hierarchy level questions
http://gerardnico.com/wiki/dat/obiee/hierarchy
thanks,
Saichand.v

Different elements of different levels of hierarchy

Hi experts,
I have a question about hierarchies obiee 11g.
I need to do a table that contains (plain text, without '+' to drill-down) different elements of different levels of hierarchy
I have a hierarchy Account like this:
Level1
-----Level2
-------Element1Level2
-------Element2Level2
------------Level3
--------------Element1Level3
-------Element3Level2
My assignment is to do a table like this
Level1---------------
Element2Level2--
Element1Level3--
Element3Level2--
So I don't want to drill-down on Element2Level2 to see Elements of Level3...
How can I achieve this??
Thanks!

If I a not wrong, you basically want to flatten out a hierarchy. You should be able to do it using the Parent-child hierarchy concept newly introduced in OBIEE 11g where the RPD generates the DDL and DML for you, but you might have to build out an intermediate table to source the final flattened hierarchy table. Refer to this link which has a great example. ( http://prasadmadhasi.com/2011/11/15/hierarchies-parent-child-hierarchy-in-obiee-11g/ )
Thanks,
-Amith.

About different levels of detail in BSC

Hi, could someone tell me what should I do if I have a measure in my BSC in SEM-BW 3.5 (this measure is "Total Expenses" of the company) but the user wants to display it by Department (a characteristic of the info cube).
Can I do that in my BSC in a natural way?
Thanks in advance.

Anyone have any thoughts on this?
Data fact with 2 sources, where source 1 & 2 have differing levels of detail, it always seems to take the data from the more detailed source

Display different level for same hierarchy value in BO 4.0

Hi Expert,
I have one question for Webi for BO 4.0
We have one hierarchy in BW side and we hope to display differet level in same report for different column
For example, column A is for level 6. column B is for level 7.
Do you know how to releaze this in Webi side?
In the 3.X version, we have different dimension for different level.
But now in BO 4, it has been combined into one\
Thanks and best regards
Alex yang

Hi,
You can still do this in BI 4.0, if you use the old 'legacy' MDX OLAP.unv from Universe Designer tool .
Yes, with the BICS connection, you are getting a native hierarchy, as it would be displayed in an OLAP environment.
Cheers,
H

Displaying different levels of the same hierarchy in the different columns

I have a parent child hierarchy and wish to display different levels of the hierarchy in different columns of the resultset eg
level 1 level 2
Europe UK
Europe France
N America US
N America Canada
However writing MDX like the below
select
{} on 0,
([Geo].[level 1],[Geo].Level 2] on 1
from cube
results in the error "The [Geo] hierarchy is used more than once in the crossjoin
How can I get around this??

Hi,
You can make use of CrossJoin function in MDX, I give a sample MDX based on the AdventureWorks database:
select {[Measures].[Reseller Sales Amount]} on 0,
crossjoin({[Sales Territory].[Sales Territory Group].[Sales Territory Group].members},{[Sales Territory].[Sales Territory Country].[Sales Territory Country].members}) on 1
from [Adventure Works]
After execut the MDX you will get the result like this:
Reseller Sales Amount
Europe
France
$4,607,537.94
Europe
Germany
$1,983,988.04
Europe
United Kingdom
$4,279,008.83
NA
NA
(null)
North America
Canada
$14,377,925.60
North America
United States
$53,607,801.21
Pacific
Australia
$1,594,335.38
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Nesting of AGO or TODATE functions with differing level arguments is not supported

I have a column in BMM which calculates the Year-To-Date Sales. This function uses the ToDate function to caculate the YTD.
I need to develop another formula column which shows the last-year's YTD.
I develop this formula in BMM by AGO on the YTD column which already uses a ToDate function.
In BI Answers when selecting this column, results in the below message:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 22044] Nesting of AGO or TODATE functions with differing level arguments is not supported. (HY000)

To reply to my own question. It appears I got it working, that is, the error message problem is solved, but I still have questions on how to use these functions.
To get it to work, I added the primary key D_TIJD.TIJDKEY at the level of the lowest grain in my dimension (level tab).
What I still wonder is how to make it select the right values. I have the following hierarchy: bookyear - bookperiod - week. A bookperiod contains 4 or 5 weeks (4,4,5 in a quarter), so 12 periods in one year. I defined a measure at period level and another at that level with the ago function, that should return the figures for that same period of the year before. My first question is, whether to go back 12 periods or 52 weeks (which is the lowest grain in my dimension)?
The second question is how to use a combination of TODATE and AGO so that if I calculate the current period (of which only 2 weeks are passed), I also only want to include the same two weeks for that period one year ago in order to make a correct comparison. How do I do that???

Controlling the main time line of a movie via a button within a movie on a different level.

Hi there!
I have two movie is two different levels,
Level 5 is my base movie and I am loading another movie on
top of this into level 10.
Once the user clicks onto a button within the movie on level
10, I would like the animation in level 5 to stop (the animation
runs on the main root timeline of level 5).
Once the user clicks on a different button within the movie
on level 10, I would like the animation on the main timeline of the
movie in level 5 to start again from the point where it previously
left off.
Is this possible?
It would be great if someone could help me out with this.
Thanks, midi_ie

midi_ie wrote:
> Hi there!
> I have two movie is two different levels,
> Level 5 is my base movie and I am loading another movie
on top of this into
> level 10.
> Once the user clicks onto a button within the movie on
level 10, I would like
> the animation in level 5 to stop (the animation runs on
the main root timeline
> of level 5).
>
> Once the user clicks on a different button within the
movie on level 10, I
> would like the animation on the main timeline of the
movie in level 5 to start
> again from the point where it previously left off.
> Is this possible?
_level5.gotoAndPlay("someLabelframe");
Use your regular action to target timeline or movie clips,
just define the level number at the beginning of the path.
Pretty much it :)
Best Regards
Urami
!!!!!!! Merry Christmas !!!!!!!
Happy New Year
<urami>
If you want to mail me - DO NOT LAUGH AT MY ADDRESS
</urami>

OBIEE Facts at different levels.

Similar Messages

Maybe you are looking for