We have a requirement to ship every other Friday (every 10 days). Would we set the GR processing time to 10 in the material master? Planned delivery time is 35 days.
Also, GR processing time of 2 would be every Tuesday, 3 Wednesday, etc. Is that correct?
Actually, the material will ship from the VENDOR every 2 Fridays, not ship from our warehouse. I have set GR processing time in the material master at 20 and that seems to hit the every 2nd Friday, but that doesn't make sense, given that this is a 5 day week. Would 5, 10, 15 be Fridays? Planned delivery time is 35 days in this case.
The planned delivery time represents the time that the material takes to be delivered from the vendor. Adding a planned delivery time to your does not ensure that it will be delivered or shipped on fridays.
If you receive this material on fixed days of the week, what you need is to use a periodic lot sizing procedure (such as PK) for your material and a proper planning calendar (you can create it on MD25).
The following document explains how to set up a scenario using a planning calendar:
Yes. Thank you. We started off with planning calendars, however the users found it very difficult because the planning calendar was in periods, not actual dates. Each forecast period was 1, 2, 3, etc. instead of the actual Friday dates. So we had to come up with an alternate way to do it. We are using a weekly forecast and trying to get the right combination for the shipments to hit on Fridays. I did a test part with 20 GR time and 35 planned delivery time and that seemed to work, but I don't understand why 20? Wouldn't it be 10 since GR processing time is based on 5 days per week and day 10 would be every other Friday.
The issue is not exactly clear for me. Which exact date would you like to fall on da friday? The delivery date? The requisition opening date?
Also, you should provide more details about your scenario. Which MRP type and lot sizing procedure are you using? This information is a key to understand the logic behind the MRP calculation. Depending on the MRP type, system may use forward or backward scheduling to calculate the dates and both may have different results.
See the following link where both backward and forward scheduling are described:
You should also consider that the goods receipt processing time is calculated in working days, therefore, the calculation may be affected by holidays on the plant factory calendar.
Thank you. I really appreciate your responses on this. We are using MRP type PD and lot sizing EX. We don't want to use backward scheduling as there is no reorder point. The material will ship from the vendor every other Friday. Forecast is in weekly buckets and forward scheduling is set at 30 days. I do understand that GR processing time is in work days which ties to our factory calendar. We set the forward time at 30 days because we don't want the MRP run to consume the entire forecast. I hope this explains things a little better.
With MRP type PD system runs backward scheduling, where the basic finish date is the requirement date.
I really think that the best option for you is to use a planning calendar and a periodic lot sizing procedure. That's the only way to ensure that the replenishment proposals will be always created on the same day of the week. Otherwise, dates calculation will be affected by non-working days and you may have replenishment proposals on different dates.
Thank you. You are correct. The issue with the planning calendar was the forecasting in MD64. The forecast is listed in periods and the user would have to have another document to see which period corresponds to what calendar date and that wasn't a viable option for them. We had to figure out some work around that would yield similar results, however as you say, it is dependent on the factory calendar. The user will need to monitor MRP and tweak the dates if they do not fall on Fridays. I very much appreciate all of your input. It was very valuable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.