Aggregation tab disabled for fx logical columns

Hello, I am new to OBIEE. Can somebody please help me understand the folowing -
Query - While defining formula column in BMM whenver we use logical column as source why Aggregation Rule tab gets disable?
How can i apply aggregation rule for such columns at RPD. These columns are recognised by icon fx.
Please find attached screenshot to help understand my question.
[https://picasaweb.google.com/105903262683032369187/OBIEE?authkey=Gv1sRgCPW2qu2x8eKdjgE]
Any help is greatly appreciated.
Thanks
Edited by: 930542 on Jun 22, 2012 10:03 PM

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.

Similar Messages

Two physical logical source formulas for on logical column

I have two fact tables :
1. W_SERVICE_REQ_F(opened_dt_wid, assigned_dt_wid, closed_dt_wid, QUEUE_WID, SERVICE_REQ_WID): grain is one row per service request
2. W_SERVICE_REQ_DAY_A(DATE_WID, QUEUE_WID, NUM_OPENED, NUM_CLOSED, num_assigned)
The goal is to answer NUM_OPENED, NUM_CLOSED per queue in a day and be able to drill-down to those service requests.
Physical model:
Common_Date.row_wid = W_SERVICE_REQ_F (Opened_Dt).opened_dt_wid
Common_Date.row_wid = W_SERVICE_REQ_F (Closed_Dt).closed_dt_wid
Common_Date.row_wid = W_SERVICE_REQ_DAY_A.DATE_WID
Queue_d.row_wid = W_SERVICE_REQ_F.QUEUE_WID
Queue._drow_wid = W_SERVICE_REQ_DAY_A.QUEUE_WID
Service_req_d.row_wid = W_SERVICE_REQ_F.SERVICE_REQ_WID. (there is no join between Queue_d and Service_req_d)
BMM Fact and LTSs:
I have W_SERVICE_REQ_DAY_A, W_SERVICE_REQ_F (Opened_Dt), W_SERVICE_REQ_F (Closed_Dt) as LTSs of "Fact - Service Request" in that order.
BMM Fact logical columns (measures):
# Closed
# Opened
Question:
I want to configure each of the above logical column with two physical columns of different aggregate forumlas. (to ensure queries that dont need service req number hit a table) (similar to http://www.gerardnico.com/wiki/dat/obiee/fragmentationlevel_based).
SUM(W_SERVICE_REQ_DAY_A.NUM_CLOSED)
COUNT("W_SERVICE_REQ_F (Closed_Dt)".SERVICE_REQ_WID)
Can someone help in configuring one logical column with two physical column sources with different aggregate formulas?
This is what I tried:
In # Opened Properites->Data Type, mapped it to both W_SERVICE_REQ_F (Closed_Dt).ROW_WID and W_SERVICE_REQ_DAY_A.NUM_CLOSED
In # Opened Properties->Aggregation tab, selected 'Default aggregation rule' as Count Distinct. In the bottom, Logical table sources override as follows:
W_SERVICE_REQ_DAY_A : SUM("Fact - Service Request"."# Closed")
W_SERVICE_REQ_F : COUNT("Fact - Service Request"."# Closed")
Should it be done in a different way?
PS: OBIEE 10.1.3.4.
added OBIEE version: Feb 3, 2012 4:40 PM

I have two fact tables :
1. W_SERVICE_REQ_F(opened_dt_wid, assigned_dt_wid, closed_dt_wid, QUEUE_WID, SERVICE_REQ_WID): grain is one row per service request
2. W_SERVICE_REQ_DAY_A(DATE_WID, QUEUE_WID, NUM_OPENED, NUM_CLOSED, num_assigned)
The goal is to answer NUM_OPENED, NUM_CLOSED per queue in a day and be able to drill-down to those service requests.
Physical model:
Common_Date.row_wid = W_SERVICE_REQ_F (Opened_Dt).opened_dt_wid
Common_Date.row_wid = W_SERVICE_REQ_F (Closed_Dt).closed_dt_wid
Common_Date.row_wid = W_SERVICE_REQ_DAY_A.DATE_WID
Queue_d.row_wid = W_SERVICE_REQ_F.QUEUE_WID
Queue._drow_wid = W_SERVICE_REQ_DAY_A.QUEUE_WID
Service_req_d.row_wid = W_SERVICE_REQ_F.SERVICE_REQ_WID. (there is no join between Queue_d and Service_req_d)
BMM Fact and LTSs:
I have W_SERVICE_REQ_DAY_A, W_SERVICE_REQ_F (Opened_Dt), W_SERVICE_REQ_F (Closed_Dt) as LTSs of "Fact - Service Request" in that order.
BMM Fact logical columns (measures):
# Closed
# Opened
Question:
I want to configure each of the above logical column with two physical columns of different aggregate forumlas. (to ensure queries that dont need service req number hit a table) (similar to http://www.gerardnico.com/wiki/dat/obiee/fragmentationlevel_based).
SUM(W_SERVICE_REQ_DAY_A.NUM_CLOSED)
COUNT("W_SERVICE_REQ_F (Closed_Dt)".SERVICE_REQ_WID)
Can someone help in configuring one logical column with two physical column sources with different aggregate formulas?
This is what I tried:
In # Opened Properites->Data Type, mapped it to both W_SERVICE_REQ_F (Closed_Dt).ROW_WID and W_SERVICE_REQ_DAY_A.NUM_CLOSED
In # Opened Properties->Aggregation tab, selected 'Default aggregation rule' as Count Distinct. In the bottom, Logical table sources override as follows:
W_SERVICE_REQ_DAY_A : SUM("Fact - Service Request"."# Closed")
W_SERVICE_REQ_F : COUNT("Fact - Service Request"."# Closed")
Should it be done in a different way?
PS: OBIEE 10.1.3.4.
added OBIEE version: Feb 3, 2012 4:40 PM

BMM derived logical column - bounced visit

In Web Metrics, a "bounced visit" is when a session views only one page on a website and then leaves. In my fact table, I capture the "total pages" viewed for each session and I define this metric in my Business Model with an aggregation rule of "sum". I'm trying to use this metric to derive the "bounced visit" metric but I'm running into issues.
Session ID Total Pages
1179860475     5
1179861625     1 <= This is a bounced visit
1179861920     7
1179866260     2
1179868693     13
If I define "bounced visits" as
CASE WHEN "total pages" = 1 THEN 1 ELSE 0 END
What I see in the session logs is:
CASE WHEN sum("total pages") = 1 THEN 1 ELSE 0 END
The aggregation of the "total pages" is being done first and then the derived metric is being calculated. This leads to incorrect results. Is there anyway of solving this in the business model? I know that I can go back to the ETL, calculate a "bounce visit" metric, store it in the fact, build out aggregates, etc. I was looking for a short term solution.
Other things I've tried:
1) make a copy of the "total pages" column and turning off the aggregation, call it "total pages - no aggregation"
this leads to queries of the form:
select distinct T22583.TOTAL_PAGES as c1
from
WEB_SESSIONS_A1 T22583
order by c1
2) Create a logical column based on "total pages - no aggregation"
bounced visit = CASE WHEN EnterpriseWarehouse."Web Sessions"."Total Pages - no aggregation" = 1 THEN 1 ELSE 0 END
This leads to [nQSError: 14020] None of the fact tables are compatible with the query request Web Sessions.bounced visit.

Cool. I now have two approaches to solve the problem. Thanks for your help. Using your technique, the new logical column shows up in the Logical Table Source screen and I can define an expression for that logical column. The second approach leaves the table type as a Physical table. This has some benefits as I've noticed that the queries that are generated when the table type is defined as a Select statement end up retrieving all of the columns, even though I only needed to act on one of them.

"last value" in the KF aggregation tab page

can u plz tell me what is the meaning of "last value" in the KF aggregation tab page. also what is use of aggregation reference char. please give explaination with example.
amit

Hi
Last value in KF Aggregation tab is
For example Amount is the Key figure with values 100,200,300,400
if u sekect last value
it will display 400 in the entire amount column..........

Logical column currency format properties at rpd level?

I need to show the currency amount with dollar symbol for a logical column and that should happen at rpd level.
Is there anyway we could do that ?
thank you

Hi User.
You can have logical column name as 'Amount in $' or 'Amount in Dollar'
this is the best practice..
Then if you want value to be suffixed by $ , you can go for data formatting in column properties.....
this is commonly used....
mark if Correct/helps .
fiaz

Error in edit formula of a logical column in report

Hi All,
I'm getting the below error when I click ok in 'Edit Formula for a logical column in Criteria of Report.
Formula syntax is invalid.
Assertion failure: !sFormula.empty() at line 998 of C:\ADE\aime_bi\bifndn\analytics_web\main/project/webreport/reportquery.cpp
Could anybody help me out in this?
Thanks in adv.

Hi,
did u included any case condition over there..kinly check the syntax and correct it.
Thanks
Deva

How To Create Logical column For Lastyear To Till Date

Hi All,
I Have to calculate Lastyear to Till Date for Logical Column.
Ex:I have Time Dime and Fact column and Dimension columns.
jan 2011 to oct 2012.
Please Let me know.
Thanks,
Abhi

Looks like you are not reading my messages
Since you are doing on logical columns getting this error.
Try this using physical columns then count from aggregate tab
CASE WHEN "Oracle Data Warehouse"."Catalog"."dbo"."Fact_W_SRVREQ_F_Open_Date"."OPEN_DT_WID" > 20110101 THEN "Oracle Data Warehouse"."Catalog"."dbo"."Fact_W_SRVREQ_F_Open_Date"."SR_WID" END
The same you can go with your variable
Or else the same can do by duplicating the existing Fact - CRM - Service Request"."# of SRs" and just add above code.
or just use the below you dont use sum since already aggregation is happend for # of SRs
CASE WHEN "Core"."Dim - Date"."Year" = VALUEOf("Warehouse Refresh Date Last Year"."CURRENT_CALENDAR_YEAR_LAST_YEAR") AND "Core"."Dim - Date"."Date" < VALUEOF("Warehouse Refresh Date Last Year"."LAST_REFRESH_DATE_LAST_YEAR") THEN "Core"."Fact - CRM - Service Request"."# of SRs" END
Hope this works, mark as correct

Logical Column Aggregation

I have CurrentDollars and CurrentUnits in my measures table, and I"ve created PriorDollars and PriorUnits logical columns utilizing the AGO function. Since 'Use existing logical columns as the source' is checked, I don't have access to the Aggregation tab, and everything I've read leads me to believe that this is OBIEE's way of forcing inheritance of the aggregation rule of the 'source' column.
Problem is, the Prior* columns don't aggregate (sum). If I create a report with Year, CurrentDollars, CurrentUnits, I get three rows... one row for each year that has data. That's what I want. But when I add either of the Prior columns, I get 52 rows per year (since my data is at the week level). If I wrap either of the Prior columns in SUM, it sums all Prior* column values. If I check the box that says I want it to use Sum aggregation, nothing changes. I get similar bogus results if I add a SUM function around the original AGO function.
This is a real drag. Am I missing something obvious? Some blogs lead me to think that this is a known bug. Does anyone have a workaround?
Edited by: Tom G. on Aug 26, 2009 11:30 AM

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

Display values for logical columns with several physical sources

Hi all,
I'm enocuntering some strange behaviour with the values displayed for a column (when we want to add it a as a filter, and in the dialogue box select 'Show All' values).
Basically the logical column is mapped against several physical columns as the base fact table is aggregated to different levels. Additionally, one column in the fact tables has an attribute value, and these vary between the aggregated and non-aggregated table. This is not a problem.
In the production environment, when we display the all values in the filters prompt for this column we are seeing the values being taken from one fact table. Naturally this means that not all the values possible for this column are being shown (i.e. values from the aggregated fact tables are missing). Now in one of our test environment where those fact tabels have additional data loaded, the values are being taken from one of the other fact tables. Unfortunately it is not necessarily the fact table with less data.
My questions are:
a) What dictates which fact table the server will use when the query in Answers doesnt use any dimensions (i.e. we are selecting just this attribute and selecting all the possible values by which it can be filtered)?
b) Is there a way of obtaining all the values from the differente physical columns? I.e. that the display values shows the values of that logical column across all the physical fact tables? Maybe we would need to model that attribute as a logical dimension just for that attribute? Im not really sure this would work, as at the physical level the join between the dimension and fact would still have to go to only one particular fact table.
Any info or help is much appreciated.

Hi,
Aggregate tables exist at physical level and are created by ETL procedures. Although i am aware that the dimension come into play when the application needs to decide which source aggregate table to use, it is not an issue here as in our query we are not involving dimensions. We are selecting just this one columen, and then the filter option on this column, then in the dialogue box we select 'All Choices', only the values from one of the source tables is being shown.
This is not a probelm within reports, i think it is a product limitation in that in that option to list all values a user can filter by, it is not possible to display all the values from the different fact tables to which that column is mapped.
Has anyone else encountered this behaviour?

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.

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

How do i disable orientations for a specific view in my tab bar project without disabling for the other views?

How do i disable orientations for a specific view in my tab bar project without disabling for the other views?
Any suggestions?

Note that you can also hide the tab bar completely with code in the userChrome.css file.
Add code to the <b>userChrome.css</b> file below the default @namespace line.
*http://kb.mozillazine.org/userChrome.css
<pre><nowiki>@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); /* only needed once */
#TabsToolbar { display: none !important; }
</nowiki></pre>
The customization files userChrome.css (user interface) and userContent.css (websites) are located in the <b>chrome</b> folder in the Firefox profile folder.
*http://kb.mozillazine.org/Editing_configuration

Logical Column for calculation

Hi guru,
My requirement is we have to display report with Total count of Opportunities , Count new Oppty ( which are created with in 30days from today ) Count Old Opptys ( which are created more than 30days ago and Overdue ( which closed date is > current Date).
For this requirement I had created one logical column and I am getting error when ever I am using Timestampdiff.
Could you please let me know how can I create these 3 logical columns in Meta Data.
I am rally appreciate for your help.

Here is what you need to do:
1. Create a Session Variable in your RPD
2. Check the "Enable any user to set the value" checkbox in the Session Variable properties
3. In your dashboard prompt, select"Request Variable" in the Set Variable section
4. Enter the name of your Session Variable in the box that appears
5. Now you can reference the session variable in the formula of your logical column. Syntax: VALUEOF(NQ_SESSION.YOUR_SESSION_VARIABLE)
Note: You cannot reference Presentation Variables in the RPD
-Dave

How to disable the tab focusing for a JTextField object because those ...

Hi All,
Here I need some help. I want to disable the tab focusing( tab index) for a JTextField objects because those objects are set as setEditable(false). Also can u tell me about how to change the tab index orders for JTextFields.
Many thanks,
Vijaycanaan.

I want to disable the tab focusing( tab index) for a JTextField objectsLook through the API and find methods with the word "focus" in the method name.
Also can u tell me about how to change the tab index orders for JTextFields."How to Use the Focus Sub System":
http://java.sun.com/docs/books/tutorial/uiswing/misc/focus.html

How to create logical columns for current period and prior period

Hello all.
Is there any way in obiee to create a new logica column in BMM layer that says "CURRENT PERIOD" AND "PRIOR PERIOD" OR ONE SINGLE COLUMN THAT SAYS "PERIOD".
In those columns what I need is if it a current period column it shoould have 03/01/2012-03/31/2012 (this month date range)
and in prior period column I shouldhave 02/01/2012 -02/29/2012(which is previous month date range).These columns I will be using in my reports.
Please help me if we can create any such columns with these conditions/requirements

Hi,I have already created he dynamic variables.But I am not getting how to use those variables and create the new logical columns in bmm layer.
this is what I am trying
case when VALUEOF("Current Month begin date"."Current Month begin date") ='..' and VALUEOF("Current Month end date"."Current Month end date")
='..' then 'current period' end
I don't really understand what I should write case when VALUEOF("Current Month begin date"."Current Month begin date") ='..'??

Aggregation tab disabled for fx logical columns

Similar Messages

Maybe you are looking for