|
Hi! I read it, but was too caught up in stuff to respond. That is a lengthy problem, with a lengthy solution - actually a series of lengthy solutions. We used to use MOVEs, but abandoned them as too time consuming for reporting. Instead, we switched to queue time for scheduling, and wrote a series of audit programs to catch people who over-claim operations. That sounds simple, but we spent a LOT of time figuring out what to do. We also have a lot of people that will "run out the bar (or sheet, or roll, as the case may be)", and that's OK, it's better than scrap and we will use it eventually anyway. The department managers handle that when the quantities are out of whack on the operations vs. the orders. It is a little manually intensive, but we set tolerances on the reports - if over a certain % above standard, the reports flags the line for checking out. I had suggested that we ONLY print the flagged operations, but they want to see them all. Eventually, I want to set up an object and view for this in Browser, but that's one of those "good ideas" that I hope to get to before I retire. Dale Gindlesperger IT Manager/Special Projects Leader Fleetwood Folding Trailers, Inc. 258 Beacon Street Somerset, PA 15501 LeLeux@xxxxxxxxxxx m To: MAPICS ERP System Discussion <mapics-l@xxxxxxxxxxxx> Sent by: cc: mapics-l-bounces@m Subject: Move Transactions.... idrange.com 01/26/2004 04:24 PM Please respond to MAPICS ERP System Discussion I'm gonna try one more time, can't believe I didn't get a single reply, not even a flame! Maybe it was my subject choice.......so here it goes again, thanks in advance! For as long as I can remember we have used MOVE operations following the CLOSE (Stat 40) of an Operation. This has worked well, but in part of the shop we are encountering some problems related to work centers needing to start subsequent operations (more than just the next op sometimes) and how to manage the MOVES, especially relating to what quantity to enter. Ultimately I'd like to eliminate the MOVES, but the problem is that we perform some validation based upon the move-in quantity compared to the Qty Complete to Date + Scrap to help ensure the close-out quantity is accurate (+/- 12% margin) and this is where we are having the problem on the practice performing MOVES before the previous operation is closed. If your current operation is for 500 pieces, after you complete, say 100, move that quantity to the next op, and to the next op when those are complete. This results in 3 active operations (that's ok) but there is real confusion as to what the practice should be on the quantity moved-in. If they only move the first 100, then the count is inaccurate, certainly for validation. Also, if they estimate the complete quantity then that could lead to validation errors. Bear in mind we do incur scrap, which is why I don't use the MO qty, plus some areas 'run out the bar' and exceed the MO qty significantly. To summarize, I'm interested in what some of you are doing, perhaps I'm simply over-analyzing? If you don't use the MOVE transaction, is the QTMVI field in MOROUT populated? How do you 'start' the Op, get it to go from 10 to 20? We do not allow clocking onto a stat 10 op via our HighJump software and we like this validation to help guide the operators. Thanks in advance for your opinions. _______________________________________________ This is the MAPICS ERP System Discussion (MAPICS-L) mailing list To post a message email: MAPICS-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/mapics-l or email: MAPICS-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/mapics-l.
As an Amazon Associate we earn from qualifying purchases.
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.