Obiee essbase time series calc todate returns 0

1) when I enter todate in answers column formula I alwaus get systen error on time level? Works fine in rpd.
2) My period dimension is Dec through Jan. What is the current month when I use todate()
3) I'm trying to do a year to date calc based on a substition variable any suggestions?

Does a month have always the same number of week and begin with the first day of a week ?
If it's not the case, your dimension is not good when you make a report on the week grain for a year ago for instance.
Here a check list:
http://gerardnico.com/wiki/dat/obiee/ago_todate_configuration#timecalender_dimension_design_verification
Success
Nico

Similar Messages

YTD, MTD, YAGO, Function (Time-series Functions TODATE, AGO) Like OBIEE

Dear BO Gurus,
I am a newbie to business object. I would like to ask are there any ready made time series functions which can be used in the BO Semantic layer (universe).
Like Year to Date, Year Ago. Functions like TODATE and AGO functions found in OBIEE semantic layer (siebel analytics). It was just simple there, I had to use the function on the semantic layer and BI server would raise the query to get the answer.
The syntax was
Todate(measure, time_dim_attribute)
Ago(measure, Time_Dim_Attribute, period)
Thanks & Regards
Ishaq

Dear Gurus,
There is no DB function in oracle to do this (AGO/TODATE).
OBIEE issues time-series queries, in the form of AGO and TODATE. AGO gives you, for example, the value of sales one month ago or one quarter ago, whilst TODATE gives you the total of sales month-to-date, or quarter-to-date, or year-to-date. Both of these time-series functions rely on the existence of a time dimension in your business model and mapping layer, with the period you can refer to in the AGO and TODATE functions being determined by what levels you have in this time dimension.
This eliminates the need to create and store complex time-based
reporting tables.
I would only like to know does the universe designer has this sort of functionality which is present in OBIEE semantic layer. Or I need to create and store time-based reporting tables.
The question can best be answered by some-one has worked on both the BI platforms (OBIEE and BO).
Thanks & Regards
Ishaq

Time series function TODATE is VERY slow

While creating a report with data at different aggregation levels I run into serious performance problems. The situation is as follows. The datamart consists of a basic star with one fact table, containg sales amounts and three dimensions:
- Product
- Store
- Time
Dimension Time has a hierarchy: BookYear --> Period --> Week
I created a measure: "MyModel"."T_SALES"."SalesAmount"
I also created a derived measure to calculate the sales as a year to date. In this case for period this is a week to period measure (week is the lowest time level) PeriodSalesWtD: TODATE( "MyModel"."T_SALES"."SalesAmount", "MyModel"."Dim_Time"."BookPeriod")
This query is VERY slow.
In Oracle Answers I select only one week (200806) for which I want to see the SalesAmount for:
- that week
- the period that week is in up to that week (200802)
- the year that week is in up to that week (2008)
- Only a specific product group number (3). Otherwise the query won't ever return...
OBIEE issues the following queries to the database:
Query 1:
     select T2392.DEPBKWK as c3,
     T2392.DEPBKJR as c4,
     T2392.DEPBKPR as c5
     from
     W_TIJDDIM T2392
     order by c4, c3
This query reads all records from the time dimension table, columns week, year and period. I do not understand why it does not filter on the weeknumber (200806).
Query 2:
     select T2313.DEVRIWD as c1,
     T2313.TIJDKEY as c5
     from
     W_ARTDIM T2032,
     W_OMZWEEK T2313
     where ( T2032.DEIKANR = 3 and T2032.ARTKEY = T2313.ARTKEY )
     order by c5
This returns per time dimension key (c5) all SalesAmounts (c1). I do not understand why this is not aggregated nor filtered on the requested weeknumber.
Query 3:
     select T2392.TIJDKEY as c3,
     T2392.DEPBKJR as c4,
     T2392.DEPBKWK as c5
     from
     W_TIJDDIM T2392
     order by c4, c5
This query reads all records from the time dimension table, just like query 1, but now key, year and week. I do not understand why it does not filter on the weeknumber (200806).
Query 4:
     select T2392.DEPBKPR as c3,
     T2392.DEPBKWK as c4,
     T2392.DEPBKJR as c5
     from
     W_TIJDDIM T2392
     order by c3, c4
Once more the time dimension is read, but this time the columns period, week and year. Cannot see why the time dimension is queried three times.
Query 5:
     select T2313.DEVRIWD as c1,
     T2313.TIJDKEY as c5
     from
     W_OMZWEEK T2313,
     W_ARTDIM T2032
     where ( T2032.DEIKANR = 3 and T2032.ARTKEY = T2313.ARTKEY )
     order by c5
Gets SalesAmounts (not aggregated, why?) per time key.
Query 6:
     select T2392.TIJDKEY as c3,
     T2392.DEPBKPR as c4,
     T2392.DEPBKWK as c5
     from
     W_TIJDDIM T2392
     order by c4, c5
Again the time dimension is read completely, now returning time key, period and week.
Query 7:
     select sum(T2313.DEVRIWD) as c1,
     T2392.DEPBKWK as c2,
     T2392.DEPBKPR as c3,
     T2392.DEPBKJR as c4,
     T2392.DEPBKWK * -1 as c5,
     T2392.DEPBKPR * -1 as c6,
     T2392.DEPBKJR * -1 as c7
     from
     W_ARTDIM T2032,
     W_TIJDDIM T2392,
     W_OMZWEEK T2313
     where ( T2032.DEIKANR = 3 and T2392.DEPBKWK = 200806 and T2032.ARTKEY = T2313.ARTKEY and T2313.TIJDKEY = T2392.TIJDKEY )
     group by T2392.DEPBKWK * -1, T2392.DEPBKPR * -1, T2392.DEPBKJR * -1, T2392.DEPBKWK, T2392.DEPBKPR, T2392.DEPBKJR
     order by c2
Overlooking all of these queries, I can understand why this is slow, but what to do about it??? Any help will be appreciated.
Message was edited by:
Paul Laman

There are examples of this in the OBIA applications. What you need to do is to do a range join to the time dimension ie txn_date between first_day_of_year and the report_Date. However you need to map along every level of the time dimension since a query request at a higher level will not return correct results by mapping to the base table always. Hence you need to map day - month - qtr - year as separate Logical table sources.

OBIEE 11g Time Series Function

Hi All,
I am trying to compare this year to date sales to last year to date sales and this code is not working:
TODATE(<Measure>,<Time_Level>) For bellow syntax we are getting an error Formula syntax is invalid.
TODATE("Fact - Sales Order Lines"."Net Ordered Amount", "Time"."Enterprise Year").
Is the above example wrong?. Please provide one example for Time level value.
Actually what should be the value for second parameter (Level)
Thanks in advance.

Hi,
What error are u getting? make sure year hierarchy level on u r time dimension and then test it
example: (via bmm)
ToDate("Subject area"."Presentation table"."measure Column", "Subject area"."Time dim table name"."year dimensional hierarchy" )
ToDate("Sample"."Fact_ICA"."Sales_Amt", "Sample"."Period"."Year" )
<<Measure>> represents the logical measure column from which you want to derive. In this example, you would select the measure "Dollars" from your existing logical fact tables.
<<Level>> is the time series grain you want to use. In this example, you would select "Quarter" from your time dimension.
Refer section About the TODATE Function
http://docs.oracle.com/cd/E23943_01/bi.1111/e10540/dimensions.htm#BABBEGHH
Thanks
Deva
Edited by: Devarasu R on Feb 18, 2013 6:02 PM

OBIEE 11g time series: regression on ago / todate function ?

Hello,
We are testing the migration to OBIEE 11G.
We are currently in 10.3 version
We have a problem on AGO / TO_DATE OBIEE functions that returns null results on existing reports.
In 10.3 version, these functions work properly with the actual TIME dimension.
Here is how we designed time Dimension:
TOTAL -> Year -> Quarter -> MONTH -> WEEK -> DATE_KEY, FULL_DATE
DATE_KEY is a number and referenced as a foreign key on our fact table.
CREATE TABLE TD_DATE
+(+
DATE_KEY NUMBER (11) NOT NULL,
FULL_DATE DATE
WEEK NUMBER (2),
MONTH NUMBER (2),
QUARTER NUMBER (1)
YEAR NUMBER (4),
TOTAL_DATE VARCHAR2 (11 BYTE)
+)+
Database version: Oracle 11g
All elements of the dimension are chronological key (except full date) in order to optimize performance.
Have you encountered similar problems in inplémentation of AGO / TO_DATE function on version 11g?
Thanks,
Romain

Does a month have always the same number of week and begin with the first day of a week ?
If it's not the case, your dimension is not good when you make a report on the week grain for a year ago for instance.
Here a check list:
http://gerardnico.com/wiki/dat/obiee/ago_todate_configuration#timecalender_dimension_design_verification
Success
Nico

Reversing Time series functions (todate)

I inherited reports with columns locked on YTD values, I cant get eg monthly sales from a report because of this. I want to find a way of finding where exactly the previous developer made these adjustments that have affected all my reports. I tried going into the logical layer(BMM) and duplicating columns and removing aggregations but no changes in answers. I need a few tips on how i can go from here... is there anyone who has encountered such, or has an idea of where to start... help needed ASAP! thanks!

Hi,
Can you elabrate more..with some screen short/example.
fyi..YTD calc -->date expression ..
http://obieeelegant.blogspot.com/2011/06/obiee-date-expressions-reference.html
Last year last day.
e.x:
"GPC_DataMart"."GPC_DataMart"."dbo"."LY_Position"."Business_Date"=
TIMESTAMPADD( SQL_TSI_DAY , -1, TIMESTAMPADD( SQL_TSI_DAY , EXTRACT( DAY_OF_YEAR FROM "GPC_DataMart"."GPC_DataMart"."dbo"."MT_BUSINESS_DATE"."Business_Date") * -(1) + 1, "GPC_DataMart"."GPC_DataMart"."dbo"."MT_BUSINESS_DATE"."Business_Date"))
Thanks
Deva

Time Series Measure : ToDate

Hi experts,
I have been facing a problem,for which I need your help.
I want to calculate No. of Pending claims till date....
I am trying achieve it using ToDate Function.
ToDate(Cliam Fact.Pending Claim,Year)
But, If I select Year=1999 it will show result like this
Pivot View :
Jan-1999 Feb-1999 Mar-1999 ....................
Pending Claims 10 15 9
ToDate_Pending 10 25 34
I want to calculate pending claims before Jan-1999 also
for ex. till Dec-1998 : if pending claim count is 210
then for Jan-1999 it has to show ToDate_Pending =220..
Can we get this by applying ToDate function on TotalLevel of Period Dimension Hierarchy?
Or do you have any better suggestion for this problem.....
Plz, reply ASAP.

As I understand, it's not a YEAR to date, because you don't want the cumul start from 0 each year. Is it right ?
If so, just try a "running sum" in the pivot table.
You will have these results :
Dec-1998 / Janv-1999 / Fev-1999 / Mar-1999
210 / 220 / 235 / 244
Jan-1999 Feb-1999 Mar-1999 ....................
Pending Claims 10 15 9
ToDate_Pending 10 25 34
If you need to "break" in function of another dimension, then use the RSUM function with "by" (ex : Rsum(measure by Category_product) )
(or Rcount, depending on what is your aggregation of your measure).

Time series functions are not working in OBIEE for ESSBASE data source

Hi All,
I am facing a problem in OBIEE as I am getting error messages for measure columns with Time series functions(Ago,ToDate and PeriodRolling) in both RPD and Answers.
Error is "Target database does not support Ago operation".
But I am aware of OBIEE supports Time Series functions for Essbase data source.
using Hyperion 9.3.1 as data source and obiee 11.1.1.5.0 as reporting tool.
Appreciate your help.
Thanks,
Aravind

Hi,
is because the time series function are not supported for the framentation content, see the content of the oracle support:
The error occurs due to the fact the fragmented data sources are used on some Time series measures. Time series measures (i.e. AGO) are not supported on fragmented data sources.
Confirmation is documented in the following guide - Creating and Administering the Business Model and Mapping Layer in an Oracle BI Repository > Process of Creating and Administering Dimensions
Ago or ToDate functionality is not supported on fragmented logical table sources. For more information, refer to “About Time Series Conversion Functions” on page 197.
Regards,
Gianluca

Perf issues with Time series function in OBIEE

Attached is the SQL:
SELECT SUM (T256675.ACTIVITY_GLOBAL2_AMT) AS c1,
SUM (T256675.ACTIVITY_GLOBAL3_AMT) AS c2
FROM X_FINANCIAL_HIERARCHY_DH T610485 /* Dim_X_GLACCT_ALTVIEW_D */,
X_FINANCIAL_HIERARCHY_DH T610414 /* Dim_X_MGMT_ENTITY_D */,
W_GL_ACCOUNT_D T256463 /* Dim_W_GL_ACCOUNT_D */,
W_GL_BALANCE_F T256675 /* Fact_W_GL_BALANCE_F */,
SAWITH3,
SAWITH6
WHERE ( T256463.ROW_WID = T256675.GL_ACCOUNT_WID
AND T256463.X_FIN_HIER1_WID = T610485.ROW_WID
AND T256463.X_FIN_HIER5_WID = T610414.ROW_WID
AND T256675.BALANCE_DT_WID = SAWITH3.c3
AND SAWITH6.c1 = SAWITH3.c1
AND T610414.ACCOUNT_HIER8_NAME = 'Worldwide'
AND T610414.HIERARCHY_SOURCE = 'EntityMgmt'
AND T610485.ACCOUNT_HIER7_NAME = 'Controllable Expenses'
AND T610485.HIERARCHY_SOURCE = 'AltViews'
AND SAWITH6.c3 = '2009 / 11'
AND SAWITH6.c2 >= SAWITH3.c2
The SAWITH3 and SAWITH6 dimensions using time series fuctions are causing a full table scan on W_GL_BALANCE_F and W_GL_ACCOUNT_D . Though we are interested in just getting 2009/11 data; the queries generated by time series function TODATE is taking us against entire W_DAY_D data and is causing several performance issues.
W_GL_BALANCE_F table has index on GL_ACCOUNT_WID and BALANCE_DT_WID.
How can we force to use index on these columns for better performance.
Please advise us on the right approach to improve performance.
SQL for SAWITH3
===========
WITH SAWITH0 AS
SELECT T31328.ROW_WID AS c3, T31328.PER_NAME_FSCL_QTR AS c4,
ROW_NUMBER () OVER (PARTITION BY T31328.PER_NAME_FSCL_QTR ORDER BY T31328.PER_NAME_FSCL_QTR DESC)
AS c5,
T31328.PER_NAME_FSCL_MNTH AS c6,
ROW_NUMBER () OVER (PARTITION BY T31328.PER_NAME_FSCL_QTR, T31328.PER_NAME_FSCL_MNTH ORDER BY T31328.PER_NAME_FSCL_QTR DESC,
T31328.PER_NAME_FSCL_MNTH DESC) AS c7
FROM W_DAY_D T31328 /* Dim_W_DAY_D_Common */),
SAWITH1 AS
SELECT CASE
WHEN CASE SAWITH0.c5
WHEN 1
THEN SAWITH0.c3
ELSE NULL
END IS NOT NULL
THEN RANK () OVER (ORDER BY CASE SAWITH0.c5
WHEN 1
THEN SAWITH0.c3
ELSE NULL
END ASC NULLS LAST)
END AS c1,
CASE
WHEN CASE SAWITH0.c7
WHEN 1
THEN SAWITH0.c3
ELSE NULL
END IS NOT NULL
THEN RANK () OVER (PARTITION BY SAWITH0.c4 ORDER BY CASE SAWITH0.c7
WHEN 1
THEN SAWITH0.c3
ELSE NULL
END ASC NULLS LAST)
END AS c2,
SAWITH0.c3 AS c3, SAWITH0.c4 AS c4, SAWITH0.c6 AS c5
FROM SAWITH0),
SAWITH2 AS
SELECT MIN (SAWITH1.c1) OVER (PARTITION BY SAWITH1.c4) AS c1,
MIN (SAWITH1.c2) OVER (PARTITION BY SAWITH1.c4, SAWITH1.c5)
AS c2,
SAWITH1.c3 AS c3
FROM SAWITH1),
SAWITH3 AS
SELECT DISTINCT SAWITH2.c1 + 5 AS c1, SAWITH2.c2 AS c2,
SAWITH2.c3 AS c3
FROM SAWITH2),
SQL for SAWITH6
===========
SAWITH4 AS
SELECT T31328.PER_NAME_FSCL_MNTH AS c3, T31328.ROW_WID AS c4,
T31328.PER_NAME_FSCL_QTR AS c5,
ROW_NUMBER () OVER (PARTITION BY T31328.PER_NAME_FSCL_QTR ORDER BY T31328.PER_NAME_FSCL_QTR DESC)
AS c6,
ROW_NUMBER () OVER (PARTITION BY T31328.PER_NAME_FSCL_QTR, T31328.PER_NAME_FSCL_MNTH ORDER BY T31328.PER_NAME_FSCL_QTR DESC,
T31328.PER_NAME_FSCL_MNTH DESC) AS c7
FROM W_DAY_D T31328 /* Dim_W_DAY_D_Common */),
SAWITH5 AS
SELECT CASE
WHEN CASE SAWITH4.c6
WHEN 1
THEN SAWITH4.c4
ELSE NULL
END IS NOT NULL
THEN RANK () OVER (ORDER BY CASE SAWITH4.c6
WHEN 1
THEN SAWITH4.c4
ELSE NULL
END ASC NULLS LAST)
END AS c1,
CASE
WHEN CASE SAWITH4.c7
WHEN 1
THEN SAWITH4.c4
ELSE NULL
END IS NOT NULL
THEN RANK () OVER (PARTITION BY SAWITH4.c5 ORDER BY CASE SAWITH4.c7
WHEN 1
THEN SAWITH4.c4
ELSE NULL
END ASC NULLS LAST)
END AS c2,
SAWITH4.c3 AS c3, SAWITH4.c5 AS c4
FROM SAWITH4),
Thanks
Srini Pendem

Hi Srini,
I've had quite a bit of performance issues with ToDate and Ago. I tended to create materialized views on my fact tables that would materialize those values as columns and that way I would avoid having to use the ToDate or Ago functions. Is there any chance you can implement a similar solution and bypass the time series functions entirely?
Just to check, those tables belong to BI Apps, right? If so, you can log an SR about the performance issue since it's an issue with the model that Oracle sold you.
Good luck!
-Joe

Time series function hfm

Hi when using HFM at a datasource the dimensions are not mapped as time. So we cant use the built in functions ( in OBIEE) for time series. How can we get this to work? or is there a workaround. ? The HFM dimensions are not able to be changed in the physical layer to represent time.

Since you only asked how to get rid of the 2011 line, here are two ways:
1) Filter on Time.Year column <> 2011
or better
2) Filter on Time.Year column <> YEAR(CURRENT_DATE)+1

How can you build time series measures in OBIEE without using TODATE AGO fu

How can you build time series measures in OBIEE without using TODATE and AGO function?
Please provide steps to build time series
measures in OBIEE without using TODATE and
AGO function. Dashboard results not storing
in cache when using TODATE and AGO functions.
eventhough its cached users queries not
hitting cache because queries doesn't match
exact date time when using TODATE and AGO
functions. so I want to build queries using
sysdate and some simple calculations. Please
send your inputs/ideas for my questions..
Thanks in Advance

This can be using Msum function in answers. Use the following formula, here dollars is my metric. Change the formula based on your metric.
Msum("Sales Measures".Dollars ,2) - "Sales Measures".Dollars
the report will be cached and better performed compared with time series. check ti
- Madan Thota

TODATE time series function in OBIEE 11g

Hi,
I have a problem with time series function. I have month level in time dimension hierarchy.
I have used below expression to get month to date results in my reports.
column
expression----> TODATE(fact.measure, hierarchy.Month level);
when i am using this column in my reports it is showing null values. The below error i am getting in view log files
----------------> Converted to null because it's grain is below query's grain
Note: Here i have measures, year,qtr,month,day,shift,hour in single physical table in physical layer.
Is it a problem to have measures and time columns in a single physical table?
Please let me know if you have any solution.
Thanks,
Avinash

Yes, it shud be a prob. Try using seperate tables for fact n timedim

Can Essbase Dynamic Time Series object be exposed to BI Server repository?

Hi everyone
I imported my Essbase cube metadata into the BI Server repository. I'm using Essbase 11.1.2.1 and OBIEE 11.1.1.5.
Everything is working fine, I'm just missing one piece. In Essbase I have a dimension tagged as time and the Dynamic Time Series has been enabled for YTD, QTD and MTD. After the metadata import, I can't see any of this in the repository's physical layer. So I am assuming that if the member doesn't physically exist in the outline, then it won't be created in the repository physical layer. Is that right? Is Dynamic Time Series integration not possible?
If so, is using TODATE in the repository the only option or are there any other possibilities?
Thanks

http://docs.oracle.com/cd/E26232_01/doc.11122/esb_dbag/frameset.htm?dcatimse.html

How to use Dynamic Time Series YTD on a calc script / member formula?

Hi,
I activated Dynamic Time Series on Essbase and would like to use the YTD function of a measure for a certain month.
I tried to use
MeasureName->YTD(Dec)
MeasureName->Y-T-D(Dec)
But couldn't use it to syntax problems. How can I call this function instead of using @Accum or @SumRange?
Thank you
Edited by: Icebergue on 10/Ago/2011 11:07

I could be wrong, but I don't think you can use DTS members in calc scripts or member formulas. As you probably know, they can be used in Financial Reports, SmartView and Excel Add-in.
You can create an alternate hierarchy in your Time dimension though:
Jan (YTD): Jan ->Jan is being a shared member
Feb (YTD): Feb+Jan (YTD) ->Both Feb and Jan (YTD) are being a shared members
Dec (YTD): Dec+Nov (YTD) ->Both Dec and Nov (YTD) are being a shared members
Cheers,
Mehmet

Time Series Wizard in OBIEE 10.1.3.3

How do I accomplish the TIME SERIES WIZARD functionality that was present in Siebel Analytics 7.7 in OBIEE 10.1.3.3. This comparison measure feature seems to be removed in OBI.
Any inputs will be greatly appreciated.
Thanks.

There are several problems with the OBE given in the first url (http://www.oracle.com/technology/obe/obe_bi/bi_ee_1013/bi_admin/biadmin.html#t11)
(1) pre-built repository and other files (e.g., SH_PartTwo.rpd, SHQuota.xls) cited in the example are not included with download- at least not with 10.1.3.3.1 version I downloaded. When followed instructions to open SH.rpd (included in the download of 10.1.3.3.1) gave error and could not open it. (My DB version is 10.2, op system XP professional)
(2) Looks like this OBE is a newer version - under Build Diemension Hierarchies the steps 33 (Customer dim), 34 (Promotion Dim) and 35 (Time Diemension) have been removed. This is good because in the older version of this OBE the time dimension (given in step 35) was wrong.
(3) In Create Time Measure section cannot select month ago sales and month to date sales columns together in a query. When selected together gave error: pls refer to this thread -
Time Series Measures
Hopefully the current version of this OBE will be updated with an example that has steps to create time dimensions (Calendar and Fiscal) and other steps so that columns created with AGO and TODATE functions can be selected together in a query.
Thanks.
Message was edited by:
rxshah

Obiee essbase time series calc todate returns 0

Similar Messages

Maybe you are looking for