RE: GL month problem

["Shaw, Dave" <dshaw@xxxxxxxxxxxx>]

Greg and Dale,

I prefer SQL to programs, myself, but I know just what you mean.  We used
13-period accounting at my old job, and at one time had an AP clerk who
could be counted on to post at least one batch incorrectly the first week of
every period.  It would sure be nice if MAPICS would actually default the
current period number correctly on those screens when using periods instead
of months.  It's not as if it would be hard to do.

Dave Shaw
MAPICS-L Moderator
Rauch Industries, Inc.
Gastonia, NC

-----Original Message-----
From: DaleGindlesperger@fft-inc.com

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
We have a very similar situation (we use a 4-4-5 period schedule).  I
couldn't come up with an assured way of handling period numbers in entry
(A/P check processing was our biggest issue, with invoice generation a
close 2nd), so I changed our internal procedures to have the users request
period specific jobs from IT operations, and that way our system operator
is responsible for keeping everything straight.  At least that way we have
accountability.

You also get good at writing little quick "blaster" programs to change
period numbers in files....  (sigh)

Dale @ Fleetwood





Greg Wenzloff <GWenzloff@beckmfg.com>
Sent by: mapics-l-admin@midrange.com
02/04/02 10:06 AM
Please respond to mapics-l


        To:     "'mapics-L@midrange.com'" <mapics-L@midrange.com>
        cc:
        Subject:        GL month problem


We used be use the calendar month as a fiscal period and everything worked
well.   Now we are using a 4-5-4 week fiscal period and are having
problems
getting things posted to the correct period.

How do other companies handle this problem?    We tried adjusting dates to
make things fit the correct period but our entry people seem to forget too
often and we spend too much time fixing things.

Greg Wenzloff
Beck Manufacturing
717-762-9141x246