Job Required Date VS Due Date - Unwanted behavior

Hello all,

Maybe someone can guide me in the right direction…

We recently added “days out” in part routings ONLY for OV parts. The end goal was to generate a warning when a job was put out IF the job didnt have enough time to get through the OV step, much less any other operations. (It’s an imprefect warning but we are not ready to attach rates/times to other ops at this time so Im working with what I’ve got.)

I feel that I may however be working against Epicor’s brain. I have defaulted “Override Material Constraints” in the Scheduling Engine, since I DO NOT WANT Epicor to override the Required date that is entered by user. I just want the warning. Problem is, although the Required by date remains unchanged, the “Last Op” field is using my days out to calculate when it thinks we will finish and changes Due Date to match.

Ultimately, I just want the due date to match the required date that the user entered, regardless of when Epicor calculates the last op to be. Due date doesn’t seem to be an accessible field…

I have tried to use a BPM to update the fields to match but can’t seem to get at the right BO.

Thanks,

Alice

I believe that you may be misinterpreting the purpose of this field. The REQUIRED by date is the date that you WANT it to be finished. The DUE date is the date that it is currently scheduled to be completed (i believe this includes receive time). The final operation is the date that the final operation will be done.
So… if you have a 10 day job, and the job is REQUIRED today, but you forward schedule it, the DUE date will be 10 days out, even though the required date is today.

1 Like

Thank you. That kind of confirms what I thought. I am I correct in thinking that “Due Date” is Epicor generated and never editable by users?

Correct… it is a calculated field. I had to get my head wrapped around it as well… to me “due date” sounds like when you want it… but in reality it is when the current schedule SAYS it is due… Think of it like when a Baby is due… You don’t get to set the due date.

5 Likes

I’m trying to figure out why the required date matches the due date exactly on some jobs… but there are some where the due date is 1 day earlier. It’s of little consequence, but I want to understand what drives the calculation. Can anyone help clear this up?

Thanks!!

Based on rates you’ve entered and the availability of resources, Epicor calculates you can complete that job a day earlier in reality than the “Required Date” that you chose. That is my understanding.

Is there a way to eliminate or change receive time?

I’m finding the Due date is consistently 2 working days after the final op shows complete.

You can set it in Part Class Maintenance. Different for each class if you need.
image

1 Like