Re: Question for the group

The holding of the unattached jobs might help, it depends what transaction
date/time you use for reporting and reconciliation. I am very lucky in
that we always close the period on Sunday, and have been able to tell
everyone they can't process anything during period end.

But in the past, that was an issue.

For the ending of the jobs, we wrote a CL that disables ALL but a select
few account IDs, then we end *immed all interactive sessions. That helps,
except for data collection jobs, and holding those unattached jobs helps
that.

Our shipping department isn't an issue, since we bill EVERYTHING through
the Offline Shipping Enhancement, which is run in batch, so I control that
through IT operations..... But receiving is another issue. (We just
don't have the receiving dock open then.)

Dale Gindlesperger
IT Manager/Special Projects Leader
Fleetwood Folding Trailers, Inc.
258 Beacon Street
Somerset, PA 15501





"Lloyd Degnon"
<ldegnon@xxxxxxxx
m> To
Sent by: "MAPICS ERP System Discussion"
mapics-l-bounces@ <mapics-l@xxxxxxxxxxxx>
midrange.com cc

Subject
08/24/2007 04:55 [MAPICS-L] Question for the group
PM


Please respond to
MAPICS ERP System
Discussion
<mapics-l@midrang
e.com>






Does anyone else have the issue with closing a period, running reports
for closing inventory levels etc., but then find out that your reports
are wrong because shipping/receiving had activity before your report
finished? Is there something that I am missing?

It would be great if I could push a button and have 50+ user profiles
deactivated, basically all but a few profiles in Finance, then push
another "Magic" button to reactivate the users? on second thought that
would not work 'cause it would not log them out if they were already
in....

Wonder if I hold Unattached batches? Any other Ideas besides firing
people who break the rules?

Lloyd H. Degnon
I.S. Manager
Ampro Computers, Inc.
5215 Hellyer Ave. Bldg 110
San Jose, CA 95138
408.360.4365
www.ampro.com