× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



It is indeed "the nature of the beast", but no means around it even if you
would use another system (transactions which influence eachother should be
processed together). Best thing I found to do on the whole is to process
transactions per department (or range), and processing is only allowed if
the department has no (0) errors.  Departments should be "independent" (ex:
no employees from a different dept range should work on the same Mfg
Order).  
If you process people who worked together on an MO you also should watch
out for crew clock (this influences machine time and therefore overhead
cost in some cases).

----------
> Van: McCready, Joan <Joan.McCready@metaltekint.com>
> Aan: MAPICS-List (E-mail) <MAPICS-L@midrange.com>
> Onderwerp: processing PMC transactions
> Datum: woensdag 7 maart 2001 20:36
> 
> To all -
> 
> Does anyone have any tips or techniques for the timely processing of PMC
> transactions that are gathered using a shop floor collection program (we
are
> using PLMC - aka PaperLess - but the problems we're having are in PMC,
not
> in the collection).
> 
> We seem to have a timing issue.  We give the supervisors until 10:00 am
to
> "fix" the previous days' transactions, then our payroll dept processes
the
> select and edit and prepare.  After the prepare, the payroll clerk runs a
> select and edit to see what didn't get "fixed."
> 
> One of the recurring problems is where two or more people work on an
> operation on an MO on the same day.  Employee #1 has some sort of error,
so
> none of his transactions are processed.  Employee #2 has no errors - her
> transactions are posted.  Thing is - she completed and closed the
operation.
> Once we fix employee #1's error - which was on a different MO's
transaction
> - his transactions still don't post, because now the operation is closed
for
> the MO both employees worked on.  So we re-open the operation and perform
> yet another select-and-edit to post employee #1's transactions.  It may
take
> several hours to get everything posted, and then the payroll clerk is
> "guessing" that the corrections are really OK - since the supervisors are
> too busy or may even be finished with their shift and gone.
> 
> Each leadman or supervisor would have literally thousands of operations
to
> wade through each day - they run the "errors only" report, but more times
> than most, the problem causing the error isn't the error itself, and
their
> attempt to "fix" the "error" screws up the employee's transactions worse!
 
> 
> We don't have MAPICS' Payroll module.  Does anyone have any suggestions,
or
> is this just the nature of the "beast" called PMC??
> 
>         -- Joan
> 
> Joan McCready, IS Manager              phone:  636-479-4499
> The Carondelet Corporation                fax:  636-479-3399
> A MetalTek International Company     www.metaltekint.com
> 8600 Commercial Blvd
> Pevely, MO  63070                      
> 
> +---
> | This is the MAPICS Mailing List!
> | To submit a new message, send your mail to MAPICS-L@midrange.com.
> | To subscribe to this list send email to MAPICS-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MAPICS-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
dshaw@spartan.com
> +---
+---
| This is the MAPICS Mailing List!
| To submit a new message, send your mail to MAPICS-L@midrange.com.
| To subscribe to this list send email to MAPICS-L-SUB@midrange.com.
| To unsubscribe from this list send email to MAPICS-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dshaw@spartan.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.