Thanks for the reply, but this operation did not have anybody clock-in to complete, so there was nothing to edit using "Labor Entry."
--tj
--tj
--- In vantage@yahoogroups.com, Adam Puchalski <a.puchalski@...> wrote:
>
> I've dealt with this issue by modifying the labor entry where the mistake was made.
> It always works fine for me to either uncheck "OP Complete" or to just delete the entry altogether depending on the circumstances.
>
> AP
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of cooner_55421
> Sent: Friday, March 25, 2011 12:26 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Cannot "uncomplete" operation in subassembly
>
>
>
> I think Op Complete is a hidden field in the Job Entry screen operation grid.
> I think I've unhid it and toggled op complete before.
> But... didn't work on all ops, can't remember the details.
>
> --- In vantage@yahoogroups.com<mailto:vantage%40yahoogroups.com>, "sanfranc415" <sanfranc415@> wrote:
> >
> > There is an open job in which a sub-assembly operation was mistakenly completed.
> >
> > Using Job Adjustment, we unchecked the operation that was complete and saved, but upon reentering the job, the operation is still complete.
> >
> > The change log even shows that the operation was changed from complete yes -> no
> >
> > Any ideas?
> >
> > I'm sure our procedure is correct, since we tested this on another job and worked fine.
> >
> > --sf
> >
>
>
>
> [Non-text portions of this message have been removed]
>