Correction Stan...
Sometime in 8.0.808+ to current (8.03.404B), Epicor changed/broke the
logic for Candidate. I logged this under call #1040109PSC. But all
they did is wrote up an SCR# 46614 for the fact that the help file
was incorrect. They still have not fixed the logic...and
unfortunately I gave up!
When in Job Closing (completion), if you click on the Job button and
choose Job Filter = Candidate, it pulls jobs where the last operation
under assembly 0 is marked complete.
It used to pull if either the last operation under assembly 0 was
marked complete OR the operation marked as FINAL under assembly 0 was
marked complete.
I had to write a BAQ/dashboard for this "issue":
for each JobHead where (JobHead.Candidate = no AND
JobHead.JobComplete = false AND JobHead.JobEngineered = true AND
JobHead.JobReleased = true AND JobHead.QtyCompleted >=
JobHead.ProdQty) no-lock by JobHead.Company Desc by JobHead.JobNum
Desc.
Thanks
Patty Buechler
UV Color
Sometime in 8.0.808+ to current (8.03.404B), Epicor changed/broke the
logic for Candidate. I logged this under call #1040109PSC. But all
they did is wrote up an SCR# 46614 for the fact that the help file
was incorrect. They still have not fixed the logic...and
unfortunately I gave up!
When in Job Closing (completion), if you click on the Job button and
choose Job Filter = Candidate, it pulls jobs where the last operation
under assembly 0 is marked complete.
It used to pull if either the last operation under assembly 0 was
marked complete OR the operation marked as FINAL under assembly 0 was
marked complete.
I had to write a BAQ/dashboard for this "issue":
for each JobHead where (JobHead.Candidate = no AND
JobHead.JobComplete = false AND JobHead.JobEngineered = true AND
JobHead.JobReleased = true AND JobHead.QtyCompleted >=
JobHead.ProdQty) no-lock by JobHead.Company Desc by JobHead.JobNum
Desc.
Thanks
Patty Buechler
UV Color
--- In vantage@yahoogroups.com, "Stan Chmura" <schmura@...> wrote:
>
> The final operation will make the job a candidate (for
completion/closing)
> when the quantity entered on that operation meets or exceeds the
production
> quantity for the job. The purpose of the check box is so that if
there is
> an operation (involving indirect labor; say packaging for example)
that
> comes after the job is otherwise complete, then the job becomes a
candidate
> for closing on completion of the operation marked as last operation
even
> though there is an operation after the "final" operation. If left
> unchecked, the highest Operation Sequence acts as the final by
default.
> This should have no bearing on the quantities completed on your
subcontract
> operation. That quantity typically is loaded from quantity passed
in
> Inspection Processing or PO receipt.
>
>
>
>
>
> _____
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf Of
> clive.1972
> Sent: Friday, May 02, 2008 11:06 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Job Entry -> Operation -> 'Final Operation'
check box,
> what's it's purpose ?.
>
> Before we went live at the start of 2008 with Vantage the check
> box 'Final Operation' on an operation on a job was not something
were
> were made aware of in any training.
>
> I'm very intrigued as to what the intended purpose of it is ?.
Right
> now it's something that we never check, even if a job has only one
> operation should we be checking this box as a matter of course ?.
>
> What brought this to light is that at the moment, since upgrading
from
> 8.03.305i to .404, when we complete a sub-contract job 'qty
completed'
> is 0.00 :(
>
> We've got no idea why this is happening ?. As it's a sub-contract
job
> we're not entering any labor against it, any internal jobs do have
> labor entered against them and they do have a 'qty completed' once
the
> job is marked as complete.
>
> Thanks :)
>
>
>
> [Non-text portions of this message have been removed]
>