Unless you have set your jobs to be (schedule) locked, the Global will reschedule them.
The only exception to that is possibly going to be Jobs in a WIP state. Any OPs that had activity started on them (labor reporting of set up or qty completions) (and had OP start dates in the 'past' when the activity began) may not move.
We forward schedule, and this is a trick we use to 'lock' the start date of jobs (that would all otherwise want to try and start 'today'). Our 1st OP is always a zero set up/cycle time OP that all materials are tied to (essentially a stockroom Issue OP). After initially scheduling to our desired start date via Job Entry's Scheduler (in Infinite Mode), we punch in 1% setup complete on this 1st OP and it then becomes the earliest the Global will ever try to start the 'real' OPs that follow.
I don't know for sure how it would treat an in-process OP that had an in-the-past Start date. (You should probably try it in a Train copy of your live db.)
My guess would be it would schedule them to always start 'today' but I'm not really sure.
The 404 global is so buggy, it is difficult to determine what is real intended behavior and what is bug induced behavior (that may disappear with the next release - or get worse).
Rob Brown
The only exception to that is possibly going to be Jobs in a WIP state. Any OPs that had activity started on them (labor reporting of set up or qty completions) (and had OP start dates in the 'past' when the activity began) may not move.
We forward schedule, and this is a trick we use to 'lock' the start date of jobs (that would all otherwise want to try and start 'today'). Our 1st OP is always a zero set up/cycle time OP that all materials are tied to (essentially a stockroom Issue OP). After initially scheduling to our desired start date via Job Entry's Scheduler (in Infinite Mode), we punch in 1% setup complete on this 1st OP and it then becomes the earliest the Global will ever try to start the 'real' OPs that follow.
I don't know for sure how it would treat an in-process OP that had an in-the-past Start date. (You should probably try it in a Train copy of your live db.)
My guess would be it would schedule them to always start 'today' but I'm not really sure.
The 404 global is so buggy, it is difficult to determine what is real intended behavior and what is bug induced behavior (that may disappear with the next release - or get worse).
Rob Brown
--- On Wed, 7/9/08, Tony Hughes <thughes281@...> wrote:
From: Tony Hughes <thughes281@...>
Subject: Re: [Vantage] Allow Scheduling before Today
To: vantage@yahoogroups.com
Date: Wednesday, July 9, 2008, 2:59 PM
One last question,
If and when that check is removed, does it leave jobs scheduled in the past? or force you to reschedule?
Thank you!
----- Original Message ----
From: Tony Hughes <thughes281@yahoo. com>
To: vantage@yahoogroups .com
Sent: Monday, July 7, 2008 2:37:54 PM
Subject: [Vantage] Allow Scheduling before Today
Are there any quirks about enabling this check box in Company Configuration?
Thank you
Tony
Anthony Hughes
ERP Manager
Logan Oil Tools, Inc.
Houston, Texas
[Non-text portions of this message have been removed]