BobLeeSwagger
asked on
Crystal 2008 - Convert fiscal year to calendar year
Our fiscal year starts in June and ends in May. The GL_Data table in our ERP database has a year field and has monthly credit and debit fields.
The field names are: gl_year,debits@1, credits@1, debits@2, credits@2 and so on.
I want to be able to run this report from January 2013 to December 2013.
This would be for periods 8-12 for FY2012 and periods 1-7 in FY2013.
I need a way to set up an automatic report with date ranges set via parameters.
We know we need to group by year, but that groups by fiscal and does not show us true Calendar year data.
This is an example of what I have
gl_year debits@1 credits@1 debits@2 credits@2 debits@11 credits@11 debits@12 credits@12
2012 7 4 20 3
2013 10 5 22 15
and the results I need
April 2013 - 3
May 2013 - 17
June 2013 - 5
July 2013 - 7
Thank you for you help,
J
The field names are: gl_year,debits@1, credits@1, debits@2, credits@2 and so on.
I want to be able to run this report from January 2013 to December 2013.
This would be for periods 8-12 for FY2012 and periods 1-7 in FY2013.
I need a way to set up an automatic report with date ranges set via parameters.
We know we need to group by year, but that groups by fiscal and does not show us true Calendar year data.
This is an example of what I have
gl_year debits@1 credits@1 debits@2 credits@2 debits@11 credits@11 debits@12 credits@12
2012 7 4 20 3
2013 10 5 22 15
and the results I need
April 2013 - 3
May 2013 - 17
June 2013 - 5
July 2013 - 7
Thank you for you help,
J
ASKER
Yes that's correct.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I don't understand your example. The results that you posted don't seem to match the example data on the two lines above that. Are your example data and results just unrelated sets of numbers, or is there some correlation that I'm not seeing?
Ignoring that for the moment ...
You said that you needed to "group by year". A potential problem with that idea is that a single record contains data from two different calendar years, and a record can only be in one group. But if the report will never include more than one calendar year, then I guess that's not a problem.
James
Ignoring that for the moment ...
You said that you needed to "group by year". A potential problem with that idea is that a single record contains data from two different calendar years, and a record can only be in one group. But if the report will never include more than one calendar year, then I guess that's not a problem.
James
mlmcc,
What's the point of using CDbl ({@myNull}) ? Why not just use 0? Just curious.
I just did a quick test and I see that it would leave the field blank on the report, but I don't see why you'd want that, instead of just letting the result be 0.
James
What's the point of using CDbl ({@myNull}) ? Why not just use 0? Just curious.
I just did a quick test and I see that it would leave the field blank on the report, but I don't see why you'd want that, instead of just letting the result be 0.
James
I wasn't sure what he was doing with the values. Since 0 could be meaningful in the results, the NULL is a better indicator that there is no data for that month
mlmcc
mlmcc
Fair enough. Like I said, I was just curious.
James
James
mlmcc