There was a recent disussion about what a business date module should
be able to do that might be interesting if you want to make this
module do other business calculations...
-ben
On Fri, Jun 20, 2003 at 08:00:17AM -0400, Jesse Shy wrote:
>
> I currently have a subclassed module I created for an application here at
> work, called Date::Calc::Fiscal. The interface takes 2 dates, the fiscal
> start date and the date your interested in - returning either the day
> number or week number of the fiscal year. So if your fiscal start day is
> Feb 1, then Feb 1 is day 1 of week 1, or iso I guess is week 0 and Jan 31
> is day 365 or 366 depending. We use this in a web app to show individual
> customers their invoicing by periods that match their internal accounting
> practices.
>
> After some thought, I realized that this was simply the application and
> that the function is realy a numerical day adjustment to either the
> gregorian or pataphysical calendars, depending on whether you have 12 or
> 13 periods in calender ( fiscal instrument ).
>
> So first I am wondering about namespace. I can not think of another place
> where this is needed other than finacial apps, so I was thinking
> DateTime::Fiscal, but as I said earlier, that is really the application
> not the function however, if this is the only application than this name
> fits.
>
> Currently I only have 2 methods, day_of_fiscal_year and
> week_of_fiscal_year. I would eventually like to use DateTime::Set, ::Span
> ::SetSpan along with calendaring to create fiscal calendars showing end of
> period dates, etc...
>
> I would love some feedback on these thoughts or anything related to this
> that I may not have thought of. Thanks.
