I'm no expert as we are still in the 1st pilot stage of implementing v8 (.305b) - converting from Profitkey (which has a FAR superior scheduling engine compared to v8) but otherwise has fallen behind other systems in nearly all other areas. However, I have a few ideas you can check out:
1. Have you actually poked into the proper db table to confirm "start date" is null? Epicor's ".Net" claims aside, it is really the UI program layers that are only ".Net". With the Progress code layer that exists (whether you are running the Progress db or SQL Server), the scheduling code itself could be as old as the hills and the UI may simply be displaying the start date as null under certain conditions.
2. Are you running scheduling as part of your MRP Regen? If so, and you "disallow historical dates", backward scheduling (even in an infinite model) may result in start dates that are in the past (historical) and, thus don't get updated.
What you say about being unable to fix an order once its 1st time schedule is flawed (no start date), seems to be a general problem I've encountered throught v8.
Good luck! If you come up with an explanation, please post it for us "neophytes".
Rob Brown
Versa Products
"Lindquist, Pam" <plindquist@...> wrote:
Has anyone seen a problem with job scheduling where a start date is not
generated, but an end date is?
We are generally doing backward scheduling with no finite scheduling.
This intermittently creates an end date with no start date, however,
most of the time it does create a start date.
We've tried over-riding material constraints checkbox, also forward
scheduling, reducing hours required, and increasing the date required
by.
Once a job has had scheduling run and no start date is created, then no
matter what we do, we never get a start date.
Just want to know if we are the only ones with this problem.
Thanks,
Metro Machine
[Non-text portions of this message have been removed]
---------------------------------
Access over 1 million songs - Yahoo! Music Unlimited.
[Non-text portions of this message have been removed]
1. Have you actually poked into the proper db table to confirm "start date" is null? Epicor's ".Net" claims aside, it is really the UI program layers that are only ".Net". With the Progress code layer that exists (whether you are running the Progress db or SQL Server), the scheduling code itself could be as old as the hills and the UI may simply be displaying the start date as null under certain conditions.
2. Are you running scheduling as part of your MRP Regen? If so, and you "disallow historical dates", backward scheduling (even in an infinite model) may result in start dates that are in the past (historical) and, thus don't get updated.
What you say about being unable to fix an order once its 1st time schedule is flawed (no start date), seems to be a general problem I've encountered throught v8.
Good luck! If you come up with an explanation, please post it for us "neophytes".
Rob Brown
Versa Products
"Lindquist, Pam" <plindquist@...> wrote:
Has anyone seen a problem with job scheduling where a start date is not
generated, but an end date is?
We are generally doing backward scheduling with no finite scheduling.
This intermittently creates an end date with no start date, however,
most of the time it does create a start date.
We've tried over-riding material constraints checkbox, also forward
scheduling, reducing hours required, and increasing the date required
by.
Once a job has had scheduling run and no start date is created, then no
matter what we do, we never get a start date.
Just want to know if we are the only ones with this problem.
Thanks,
Metro Machine
[Non-text portions of this message have been removed]
---------------------------------
Access over 1 million songs - Yahoo! Music Unlimited.
[Non-text portions of this message have been removed]