To Move or not to Move?

[LeLeux@xxxxxxxxxxxx]

For as long as I can remember (nowadays less than 5 minutes!) 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.