Aggregation Rule in a Dimension Logical Table

Hi!
I have a Dimension Logical Table which is related (one-to-many) with several Fact Logical Tables.
This Dimension has 1 logical column which has an aggregation defined:
- Account Last Creation Date = Max(D_CUSTOMER_ACCOUNT.CREATION_DATE)
When I use Answers to build a report using this Logical Columns the following error appears:
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: IWS Client - Last Account Creation Date:[DAggr(ACCOUNT.IWS Client - Last Account Creation Date by [ ACCOUNT.TLC Account Warehouse Key Account Table] SB CUSTOMER ACCOUNT)]. Please fix the metadata consistency warnings. (HY000)
SQL Issued: SELECT ACCOUNT."IWS Client - Last Account Creation Date" saw_0 FROM "VFPT - Upgrade Siebel"
How can I workaround this issue?
Thanks.

Hi!
My understanding is that you have set an aggregation (in the aggregation tab) to a mapped field.
Wildmight is right, you can't use aggregation is dimension tables. Which makes sense.
Instead, you can try to create a new logical field with the name of your choice, checking the "use existing logical columns as the source" check box and put your formula in it. At the right of the text box, there's a little button [...] that can help you building a correct formula.
I hope this helps.
Ced.

Similar Messages

How to define an aggregation rule for a dimension based on bridge table?

Hello,
I need a solution for aggregating data correctly when using a dimension based on a set of dimensione tables containing a bridge table. Please find below a description of my business case and the OBIEE model which I’ve created thus far.
Business Case
The company involved wants to report on the number of support cases, the different types of actions that were taken and the people involved in those actions. One support case will undergo a number of actions (called ‘handelingen’) until it is closed. For each action at least one person is involved performing a specific role, but there can also be multiple persons involved with 1 action, each performing a different role for that action. This is the N : N part of the model.
The problem that I face is visible in the two pictures below:
http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/sample.png
As long as I don’t include anything from the Dimension Meelezer in my report, I get the correct number of handelingen (7). When I include the person (called ‘Meelezer’), the measuere per action is multiplied by the number of persons/roles involved with that action.
When I changed the Aggregation rule in the report column #Handelingen to ‘Server Complex Aggregate’ I do get the correct endtotal:
http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/sample2.png
I believe it should be possible to define in the repository a different aggregation rule for individual dimensions, but I’ve not been able to achieve this.
Explained below is what I have created in my Physical and Business Model & Mapping layers:
The Physical Model is built like this:
(This is just a small part of a much larger physical model, but I’ve only included the most relevant tables)
http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/PhysicalDiagram-1.png
The Fact table (ALS Feit Zaakverloop) contains FK’s for the action (FK_HANDELING, joined to ALS Dim Handeling), the date the action took place (FK_DATUM_ZAAKVERLOOP, joined to ALS Dim Datum Zaakverloop) and the uniqe group of people involved (FK_MEELEZERS, joined to ALS Groep Meelezers) and a measure column (SUM_HANDELINGEN) populated with the value ‘1’ for each row.
The Bridge table (ALS Brug Meelezer/Reden Meelezen) contains three FK’s: FK_GR_MEELEZERS (joined to ALS Groep Meelezers), FK_MEELEZER (joined to ALS Dim Functionaris) and FK_REDEN_MEELEZEN (joined to ALS Dim Reden Meelezen).
The Business Model
In the business model, the four physical tables for the N:N relation have been combined into one logical dimension table.
http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/BusinessModel-1.png
DIM Meelezer contains one LTS in which the four physical tables have been combined:
http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/LTS1.png
And all the required locical columns have been created:
http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/LTS2.png
DIM Meelezer has also been identified as a bridge table and a Business Key has been defined on a combination of the FK’s in the bridge table and business codes of the two dimension tables.
http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/BMDIM.png
Next a hierachy was created for Dim Meelezer:
http://i84.photobucket.com/albums/k24/The_Dutchman_2006/OBIEE/Hier.png
In Feit Zaakverloop, a measurement called ‘# Handelingen’ was created using SUM_HANDELINGEN, with an aggregation rule of SUM.
In the LTS of both the DIM Meelezer and Feit Zaakverloop, the Logical Content Levels have both been set to: LVL Detail – Meelezer.
Please provide suggestions that will NOT require changes to the physical datamodel as they would require too much time to achieve (or at leats would not be ready before my deadline.
Thanks!
Edited by: The_Dutchman on Dec 13, 2011 11:43 AM

Hmm, no replies yet...
Am I in 'uncharted territory' with this issue?

How to set Grand Total of a Measure when its aggregation rule is Max in Logical Layer

Hi
I have a Measure Column (Budget) and in Logical layer the aggregation rule is set as (Max) which looks like Max(Budget). But now it is included in the report and when my client is trying to see its grand total, it is giving the Max Budget figure of the report rather than giving the total sum(grand total).
Kindly share some ideas in achieving the grand total without disturbing the actual aggregation of the measure.

Thank You for your reply.
In my case i don't have a problem with aggregation for Budget Measure(max(Fact_XXKC_SHIP_TO_BUDGET_CAT_F.SALESREP_BUDGET_YTD)). This is the aggregation rule applied on the Salesrep Budget YTD.
Now i created a report with columns
Salesrepresntative(Dimension),, Sales Invoices(Measure1),, SALESREP_BUDGET_YTD(Measure 2).
In the above report the values are perfect, but when we used Grand total option at ROW level in table view, the grand total of Measure1 is cumulative of all the rows, but the Grand total of SALESREP_BUDGET_YTD (measure2) is the max of all the columns.
What i require is the Grand total of SALESREP_BUDGET_YTD (measure 2) should be cumulative of all the columns.
I have shared my SQL query, kindly verify it and share any idea.
select sum(case when T97600.W_XACT_TYPE_CODE = 'Chargeback' then T93664.NET_AMT * T93664.GLOBAL1_EXCHANGE_RATE end ) as c1,
sum(case when T97600.W_XACT_TYPE_CODE = 'Credit Memo' then T93664.NET_AMT * T93664.GLOBAL1_EXCHANGE_RATE end ) as c2,
sum(case when T97600.W_XACT_TYPE_CODE = 'Debit Memo' then T93664.NET_AMT * T93664.GLOBAL1_EXCHANGE_RATE end ) as c3,
sum(case when T97600.W_XACT_TYPE_CODE = 'Standard Invoice' then T93664.NET_AMT * T93664.GLOBAL1_EXCHANGE_RATE when T97600.W_XACT_TYPE_CODE = 'Invoice Cancellation' then T93664.NET_AMT * -1 * T93664.GLOBAL1_EXCHANGE_RATE end ) as c4,
T315597.XXKC_RESOURCE_NAME as c5
from
W_CUSTOMER_LOC_USE_D T315597 /* Dim_W_CUSTOMER_LOC_USE_D_Status */ ,
W_SALES_INVOICE_LINE_F T93664 /* Fact_W_SALES_INVOICE_LINE_F */ ,
W_XACT_TYPE_D T97600 /* Dim_W_XACT_TYPE_D_Sales_Ivclns */
where ( T93664.XACT_TYPE_WID = T97600.ROW_WID and T93664.DELETE_FLG = 'N' and T93664.XX_SHIP_TO_LOC_USE_WID = T315597.ROW_WID )
group by T315597.XXKC_RESOURCE_NAME
) D1 full outer join (select max(T313184.SALESREP_BUDGET_YTD) as c1,
T315597.XXKC_RESOURCE_NAME as c2
from
W_CUSTOMER_LOC_USE_D T315597 /* Dim_W_CUSTOMER_LOC_USE_D_Status */ ,
XXKC_SHIP_TO_BUDGET_CAT_F T313184 /* Fact_XXKC_SHIP_TO_BUDGET_CAT_F */
where ( T313184.SITE_USE_WID = T315597.ROW_WID )
group by T315597.XXKC_RESOURCE_NAME

Default Aggregation Rule

Can someone explain me as to how BI interprets the default aggregation rule.
Say when we say the defualt aggregation rule on the sales fact table column revenue is SUM. what does it actually imply.
Similarly when we use the Aggregation Content tab in the Logical table source and set aggregation content group by what does it actually mean.
Thanks,
Chan

If you didnt set content tab that would be default aggregation, means based on the columns pull in the criteria SUM changes like drill down or roll up.
'Group by' clause keep on changes as per the column in the criteria.
When you set any level for a metric then it alway aggregated to that level, values will not change as per column selection.
Pls mark if helps
Edited by: Srini VEERAVALLI on Nov 1, 2012 4:48 AM
Any updates on this?
Edited by: Srini VEERAVALLI on Jan 7, 2013 1:56 PM

Aggregation rule in Logical table source

hi all,
please help me about aggregation rule in logical table source. why,when and how they are used.
thank you.
Regards,
Imtiaz
BI Trainee.

Check page no 115, for explanation
http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/b31770.pdf
save this PDF file, as it helps you in understanding every thing related to RPD developement.

Aggregation rule ignored for Logical sources

Hi,
We are using materialized views as logical sources for our logical tables. These logical sources contain aggregated data at higher level for dimensions. However, we have a logical source at the most detailed level for the dimensions.
Problem: We OBIEE hits the correct logical source based on dimensions selected in answers, it does not apply the default aggregation rule.
For instance, if a measure has aggregation as AVG, then when the logical sources corresponding to aggregated tables are queried, OBIEE does not apply AVG function. However, it does apply the aggregation rule when it uses the logical source at the most detailed level.
I have specified the aggregation content properly for every dimension.
Any pointers to debug the issue will be helpful.
Thanks,

Click on LTS of Table - Column Mapping - Select the logical column - click on expression - Put your logic here. You will get Aggregation rule is enalbed for the column.
Why ? -- Reason could be nested aggregation is not allowed. Aggregation on the normal column applied during query generation at run time. If you use that Agg.Measure to derive another Agg.measure server could not recognize it during runtime.

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

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.

Multiple dimensions from single logical table

Hi,
I cannot seem to create multiple dimensions based one one single logical table. For example, I have a Time table from which I'd like to create a calendar time dimension and a fiscal time dimension. However, as soon as one dimension is created, I cannot create another dimension from the same logical table.
Is it possible?
Thanks

Jlin,
If I understood your requirement correctly you need to create multiple Hierarchies out of a single Logical Dimension table, this is possibe the base rule for creating a hierarchy is you should have a common starting point( Grand Total Level) and a common ending point( Detail Level), first create this and create sublevels and share the Detail Level as a child. This will allow you to create multiple hiearchies out of a single dimension. One level will have drill down on the Calendar dimension and one one the Fiscal and both will have the common detail key like day key.Hope this helps.
Arjun

Aggregation rules and pivot tables

I have 3 measures in a pivot table out which 2 have aggregation rule set to SUM. The third measure has aggregation rule set to NONE.
Although the third measure is a number I do not wish to show a grand total as it is the value in local currency and hence not additive as different regions have different currencies.
However the Pivot table does not display the values of the third measure if the aggregation rule is set to NONE. The cells are blank.
Is this expected behavior ? Can I over-ride this behavior ?
Thanks

What I have is a measure, value of inventory in local currencies. It is not additive because in the context of the report that I am working.
I cannot move it to a dimension. One option I have is to move it to the rows section. But that messes up the format that is expected by the client.
Any other ideas ?

Joining two fact tables with different dimensions into single logical table

Hi Gurus,
I try to accomplish in Oracle Business Intelligence 11.1.1.3.0:
F1 (D1, D2 and D3)
F2 (D1 and D2 and D4)
And we want to build a report F1 F2 D1 D2 D3 D4 to have data for:
F1 that match only for D1-D2-D3
and data for
F2 that match only D1-D2-D4
all that in one row, so D3 and D4 are not common dimensions.
I can only do:
F3 (D1, D2)
F4 (D1, D2 and D4)
And report
F3 F4 D1,D2,D4 (all that in one row, and only D4 is not a common dimension)
Here is the very good example how to accomplish the scenario 1
http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
But looks like it does not work in 11.1.1.3.0
I get
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 14025] No fact table exists at the requested level of detail: [,,Clients,,Day,ROI,,,,EW_Names,,,,,,,,,,,,,,,,,]. (HY000)
I am sure I set up everything correctly as advised in the blog but it works with only one not a common dimension
Is it a bug in 11.1.1.3.0 or something?
Thanks,
Kate

Thanks for all your replies.
Actually, I've tried the solutions you guys mentioned. Generally speaking, the result should be displayed. However, my scenario is a little bit tricky.
table Y's figures are not the aggregation of table X for D dimension. Instead, table Y's figures include not only D dimension total, but also others (others do not mean A, B, C dimension). For example, table Y stores all food's figure, while table X stores only drink's figure. D dimension is only about drink's detail. In my scenario, other foods' figure is not provided.
So, even if I set D dimension to all/total for table X, table X's result is still not the same as table Y.
Indeed, table Y does not have a column key to join to D dimension's key. So, if I select D dimension and table Y's measures at the same time in BI Answer, result returns no data. Hence, I can't compare table X and table Y's results with selection of D dimension.
Is there any solution to solve this problem?
Edited by: TomChan on Jun 3, 2009 9:36 AM

Two Dimension Hierarchys based on one Logical Table

Is it possible to have two dimesion hierarchys based on one logical table? Suppose we have the following case:
Accounts Table
Code
Name
Category
Subcategory
Level 1
Level 2
Level 3
I would like to have one dimension Total > Category >Subcategory > Code and one Total > Level 1 > Level 2 > Level 3 > Code, so I can drill down on both paths. Is this possible?
Thanx

Yes, the trick is to have the same key on the lowest level in your hierarchy.
regards
John
http://obiee101.blogspot.com/

BMM Logical Table - Create Multiple dimension

Hi All,
In BMM , I want to create more than one Dimension for a Logical Table. Is it possible to create multiple dimensional hierarchies on a single logical table. Can one share the thoughts or provide inputs. Thanks is Advance
S

If I understood your requirements, you are basically trying to do the "Role Playing" dimensions. Is that correct? Ifso, You can create alias for the associated physical table, and then use those aliases as logical tables and then create dimensions of this.
HTH
Mahesh

Aggregation on multiple Logical table source

I have mapped two logical table source(LTS) to a measure.
Sum needs to be used for Essbase LTS and count distinct needs to be used for Oracle DB.
Is there any option to set aggregation on LTS level?
Thanks,

Interesting!!
We may not set aggregate tab based on LTS but you may try this:
Do not use the aggregate tab, during the creation of metric using physical sources and use count distinct for Oracle db and sum for other.
You should see 2 different expressions in 'Data Type' tab->Mapped as
Note: I didnt tested it let me know updates.

Logical table source

Hello!
Can someone please explain difference between dragging and dropping a physical column from a table in Physical Layer to a Logical Table in BMM layer and ragging and dropping a physical column from a table in Physical Layer to a Logical Table Source? When to use these two options?
Thanks,
-D

Hi,
First you have to read the OBIEE Administrator concept and will clear you doubt,
OBIEE Administrator, Windows based client tool to develop and manage Metadata repository. Repository changes can be done in either online or offline mode.
Online mode is when BI Server is actively reading the repository file (when a user is logged in).
Offline is when BI Server is idle. Best practice is to develop in Offline mode.
Minor changes can be made when in online mode. Administrator uses ODBC connectivity to connect to physical data sources, uses Native Drivers for Oracle and DB2.
OBIEE defines three layers of abstraction.
Physical Layer – connections to physical data sources (OLTP, OLAP, Flat Files, Oracle, SQL*Server, Teradata, etc.).
Business Model Layer – Brings together data elements from Physical sources into a logical Star-Schema representation. This is where business rules and definitions are setup.
Presentation Layer – An abstraction from the Business Model, defines exactly how users will see tables and fields.
Connection Pool is a connection to a Physical data source. Multiple connection pools can be created to the same source to improve end-user query performance.
All tables in the Physical layer must have a Primary Key column. Column properties can be edited to set the Primary Key. Physical joins need to be established between tables, using Foreign Keys and Primary Keys. Right-click on Connection pool to create the Physical diagram joins.
A Business Model can be created by drag and drop of objects from the Physical Layer. It’s a logical Star-Schema representation of the Physical objects. Tables from different sources can be merged to form one Logical table. These sources are called Logical Table Sources.
Logical Fact tables hold Metrics; every Metric must have an aggregation rule. Hierarchies can be setup on dimensions for drilldown functionality.
It is important to join logical Facts and Dimensions together, much like the Physical Diagram. Right-click on Model, click Business Model Diagram to create joins. Use Complex joins in the Business Model.
Presentation Layer is exactly what End-Users will see in BI Answers, contains multiple Subject Areas that answer specific Business questions.
Thanks,
Balaa...

Aggregation Rule in a Dimension Logical Table

Similar Messages

Maybe you are looking for