MTD Measure

Hi,
I am working on BPC 7.5NW SP03.
When I try to select the member from MEASURE dimension, I can see only PERIODIC, QTD and YTD. I do not see MTD measure.
Can anyone let me know if MTD measure is SAP provided measure OR we need to customize it?
How to get MTD measure?
Please suggest.
Regards,
Rashmi

Hi all!
I just have found how add new member to Measures dimension, and I did it in following steps:
1) Add new member in tblFormula and tblYTDFormula with needed logic
2) Add new member in dimesion time with corresponding properties, which using in Statment tblFormula and tblYTDFormula ( LEVEL = DAY, LEVEL = WEEK for my Example). It's most important step.
3) Process all Dimension in all App for your App Set
4) Add to file \BPC\Data\Webfolders\"Your App Set"\System Files\"App",Measures.XML and "App",Measures.DIM corresponding Measure Member ID and Description
5) Refresh Dimension Members via eTools menu in Excel.
That's all
Thank a lot for all, who have tried to help.

Similar Messages

News YTD, YTD LY, MTD measures in OBIEE repository

Hello All,
I wanted some help in creating the following kind of measures:
1) YTD LY
E.g if today is 25/12/2013
It should give the total of all sales from 01/01/2012 to 25/12/2012
2) YTD
E.g if today is 25/12/2013
It should give the total of all sales from 01/01/2013 to 25/12/2013
3) MTD
E.g if today is 25/12/2013
It should give the sum of all sales from 01/12/2013 to 25/12/2013
Thanks

If you have a properly defined time dimension which supports aggregation at year and month level, then provided you do not have future dated data (!) in your system the standard YTD measures created at the appropriate level of aggregation will do what you describe, but the L YTD would have to be done in the analysis itself.
BUT - usually end users ask for this kind of functionality and then subsequently add the requirement that they want to be able to run this 'for any point in time', for which the only way to go is parameters coupled with filter / case logic in the analysis.
regards,
Robert.

Creating a cumulative total by day measure which resets each month.

Hi,
I need to creative a cumulative total measure (or calculated column) which accumulates my revenue sales for each day in a month, but resets each month.
I've created an example below:
The dates are from a linked date table and are based on a fiscal year. When the months are collapsed the months can either accumulate or stay fixed to the max for the month, that does not affect me.
I have tried various attempts using the guides below and I'm sure the answer is there but I can't get the filtering right.
I can get it to work but accumulate since the start of my data but this is not what I need.
http://www.daxpatterns.com/cumulative-total/
http://javierguillen.wordpress.com/2012/11/28/running-total-techniques-in-dax/
Thanks.

It appears that your months align with the standard calendar's months. I.e. your fiscal calendar's October always aligns with regular October. If this is the case, then you can simply use the built-in time intelligence function TOTALMTD().
MTD Measure:=
TOTALMTD(
[Measure]
, DimDate[Date Field]
If this is not the case and your month does not always line up with the standard calendar month, you can implement identical behavior with this FILTER():
Custom MTD Measure:=
CALCULATE(
[Measure]
, FILTER( ALL( DimDate )
, DimDate[Month Number] = MAX( DimDate[MonthNumber] )
&& DimDate[Date Field] <= MAX( DimDate[Date Field] )
Both of these will give identical behavior:
At the day level, they will show the running total for the current month, including the current day.
At the month level, they will show the total for the month.
At the quarter level and above (semester, year, decade, ...) they will show the total for the last month in that period. E.g. for a standard year, they will show December's total.
If these don't work, please provide more details about your date dimension, your data model, and how you are constructing your pivot table, preferably all in the form of a copy of your workbook on OneDrive or similar.

MDX MTD with a Date Range

Hi All
I need some advice on the below, it works, gives the answers I want, but I believe the filter on the set can be moved to a where clause, and the MTD can work effectively then with the sum of the date range on the [RangeHasResponse] measure (advice apart
from "if it ain't broke don't fix it" ;) ). This is query for a report where I can sub in a param date range (set the Today value, and the from in the DateRange), and produce the Sum of Has Response across that date range, and also the MTD
for last month up to the ToDate.
Any advice on how the MDX could be better structured would be great, I can understand I'm calculating members, then adding them to my query, it just seems I should be calculating them in the SELECT based on a filter. Output just needs to be
[MTD]: single sum of Has Response to the current todate for that month
[RangeHasResponse]:Sum of the entire range
[Has Response] : sum on the last day, this isn't necessary, I'm just curious to see how that would tie into a filter, if it ruins the above leave it out.
WITH
SET [ToDate]=[Date].[Year - Quarter - Month - Date].[Date].&[2014-02-22T00:00:00]
SET [DateRange] =
[Date].[Year - Quarter - Month - Date].[Date].&[2014-01-01T00:00:00]:
[ToDate].item(0)
MEMBER [Measures].[MTD] AS
SUM(MTD([Date].[Year - Quarter - Month - Date].CurrentMember),[Measures].[Has Response])
MEMBER [Measures].[RangeHasResponse] AS
SUM([DateRange],[Measures].[Has Response])
SELECT
{[Measures].[MTD],[Measures].[Has Response],[Measures].[RangeHasResponse] } on columns
,[ToDate] on rows
FROM
[ISD Prototype]
Thanks
Best Wishes, The Redman; If something helps, please help show it by voting, if it solves, bonus!

Hi GGoldspink,
In MDX, the CREATE MEMBER statement defines calculated members that are available throughout the session, and therefore, can be used in multiple queries during the session. So if the members can will be used in multiple times in SELECT clause, we can create
a calculated member, and then use this members on SELECT clause which will improve the query performance.
In your scenario, are there any performance issue in your MDX query? In this case, I'd suggest you enable SQL Sever profiler to monitor the queries, and check which part in the query took a very long time to run. Here is a useful link for your reference.
http://sqlmag.com/database-performance-tuning/using-sql-profiler-tune-mdx-queries
Besides, here is a document which will help you understand where issues can occur in your existing MDX code that will prevent you from experiencing the performance improvements, and provide advice on how to avoid these issues in your new MDX coding.
http://technet.microsoft.com/en-us/library/bb934106(v=sql.105).aspx
Regards,
Charlie Liao
If you have any feedback on our support, please click
here
Charlie Liao
TechNet Community Support

Wrong SSAS Grand Total Value Monthly Value base on Weekly Value

Dear All,
I Have calculated measures in my cube base on Weekly and Base on Monthly and different
Template Base .
For grand Total Weekly is fine but for Monthly is bad one.
Say calculated Measure Name "Weekly" with Syntax
CREATE MEMBER CURRENTCUBE.[Measures].[Weekly]
AS IIF(isempty([Measures].[Actual Quantity MTD]) or [Measures].[Actual Quantity MTD]=0 or isempty([Measures].[Original Plan Quantity MTD]) , null ,
IIF([Measures].[Original Plan Quantity MTD] =0 or isempty([Measures].[Original Plan Quantity MTD]),null,
IIF(
([Measures].[Actual Quantity MTD]-[Measures].[Original Plan Quantity MTD]) > 0 , 1 ,[Measures].[Actual Quantity MTD]/ [Measures].[Original Plan Quantity MTD] )))
The Result is good
here the picture
http://hpics.li/9fd22f2
https://drive.google.com/open?id=0ByY5H-XcydgiWGp0RzdWYWp0M2c&authuser=0
and for Monthly Calculation it was AVG of Weekly base on Time, Plant, and PSL Dimension
My calculated Monthly Measure Name "Monthly" with Syntax
CREATE MEMBER CURRENTCUBE.[Measures].[Monthly]
AS AVG (
DESCENDANTS([PSL].[PSL Description])*
DESCENDANTS([Plant].[Plant])*
DESCENDANTS([Finish Date].[Calendar],[Finish Date].[Calendar].[Month Year])
, AVG(([Finish Date].[Calendar].CURRENTMEMBER.CHILDREN), [Measures].[Weekly]))
The Result is Bad on Grand total
here the Picture link
http://hpics.li/5233b50
https://drive.google.com/open?id=0ByY5H-XcydgicEhtT1FpekRsbW8&authuser=0
Please help me why for the Result doesn't same. What do i Miss
Thank You
Yan

Hi Yan,
According to your description, you create a calculated measure in your cube, the problem is that grand Total for Monthly is incorrect, right?
In your scenario, the issue can be caused by that you used "*" and "/" in your calculated measure. In SSAS, one of the most common issues faced in mdx is grand total or sub total not coming properly when some arithmetic operations like
measure1 [* or + or - or /] measure2 is used, please refer to the link below to see the details.
http://vnu10.blogspot.jp/2011/01/mdx-grand-total-sub-total.html
Regards,

OLAP 11g - Passing external Paramteres into AW

We are on OLAP 11gR2 release
I have a scenario where in I need to pass Period dimension chosen by the USERS while they run queries ( via Cube ET views from BO application) against OLAP Cube. Since this is dynamic scenario, is there a way to do it via DML program?? Our ACCOUNT dimension has attributes BEGIN date and END date. QTD and YTD needs to be calculated based on the period parameter being passed, if it is outside the this date range the no else yes.
PERIOD dimension member would be something like 201112 for Dec2012 which i think needs to be converted to proper date format.
HAs this been done before? Any help would be much appreciated.
Thanks.

Assume you're using sql to access aw, then BO parameters you need to pass would become oracle olap aw sql query where clause filters.
I dont think you're constructing the report/solution correctly by thinking in terms of passing parameters.
So instead of "passing parameters", think "framing/constructing the right sql".
What you need to do is define YTD, QTD appropriately in AW. They can be defined for all periods based on the time dimension in your model.
However you need to use the control parameter within the calling application/program: if account dimension attribute values meet the period specification criteria then call/reference YTD/MTD measures else use null instead.
YTD, MTD being defined as a calculated measure does not imply that the fromulae are pre-calculated and stored for all periods. It's only the measure definition which is stored and this defn results in the right calculation for MTD/YTD. No harm/work is done just because they're defined. Based on the scope/dimension members involved in the call to the cube/aw referencing these formulae/measures, these calculations are fired/triggered and the results calculated for the cells in question.
If you frame the right question (i.e. right sql from BO), you'll get the right answer/results from oracle olap quickly.
HTH
Shankar

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

Need to apply MTD logic for actual and prior year

Hi Team,
We are facing an issue with MTD calculation based on formula variables,
Issue: MTD Only (Actual and Prior Year) – show the same value for MTD.
Requirement:
When the query is run for a selected month, the query should be run for that month based on the Last TECO Date (Input Variable).
• For example, dashboard is run for January 2014, the calculation of MTD should be based on the Last TECO Date : i.,e if I enter older date/month (not current date)[ 1/20/2014 means it should calculate for 1/1/2014 – 1/31/2014]
• If the dashboard is run for the current month, the MTD calculation should be on Last TECO Date = 1st day of month – Current Day
The above same calculation logic should be applicable for MTD prior year: instead of the input variable value, the value for previous year should be considered
Final Calculation:
If Last Labour Date is blank, 0, else Last TECO Date – Last Labour Date (by individual line item)
Here we created two formula variables for last teco date and last labour date.
Also created 2 Customer Exit variable for MTD Actual calculation.
We have pulled the formula variable and CE variable into the selection and created a new CKF (Teco date).
We have done the final calculation on the basis of the ( (labour date ==0)*0 + last teco date-last labour date )for MTD ACTUAL.
MTD Prior Year-
when have done calculation on the basis of the( (labour date ==0)*0 + last teco date-last labour date )for MTD Prior year by giving offset -12 to the value.
Here for MTD Actual and MTD Prior year values are coming same ,we tried with by doing customer exit variables as well, Still values are coming same.
please give your valuable inputs/suggestions to proceed for this requirement .

I assume the Sales measure is a monthly measure. The Prior year calculation as I described will give you the sales for the same month in the previous year when selecting month in your report. When selecting year it will add up all months of the prior year until now and you will indeed see the Prior year YTD.
If you want to see the total sales for the previous year you have to use the same calculation as 'Prior year' and map it to the year level of your time dimension. This will work as a 'partition by year'.

Date Based Dynamic Member Calculation Performance (MTD, YTD, PeriodsToDate)

I'm working on an SSAS 2012 cube and I have defined several dynamic calculations based on a Date (MTD, YTD, TD, Thru Previous Month, etc.).
The cube has a well defined Date dimension and I have set up a DYNAMIC calculated set in the cube as shown below.
CREATE DYNAMIC SET CURRENTCUBE.[Latest Date]
AS TAIL(EXISTS([Payment Date].[Calendar Date].[Date].Members,[Payment Date].[Calendar Date].CURRENTMEMBER,"Claim Payment"));
... and here is an example of one of my calculations.
CREATE MEMBER CURRENTCUBE.[Measures].[Face Amount Paid MTD]
AS SUM(MTD([Latest Date].ITEM(0).ITEM(0)), [Measures].[Face Amount Paid]),
FORMAT_STRING = "$#,##0.00;-$#,##0.00",
//NON_EMPTY_BEHAVIOR = { [Claim Payment Fact Count] },
VISIBLE = 1 , DISPLAY_FOLDER = 'Face Amount' , ASSOCIATED_MEASURE_GROUP = 'Claim Payment';
This calculation returns the correct results, but performs horribly. I've noticed that changing the [Latest Date] set to STATIC, performance greatly improves, but numbers are no longer accurate as they are based on the Tail of the Claim Payment measure
group without considering the filtered dates. This is because the date is evaluated at process time, but needs to be based on users date selection to be accurate. Therefore, STATIC does not appear to be an option. Is there a better way to
perform this calculation dynamically based on the filtered or unfiltered date dimension?

Typically I would just do YTD/MTD/etc off the date the user has selected. It seems like you want to do it based on the last date with data within the range they have selected. Why not just give the user what they are asking for?
In other words, why not
YTD([Payment Date].[Calendar Date].currentmember)

Drilldowns on measure columns based on time series functions.

Guys,
I am new to OBIEE and i need your Help!! I have a dashbaord report which shows the sales USD for the colums below.
REGION , PRIOR MONTH , CURRENT MONTH PRIOR YEAR , CURRENT MONTH PRIOR YEAR MTD , CURRENT MTD , ACTUALS YTD.
All the measures are logical columns caluculated in the RPD using the Time Series Functions. The dasboard report has a Prompt Calender Date and all the measure values are caluclated based on the date entered in the prompt.
For example if the Calender Date on the prompt is 5/31/2011 then the value for the PRIOR MONTH will the sales for APR-2011 and the value for CURRENT MONTH PRIOR YEAR will be MAY-2010 and so on.
The business requirement is to provide the drill down capability on these measure columns. When i click the sales number on the prior month column it should give me all the detailed transactions for the month of APR-2011 considering the prompt for calender date is 31-MAY-2011.
I have provided drilldowns based on the Navigation using the column interatcion but i am unable to understand how to provide the drilldown on the measure columns using the time series functions to caluclate the sales for PRIOR MONTH. CURRENT MONTH PRIOR YEAR...etc.
Please Help!!!
Thanks,
Sandeep.

1. Create an alias fact table (Year Ago) to pull last year value.
2. Extend your fact table to store another measure (last year sales)
3. Based on volume of granular data and query pattern on year ago measures, you may create aggregate fact tables.
hope this helps.

Using a Custom Measure w/ BI Beans

In order to create month-to-date and year-to-date totals, I have created a custom measure using the create_custom_measure procedure in the dbms_aw_utilities package. These two new measures, MTD and YTD, are simply cumulative sum functions applied over the date dimension. I have created this new measure as 'permanent' and it will exist beyond the current session, persisted in the analytic workspace views. I would now like to enable this new measure for use with the OLAP API and BI Beans so that I can simply display the measure along with my other 'static' measures. However, after refreshing and re-enabling the cube, the measure is still not available outside AWM.
Is it possible to use a custom measure with BI Beans? Is there a simpler way to accomplish this?
Thanks,
Jeff

You need to post this question on the database OLAP forum as the enablement for OLAP process is owned by the database team.
I presume you did run the 'enable Analytic Workspace for OLAP API and BI Beans' option from within AWM after you added the two new measures? If not you will need to generate the CWM2 metadata to register the new measures.
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation

"Semi/Non additive measure with" : "LastChild Across All Dimension" OR "LastChild Across Time and MAX across All Other Dimension"

Hey All
I am using the SQL SERVER 2008R2 standard edition so please be mindful when posting any suggestion if that will work on this edition or not.
Here is the situation: I have Cube with one fact table "Positions". Measure I am querying is "AUM" and Dimensions across user can query are combinations of {"Portfolio", "Security" and "Time"}.
I am receiving the "AUM" values at "portfolio+Security+Time" level. AUM is actually the Portfolio level value. so sample data I receive would like this.
PORTFOLIO SECURITY TME AUM
A SEC1 JAN-1 100
A SEC2 JAN-1 100
B SEC1 JAN-1 200
B SEC3 JAN-1 200
A SEC1 JAN-2 300
A SEC2 JAN-2 300
B SEC1 JAN-2 400
B SEC3 JAN-2 400
So, as shown in above example , we received same "AUM" value for a given portfolio and time. (regardless of what security value is).
And as AUM is the snapshot values, we can not sum across time as well, so if user is looking across time we need to pick Last values.
Now when user wants to view this data from cube, two different ways s/he wants to look at it.
option one: AUM at port+sec+time level. that is same as shown above in example.
option two: AUM at portfolio level only, (notice that this is across time so results are picking values for time=JAN-2)
PORTFOLIO AUM
A 300
B 400
GRAND TOTAL 700
I have applied the "LastChild" aggregation property to measure to achieve "Do no Sum across Time "behavior. but with this I also get "SUM Across Except time" and hence my AUM values get summed across Portfolio and security as
well. I have also enable Time Intelligence to enable MTD, YTD calculations.
I tried to add SCOPE statement for Security before and after the "time calculations" yet I am not able to achieve expected behavior.
here is the calculated member definition, and scope statement i have tried.
CREATE MEMBER
CURRENTCUBE.[MEASURES].[AUMNetBaseCurrency] AS
[Measures].[AUMNetBaseCurrency_Raw_Max],
FORMAT_STRING = "#,##0.00 ;( #,##0.00 )",
VISIBLE = 1 , DISPLAY_FOLDER = 'Position';
After this I have MTD and YTD time calculation for few measures including AUM.
I tried placing the following SCOPE for AUM before and after the Time calculations but it no difference in result, in fact it seems like it has no affect of scope at all due to the "LastChild" aggregate property applied on measure.
SCOPE([MEASURES].[AUMNetBaseCurrency]);
SCOPE([Security].[Symbol].[All]);
THIS = MAX([Measures].[AUMNetBaseCurrency_Raw_Max]);
END SCOPE;
END SCOPE;
so options I am thinking of but do not have clear idea how to implement those are:
0) why my Security Scope Statement are not showing any effect, and can we do something about it?
1) Can be change "SUM" behavior to "MAX" / "MIN" across all Dimension except time.
2) Is there a way to implement "LastChild" across all dimension instead only across Time.
3) Should I need to make any changes at Fact table level to achieve this ? I refer one Q&A in this forum that suggested to create such measure in different measure group but it doesn't have any clarification.
Any help would be appreciated.
Thanks
Anup Shah

hi,
you will have to enable cache in your nqsconfig.ini file under the section
# Query Result Cache Section
[ CACHE ]
ENABLE = YES;
cache seeding is also a mechanism through which the data would be updated in the cache.

Please help me in Calculating Sybase IQ Daily,WTD,MTD, YTD,QTD,SPLM,SPLY

Hi Team,
Need to Calculate No of Customers from a particular dimension table on these measures Daily,WTD,MTD, YTD,QTD,SPLM,SPLY
Can anybody help me with the Logic its extremely urgent.
Thanks all for your help
Regards,
Yedu

Is that part of an entire script, I don't see the tokens changing as TimG observed is this being called from a different routine. (are you calling the same script using a for loop?)
I think instead of updating the subvar everytime, he just used a bat/sh script to run it for various members.
Regards
Celvin
http://www.orahyplabs.com

QTD, MTD functions

Hi All,
I have a logical table based on Time and created a corresponding Dimension.
These are the columns
1) Year
2) Quarter
3) Month
4) Week
5) Day
In the properties of Time Dimension, I made as the dimension as TIme Dimension CHECKED.
Default Root Level is Year.
Chronological Key is Day.
I have a fact table called Interactions which contains the number of interactions maintained at a granularity of each Day.
I tried to create a Logical Column in fact table Interactions based on logical column and tried to use ToDate for YTD Interactions,QTD Interactions, MTD Interactions.
I tried to create function based on Measure and Level values as ToDate(BusinessMode.FACTTable.Column, TimeDimension.Table.YEAR)
First I got a error saying invalid identifier and kept the column of the Year from Time Dimension
It got rectified.
Then I am getting error as Invalid Expression. I think it expects two parameters and I am providing both.
Please let me know if I am missing anything.
Regards
(S.Prashant)

Hi Kishore,
I made a change over here and the error is not occuring now. But different error is occuring.
Instead of year (which is default root level in Dimension), I picked either Month or Quarter and I am not facing the error (Invalid Expression).
I have a questions now
1) is it that we cannot use a column defined as Default Root level in Todate and AGO functions?
The other part is I have a new error ([nQSError: 22038] Function TODATE requires at least one measure attribute in its first argument.)
My fact column (FACT Table as partner_id,Id (primary_key) and ..). For the fact column to be the first parameter is that is should have some aggregation rule?
Please let me know...
Thanking you in Advance
Regards
(S.Prashant)

YTD in Measures or TIME

Hi Guys,
I wonder what is best practice, having YTD and MTD as a Measure for each of the core measures like:
Actual
Actual YTD
Actual MTD
Budget
Budget MTD
Budget YTD
.. about 30 measures
Or having it in the time dimension
2010
---Qtr
----Jan
-----Jan YTD
-----Jan MTD
-------1
-------2
-------3
-------4
-------

While I agree with Cameron I also disagree with him at the same time. There are many isntances where it is favorable to have these calcualtions outside of the time dimension. Doing MDX range based formulas in an ASO cube is one. Also using TB in ASO cubes is another. Cameron's point "you are duplicating members for Actual, Budget, etc" is slightly accurate. Typically you are creating formula based member based on those other members. If a BSO cube is you make the formula members dynamic, you have not increased block size or calculation time. What I think one of the best solutions is what Gary Crisci describes in his blog as an Analytic (what I call a View) dimension. It works well for either ASO or BSO and really does not increase your DB size.

MTD Measure

Similar Messages

Maybe you are looking for