We are having one hell of a time with MRP giving us usable suggestions. We’ve paid Epicor consultants, we’ve paid third party consultants and neither have made a positive impact on the results. With that said, I typically don’t deal with MRP so forgive me in advance if I ask any ignorant questions.
In this instance, we have a part that we would like to have FINISHED 10 (work) days before the due date.
Ditto on Receive Time, although it changed behavior between Epicor 9 and Epicor 10. In Epicor 9, MRP would actually back the JobHead.DueDate up 10 days if you had receive time set to 10 on the part. In Epicor 10/10.1, the JobHead.DueDate will not be backed up at all, but the JobAsmbl.DueDate and JobOper.DueDate fields will all be backed up 10 days, so essentially it will have you completing the final operation 10 days before the “due” date (the date you need it done for shipping).
We’ve tried it and now we’re even more confused. We added 10 days Receive Time (first it appears to be calendar days and not work days).
In the production planner workbench it almost seems correct. It’s off by a day or two but probably because it cant suggest a job earlier than todays date - which is where it did. Original date was 25th, revised date 18th
What version of Epicor are we on again? If you open that job suggestion up in Job Entry, do you see a Start Date and Final Opr Date on the summary tab? What do those say?
As far as the calendar vs. work days, do you have a Production Calendar setup that is off Saturday/Sunday? Example:
When we need to add fat its more operational than by part… we use move time and queue time. Try adding another operation that has a prod std of .00001 and either use queue time or move time. We have an outside service operation that adds 48hrs to a particular subassembly, it is there purely so the start time and end time of the subassembly is realistic. We generally use queue time as occasional we have found the system can ignore the move time if its the last operation.
We also use queue time on a zero dollar resource group “Shipping” with a final operation “Shipping” to give us padding for items that must have extra time for packing.
We don’t use receive time for adding padding for the packing. We use queue time on the resource group. Using this, it does not move the due date up. See below
Do these fields need some special setting to be factored into the MRP time calculation? We have set them manually on some test parts and as far as we can see they are ignored by the MRP
Sorry for the delayed response, last week I was straight out.
I did a very poor job on my prior response, I did not get far enough into the weeds. Let me do a better job.
To add a random 10 days to a MOM, I would do the following. First, make sure that the “Include in Manufacturing Lead Time Calculation” option is enabled on the Site record. Underneath that, I would at a minimum enable “Kit Time”, “Lead Time”, and “Receive Time”. If you use rough cut parameters, you can also enable that one.
Now, with these options enabled, you can use them to add time at the part level to certain steps. So, to have the material available 10 days before you want to ship, add 10 to “Kit Time”. This only works on manufactured parts and would tell the system that it takes 10 days to kit for shipment (even thought it doesn’t).
“Lead Time” and “Receive Time” only work on purchased parts. So, if you wanted to ship to a vendor early (if subcontract) or wanted to pad the time it takes for a vendor to send you items, you would add time into “Lead Time” and the system would tell you to cut the PO earlier. If you wanted to pad time after the parts/items are received, you would add time into “Receive Time”.
Alternatively, if you use the “Manufacturing Lead Time Calculation” under Engineering/Gen Ops, after you run it, you could add 10 days to what the system calculated in the Cumulative Time/This Level Time and enter it into the manual Cumulative Time/This Level Time.
Please let me know if you have any questions as I am not the best explainer.
