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

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.

Multiple Hierarchies from Single Dimension Table in OBIEE-11g?

Is it possible to have Multiple Hierarchies from Single Dimension Table in OBIEE-11g?
Like 1)Year-Qtr-Month-Weeks 2)Year-Month-Days

Hi,
or if your lowest level is the same like
Day->month->year->Total
Day->businessMonth->businessyear->Total
Then yes, it is.
Create the first, then you start to create the second by adding your top(business year) level on the same level as the one you have (year) both under your total.
Then when you would add your second base level, there is a special option for it, something like use other hierarchy level/shared level (sorry can't recall and does not have a connection right now) then you select your existing day level under your businessmonth level.
Hope this helps,
Regards,
D

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.

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.

Dashboard prompt on a Dimension Hierarchy in Obiee 11g

Hi All,
I have created a hierarchy (parent-child) on a dimension 'A'. I am able to create a dashboard prompt for the dimension hierarchy. However I am not sure how to create a report that is to be filtered on this dashboard prompt. I tried using the attribute name that the hierarchy uses but that does not work. Can some one please let me know how i can filter a report by a hierarchy dimension prompt.
Thanks,
Nikita
Edited by: user12438396 on May 8, 2011 1:16 PM

Hi Nikita,
For your requirement, you need to go for Selection steps pane in the analysis(report). Click on steps link and then add the hierarchy column that you want to use and expand the hierarchy to the lowest level. Now select all these and all the attributes will now appear in the other side.
If you dont expand the hierarchy to the lowest level, then only the highest level values will appear in your selection at prompt.
Also make sure to check the 'override' checkbox in the bottom, this helps in filtering the values.
Hope this answers your question.
Cheers,
Obul

Sum Aggregation Error in Physical & BMM Layer in OBIEE 11g with Essbase 11

Hi everyone,
I'm using OBIEE 11g with Essbase 11 as the data source. I'm using Sample Basic database from the Essbase as my data source. If I'm using the hierarchy for the measures (so I don't flatten the measures), and when I changed the aggregation in both physical and BMM layer from Aggregate_External to Sum, I can't create a report at all from the Answers.
Does anyone encounter the same thing? Any ideas/solution about this? Please help.
Thanks a lot!

Hi Deepak,
When I picked the "Basic - measure" alone, I got this error.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
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: 96002] Essbase Error: Unknown Member Basic - measure used in query (HY000)
SQL Issued: SELECT 0 s_0, "Sample Basic"."Basic"."Basic - measure" s_1 FROM "Sample Basic".
When I picked the "Gen1,Measures" alone from the measure dimension, I got this error:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
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: 46008] Internal error: File server\Query\Optimizer\ServiceInterfaceMgr\SIMDB\Src\SQOIMDXGeneratorGeneric.cpp, line 2610. (HY000)
SQL Issued: SELECT 0 s_0, "Sample Basic"."Measures"."Gen1,Measures" s_1, SORTKEY("Sample Basic"."Measures"."Gen1,Measures") s_2 FROM "Sample Basic"
But when I queried the dimensions one by one (only single dimension each), no error was shown.
This only happens if I use Sum in the physical and BMM layer. If I use External_Aggregation, these errors do not happen. And if I flatten the measures, these errors also do not happen.

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;
/

OBIEE 11g: Non conformed dimension filter

Hi,
I have two fact tables and some confromed and non conformed dimensions between the fact tabels.
The hiearchies being built and proper levels were set for the fact tables. The measures of the fact were set to the total level of the non confromed dimension tables.
The fact also hold some non aggregated columns (baseline columns), all the base line columns where moved to a logical dim table.
The report involves both the fact tables, conformed and non conformed dimension columns.
When we built the report with all these columns the report is showing fine. But when we add the filter with the non conformed dimension the report is throwing some error.
Error Details
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
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: 14023] None of the fact sources for D01 Date.Date are compatible with the detail filter [D05 Non Confrm Dimension.Code = 'AFS']. (HY000)
The above functionality was working fine with OBIEE 10g and have implemented it many times before.
There is one patch available for this issue but it is available only for windows 32 bit enironment.
Patch details
Patch 14210864: OBIEE 11G: CONFORMING DIMENSION SETTINGS FROM 10G NOT WORKING IN 11G
Can anyone give some suggestion or workaround? I can't do any change in Datamodel.
Thanks,
Vino

Hi Vinod,
In OBIEE 10g, we are running into similar error when we add filter from non conformed dimensions in a report, so can you please share patch download details like where to download or if we have to raise a SR for the Patch 14210864.
Thanks in Advance!!

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

Modelling 2 Fact Tables with Non-Conforming Dimension in OBIEE 11g

Hi all,
I have two fact tables (Fact 1 and Fact 2) and two dimension tables (Product and Rule). The Product dimension table is a conforming dimension and is used in both fact tables, but the Rule dimension is a non-conforming dimension which is used only one fact table. I'm using OBIEE 11g (11.1.1.6.0).
====
Fact 1
====
Sales ID | Product ID | Quantity | Sales Description | Sales Status
S001 | P001 | 100 | bla bla bla bla bla | N
S001 | P002 | 200 | bla bla bla bla bla | N
S002 | P001 | 200 | lab lab lab lab lab | Y
S002 | P003 | 250 | lab lab lab lab lab | Y
Notes for Fact 1:
- One Sales ID can have multiple Product IDs
- Sales Description and Sales Status are the same for one Sales ID (repeating Sales Description and Sales Status for the same Sales ID)
====
Fact 2
====
Sales ID | Product ID | Rule ID | Score
S001 | P001 | R001 | 2
S001 | P001 | R002 | 3
S001 | P002 | R003 | 1
S002 | P001 | R003 | 1
S002 | P003 | R002 | 2
S002 | P003 | R004 | 5
Notes for Fact 2:
- One combination of Sales ID and Product ID can have multiple Rule ID
I'm wondering how best to model these tables so that I can create this report (number of the dimension and fact tables created in the business model, level mapping, aggregation rule, etc)? Any suggestion/advice on how to achieve this?
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID | Score
S001 | P001 | 100 | bla bla bla bla bla | N | R001 | 2
S001 | P001 | 100 | bla bla bla bla bla | N | R002 | 3
S001 | P002 | 200 | bla bla bla bla bla | N | R003 | 1
S002 | P001 | 200 | lab lab lab lab lab | Y | R003 | 1
S002 | P003 | 250 | lab lab lab lab lab | Y | R002 | 2
S002 | P003 | 250 | lab lab lab lab lab | Y | R004 | 5
Thank you very much!

Hi Dhar, thanks for the suggestions.
I tested what you suggested, but the result is not as per my expectation mentioned above. Here's what I did:
1. In physical layer:
- I joined Fact 1 table with Product dimension table only
- I joined Fact 2 table with Product and Rule dimension tables
2. In business model layer:
- I created 3 logical tables: Fact, Product, and Rule
- The Product table contains the Product ID and Product Name from the Product dimension table in the physical layer
- I created the hierarchy (logical dimension) for Product with only ProductTotal level (as the grand total level) and ProductDetail level that contains Product ID and Product Name
- The Rule table contains the Rule ID and Rule Name from the Rule dimension table in the physical layer
- I created the hierarchy (logical dimension) for Rule with only RuleTotal level (as the grand total level) and RuleDetail level that contains Rule ID and Rule Name
- The Fact table contains 2 logical tables sources: Fact 1 (which logical level in the Content tab is mapped to ProductDetail and RuleTotal) and Fact 2 (which logical level in the Content tab is mapped to ProductDetail and RuleDetail)
- The Fact table contains Sales ID logical column (mapped to both Fact 1 and Fact 2 logical table sources)
- The Fact table also contains Sales Description and Sales Status logical columns (mapped to only Fact 1), which aggregation rule is the default to None
- The Fact table also contains Quantity logical column (mapped to only Fact 1), which aggregation rule is set to Sum
- The Fact table also contains Score logical column (mapped to only Fact 2), which aggregation rule is set to Sum
OBIEE returns the expected result when I retrieve the report:
Sales ID | Product ID | Quantity | Sales Description | Sales Status
However, OBIEE returns an error when I retrieve the reports:
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID
or
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Rule ID | Score
The error is:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
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: 14020] None of the fact tables are compatible with the query request FACT.SALES_STATUS. (HY000)
And the Score column is blank when I retrieved this report:
Sales ID | Product ID | Quantity | Sales Description | Sales Status | Score
Any suggestion anyone? Please help. Thanks a lot!
Edited by: stewartlife on Nov 29, 2012 4:01 PM

Dynamically Aggregations Selection during runtime in OBIEE 11g

Can anyone help me how to choose aggregations dynamically in OBIEE 11g while runtime.
Say i have SUM and AVG as two aggregations, and depending on any one of selection my column total should vary.
I acheived this using Variable prompt, but i want it as a drop down and just by toggling between the two my report should change with out using go / apply button.
I tried and came to conclusion that these are static text and doesn't have any database value it can't be showed as dropdown.
Thanks,
Swathi

shud be simple...Simply Create 2 Pivot Views for same Criteria in Single report and perform SUM and AVG for each. Now use View Selector to toggle between two Pivot to get SUM and AVG reports.

OBIEE 11g 11.1.1.7 NON Confirmed dimensions and facts

Hi All,
In OBIEE 10g if we had non-conformed dimensions we used to work with by defining logical level of the conformed dimensions to grand total and confirmed dimensions to detail in the LTS of the fact table
and also set metrics to grand total level.
But in OBIEE 11g doing same is throwing error
[nQSError: 14025] No fact table exists at the requested level of detail
How do we achieve this?
Regards,
deep

You need to create a complex join with non conformed dimension and the fact with 1=1 and set the logical level of the measure to total for a non conformed dimension.
You can refer: https://s3.amazonaws.com/rmc_docs/biforum2011/Mcquigg_Metadata.pdf

OBIEE 11g and Essbase and Dimension Filter / Selection Steps

We are doing a prototype using OBI 11g with Essbase 11.1.2 as a datasource. Our prototype consist of several reports, graphs and dashbaords. The Essbase cube is an ASO cube with 12 dimensions. Most of our dimensions are ragged/unbalanced so we have set up the dimension type to be "Value" in the RPD. There is one dimension - Product and it is a ragged dimension. We are trying to create a simple report that has level zero products as rows. This is something pretty easy to do in Essbase Financial Reporting but it does not look like there is an easy way to filter only on the Level 0 members of a particular dimension. I have tried with selection steps as well as changing the dimension back to unbalanced without much luck.
Has anyone out there done something similar before? Thx.

Hi user,
Check this out OBIEE 11g - Essbase connection Failed
And 1 more thing admin tool works only for 32-bit ...but not in 64 bit.So ensure you install 32-bit for admin tool.
UPDATED POST
Jacob->its same for stand alone application also,it works only on 32-bit
hope helps you.
Cheers,
KK
Edited by: Kranthi.K on Mar 7, 2011 9:00 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

Based on Dimension Aggregation method - OBIEE 11G

Similar Messages

Maybe you are looking for