I have a part, under min, where MRP is generating change suggestions and not new suggestions. What drives that? What causes a change instead of a new?
Thanks!
What are your Reschedule In/ Out delta’s set to.
I set these to 365 and have a planning time fence of 0 and this forces only new suggestions
I suggest you take a copy of your DB, restore to test, change the settings on the deltas to 365 and your planning time fence to zero and check the results after running ‘Generate Suggestions’ (n.b. there is no need to rerun MRP, if the job demand is already there from a prior run)
If your happy with the results, you can then implement it to test.
Sorry I meant ‘If your happy with the results, you can then implement it to live’
Hi Andrew,
Locking the PO release for date or quantity will make a new suggestion occur instead of change suggestions… can’t change a locked one.
Nancy
Planning time fence stops PO change suggestions from generating with in that time window, correct?
example if i set it for 10 i wont get cancel suggestions for POs due to come in with in 10 days?
Help isnt very clear on what this value does.
Got clarification from Epicor support.
Reschedule In Time Delta
Only for Purchase Orders
This prevents a change suggestion from being created for a PO line that would move up the PO due date for this many days. Example, if the PO line Due Date is the 10th and this In Delta is 5 days. When Generate Suggestions is run, a change suggestion cannot be created to move this Due Date up to any time between the 5th and the 10th.
But it can still create a change suggestion for the 4th and before.
Calculates using Regular Straight Calendar Days, 24x7. Does not calculate using any related production Calendar.
Reschedule Out Time Delta
Only for Purchase Orders
This prevents a change suggestion from being created for a PO line that would move out the PO due date for this many days. Example, if the PO line Due Date is the 10th and this Out Delta is 5 days. When Generate Suggestions is run, a change suggestion cannot be created to move this Due Date out to any time between the 10th and the 15th.
But it can still create a change suggestion for the 16th and after.
Calculates using Regular Straight Calendar Days, 24x7. Does not calculate using any related production Calendar.
Planning Time Fence
This is the number of days from the Current System Date that demands requiring supply changes through jobs, transfer orders, or purchase orders for this part in this plant will not be considered by the system. All demands outside of this time limit, however, will be processed as normal.
Looking at the Time Phase screen, the Balance could go negative due to Demand Requirements from stock during this Time Fence Time From because MRP cannot create Unfirm Jobs or Manufacturing Suggestions during it. Nor will Generate Suggestions create Purchase Suggestions during this time. Then on the date after the end of the Planning Time Fence, an unfirm job or suggestions will be created to meet the pas
If this field is left blank, the value assigned to the part class associated with this part is used.
Calculates using Regular Straight Calendar Days, 24x7. Does not calculate using any related production Calendar. Also see related Change Requests 39742mps and 38799mps that discuss this topic in depth.
Planning Time Fence
The Planning Time Fence modifier allows you to prevent changes to job suggestions, purchase suggestions, and unfirm jobs. This is a date value. If a Due Date on an MRP generated record occurs on a date between the Scheduled Start Date (defined on the Process MRP program) plus this value, the MRP engine will not change the Quantity and Date values on these records. New suggestions will not be made against these records.
Adjustments
Here are the adjustments you can do with this modifier:
Planning Time Fence (Part Maintenance) - You can define this value on each part-plant detail within a part record. This lets you define different Planning Time Fence values for each plant producing a specific part.
If this field is left blank on a part-plant detail, the MRP engine uses the value entered on the Part Class linked to the part record.
Planning Time Fence (Part Class Maintenance) - You can define this value on Part Class records. This lets you use a uniform value for all parts linked to the part class. As long as a Planning Time Fence value is not defined on the part-plant detail, the MRP engine uses the part class value instead.
4 Likes