AGO function problem 10.1.3.4

Hi,
Anyone have any suggestions on this please???
Still hoping for suggestions from anyone who has had similar problem with AGO function yielding strange results at certain levels of hierarchy??
I have a facts folder with both AGO and 'regular' columns of data.
I create a simple query with filters on period name and expense type.
When I add 'regular' columns (default aggregate SUM) - it works okay.
I then remove all 'regular' facts columns.
When I add AGO based columns - it works fine.
When I try any combination of AGO and 'regular' suddenly a lot of my data disappears.
I have tried experimenting with report based totals off and setting the function aggregation to SUM for the AGO columns, but nothing works.
i.e. AGO is pointing at previous period, so I have Yr, Qtr, Period in my time dimension and the AGO is linked to Period level (like a calendar month, but financial) and the AGO is -1.
Filter is on period name - so for example "PERIOD NAME" is equal to / is in 'NOV-11'
Any suggestions please??
thanks,
Robert.
Edited by: Robert Angel on 08-Dec-2011 06:02 to clarify ago usage
Further information; -
I have just discovered that this strange behaviour only manifests when the 2nd segment of our five segment chart of accounts structure is present.
I have checked the properties of this field and can see nothing strange, when compared to its (working) peers.
Could it be a problem related to the dimension hierarchy that is associated with this chart of accounts dimension>??
thanks for your input,
Robert.
Edited by: Robert Angel on 08-Dec-2011 07:30 additional detail
Edited by: Robert Angel on 12-Dec-2011 07:33
Edited by: Robert Angel on 19-Dec-2011 08:07

To explain the structure first; -
Chart of Accounts Dimension
Trust Id
Cost Centre
Expense Type
Sub Expense Type
External Organisation
Each level of the hierarchy is from the same phyical table 'Chart of Accounts'. The dimension references the underlying field as the Key at each level.
Financial Periods Dimension
Year
Quarter
Period
Again all are from the same physical table, again all use the underlying field as the key at each level.
FACTS table has; -
Actual in Month, Budget In Month, Month Ago Actual in Month
Working scenario ; -
Add; -
Cost Centre, Actual in Month, Budget In Month, Month Ago Actual in Month
Filter on period_name = 'NOV-11'
Cost Centre in ('801040','801041')
results; - (works fine!)
Cost Centre, Actual in Month, Budget In Month, Month Ago Actual in Month
801040                 50000          65000                    55000
801041                 15000          18000                    19000To the above scenario I can add any of the other Chart of accounts segments and it works.
When I add Expense Type I get
Cost Centre,   Expense Type, Actual in Month, Budget In Month, Month Ago Actual in Month
801040                3001                    50000          65000                   55000i.e. I still get results, but less cost centres than I had when only cost centre was included.... all other things being equal??!!
I can workaround this by pulling my concatenated version of all codes to get the full chart of account 'string' and then use substring to pull expense type only out of it, but this is less than ideal to suggest to a user community when it should work as is...
Anyone seen anything like this before, can give me anything to investigate that might be making the difference??
Edited by: Robert Angel on 13-Dec-2011 02:20
Edited by: Robert Angel on 14-Dec-2011 08:28

Similar Messages

  • OBIEE AGO function Problem

    Hi all,
    What a funny attitude in OBIEE11g.
    when i apply the following script in OBIEE11g then it work
    AGO("myFact.rev", "Time"."TimeHierarchy - QUARTER"."MONTH", MONTH(CURRENT_DATE))
    but the following is not working,
    AGO("myFact.rev", "Time"."TimeHierarchy - QUARTER"."MONTH", MONTH("Time"."Month Ending Date"))
    --need help                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

    Hi,
    check both "TimeHierarchy - QUARTER"."MONTH" and "Time"."Month Ending Date" might be from same time dimension.
    I think you can't use time hirarchy columns more than once in ago or todate functions. BI server might be confused because both the columns.
    otherwise I have no idea . you may create a variable and use as an alternate solution.
    Thanks
    Jay.

  • Problem using Ago function

    Hi all,
    My problem is that when i use ago function it displays next months value for example first column shows balance of april month and next to it ago column displays balance of the may not march. I am really confused. Please help,
    AGO(SR02BriefIncome.sr02_cube.BALANCE, SR02BriefIncome.timesDim."times Detail", 1);

    Hi Nico,
    Another question in relation to Ago function; I need to get value/balance a year ago which is 12 months ago, and also previous year's last months balances; the problem is that Ago function takes only integer, I have tried to put a variable, Is there is way i can get balances of the previous year's last month because it will be much easier to get it using built-in ago function.
    Also i need help with your answer for thread How to use row values in Presentation or Administration for calculation
    Re: How to use row values in Presentation or Administration for calculation
    "Yes, I forgot this one. Of course, this solution work when you have a pivot column.
    If you talk about period to period comparison, really often I must do a share like this one : ($2-$5)/$5.
    And unfortunately, this is not possible in a calculated item. Is it ?"
    We have a lot of reports with inter-row calculations, we have already used a lot sql model but we would like use answer also. Can u explain it with exact examples or steps.
    thank you again,

  • Problem with AGO function in OBIEE

    Hi I am new to OBIEE,
    I am working on Trend Analysis of ETL Mappings,
    I am using AGO Function to get the Previous day Elapse Time of a mapping but while generating the report its behaving in a strange way.
    like
    AGO("BI Performance"."Map Val Fact"."Elapse Time Minutes","BI Performance".ETLStartDim."Day",1) -- Day Ago Elapse time
    AGO("BI Performance"."Map Val Fact"."Elapse Time Minutes","BI Performance".ETLStartDim."Day",2) -- Two Day Ago Elapse time
    For example, in database there is date like
    Date Elapse Time
    2nd June 10 min
    1st June 11 min
    30th may 10 min
    My date in Report should be like
    Date Elapse Time Day Ago Elapse Time Two Day Ago Elapse Time
    2nd June 10 11 10
    But the date coming over here is
    Date Elapse Time Day Ago Elapse Time Two Day Ago Elapse Time
    2nd June 10
    3rd June 10
    4th June 10
    So if any one could help me out of this, it would of great help.
    With Regards
    Chaitanya

    This is posted to the incorrect forum. Please post to an OBIEE forum.

  • Nested Ago and Todate function problem

    Hi,
    in my rpd i have following Time hierarchy:
    Year
    Quarter
    Month
    and a fact table Fact Shop which contains Monthly measure "Number of Hearing Aids Delivered".
    I must calculate PY_QTD, PY_YTD versions of above measure.
    I have tried to use built-in Time Functions Ago and ToDate in the following way:
    PY_QTD
    Todate(Ago("Number of Hearing Aids Delivered",1,"Time.Year"), "Time.Quarter")
    PY_YTD
    Todate(Ago("Number of Hearing Aids Delivered",1,"Time.Year"), "Time.Year")
    but when i check consistency i have error which says approximately "You can nest Ago and ToDate functions".
    There's another way, to calculate it? Can you help?
    Thanks
    Giancarlo

    So u r referring PY as previous year ;)
    Here u go;
    it’s a combination of AGO and TODATE.
    You create a value – let’s say Sales MTD by just following normal process…then you create a logical column with the following formula AGO (Sales MTD, Month Dim, 12)
    that should give you a MTD measure you’re looking for. I hope this is useful. Just dont use both function in single logical column....use seperate by first creating YTD n then AGO function to create previous year data.
    For ur case use to calculate PY_YTD use below:
    Create logical column
    Aids Delivered YTD with formula as TODATE("Number of Hearing Aids Delivered"), "Time.Year")
    and then create another logical column as
    Aids Delivered PY_YTD with formula as AGO("Aids Delivered YTD","Time.Year",1)
    This will work for sure....

  • 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 with two dates

    I use OBIEE and I got some difficulties with the times dimensions and the function AGO because I used two differents dates for my measure.
    My fact table:
    Ordered ||Delivered||Amount
    12/21/2008 ||1/20/2009||30000
    1/1/2009 ||2/1/2009 ||20000
    1/1/2009 ||3/1/2009 ||10000
    2/1/2009 ||2/1/2009 ||50000
    2/1/2009 ||3/1/2009 ||50000
    12/25/2009||1/15/2010||10000
    1/1/2010 ||2/1/2010 ||25000
    1/1/2010 ||3/1/2010 ||20000
    1/1/2010 ||2/1/2010 ||20000
    1/1/2010 ||3/1/2010 ||15000
    I have two Times Dimensions (Ordered Times AND Delivered Times) and one fact table. I already tried with 2 facts table and 1 time table without success too cause they not link the value for delivered and ordered
    I want to compare the delivered situation (Amount Qty) for the same ordered day last year
    I created a prompt with a date (ex.: Ordered date <=1/1/2010 AND Delivered date >=1/1/2010) and I want to compare one year ago with 1/1/2009 (Ordered Date situation…)
    I wish the results below:
    Delivered Month||Amount||Previous Amount Year Ago
    1 || 10000 || 30000
    2 || 45000 || 20000
    3 || 35000 || 10000
    I got some problem cause I had the 100 000 in my previous year (Ago) and I don’t want it because it was ordered after 1/1/2009 (Previous year). I know that the ago function concerns the Sum of Amount by Delivered Date, Year -1 ...
    Does somebody has a solution for this ? Thank you

    Hi,
    The problem is that I only know the offset values at row level, i.e., when I run my answer report some records use a certain offset value (offset1) while others use another offset value (offset2)
    The offset value can be determinate by a logical column.
    Is it possible?
    Thanks.

  • 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

  • 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.

  • Todate and AGO function in both Fiscal yer and Calendat year

    I want to create report having column with Todate and ago function formulas. I have to display the facts both in fiscal year and calendar year... how to do this? What value shall i choose in the content tab for the time dimension in this case? My fact table has values for each day...
    I am able to display only columns with fiscal year in time series function with timeDim.fiscal_year... similarly only calendar year with time seriese with calendar year columns... In my hierarchy, I have two branches for Time Dim...one is Fiscal and other is Calendar... and they both are at same level
    Help!

    I have an answer for you...Since you have a correctly defined time dimension (with branches - Fiscal Year->Fiscal Qtr ->Fiscal Month->Fiscal Week and Calendar Year->Cal Qtr->Cal Month->Cal Week->Cal that I assume have the common Child level - Day...) - you should have no problem building time-series logical columns
    In TODATE and AGO you must use relevant Time Dim Level - for example:
    AGO (Column, TimeDim.FiscalYear, 1) = would give you data for previous fiscal year
    AGO (Column, TimeDim.CalYear, 1) = would give you data for previous calendar year
    same goes for qtrs, months, weeks
    If you want to take it to the lowest level Day - it won't matter if you pick Fiscal or Calendar since it's essentially the same.
    I hope this is helpful

  • Proper use of AGO function

    Dear All,
    I have to report on cubes that have their data aggregated on the day level. Standard reporting works fine. Now I want to do some historic comparison. I therefore created some calculation columns in Administrator, e.g.
    AGO(fact, dim_time.month,1)
    which shall give me the value of the fact just one month (and quarter and year in other columns) ago. If I report this on a daily basis, e.g day, fact, fact_month_ago I can see the report and calculation is correct, fact_month_ago is exactly the sam as fact from one month ago.
    But now I start to aggregate such a report to the month level (in Answers). So the report is month, fact, fact_month_ago. Now, some months are correct some are different. Looking deeper into this I assume this belongs to the number of days in a month. February has 28 days, so in the monthly report 28 lines are aggregated, even for the fact_month_ago table.
    In this case month_ago is January, which has 31 days, but 29 to 31 are not aggregated, as the report goes only from feb 1st to feb 28th.
    In the end the sum of the month_ago calculation is unequal to the sum of the last month.
    Does this mean I cannot use AGO function to calcualte things like that, or is there any trick or other function that would help here ?
    Regards,
    Knut

    You can have problem if you are going in a lower level such as week or date but if you stay on the month level, normally you must have the good result.
    Check here to have an example of this problem:
    http://obiee101.blogspot.com/2009/01/obiee-leap-year-challenge.html
    Otherwise, check your set up:
    http://gerardnico.com/wiki/dat/obiee/bi_server/design/dimension/time_dimension_parameters_for_ago_and_td_functions#timecalender_dimension_design_verification
    See each punt that are listed under the paragraph Time/Calender Dimension Design Verification. A good time dimension is the key for a good result with the time series function.
    Cheers
    Nico

  • AGO function error in Pivot Table

    Hi,
    I have a typical time dimension - year, period, week, date. Most of my facts are available at the most detailed level of date however I have some Budget facts that are only available at the week level. When I combine these facts in a report I am having the below problem.
    I use an ago function at the yearweek level ( I needed this so that I can compare week numbers as oppposed to week date ranges which is how the year ago function works - I believe).
    If I have a total on year in my pivot table I get the below error -
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 22036] Level in AGO function (YearWeek) must be a rollup of (or equivalent to) the measure level (Year). (HY000)
    Has anyone come across this before ?
    Thanks
    Patricia

    I am getting the following error message, not sure how to get rid of this.
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 22036] Level in AGO function (Fiscal Period) must be a rollup of (or equivalent to) the measure level (Fiscal Year). (HY000)
    SQL Issued: SELECT "GL Calendar"."Fiscal Period" saw_0, "Project Manager"."Project Manager Name" saw_1, Project."Project Number" saw_2, Project."Business Area" saw_3, Project."Business Unit" saw_4, Project."Delivery Ownership" saw_5, Project.Programme saw_6, "Fact - Project Cost".Cost saw_7, "Ago Measures"."MAGO Cost" saw_8, "Fact - Project Cost".Cost-"Ago Measures"."MAGO Cost" saw_9, REPORT_SUM(saw_7 BY ), REPORT_SUM(saw_8 BY ), AGGREGATE(saw_9 BY ) FROM "Project - Cost" WHERE ("GL Calendar"."Fiscal Year" = '2011') ORDER BY saw_0, saw_1, saw_2, saw_3, saw_4, saw_5, saw_6

  • OBIEE 10g AGO Function Dynamically Change the Heading

    I created columns in my rpd named Sales Previous Month, Sales 2 months ago and Sales 3 months ago using the AGO Function. This is working fine.
    My problem is when displaying these headings the users would like to see the Month Name instead of the Headings I created. For example if looking at a report for January the users would like to see:
    Sales Previous Month = December
    Sales 2 Months ago = November
    Sales 3 Months ago = October
    Is there any way to dynamically change the value of the column header to show the name of the month?

    Hi SriniVEERAVALLI,
    Thanks for the reply. I have found that I might haven't created the relationship between dimension and fact tables correctly.
    I initially created the foreign key relationship (instead of creating complex join) in physical diagram between the dimension and fact table. And the relationship type is hence greyed out.
    I have deleted the foreign key relationship in physical diagram. Then
    1. In physical diagram, create complex join between dimension and fact . The relationship is 'inner' and can't be changed.
    2. In Logical table diagram, create foreign key between dimension and fact . The relationship can be changed (inner, outer, etc).
    Is this the correct way?
    I tried these on two newly created dummy tables and it worked.

  • Any alternative to ago function

    Hello,
    I am using obiee 11g.Trying to use ago function at quarter level with the date prompts as filter
    instead of year prompt but somehow the data is not matching properly.
    Would like to know if there is any alternative to ago function?
    I just want to calcultate the count(distinct(id)) for current and previous quarter,where the report gets filtered by date fields.
    The report has user column,quarter column and the currrentcount and previous count.
    like
    user1->Q1->10->19
    user1->Q2->20->10
    User3->Q1->11->26
    Any help on this please?
    Thanks

    Hello,
    Thanks for reply.
    Is the grain below quarter level?
    ------> Calc date is below quarter level in the time dimension,Time dimesnion has FS Year(level1)->FS Quarter(level2)->Cal Date and Time key(Time key is the primary key with the combination of cal date and the pk of some other table (level3))
    Does quarter exists as a field in your date dimension?
    --------->Yes Fs Quarter is a field/column in the table and in the dimension
    check if quarter is a chronological key, does your quarter contain year in it(2011-02)?
    -------->In each level i have key defined, also in the FS Quarter i have.
    In the level3 i have both the key defined as key but cal_date as pk.
    Yes, Data of the qtarter is in the form 2012-01.
    Do you have quarter in your report, without date field?
    --------->yes, the report has FS_qtr,count for current qtr,count for previous qtr using ago function
    and the filter used is cal_date>='01-JUN-11'
    facts->
    There is a view in the database which is being created for time dimesnion.
    The view has
    FS_Year , FS_Qtr , Calc_Date ,Cal_month , cal_qtr, TimeKey(PK) , Pk_from someother_table_acting_as_fk.
    Please let me know where i am going wrong?
    One more thing i would like to add if i use the filter as FS_YEAR>=2011 then the counts comes perfectly.Problem is with cal date field.Just not bale to understnd where i am i going wrong?
    Please help
    Thanks
    Edited by: user123 on Feb 10, 2012 11:00 AM

Maybe you are looking for