Sorry, that last sentence should read "Job Tracker", not "Part
Tracker".
-Peter
Tracker".
-Peter
--- In vantage@yahoogroups.com, "pvolkert365" <pvolkert@...> wrote:
>
> We have found that Job Adjustments affect the labor record
quantity
> but do not affect the WIP location quantity, which is stored in
the
> PartWip table, and which is displayed in Part Tracker on the Part
> Locations tab.
>
> -Peter
>
> --- In vantage@yahoogroups.com, "Charlie Smith" <CSmith@> wrote:
> >
> > And the Job adjustments (Labor, Material or Subcontract) don't
> resolve
> > the matter? If the second operator makes a mistake, you can
> > update/correct the labor card or do a job adjustment to the
labor.
> That
> > would resolve the WIP issues.
> >
> >
> >
> > From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
On
> Behalf
> > Of pvolkert365
> > Sent: Monday, July 16, 2007 11:55 AM
> > To: vantage@yahoogroups.com
> > Subject: [Vantage] WIP Tracking (8.03)
> >
> >
> >
> > I don't hear any chatter on this topic and do not understand why
> we
> > are the only ones experiencing this problem. We cannot seem to
get
> > our WIP tracking numbers to come out right. And then we have a
> heck
> > of a time fixing them when they are wrong. We do have AMM, but I
> do
> > not believe it comes into play here. We are producing
electronics,
> > so we have enormous BOMs and extensive BOOs.
> >
> > When an operator completes 10 units at operation 30, Vantage
moves
> > 10 units of WIP to operation 40. If two operators both (by
> mistake)
> > report the 10 units, operation 40 now has 20 units of WIP, even
if
> > the job is only for 10. I do understand that a Shop Warning can
be
> > activated to warn the second operator. If we elect to do steps
out
> > of sequence, I do understand that there is a selection on the
> > completion screen to designate what operation is next. But if an
> > error is made, the WIP quantity goes to the next sequential
step,
> > not the next intended step.
> >
> > Vantage actually has an answer for all the possible mistakes an
> > operator can make. So if our operators paid attention and never
> > made a mistake, there would be no issue. But what Epicor does
not
> > provide is a way to correct a mistake once the WIP is either
> > overstated or is on the wrong operation. We have come up with a
> > workaround where we create a new operation sequence 3 and move
> > undesired WIP to it, and then we don't include operation 3 on
any
> > WIP reports we create. Does anyone have a better way? Is this
even
> > an issue for anyone else?
> >
> > Peter Volkert
> > Symetrics Industries
> >
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>