Based on dimension aggregation

I have a fact table with 2 sources. One of these sources has only one measure and I am having problems with it.
This measure must use based on dimension aggregation, but it don't work. When I set this option, the measure shows a blank value in Answers, but when I switch to a default aggregation rule (not based on dimension), like sum or max, the value is shown correctly in Answers.
My doubt is: is it necessary any other configuration on dimensions or fact tables in order to use based on dimensions aggregation? I just change the value in the aggregation tab of the measure, is there any other step necessary?
Thanks

I found this text on the help, but I didn't understand, because when I check the "based on dimensions" check box, I can choose aggregation rules for each dimension, not only the time dimension.
Also, I found in the help menu:
"In the Aggregation tab, select the Based on dimensions check box.
The Browse dialog box automatically opens.
In the Browse dialog box, click New, select a dimension over which you want to aggregate, and then click OK.
In the Aggregation tab, from the Formula drop-down list, select a rule."
I did the same steps suggested by the text above, but it didn't work.

Similar Messages

OBI EE 10g: Bridge tables and Based on Dimensions Aggregation

hi experts,
i am working on OBI EE 10 g (10.1.3.4)
The BM&M layer consist of:
1) Logical fact table "Sale_Indicators"
Fields: SALE_ID (PK, FK),
D1_ID (FK),
D2_ID (FK),
Indicator1 (measure, level of granularity: SALE_ID),
Indicator2 (measure, level of granularity: SALE_ID),
Indicator3 (measure, level of granularity: SALE_ID)
2) Logical dimension table
"Sales" (PK: SALE_ID),
"D1" (PK: D1_ID),
"D2" (PK: D2_ID),
"Customers" (PK: SALE_ID, CUST_ID) - bridge table!
"Products" (PK: SALE_ID, PROD_ID) - bridge table!
3) Dimensions: SalesDim, D1Dim, D2Dim, CustomersDim, ProductsDim
If fact table is joined with bridge table, the number of rows in fact table is multiplied, for example:
D1_ID | SALE_ID | CUST_ID | Indicator1
777 | 1 | 14 | 10
777 | 1 | 17 | 10
777 | 2 | 15 | 12
888 | 3 | 16 | 20
888 | 3 | 17 | 20
888 | 4 | 19 | 30
I need to get report:
D1_ID | Indicator1 (SUM)
777 | 22
888 | 50
and with filter by customer, for example (CUST_ID = 17):
D1_ID | Indicator1 (SUM)
777 | 10
888 | 20
i am trying to use "based on dimension" aggregation, for example (Indicator1):
Dimension Formula
CustomersDim MIN
ProductsDim MIN
Others SUM
The generated physical SQL performs joining EVERY dimension to the fact table, even though they are not included in the final result set.
Is there any way to tweak logical or physical model in order to eliminate excessive joins?
Thanks in advance!
Edited by: 859688 on 31.10.2011 4:04
Edited by: 859688 on 31.10.2011 4:06
Edited by: 859688 on 31.10.2011 4:08

I found this text on the help, but I didn't understand, because when I check the "based on dimensions" check box, I can choose aggregation rules for each dimension, not only the time dimension.
Also, I found in the help menu:
"In the Aggregation tab, select the Based on dimensions check box.
The Browse dialog box automatically opens.
In the Browse dialog box, click New, select a dimension over which you want to aggregate, and then click OK.
In the Aggregation tab, from the Formula drop-down list, select a rule."
I did the same steps suggested by the text above, but it didn't work.

Aggreation Based on Dimensions - Aggregation rule: Evaluate_Aggr

Hello Experts,
Can any of you explain to me how do you use the Logical Column Aggregation based on dimensions?. If you can set up a simple example would be great. Also, what is the definition of the aggregation rule : Evaluate_Aggr?, please give a simple example
Thanks for your time
Pablo.

And it's not the same than a level based measure :
The definition of a level based measure :
http://gerardnico.com/wiki/dat/obiee/bi_server/design/fact_table/level_based_measure_calculations
An example with evaluate (lag analytic function)
http://gerardnico.com/wiki/dat/obiee/presentation_service/obiee_period_to_period_lag_lead_function
Check the two and you will see the difference in the definition.

Based on Dimension Aggregation method - OBIEE 11G

Hi,
I have a fact table with one measure value and 3 dimensions (Time, Issue, status). Fact table is loaded monthly data for different issues and with status and a corresponding value.
I want my report to show always issues that is latest of that period and then status of the same.
Lets say:
Fact table has data like this:
31/Jan/2011 - Issue1 - Open - 10
28/Feb/2011 - Issue1 - WIP - 20
31/Mar/2011 - Issue1 - WIP - 30
30/Apr/2011 - Issue1 -WIP - 40
31/May/2011 - Issue1 -Closed - 50
31/May/2011 - Issue2 -Open - 60
31/May/2011 - Issue3 - Open - 20
Now I want to see the report by status and value and it should show me the latest of that time period.
For Quarter1 :
WIP - 30
For Quarter2:
Open - 80
Closed - 50
If I take Year then it should show me :
2011 - Open - 80
2011 - Closed - 50
I tried using aggregation "Based on dimension" option in BMM layer and put Others - Sum() and LAST against time dimension.
But in that case it is giving me the results by status what is latest for the time period. So it is ding sum by other dimension first and then applying LAST method.
In that case result of Quarter -1 will be :
Open - 10
WIP - 30
If I can change the order of aggregation method like first apply LAST method and then do sum then I think desired result will come. But I am not able to change the order.
Is there any other of doing this solution?
Any help is highly appreciated.
Thanks

Hi,
There will be multiple records for an entire month as there are many issues. For a particular Issue it will be one with one particular status for a particular month.
The join is based on the date colum of fact table and the dimension table.
Regards,
SS

Logical column - Aggregation - based on dimensions

Hi,
Can anyone explain the working of the aggregation based on dimension functionality. I understand it is different from level - based measures.
Thanks in advance.
- Priti

Hi priti,
Aggregation based on dimension .
Hav a look at this you get an idea http://gerardnico.com/wiki/dat/obiee/measure_level_based
UPDATED POST
Sorry i gave you the wrong link.This is what your looking for
http://gerardnico.com/wiki/dat/obiee/aggregation_based_on_dimension
follow this etiquette as your new http://forums.oracle.com/forums/ann.jspa?annID=939
Cheers,
KK
Edited by: Kranthi on Feb 24, 2011 12:20 AM

Aggregation based on dimension

Hi all,
Can anyone help me in knowing the difference between normal aggregation set for a measure irrespective of dimensions and different aggregations set for the same measure based on dimension...

hi User,
Look at http://oraclebizint.wordpress.com/2007/12/03/oracle-bi-ee-101332-level-based-measures-lbms/
thanks,
Saichand.v

Preaggregation across value based hierarchy dimension in 11g

Hi All,
I have created a cube with 6 dimensions in olap 11g. One of those six dimensions has only one hierarchy which is value based hierarchy. I have chosen level based aggregation as I know at what levels exactly users are going to query. When I was going through the dimensions to choose levels to preaggregate I noticed there were no options available for my value based hierarchy dimension ( I could see "all" option for the same case in 10g) then I tried to look for definitions of underlying objects just to make sure it will preaggregate data across my value based hierarchy dimension.
I found value set corresponding to my value based hierarchy dimension in <CUBE NAME>SOLVEAGGMAP object , which AWM uses to decide which dimension values to preaggregate but if I do rpr on that value set (rp r<CUBE NAME>SOLVE<DIMENSION NAME>_PVSET) it shows NA so my question is can I pre aggregate across value based hierarchy dimension in olap 11g?
Olap Version: 11.2.0.1
AWM version: 11.2.0.1
Thanks

Even if you know exactly which levels your users will query, percent based precompute (e.g. 30%) may still be faster in practice because queries are returned using 'sparse looping' instead of 'dense looping'. This was the single biggest performance advantage of 11g over 10g.
But if you still want to use level based precompute, then you should look at the XML template for the cube (as saved by AWM, for example). In it you should find something called PrecomputeCondition. This defines the set of members that are precomputed. Here is an example I just created using the GLOBAL schema
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT LEVELS (PRODUCT.CLASS, PRODUCT.FAMILY, PRODUCT.ITEM)]]>
</PrecomputeCondition>The PrecomputeCondition is also visible through the USER_CUBES view.
SELECT PRECOMPUTE_CONDITION
FROM USER_CUBES
WHERE CUBE_NAME = 'MY_CUBE';You can hand modify this condition in the XML to specify an alternative 'non level based' precompute condition for any dimension. For example, if you define an attribute named 'SHOULD_PRECOMPUTE' on your PRODUCT dimension that is 1 for members to be precomputed and 0 for all others, then you can change the condition as follows.
<PrecomputeCondition>
<![CDATA[
"TIME" LEVELS ("TIME"."MONTH", "TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL, CHANNEL.CHANNEL),
CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT, CUSTOMER.REGION, CUSTOMER.SHIP_TO),
PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
</PrecomputeCondition>If you recreate the cube from the XML with this condition, then the PVSET valueset you discovered should contain all dimension members for which the attribute value is 1.   This gives you complete control over what is precomputed.   Note that AWM doesn't support this form of condition, so it won't show up if you go to the Precompute tab, but it is valid for the server. The PL/SQL below will modify the PrecomputeCondition (for the cube named MYCUBE) without going through AWM.
begin
dbms_cube.import_xml(q'!
<Metadata
Version="1.3"
MinimumDatabaseVersion="11.2.0.2">
<Cube Name="MY_CUBE">
    <Organization>
      <AWCubeOrganization>
        <PrecomputeCondition>
          <![CDATA[
           "TIME" LEVELS ("TIME"."MONTH","TIME".CALENDAR_QUARTER, "TIME".CALENDAR_YEAR),
           CHANNEL LEVELS (CHANNEL.TOTAL_CHANNEL,CHANNEL.CHANNEL),
           CUSTOMER LEVELS (CUSTOMER.MARKET_SEGMENT,CUSTOMER.REGION,CUSTOMER.SHIP_TO),
           PRODUCT WHERE PRODUCT.SHOULD_PRECOMPUTE = 1]]>
        </PrecomputeCondition>
      </AWCubeOrganization>
    </Organization>
</Cube>
</Metadata>
end;
/

Tutorial for "aggregate based on dimensions"?

Hi, has anyone seen a detailed, step by step explanation of how to use the "aggregate based on dimensions" functionality? I easily understand how this is used in "time based" examples - i.e. average balances over time, beginning and ending balances, etc.
However, I'm thinking I may be able to use this to solve a problem I have where I need to average employee ages - but because employees can have more than one job, their ages often show up more than once (which I don't want). Somehow it seems like I should be able to use the FIRST or LAST aggregation function on one and/or some of the dimensions to achieve what I want...but I'm a bit stumped on how.
Thanks in advance!
Scott

I believe you want to use the FILTER function:
FILTER("Auto AR".UBI_AUTO_AR.PATIENT_AR USING "Auto AR"."UBI_AUTO_AR"."YEAR_MONTH" = last("Auto AR"."UBI_AUTO_AR"."YEAR_MONTH" ) )
I am not positive that it will work with the last() function, but it is worth a shot. This will aggregate based on the aggregation setting for "Auto AR".UBI_AUTO_AR.PATIENT_AR.

Need a measure variable based on dimension

Dear Experts,
I need a variable based on dimension.This should gives the values from 1 to n based on dimension.
Suppose i have a column "Wage type".If it has 10 rows,Then for first one it should be 1 and second one it should be 2 and so on.I want to implement break for this dimension,even though the variable should give same values as i mentioned above.
I try to use RowIndex and Count functions.But i couldnt get my requirement.
I want to use this values in Xcelsius.
I hope you can understand issue.
Regards
Venkat
Edited by: Venkat8130 on Jun 23, 2011 7:24 AM

Hi,
I worked on the same issue, in my case result in following format
year........count...month......revenue
2001........ 1........ jan............100
.................2.........feb............200
.................3......... mar...........300
.................4......... apr............400
2002.........1...........jan..........500
.................2..........feb...........600
.................3..........mar..........700
If you are expecting the same format, first break the report deportment wise. Create the variable count with bellow formula.
=RunningCount([Month];Break)
Regards,
Shahin.
Edited by: shahin13 on Jul 19, 2011 8:58 AM
Edited by: shahin13 on Jul 19, 2011 9:04 AM

In SSRS, aggregate measure based on dimension value

I am writing an SSRS 2012 report whose data source is an SSAS cube. In one table of this report, I am using a very simple data set with one dimension (Category) and one measure (Sales). The dimension has 4 members, A B C D. For the purposes of this
report table, I want to show the sum of sales for A, the sum of sales for C, and the sum of sales for B and D combined. I then want to show each of these 3 values as a percent of the total (sum of A B C D).
The data set looks like this:
CATEGORY SALES
A                10000
B                14000
C                 8000
D                 8000
The resulting report table should look like this:
CATEGORY SALES % OF TOTAL
A                10,000      25.0
B+D            22,000      55.0
C                 8,000       20.0
TOTAL         40,000

Hi ,
As you mentioned you need such aggregation in SSRS and you are using SSAS datasource.
so you can achieve this using MDX Query.
I have done this in my environment . I took below for achieving this
Dimension : Category
Relationship : There should be Facttable relationship with Dimension table Category.
Measure : Unit Price (in your case sale)
Please find below solution using MDX Query.
Please share if you have any doubt.
Thanks

Create different hierarchy based on Dimension values

I have a dimension called period. This dimension is having 4 different types of periods. The period table looks as below. I need to create 4 different hierarchies for these 4 types of periods based on l1 to l5 values. But all these values are in the same
table. Is it possible in SSAS? If so please let me know how can I do it.

If i understand it correctly, you want one hierarchy for one row, then you need to flat the table in the view and then you can create those hierarchy. But it is no different from having one hierarchy with the table you have. your hierarchy is going to look
like "Priod5" <- "Priod4" <- "Priod3" <- "Priod2" <- "Priod1". this hierarchy will have all the values. Don't forget to use the composite key for each attribute except key attribute.
hope this is helpful.
prajwal kumar potula

Problem with time dimension aggregation

I have a time dimension with 2 columns:Year and week
I've created a hierarchy in it to drill down from the year to the week.
when I report the sales in week level I have the right values but when I report the sales value in year level I don't have the right aggregation.Even if the year Level is a grand Total in the hierarchy.
The problem is that for all the years I have the same value but when I add the week level to the report Then I have the right values.
What could be the problem

Hi,
1.Actually the drill down Route path is not properly generated with your given key columns in herarchies.
need to give correct key columns
like year(YYYY)-->Week(wee should be the unique column for each and evry year)
suppose:
2000-sunday
2001-sunday should be different
so mostly the problem at your week column make the unique yearweek column as the key identifier at that level
Every Week is unique cause the logical key is a combination of the year and the weeknumber
2.if not you need to set individual levels for measures in content tab...
you mean by the content tab the level tab when you doubleclick into the measure???
Thanks

Prompt based on Dimension Hierarchy

Hi there,
We have a Organization dimension built with 5 levels : All, Company, Operating Unit, Division, Site.
eg
All
Company A
Operating Unit 1
Division 1
Site1
Site2
Division 2
Site3
Site4
Operating Unit 2
Division 3
Site5
Site6
Division 4
Site7
Site8
Company B
Operating Unit 3
Division 5
Site9
Site10
Operating Unit 4
Division 6
Site11
Site12
Division 7
Site13
Site14
Users access is determined via the security model where users are given access depending on which level they are allowed to see.
My requirement is to give users that have access to more than one level, a prompt where they can see data for any individual level they wish eg
If user1 has access to Company A, when she logs in, thh prompt must display Company A (for aggregated data) as well as all the Operating Units withing Company A and all Divisions in those Operating Units and all Sites in those Divisions...ie as per example above, she should see:
Company A
Operating Unit 1
Division 1
Site1
Site2
Division 2
Site3
Site4
Operating Unit 2
Division 3
Site5
Site6
Division 4
Site7
Site8
If user 2 with access only to Division 4 logs in, she should see data for only:
Division 4
Site7
Site8
I have tried doing this and have achieved it using 5 different prompts using the constrain option.
Is there any way that I can consolidate this into one parameter/ prompt; whereby when the user logs in, he/she can see a list of all the levels that he/she has access to in a single prompt / list of values???
Any help would be much appreciated.
Thanks alot,
Ash.

Yes, this can be done.
but there is little work around.. Using guided navigations
1. Create a report with column fx as case when 1=0 then markets.region else user() end
2. apply filter on this column is equal to User_1
3. Create another report with column fx as case when 1=0 then markets.region else user() end
4. apply filter on this column is equal to User_2
5. Now add all your prompts to dashboard, but each prompt should in each section object of dashboard.
6. For first section click on section properties, go to Guided Navigation...
7. Browse Source Request as first report.. and keep If request returns rows selected.
8. Repeat above step for another section.. but this time browse 2nd report.
9. Just save dashboard.
Check now..
Hope you understood..
Regards
Kishore Guggilla
Edited by: Kishore Guggilla on Feb 18, 2009 12:57 PM

Dense dimension aggregation

Hi All,
Is it possible to only aggregate and avoid calculation on dense dimension. I just want to get the aggregated values at the top level and avoid calculation.
AGG("Account"); is not working. essbase is accepting only CALC DIM.
Is there any command which only aggregates dense dimension?

Ah, OK. Is the dense member you have problems with a dynamic calc member, or is it a stored formula member? In either case, is the formula sensitive to month (i.e. why does it calculate a different value in Jan vs Dec, despite the fact that you have copied the same data)?
Incidentally, the reason I was talking about performance etc is that improved calculation performance is the usual motivation to use AGG vs CALC DIM.

Different Languge/Description Based on Dimension Level

Is it possible at all to have either short or long description be chosen through a function depending on a condition e.g. different level in cube?
Example. If Condition A is met than Long Description is used, Condition B is met than Short Description is used.
Edited by: user7853353 on Aug 14, 2012 2:36 PM

Not through Oracle OLAP alone. This is more of a Reporting issue and can be done via db view or using reporting tool features:
a) Mapping is restricted to a single column. So Long and Short Descriptions need to be mapped to a specific column in source table/view. If your condition is static or related to backend dimension attribute value conditions then you can define the logic in a source view and map both desc attributes to the special column.
define column green_ldesc_else_sdesc in dimension view....
case when product_alias.color = 'GREEN' then product_alias.long_desc else product_alias.short_desc end as green_ldesc_else_sdesc
Use this column to map to short_description/long_description attributes in olap aw dimension mapping.
b) In OBIEE Answers, you can expose the relevant fields in the reporting layer or Presentation layer of rpd and use it in a case statement to implement your logic.
E.g:
CASE WHEN "OLAP Presentation Layer Name"."Product"."Level Name" = 'CLASS' THEN "OLAP Presentation Layer Name"."Product"."Long Description" ELSE "OLAP Presentation Layer Name"."Product"."Short Description" END

Based on dimension aggregation

Similar Messages

Maybe you are looking for