Database field: PartPlant.ReceiveTime (behind part entry). Database field: PartClassPlt.ReceiveTime (behind part class maintenance).
Description: Days needed to move part to stock or next job. Deducted from Due Date.
1) What is the hierarchy on the above fields? - which has priority? 2) In terms of the “due date” described in the description…which “due date” is it referring to? the due date on the purchase order release? 3) If the user manually enters a due date of 15/05/2018 and there is a ReceiveTime of 2 days, does the due date automatically change to 13/05/2018? or is the calculation sat in the background somewhere and the field stays as 15/05/2018?
I’ve also logged the above directly with epicor, so I’ll update this post in due course.
After reading that a couple of times, that’s not exactly clear.
Here’s some more from the E10 Tech Ref
Example(s)
The following example(s) illustrate how you use the Receive Time functionality.
Manufactured Part Example
Job 4582 has a Required By Date of August 22nd. The part-site detail for this manufactured part has a Receive Time value of 4, indicating it takes 4 days for a part quantity to arrive at your warehouse. The MRP engine calculates that this unfirm job will have an End Date of August 18th.
Purchased Part Example
You need to receive Part Sheet Metal, a purchased part, by April 20th. The part-site detail for this purchased part has a Receive Time value of 2, which accounts for how long it takes to unpack and inspect the part quantity. The MRP engine calculates that this purchase suggestion requires a Supply Date value of April 18th. The supplier will need to ship the part quantity to your manufacturing center by this date.
EDIT : One more thing :
• You can also leave this field blank on a part-site detail; the MRP engine will then use the Receive Time value defined within the Part Class record instead.
Receive time is the amount of EXTRA time needed to receive the part to stock. This is added by MRP/PO Suggestions automatically when creating those suggestions.
PartPlant overrides any more generic setting (PartClass).
Hi Mark,
Please find below the answers for the queries raised:
Receive Time in Part maintenance DB PartPlant.ReceiveTime:
Displays the amount of days required to move a part to stock or to the next job. The Receive Time is subtracted from the Requested by Date.
Receive time in Part class: : PartClassPlt.ReceiveTime
In the case of a part class for manufactured items, this is the number of days that are required to move the assembly either to stock or to the next job.
For manufactured parts this buffer is added to the due date of the job.
In the case of a part class for purchased or transferred parts, this is the time required to receive and inspect the part. This time would be deducted from the calculated demand date to give the suppliers the correct supply date.
What is the hierarchy on the above fields? - which has priority?
MRP receive time in part class:
The receive time defined within the Part class record is used. Part class records let you create blanket values that you can then assign to parts.
In terms of the “due date” described in the description…which “due date” is it referring to? the due date on the purchase order release?
This is the Due date on the job order.
Job order Due date:
Specifies the date when production should be complete on this job; this is the date of the last operation on the job. If you are backward scheduling, this date is used to calculate the Start Date. If you are forward scheduling, this date is calculated from the Start Date. You cannot edit this field; it is displayed only for your information. For example, 05/15/13.
If the user manually enters a due date of 15/05/2018 and there is a ReceiveTime of 2 days, does the due date automatically change to 13/05/2018? or is the calculation sat in the background somewhere and the field stays as 15/05/2018?
Due date cannot be edited.
Thanks.
I believe the answer to Number 1 is that the part plant receive time is used first, if 0 then uses receive time from Part class for item. Easily tested.
