Job Operations not completing

system · February 5, 2009, 10:09am

We've stayed on 405a. Nothing compelling in 407 for us (as we can live with this propblem with our process) & 408 is promised to include the fixes we initiated that are important to us (a nasty global rescheduler bug).
Rob

--- On Wed, 2/4/09, Steve_E <vantage@...> wrote:

From: Steve_E <vantage@...>
Subject: RE: [Vantage] Job Operations not completing
To: vantage@yahoogroups.com
Date: Wednesday, February 4, 2009, 7:57 AM

Rob,

I was told by support that this problem is gone in version .407. Have you
confirmed if this is true?

Steve

-----Original Message-----
From: Robert Brown [mailto:robertb_versa@ yahoo.com]
Sent: February 04, 2009 12:51 AM
To: vantage@yahoogroups .com
Subject: Re: [Vantage] Job Operations not completing

Tony,

There are 3 Op complete related fields (spread across JobOpr & JobOpDtl).

MES seems to only trigger setting one of them (I'll confirm which one when
at work tomorrow and let you know). It also seems to be only an issue with
Time & Quantity reporting type OPs. (Qty reporting and Backflush work fine.)

This is purely and MES quirk as full license Labor Entry DOES set all the
flags properly for T&Q reporting type OPs.

In your example, do NOT have your 1st person (doing the initial 6 pc partial
complete) report force check off OP complete. This will screw things up
(particularly if you are running the Job Qty Op Yield recalc process).

I'll send more specific info in the AM when I can connect to Vantage.

Rob

--- On Tue, 2/3/09, Tony Hughes <thughes281@ yahoo.
<mailto:thughes281% 40yahoo.com> com> wrote:
From: Tony Hughes <thughes281@ yahoo. <mailto:thughes281% 40yahoo.com> com>
Subject: [Vantage] Job Operations not completing
To: vantage@yahoogroups <mailto:vantage% 40yahoogroups. com> .com
Date: Tuesday, February 3, 2009, 3:47 PM

Not sure how it is happening, but the pattern seems to be like this:

Job is for 10 pieces

First person starts production, on MES.

Finishes a quantity of 6 pieces. On "End Activity" screen, the check box for
Complete is not checked. saves, closes.

Next person starts production on MES>

He completes the remaining 4 pieces. On "End Activity" screen, once he
enters 4, the Complete checks automatically, saves and closes.

In many cases this is not triggering the Job Operation to be complete and I
cannot figure out why.

They suggested running a database conversion (5090) to fix it.

I just don't think that is the problem, otherwise everyone on this board
would be complaining about it.

Is this something that any of you have seen?

Checking the Complete box in MES sets the field labordtl.complete of that
record as true, this is manual.

What is supposed to happen when the laborqty fields of your labordtl records
match up to the amount on the job, then your joboper.opcomplete marks as
true.

in my example, would the first person need to mark Complete, even if his
quantity is not the complete job quantity?

Is the fact that two labordtl records have quantity matching the job
quantity, but one or more of them is not marked complete, so
joboper.opcomplete never markes True?

Thank you for any help?

[Non-text portions of this message have been removed]

system · February 3, 2009, 3:47pm

Not sure how it is happening, but the pattern seems to be like this:

Job is for 10 pieces

First person starts production, on MES.
Finishes a quantity of 6 pieces. On "End Activity" screen, the check box for Complete is not checked. saves, closes.

Next person starts production on MES>
He completes the remaining 4 pieces. On "End Activity" screen, once he enters 4, the Complete checks automatically, saves and closes.

In many cases this is not triggering the Job Operation to be complete and I cannot figure out why.
They suggested running a database conversion (5090) to fix it.
I just don't think that is the problem, otherwise everyone on this board would be complaining about it.

Is this something that any of you have seen?

Checking the Complete box in MES sets the field labordtl.complete of that record as true, this is manual.
What is supposed to happen when the laborqty fields of your labordtl records match up to the amount on the job, then your joboper.opcomplete marks as true.

in my example, would the first person need to mark Complete, even if his quantity is not the complete job quantity?

Is the fact that two labordtl records have quantity matching the job quantity, but one or more of them is not marked complete, so joboper.opcomplete never markes True?

Thank you for any help?

system · February 3, 2009, 3:53pm

Tony,

This is a reported bug and was told it was fixed on the release 407 patch. I
am not live on the 407 patch to confirm that it fixes the problem due the
the supplier price list problem.

Steve

-----Original Message-----
From: Tony Hughes [mailto:thughes281@...]
Sent: February 03, 2009 2:48 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Job Operations not completing

Not sure how it is happening, but the pattern seems to be like this:

Job is for 10 pieces

First person starts production, on MES.
Finishes a quantity of 6 pieces. On "End Activity" screen, the check box for
Complete is not checked. saves, closes.

Next person starts production on MES>
He completes the remaining 4 pieces. On "End Activity" screen, once he
enters 4, the Complete checks automatically, saves and closes.

In many cases this is not triggering the Job Operation to be complete and I
cannot figure out why.
They suggested running a database conversion (5090) to fix it.
I just don't think that is the problem, otherwise everyone on this board
would be complaining about it.

Is this something that any of you have seen?

Checking the Complete box in MES sets the field labordtl.complete of that
record as true, this is manual.
What is supposed to happen when the laborqty fields of your labordtl records
match up to the amount on the job, then your joboper.opcomplete marks as
true.

in my example, would the first person need to mark Complete, even if his
quantity is not the complete job quantity?

Is the fact that two labordtl records have quantity matching the job
quantity, but one or more of them is not marked complete, so
joboper.opcomplete never markes True?

Thank you for any help?

[Non-text portions of this message have been removed]

system · February 3, 2009, 4:15pm

Hey Steve,
I cannot reproduce the problem even though I see it a few times a times a day.
Is there a circumstance where it is occurring, that you know of?

Anyone else having this problem?

Also, as long as job is not closed, how do you manually complete a job operation?

________________________________
From: Steve_E <vantage@...>
To: vantage@yahoogroups.com
Sent: Tuesday, February 3, 2009 2:53:01 PM
Subject: RE: [Vantage] Job Operations not completing

Tony,

This is a reported bug and was told it was fixed on the release 407 patch. I
am not live on the 407 patch to confirm that it fixes the problem due the
the supplier price list problem.

Steve

-----Original Message-----
From: Tony Hughes [mailto:thughes281@yahoo. com]
Sent: February 03, 2009 2:48 PM
To: vantage@yahoogroups .com
Subject: [Vantage] Job Operations not completing

Not sure how it is happening, but the pattern seems to be like this:

Job is for 10 pieces

First person starts production, on MES.
Finishes a quantity of 6 pieces. On "End Activity" screen, the check box for
Complete is not checked. saves, closes.

Next person starts production on MES>
He completes the remaining 4 pieces. On "End Activity" screen, once he
enters 4, the Complete checks automatically, saves and closes.

In many cases this is not triggering the Job Operation to be complete and I
cannot figure out why.
They suggested running a database conversion (5090) to fix it.
I just don't think that is the problem, otherwise everyone on this board
would be complaining about it.

Is this something that any of you have seen?

Checking the Complete box in MES sets the field labordtl.complete of that
record as true, this is manual.
What is supposed to happen when the laborqty fields of your labordtl records
match up to the amount on the job, then your joboper.opcomplete marks as
true.

in my example, would the first person need to mark Complete, even if his
quantity is not the complete job quantity?

Is the fact that two labordtl records have quantity matching the job
quantity, but one or more of them is not marked complete, so
joboper.opcomplete never markes True?

Thank you for any help?

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

system · February 3, 2009, 4:22pm

I was told that it has something to do with the material backflushing. I
can not find the scr number, but will look for it.

Steve

-----Original Message-----
From: Tony Hughes [mailto:thughes281@...]
Sent: February 03, 2009 3:16 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Job Operations not completing

Hey Steve,
I cannot reproduce the problem even though I see it a few times a times a
day.
Is there a circumstance where it is occurring, that you know of?

Anyone else having this problem?

Also, as long as job is not closed, how do you manually complete a job
operation?

________________________________
From: Steve_E <vantage@rmgfelm. <mailto:vantage%40rmgfelm.com> com>
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Sent: Tuesday, February 3, 2009 2:53:01 PM
Subject: RE: [Vantage] Job Operations not completing

Tony,

This is a reported bug and was told it was fixed on the release 407 patch. I
am not live on the 407 patch to confirm that it fixes the problem due the
the supplier price list problem.

Steve

-----Original Message-----
From: Tony Hughes [mailto:thughes281@yahoo. com]
Sent: February 03, 2009 2:48 PM
To: vantage@yahoogroups .com
Subject: [Vantage] Job Operations not completing

Not sure how it is happening, but the pattern seems to be like this:

Job is for 10 pieces

First person starts production, on MES.
Finishes a quantity of 6 pieces. On "End Activity" screen, the check box for
Complete is not checked. saves, closes.

Next person starts production on MES>
He completes the remaining 4 pieces. On "End Activity" screen, once he
enters 4, the Complete checks automatically, saves and closes.

In many cases this is not triggering the Job Operation to be complete and I
cannot figure out why.
They suggested running a database conversion (5090) to fix it.
I just don't think that is the problem, otherwise everyone on this board
would be complaining about it.

Is this something that any of you have seen?

Checking the Complete box in MES sets the field labordtl.complete of that
record as true, this is manual.
What is supposed to happen when the laborqty fields of your labordtl records
match up to the amount on the job, then your joboper.opcomplete marks as
true.

in my example, would the first person need to mark Complete, even if his
quantity is not the complete job quantity?

Is the fact that two labordtl records have quantity matching the job
quantity, but one or more of them is not marked complete, so
joboper.opcomplete never markes True?

Thank you for any help?

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

system · February 3, 2009, 4:24pm

You can do it through labor adjustment. If you open the user up the marked
the completion change the time and change it back it will complete the
operation.

Steve

-----Original Message-----
From: Tony Hughes [mailto:thughes281@...]
Sent: February 03, 2009 3:16 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Job Operations not completing

Hey Steve,
I cannot reproduce the problem even though I see it a few times a times a
day.
Is there a circumstance where it is occurring, that you know of?

Anyone else having this problem?

Also, as long as job is not closed, how do you manually complete a job
operation?

________________________________
From: Steve_E <vantage@rmgfelm. <mailto:vantage%40rmgfelm.com> com>
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Sent: Tuesday, February 3, 2009 2:53:01 PM
Subject: RE: [Vantage] Job Operations not completing

Tony,

This is a reported bug and was told it was fixed on the release 407 patch. I
am not live on the 407 patch to confirm that it fixes the problem due the
the supplier price list problem.

Steve

-----Original Message-----
From: Tony Hughes [mailto:thughes281@yahoo. com]
Sent: February 03, 2009 2:48 PM
To: vantage@yahoogroups .com
Subject: [Vantage] Job Operations not completing

Not sure how it is happening, but the pattern seems to be like this:

Job is for 10 pieces

First person starts production, on MES.
Finishes a quantity of 6 pieces. On "End Activity" screen, the check box for
Complete is not checked. saves, closes.

Next person starts production on MES>
He completes the remaining 4 pieces. On "End Activity" screen, once he
enters 4, the Complete checks automatically, saves and closes.

In many cases this is not triggering the Job Operation to be complete and I
cannot figure out why.
They suggested running a database conversion (5090) to fix it.
I just don't think that is the problem, otherwise everyone on this board
would be complaining about it.

Is this something that any of you have seen?

Checking the Complete box in MES sets the field labordtl.complete of that
record as true, this is manual.
What is supposed to happen when the laborqty fields of your labordtl records
match up to the amount on the job, then your joboper.opcomplete marks as
true.

in my example, would the first person need to mark Complete, even if his
quantity is not the complete job quantity?

Is the fact that two labordtl records have quantity matching the job
quantity, but one or more of them is not marked complete, so
joboper.opcomplete never markes True?

Thank you for any help?

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

[Non-text portions of this message have been removed]

system · February 4, 2009, 1:51am

Tony,

There are 3 Op complete related fields (spread across JobOpr & JobOpDtl).

MES seems to only trigger setting one of them (I'll confirm which one when at work tomorrow and let you know). It also seems to be only an issue with Time & Quantity reporting type OPs. (Qty reporting and Backflush work fine.)

This is purely and MES quirk as full license Labor Entry DOES set all the flags properly for T&Q reporting type OPs.

In your example, do NOT have your 1st person (doing the initial 6 pc partial complete) report force check off OP complete. This will screw things up (particularly if you are running the Job Qty Op Yield recalc process).

I'll send more specific info in the AM when I can connect to Vantage.

Rob

--- On Tue, 2/3/09, Tony Hughes <thughes281@...> wrote:
From: Tony Hughes <thughes281@...>
Subject: [Vantage] Job Operations not completing
To: vantage@yahoogroups.com
Date: Tuesday, February 3, 2009, 3:47 PM

Not sure how it is happening, but the pattern seems to be like this:

Job is for 10 pieces

First person starts production, on MES.

Finishes a quantity of 6 pieces. On "End Activity" screen, the check box for Complete is not checked. saves, closes.

Next person starts production on MES>

He completes the remaining 4 pieces. On "End Activity" screen, once he enters 4, the Complete checks automatically, saves and closes.

In many cases this is not triggering the Job Operation to be complete and I cannot figure out why.

They suggested running a database conversion (5090) to fix it.

I just don't think that is the problem, otherwise everyone on this board would be complaining about it.

Is this something that any of you have seen?

Checking the Complete box in MES sets the field labordtl.complete of that record as true, this is manual.

What is supposed to happen when the laborqty fields of your labordtl records match up to the amount on the job, then your joboper.opcomplete marks as true.

in my example, would the first person need to mark Complete, even if his quantity is not the complete job quantity?

Is the fact that two labordtl records have quantity matching the job quantity, but one or more of them is not marked complete, so joboper.opcomplete never markes True?

Thank you for any help?

system · February 4, 2009, 7:57am

Rob,

I was told by support that this problem is gone in version .407. Have you
confirmed if this is true?

Steve

-----Original Message-----
From: Robert Brown [mailto:robertb_versa@...]
Sent: February 04, 2009 12:51 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Job Operations not completing

Tony,

There are 3 Op complete related fields (spread across JobOpr & JobOpDtl).

MES seems to only trigger setting one of them (I'll confirm which one when
at work tomorrow and let you know). It also seems to be only an issue with
Time & Quantity reporting type OPs. (Qty reporting and Backflush work fine.)

This is purely and MES quirk as full license Labor Entry DOES set all the
flags properly for T&Q reporting type OPs.

In your example, do NOT have your 1st person (doing the initial 6 pc partial
complete) report force check off OP complete. This will screw things up
(particularly if you are running the Job Qty Op Yield recalc process).

I'll send more specific info in the AM when I can connect to Vantage.

Rob

--- On Tue, 2/3/09, Tony Hughes <thughes281@yahoo.
<mailto:thughes281%40yahoo.com> com> wrote:
From: Tony Hughes <thughes281@yahoo. <mailto:thughes281%40yahoo.com> com>
Subject: [Vantage] Job Operations not completing
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Date: Tuesday, February 3, 2009, 3:47 PM

Not sure how it is happening, but the pattern seems to be like this:

Job is for 10 pieces

First person starts production, on MES.

Finishes a quantity of 6 pieces. On "End Activity" screen, the check box for
Complete is not checked. saves, closes.

Next person starts production on MES>

He completes the remaining 4 pieces. On "End Activity" screen, once he
enters 4, the Complete checks automatically, saves and closes.

In many cases this is not triggering the Job Operation to be complete and I
cannot figure out why.

They suggested running a database conversion (5090) to fix it.

I just don't think that is the problem, otherwise everyone on this board
would be complaining about it.

Is this something that any of you have seen?

Checking the Complete box in MES sets the field labordtl.complete of that
record as true, this is manual.

What is supposed to happen when the laborqty fields of your labordtl records
match up to the amount on the job, then your joboper.opcomplete marks as
true.

in my example, would the first person need to mark Complete, even if his
quantity is not the complete job quantity?

Is the fact that two labordtl records have quantity matching the job
quantity, but one or more of them is not marked complete, so
joboper.opcomplete never markes True?

Thank you for any help?

[Non-text portions of this message have been removed]

system · February 4, 2009, 9:09am

Not sure if this matters to your specific case...
What version are you on?
I assume 8.03.4XXx since 407 is within your reach.

But we encountered several times between 8.00.807 - 8.00.811 and
again in 8.03.403C where this functionality was not working correctly.
It was auto completing when you exceed the planned run qty. So even
if you don't have planned scrap, it was not auto completing until the
total good qty was > planned run qty on the joboper. In your test,
you might want to start production activity and then end reporting a
qty of 1 to see if this little devil has come back.

We do have some operations where we plan scrap. Consequently, we
couldn't understand why you would want to leave an operation open
until you meet or exceed the planned run qty. So our logic is if the
total good qty complete meets the planned production qty, then the
operation will auto complete forcing the rules of Lean
Manufacturing.

Thanks
Patty Buechler

--- In vantage@yahoogroups.com, "Steve_E" <vantage@...> wrote:
>
> Rob,
>
> I was told by support that this problem is gone in version .407.
Have you
> confirmed if this is true?
>
> Steve
>
> -----Original Message-----
> From: Robert Brown [mailto:robertb_versa@...]
> Sent: February 04, 2009 12:51 AM
> To: vantage@yahoogroups.com
> Subject: Re: [Vantage] Job Operations not completing
>
>
>
> Tony,
>
> There are 3 Op complete related fields (spread across JobOpr &
JobOpDtl).
>
> MES seems to only trigger setting one of them (I'll confirm which
one when
> at work tomorrow and let you know). It also seems to be only an
issue with
> Time & Quantity reporting type OPs. (Qty reporting and Backflush
work fine.)
>
>
> This is purely and MES quirk as full license Labor Entry DOES set
all the
> flags properly for T&Q reporting type OPs.
>
> In your example, do NOT have your 1st person (doing the initial 6
pc partial
> complete) report force check off OP complete. This will screw
things up
> (particularly if you are running the Job Qty Op Yield recalc
process).
>
> I'll send more specific info in the AM when I can connect to
Vantage.
>
> Rob
>
> --- On Tue, 2/3/09, Tony Hughes <thughes281@yahoo.
> <mailto:thughes281%40yahoo.com> com> wrote:
> From: Tony Hughes <thughes281@yahoo. <mailto:thughes281%
40yahoo.com> com>
> Subject: [Vantage] Job Operations not completing
> To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> Date: Tuesday, February 3, 2009, 3:47 PM
>
> Not sure how it is happening, but the pattern seems to be like
this:
>
> Job is for 10 pieces
>
> First person starts production, on MES.
>
> Finishes a quantity of 6 pieces. On "End Activity" screen, the
check box for
> Complete is not checked. saves, closes.
>
> Next person starts production on MES>
>
> He completes the remaining 4 pieces. On "End Activity" screen, once
he
> enters 4, the Complete checks automatically, saves and closes.
>
> In many cases this is not triggering the Job Operation to be
complete and I
> cannot figure out why.
>
> They suggested running a database conversion (5090) to fix it.
>
> I just don't think that is the problem, otherwise everyone on this
board
> would be complaining about it.
>
> Is this something that any of you have seen?
>
> Checking the Complete box in MES sets the field labordtl.complete
of that
> record as true, this is manual.
>
> What is supposed to happen when the laborqty fields of your
labordtl records
> match up to the amount on the job, then your joboper.opcomplete
marks as
> true.
>
> in my example, would the first person need to mark Complete, even
if his
> quantity is not the complete job quantity?
>
> Is the fact that two labordtl records have quantity matching the job
> quantity, but one or more of them is not marked complete, so
> joboper.opcomplete never markes True?
>
> Thank you for any help?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

system · February 4, 2009, 9:23am

Patty,

Did you use the BPM to complete the operation?

Steve

-----Original Message-----
From: bpbuechler [mailto:pbuechler@...]
Sent: February 04, 2009 8:03 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Job Operations not completing

Not sure if this matters to your specific case...

But we encountered several times between 8.00.807 - 8.00.811 and
again in 8.03.403C where this functionality was not working correctly.

Not that is matters any more as we ended up changing the logic to
auto complete an operation when the total Labor Qty (total good) >=
Planned Production Qty on the JobOper.

We couldn't understand why you would want to leave an operation open
to acheive planned scrap. If the total good qty complete meets the
planned production qty, then I want the operation to auto complete
forcing the rules of Lean Manufacturing.

Thanks
Patty Buechler

--- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com,
"Steve_E" <vantage@...> wrote:

>
> Rob,
>
> I was told by support that this problem is gone in version .407.

Have you

> confirmed if this is true?
>
> Steve
>
> -----Original Message-----
> From: Robert Brown [mailto:robertb_versa@...]
> Sent: February 04, 2009 12:51 AM
> To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> Subject: Re: [Vantage] Job Operations not completing
>
>
>
> Tony,
>
> There are 3 Op complete related fields (spread across JobOpr &

JobOpDtl).

>
> MES seems to only trigger setting one of them (I'll confirm which

one when

> at work tomorrow and let you know). It also seems to be only an

issue with

> Time & Quantity reporting type OPs. (Qty reporting and Backflush

work fine.)

>
>
> This is purely and MES quirk as full license Labor Entry DOES set

all the

> flags properly for T&Q reporting type OPs.
>
> In your example, do NOT have your 1st person (doing the initial 6

pc partial

> complete) report force check off OP complete. This will screw

things up

> (particularly if you are running the Job Qty Op Yield recalc

process).

>
> I'll send more specific info in the AM when I can connect to

Vantage.

>
> Rob
>
> --- On Tue, 2/3/09, Tony Hughes <thughes281@yahoo.
> <mailto:thughes281%40yahoo.com> com> wrote:
> From: Tony Hughes <thughes281@yahoo. <mailto:thughes281%

40yahoo.com> com>

> Subject: [Vantage] Job Operations not completing
> To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
> Date: Tuesday, February 3, 2009, 3:47 PM
>
> Not sure how it is happening, but the pattern seems to be like

this:

>
> Job is for 10 pieces
>
> First person starts production, on MES.
>
> Finishes a quantity of 6 pieces. On "End Activity" screen, the

check box for

> Complete is not checked. saves, closes.
>
> Next person starts production on MES>
>
> He completes the remaining 4 pieces. On "End Activity" screen, once

he

> enters 4, the Complete checks automatically, saves and closes.
>
> In many cases this is not triggering the Job Operation to be

complete and I

> cannot figure out why.
>
> They suggested running a database conversion (5090) to fix it.
>
> I just don't think that is the problem, otherwise everyone on this

board

> would be complaining about it.
>
> Is this something that any of you have seen?
>
> Checking the Complete box in MES sets the field labordtl.complete

of that

> record as true, this is manual.
>
> What is supposed to happen when the laborqty fields of your

labordtl records

> match up to the amount on the job, then your joboper.opcomplete

marks as

> true.
>
> in my example, would the first person need to mark Complete, even

if his

> quantity is not the complete job quantity?
>
> Is the fact that two labordtl records have quantity matching the job
> quantity, but one or more of them is not marked complete, so
> joboper.opcomplete never markes True?
>
> Thank you for any help?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

[Non-text portions of this message have been removed]

system · February 4, 2009, 9:27am

Sorry did not answer your first question. We are on version 406A and have
not moved to 407 with the problems with the price list maintenance in the
part master.

Steve

-----Original Message-----
From: bpbuechler [mailto:pbuechler@...]
Sent: February 04, 2009 8:10 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Job Operations not completing

Not sure if this matters to your specific case...
What version are you on?
I assume 8.03.4XXx since 407 is within your reach.

But we encountered several times between 8.00.807 - 8.00.811 and
again in 8.03.403C where this functionality was not working correctly.
It was auto completing when you exceed the planned run qty. So even
if you don't have planned scrap, it was not auto completing until the
total good qty was > planned run qty on the joboper. In your test,
you might want to start production activity and then end reporting a
qty of 1 to see if this little devil has come back.

We do have some operations where we plan scrap. Consequently, we
couldn't understand why you would want to leave an operation open
until you meet or exceed the planned run qty. So our logic is if the
total good qty complete meets the planned production qty, then the
operation will auto complete forcing the rules of Lean
Manufacturing.

Thanks
Patty Buechler

--- In vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com,
"Steve_E" <vantage@...> wrote: