Use difference between 2 dates in calculation

Question

Hello,
I want to create a calculation that compares between each month in the year of the forecast and 'Hire Date', so if our year starts in jan-2011. I want to get the difference between jan-2011 and hire date, next month it should get difference between feb-2011 and hire date and so on. The calculation below is trying to check if the difference is more than or equal 1 year.
I have an account named 'Hire Date' of Date type.
I'm trying to write a calculation as follows:
@DateDiff("Hire date",*Current_Date*",DP_Year) >=1)
I need the "Current Date" to contain the full formated date as hire date. I was thinking of producing the current date for example: 01-Jan-2010 to be used in the calculation as follows:
IF(@DateDiff("Hire date",(@CONCATENATE("01",@CONCATENATE(@CURRMBR("PERIOD"),(@CONCATENATE("-",@CURRMBR("YEAR"))))),DP_Year) >=1)
a=b*c;
end if;
Am I on the right track or there's any straight function function or method that can return the current month-year being proccessed in the calculation and use it directly in datediff calculation? or there's any method other than datediff to perform the same ?
Thank you.

Answer 1

I know that it takes date as input parameters, and this is what I was trying from the beginning until my last message that I was pretty sure I'm using it correctly but its not working correctly and returns zero, I started wondering if it's not working with members of date type!, and actually it came to be true as per Oracle support confirmation below! :
"Oracle Support - March 1, 2011 5:06:21 PM GMT+02:00 [ODM Research]
Issue is related to enhancement request
Bug 9576187 - PLN SHOULD SAVE DATES AS ESSBASE DATE SO DATE FUNCTIONS CAN BE LEVERAGED IN HBRS
Oracle Support - March 1, 2011 5:12:12 PM GMT+02:00 [ODM Question]
The Essbase function "@DateDiff" is not returning the expected result when used with Planning date members.
Oracle Support - March 1, 2011 5:16:42 PM GMT+02:00 [ODM Answer]
Essbase saves dates as a number representing the seconds elapsed since midnight, January 1, 1970 (POSIX format). However, Planning saves the dates as a 6-digit number.
Since all native Essbase date functionalities (@DATEDIFF, @DATEDIFF, @DATEPART etc.) require their date parameters in the POSIX format, Planning dates cannot be processed with Calculation Scripts and Business Rules.
There is currently an enhancement request pending which aims to address this issue. However, currently there is no indication of whether this enhancement is going to be incorporated into a future release.
Enhancement Request:
BUG 9576187 - PLN SHOULD SAVE DATES AS ESSBASE DATE SO DATE FUNCTIONS CAN BE LEVERAGED IN HBRS
Oracle Support - March 1, 2011 5:26:45 PM GMT+02:00 [ODM Action Plan]
Unfortunately, the Essbase date functions (@DATEDIFF, @DATEDIFF, @DATEPART etc.) are not supposed to work with Planning members of type date. There is currently an enhancement pending. I will follow up this enhancement request to get clarification on whether it's actually considered for future releases.
I will keep you updated.
Oracle Support - March 2, 2011 10:32:20 AM GMT+02:00 [ODM Action Plan]
With Oracle EPM 11, those new date functionalities have been introduced to Essbase. As previously outline, any date function in Essbase expect the date to be in the POSIX format but Planning's date form consists of 6-digit number. Hyperion Planning and Essbase are two independent products which are available as part of one suite. Although Hyperion Planning requires Essbase, it does not necessarily support every functionality available in Essbase. A couple of years back, when Hyperion Planning's date format was definded, it didn't use Essbase. Unfortunately at the time, Planning development decided to use a 6-digit number rather than the POSIX format. During the past couple of years, efforts have been made to "sync" Planning and Essbase to provide a seemliness experience. The mentioned enhancement request serves the purpose to make it possible to use the Essbase date functions against Planning date members.
Please understand that this issue is not a technical problem as such. Any suggestions concerning a possible approach in order to achieve a date comparison falls into the scope of functional consultancy. The only possible workaround I can see, is to write a rule which follows the same logic as a POSIX date converter in order to be able to use the resulting date values in conjunction with the Essbase date functions as well as to be able to save the corresponding date value in a 6-digit format to Planning date members."