AGO function issue

Hello
Im trying to use the AGO function in in my Column Formula to compare the difference between month to month. The formula is as follows:
AGO("Fact - Revenue"."Revenue - DW","Period"."Period",1)
... but every time im getting the error message:
Formula syntax is invalid.
[nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 27037] Unresolved level: "Period"."Period". (HY000)
SQL Issued: SELECT AGO("Fact - Revenue"."Revenue - DW","Period"."Period",1) FROM "LC ELT - Revenue and Margin"
Not sure why this is. I have tried not inserting the 'time level' option which doesn't give me an error but does give me slightly incorrect results, just off the correct value.
Has anyone experienced this before? If so, could you please let me know what you did to resolve it?

The Ago syntax is
Ago(<<Measure>>, <<Level>>, <<Number of Periods>>)
I dont think "Period"."Period" is a level from time dimension.
In your case valid Levels are
- Year
- Half
- Quarter
Pls mark as correct/helpful if helps
Edited by: veeravalli on Nov 19, 2012 5:31 PM

Similar Messages

AGO function in OBIEE

Hi,
I am creating a new logical column on my fact table and would like to use time series function(AGO) to compare trends a month ago. I have a time dimension too.
I am using this expression defined in the new logical column properties:
Ago("HCBF"."Workflow Fact"."Total Case Handlers" , "HCBF"."Time"."Month of Year" , 1)
I get the following error message:
[nQSError: 27009] Unresolved identifier: "HCBF"."Time"."Month of Year".
The function expression appears to be fine, month of year is numeric and total case handlers is a count.
Can anybody help resolve this error message.
Thanks

Hi,
An issue remains with the AGO function in BI Answers, when I try to run a report in answers with the new column created in the fact table I get the following error in the log file:
Query Status: Query Failed: [nQSError: 22040] To use AGO function, the storage level of the query ('[Time.Dimension Key]') must be a static level.
I am selecting month name(Filtered on May 2010) and choosing fact measures(total cases, lastmonthcases). lastmonthcases is the new logical column created using AGO function.
Does this error look familiar, there is a time dimension key in the logical time dimension table but this is not referenced in the hierarchy.
Thanks

OBIEE 11g Ago Function

Hi All,
I am using ago function in Answers it works fine
But
when observing the data, data is mismatched at particular Product category, why because two category s (A,B)   has same subcategory name (Basic)
CAT       Sub Cat
A ------        Basic
A ------       Value Add
A ------       High
B -------     Basic
B ------       low
B ------     medium
My report has five columns like CM -1 , CM-2,CM-3,CM-4,CM-5 ,
when i was selecting cat A and subcat is Basic, Data as below ....
CM-1         CM-2     CM-3     CM -4    CM -5
A basic   A basic B basic B basic   A basic
if sub cat name is different no issue
Please help me.
Regards
Rm

You can create a compound key of Cat + SubCat (concatenation in a logical column is a quick win) which will render the SubCats unique and assign that as the logical level key:
SubCat:
A-Basic
A-Value Add
A-High
B-Basic

Level based measure and AGO function

Hi,
I've a TIME fact table with a single dimension (TIME_DIM) and a single measure (WORK_DAY).
WORK_DAY is 1 if the day is a working day, otherwise it is 0.
This way I can get the number of working days by month, quarter and year.
(TIME is a logical fact table. WORK_DAY is phsical stored inside the physical TIME_DIM).
To have WORK_DAY work correctly when used with others fact tables, I've defined it as a level based measure, where all the dimensions are set to the "total" level, apart TIME_DIM.
So far so good.
Then I created a new calculated measure WORK_DAY_PREVIOUS_YEAR.
I used the AGO function this way: AGO (TIME.WORK_DAY, TIME_HIERARCHY.YEAR, 1)
No complains by OBIEE, but this column always returns 1...
I've no trouble using level based measures.
I've no trouble using AGO.
But if I mix them together they no longer work.
Do you experience this issue? Any workaround?
I'm using OBIEE 11.1.1.5
Regards,
Corraod

What is the month level key column functionality in your time dimension?
it should be in format of yyyymm but not in just mm ..

TODATE and AGO function errors in OBIEE

I have aggregated time dimension. The time calendar comprises of the following structure with a physical table for each level in the Physical Layer -
Year -> Half Year -> Quarter -> Month -> Week -> Day
These tables form the calendar. The RPD works fine until I use the TODATE and AGO based fields in the query.
When I use the AGO and the TODATE time series function to generate the YTD and PY YTD calculations in the Business Modelling Layer. The system gives the following error on Answers -
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 22045] AGO function is used on a time dimension which is logically snowflaked. (HY000)
SQL Issued: SELECT "- Retail Calendar"."Year Identifier" saw_0, "- Sales"."Gallons Sold" saw_1, "- Sales"."Profit Amount" saw_2, "- Sales"."Sales Quantity" saw_3, "- Sales"."Retail Sales Amount" saw_4, "- Sales"."Licensee Sales Amount" saw_5, "- Sales"."% Retail Sales Amount" saw_6, "- Sales"."% Licensee Sales Amount" saw_7, "- Sales"."Store Average Profit" saw_8, "- Sales"."Sales Amount - Last Year" saw_9 FROM "Reporting Objects" ORDER BY saw_0
Let me know what I am doing incorrect here?
I have checked all the joins to see if the time calendar has been incorrectly joined, but I can't find anything. Please help.

Below are the physical tables involved -
Year - TIME_YEAR_DM
Half Year - TIME_HALF_DM
Quarter - TIME_QTR_DM
Month - TIME_MTH_DM
Week - TIME_WK_DM
Day - TIME_DAY_DM
Each of these tables has an Identifier key (for example, YR_IDNT, HALF_IDNT, QTR_IDNT, etc.) that uniquely identifies the rows. I am using these IDNT fields as my hierarchical keys.

Time series questions - how to do AGO function for prior year end

Question on how to perform the following calculation in OBIEE:
I need to create a time series calculation that will calculate a metric as of Dec prior year. For example, my users will select Mar 2010. I want to show the amount for Mar 10 as well as the amount for Dec 09. If the select Jun 10, I will show them the amount for that month as well as Dec 09.
Is there a way to do an AGO function that will give me this value? I can't use a filter calculation on my column because filter on the period will exclude these records

Thanks John. Your suggestions seems promising but I'm having issues when I tried it out. I am receiving the following error message:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 22046] To use AGO function, the query level ('Fiscal Period, Prior Fiscal Year End Date') must be a static level. (HY000)
What I did was create a new level off my Fiscal Time dimension which is a child of Total. I tried creating my AGO calculation using this level but received that error message in Asnwers. Any ideas on what I may be doing wrong?

OBIEE 11.1.1.7-Ago Function Error-[nQSError: 46008] Internal error: File server\Query\Optimizer\SmartScheduler\PhysicalRequestGenerator\Src\SQOSPMarkMultiTargetSupport.cpp

Hi All,
I was performing the steps mentioned in Oracle Tutorial"http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi11115/biadmin11g_02/biadmin11g.htm#t10"-BI RPD creation.
After Using the AGO function data in the Time series metric(Month Ago Revenue) was null always. I updated the DB features in RPD physical layers by selecting support for time series functions.
After that report started to fail with below error. Please let me know if its a bug and any option to fix it.
Thanks,
Sreekanth
Error
View Display Error
Odbc driver returned an error (SQLExecDirectW).
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: 46008] Internal error: File server\Query\Optimizer\SmartScheduler\PhysicalRequestGenerator\Src\SQOSPMarkMultiTargetSupport.cpp, line 1680. (HY000)
SQL Issued: SELECT 0 s_0, "Sample Sales"."Time"."Year-L1" s_1, "Sample Sales"."Revenue"."Ago-Year Revenue" s_2, "Sample Sales"."Revenue"."Revenue" s_3 FROM "Sample Sales" FETCH FIRST 65001 ROWS ONLY
Refresh

I know that there is no relation between "SampleApp Lite"."D3 Orders (Facts Attributes)"."Order Date", "SampleApp Lite"."D0 Time"."Calendar Date", it's also the same thing in my own RPD.
But as it's working with the 11.1.1.6.2 BP1 version I don't understand why it's not working with 11.1.1.6.9.
Implicit fact column is not set on my repository, but I don't have any request with only dimensional column, so if my understanding is correct I don't need to use it. Also, the problem appears during the check of the repository not in answers.
thanks anyway

Ago Function

Hi all
I upgraded from 10g to 11g and now my Ago function seems to not be working but i have no idea why.
The data is basically coming from a table like so:
AcctNbr EffDate Balance
12345 01/01/2010 $200
12345 01/02/2010 $205
12345 01/01/2011 $206
12345 01/02/2011 $207
So you can see that I have a balance amount for each day of the year.
So What I am trying to do is get the Year Ago amount.
I have this table joined to a basic time dimension table. Year > Quarter > Month > Week > Day.
In 10g I created a logical column using this and it worked fine:
AGO("LDW"."FA_ACCTBAL"."NOTEBAL", "LDW"."DimTime"."Year", 1)
In 11g I get no results. The log file says it my YAGO Measure is being converted to a null. (converted to NULL because its grain is below query's grain.)
SELECT s_0, s_1, s_2, s_3, s_4, s_5, s_6 FROM (
SELECT
0 s_0,
"LDW"."FA_ACCTBAL"."EFFDATE" s_1,
CASE WHEN "LDW"."FA_ACCTBAL"."MAJOR" ='CK' THEN 'Chequing'
WHEN "FA_ACCTBAL"."MAJOR" ='TD' THEN 'Term Deposit'
WHEN "FA_ACCTBAL"."MAJOR" ='SAV' THEN 'Savings'
WHEN "FA_ACCTBAL"."MAJOR" ='MTG' THEN 'Mortgage'
WHEN "FA_ACCTBAL"."MAJOR" ='CNS' THEN 'Consumer'
WHEN "FA_ACCTBAL"."MAJOR" ='CML' THEN 'Commercial' END s_2,
"LDW"."FA_ACCTBAL"."% Chg YAGO Notebal" s_3,
"LDW"."FA_ACCTBAL"."Chg YAGO Notebal" s_4,
"LDW"."FA_ACCTBAL"."NOTEBAL" s_5,
"LDW"."FA_ACCTBAL"."YAGO Notebal" s_6
FROM "LDW"
WHERE
((FA_ACCTBAL.MAJOR IN ('CML', 'CNS', 'MTG')) AND (((FA_ACCTBAL.EFFDATE IN (current_date-1)) OR (FA_ACCTBAL.EFFDATE IN (current_date-366)))))
) djm ORDER BY 1, 3 ASC NULLS LAST
[2011-03-23T21:51:55.000+00:00] [OracleBIServerComponent] [TRACE:7] [USER-23] [] [ecid: 0000Iv^gxcn99hWjLxMMOA1DX^y9000GDt] [tid: 1b6c] [requestid: 5df40012] [sessionid: 5df40000] [username: Administrator] -------------------- General Query Info: [[
[2011-03-23T21:51:55.000+00:00] [OracleBIServerComponent] [TRACE:7] [USER-52] [] [ecid: 0000Iv^gxcn99hWjLxMMOA1DX^y9000GDt] [tid: 1b6c] [requestid: 5df40012] [sessionid: 5df40000] [username: Administrator] -------------------- Expression 'Ago(NOTEBAL:[DAggr(FA_ACCTBAL.NOTEBAL)], [Level Year], 1)' converted to NULL because its grain is below query's grain.
[2011-03-23T21:51:55.000+00:00] [OracleBIServerComponent] [TRACE:7] [USER-52] [] [ecid: 0000Iv^gxcn99hWjLxMMOA1DX^y9000GDt] [tid: 1b6c] [requestid: 5df40012] [sessionid: 5df40000] [username: Administrator] -------------------- Expression 'Ago(NOTEBAL:[DAggr(FA_ACCTBAL.NOTEBAL)], [Level Year], 1)' converted to NULL because its grain is below query's grain.
[2011-03-23T21:51:55.000+00:00] [OracleBIServerComponent] [TRACE:7] [USER-52] [] [ecid: 0000Iv^gxcn99hWjLxMMOA1DX^y9000GDt] [tid: 1b6c] [requestid: 5df40012] [sessionid: 5df40000] [username: Administrator] -------------------- Expression 'Ago(NOTEBAL:[DAggr(FA_ACCTBAL.NOTEBAL)], [Level Year], 1)' converted to NULL because its grain is below query's grain.
[2011-03-23T21:51:55.000+00:00] [OracleBIServerComponent] [TRACE:7] [USER-52] [] [ecid: 0000Iv^gxcn99hWjLxMMOA1DX^y9000GDt] [tid: 1b6c] [requestid: 5df40012] [sessionid: 5df40000] [username: Administrator] -------------------- Expression 'Ago(NOTEBAL:[DAggr(FA_ACCTBAL.NOTEBAL)], [Level Year], 1)' converted to NULL because its grain is below query's grain.
[2011-03-23T21:51:55.000+00:00] [OracleBIServerComponent] [TRACE:7] [USER-52] [] [ecid: 0000Iv^gxcn99hWjLxMMOA1DX^y9000GDt] [tid: 1b6c] [requestid: 5df40012] [sessionid: 5df40000] [username: Administrator] -------------------- Expression 'Ago(NOTEBAL:[DAggr(FA_ACCTBAL.NOTEBAL)], [Level Year], 1)' converted to NULL because its grain is below query's grain.
[2011-03-23T21:51:55.000+00:00] [OracleBIServerComponent] [TRACE:7] [USER-52] [] [ecid: 0000Iv^gxcn99hWjLxMMOA1DX^y9000GDt] [tid: 1b6c] [requestid: 5df40012] [sessionid: 5df40000] [username: Administrator] -------------------- Expression 'Ago(NOTEBAL:[DAggr(FA_ACCTBAL.NOTEBAL)], [Level Year], 1)' converted to NULL because its grain is below query's grain.
Any idea what has happened here?

Hi,
I'm facing the same issue. Did you find a solution for this problem?
Thx
Jan

Ago function not working properly with time dimension

Hi all,
In OBIEE 11g we have the following issue:
We have a fact which contains transaction's sum for the last day of each month.
We use ago function like this : ago(<fact.column>,1)When we want to see the result from the time hierarchy the fact with the ago function works properly for quarters and half years but for the months shorter than the previous one can't take the right value /equals to NULL/.
For example :
sum for YEAR: 10000
sum for Half Year 1 : 4000
sum for Half Year 2 : 6000
sum for Quarter 1: 1000
sum for Quarter 2: 3000
sum for Quarter 3: 2000
sum for Quarter 4: 4000
sum for month... - here the ago function is confused with the last day of previous month if it's shorter than itself: For example - for march it cannot take value for end of February ..etc.
Any ideas?
Thanks in advance,
Alexander.

Hi,
I faced some issues previously with month, so I used month+year as id instead of month id. Instead of tragging month id 1-12 into your hierarchy, create another column into your table like month+year - 201201, 201202 which creates unique month_year_id and drag this column into month level instead of month_id. So the problem might be solved.
Regards,
Anitha.B

Ago function not working in reports

Hi
I created a logical column using ago function,when I'm using this column in the report it throws the following error.I'm using 10.1.3.4.1 version of OBIEE.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 22040] To use AGO function, the storage level of the query ('[TIMES.TIME_ID]') must be a static level. (HY000)
SQL Issued: SELECT COUNTRIES.COUNTRY_NAME saw_0, SALES.AMOUNT_SOLD saw_1, SALES."Amount Sold LY" saw_2 FROM KNOWLEDGE WHERE (TIMES.CALENDAR_YEAR = 1999) ORDER BY saw_0
Thanks
Don.

Hello Don,
Have you set the chronological key for the time dimension ?
Please refer the below post by Nico..
http://gerardnico.com/wiki/dat/obiee/function_time?s[]=ago&s[]=function
Same error it has been posted in below mentioned thread
Re: Using the Ago Function
One Request : Please if your post has been answered then please try to close the thread by awarding so that it can be helpful to others.
thanks
Edited by: user12116294 on Feb 4, 2011 5:18 PM
Edited by: user12116294 on Feb 4, 2011 5:20 PM

Last argument in AGO function

Hi Everyone...
Hope everyone is good .
So we have this requirement where user want to see selected quarter last month, then previous quarter last month and previous year last month based on Year and Quarter selection. for example.
Prompts: Year - 2013; Quarter - Q2
Selected Month (1)
Last Qtr Last Month (2)
Diff of 1 - 2
Last Yr Last Month (3)
Diff of 1 - 3
Country
Jun-13
Mar-13
Qtr Diff
Dec-12
Yr Diff
USA
1000
500
500
700
300
UK
1500
900
600
1200
300
Now if user select Quarter as Q3 then report will show:
Selected Month (1) - Sep-13
Last Qtr Last Month (2) - Jun-13
Last Yr Last Month (3)- Dec-12
So the idea is to take always last month of selected last month, last qtr last month and last yr last month.
Now I am using AGO function to get the Last Yr Last Month (3) where I need to pass the last argument as a dynamic value.
AGO("measure","month","month Number")
But OBIEE say that the last argument should be a consistent integer. So is there any way where we can pass dynamic value of "Number of Period". For example
for Q1 : AGO("measure","month",3)
for Q2 : AGO("measure","month",6)
for Q3 : AGO("measure","month",9)
for Q4 : AGO("measure","month",12)
I can use CASE statement for this but will it not create performance issue, just curious?
Please help me if we can do this in this way or can you please suggest me any other way to do this.
Thanks,
Suhel Dayer

Any thoughts here.... Need help..
Appreciate your time and efforts.
Thanks....
Suhel

LAST Aggregation and AGO Function in OBI Administration Tool

I'm struggling a bit with the AGO function and LAST aggregation. The problem is when I try to compare balance from the last day from last month compared with last day of this month.
To get the balance of the last day of this month, I'm using based on dimensions LAST aggregation in the logical column KNSALDOPROMEDIOlast (avg balance).
KNSALDOPROMEDIOlast:
Dimension Formula
Other SUM(BWM.DWH_FTASA.KNSALDOPROMEDIOlast)
DTIEMPO_Dim LAST(BWM.DWH_FTASA.KNSALDOPROMEDIOlast)
To get the last day of last month I’m using the existing logical colum KNSALDOPROMEDIOlast applying the AGO function over the time dimension Month -1.
KNSALDOPROMEDIOlast-1:
AGO(BWM.DWH_FTASA.KNSALDOPROMEDIOlast, BWM.DTIEMPO_Dim.MES_Dim,1).
The problem is when the last month has more days than the current month.
Example:
Month     Last Day     KNSALDOPROMEDIOlast     KNSALDOPROMEDIOlast-1
JAN 2010     JAN 31     437,880,393     0
FEB 2010     FEB 28     484,804,165     442,880,934
MAR 2010     MAR 31     562,201,480     484,804,165
APR 2010     APR 30     583,255,351     570,661,690
MAY 2010     MAY 31     663,660,138     583,255,351
1. The balance of last day of previous month of February is 442,880,93, is wrong this amount, is from Jan 28th, the real is 437,880,393 from last day of January, Jan 31st. January has more days than February.
2. The balance of last day of previous month of March is 484,804,165, is correct this amount is from last day of February, Feb 28th. March has less days than February.
3. The balance of last day of previous month of April is 570,661,690, is wrong this amount, is from mar 30th, the real is 562,201,480 from last day of March, Mar 31st. March has more days than April.
4. The balance of last day of previous month of May is 583,255,351, is correct this amount is from last day of April, Apr 30th. April has less days than May.
Edited by: user10541559 on Aug 18, 2010 1:44 PM

Hi,
I'm not sure about your issue.
The aggregation option "LAST" is used when you need the last value, the most typical example of this is inventory, if you want the inventory quantity of a product in a month, you don't sum the value for each day in the month, you only get the value of the inventory in the last day of required month, right?
Have you tried using session variables?
You can get the last day of the last month from Oracle DB with the function "LAST_DAY". For example:
SELECT LAST_DAY(ADD_MONTHS(CURRENT_DATE, -1)) from DUAL
I know that is not exactly what you need, but I hope I gave you an idea what other things you can try.
Regards,
Jorge.

Ago Function gives NULL values

Friends,
I need help regarding Ago function available at column level in BMM.
I am not at all receiving any error. Unfortunately after Ago function implementation i am getting NULL values for that particular column.
Here are my implementation steps for getting "Month Ago" values for "Amout column" in Sales table.
1. i have created Time dimension hieararchy.
It is like this - Year - > Quarter - > Month - > Actual Date
2. Defining Keys and making them chronological are also done.
3. Actual Date is the PK and joins with my Fact.
4. "Amount" Column in Fact is set to 'Sum'.
5. i created a new column named " Amount Month Ago" and set following logic to its expression builder.
Ago("AR Reserve"."Fact - AR Reserve Calc Dtl"."Amount" , "AR Reserve"."Dim - TimeDim"."Month" , 1)
I have not received any error.
Once i pull this new column (Amont Month Ago) into the presentation layer and try to create a Tabular report. It is not showing any value. Other column values are OK as expected.
I know i am missing something important here.
Requesting you all to guide me. I am working on OBIEE 10g.

Hi,
Hitting a 'NULL' value in the report hints me of some issues with the Hierarchy/Content setup of the LTS. I suggest you to enable level 7 log and see if the AGO(<measure>) is being nullified by the BI Server due to incompatible facts.
If it is, then you got to revisit your Period hierarchy and content settings in the Fact LTS. Some generic suggestions are,
1. Create hierarchies for all dimensions available.
2. Set the granularity of the sources in the fact to all available hierarchies.
Hope this helps.
Thank you,
Dhar

AGO Function doesn't use full previous period

Hi,
I am using ago function in obiee 11.1.1.6. If my current period is April, AGO (quantity, MONTH, 1) only returns the data from 1 to 30th of March and not the full month. Seems it's trying to match the number of days in the current month and uses the same number of days in the previous month. Is this the known issue? Is there any workaround? I want full month data for the previous month using AGO function.
TIA

HI,
Obviously it must use all the dates from the previous months, just check with dimension hierarchy you created.
Take a look @ this mkashu.blospot.com/2013/08/obiee-model-time-series-in-obiee.html
Regards,
VG

Error on AGO function

I'm using AGO function to calcuate the Month ago value of the fact. But I get following error:
[nQSError: 14026] Unable to navigate requested expression: Ago(Proforma Usage:[DAggr(Pro Ancillary Usage and Revenue Monthly Fact.Proforma Usage by [ Period.Month Name, Period.Year] )], [Level Month], 1). Please fix the metadata consistency warnings. (HY000)
The Period dimension is joined with the fact at month level. there are no metdata consistency warnings in the repository.
I have another fact in the same Subejct area joining similarly to the dimensions and hte AGO function works fine there. I can not figure what I'm doing wrong that I'm getting this error.

I was abel to fix this issue on my own. I needed to set the Chronological Key for the Time dimension. Once that was set, the error was gone.

AGO function issue

Similar Messages

Maybe you are looking for