Using forecast 1 vs forecast 0 did not solve the issue. Same problem, MS will not create Purchase Req’s (only MS Supply lines) if any min/max/multiple are set non zero, and Purchase req’s only if min/max/multiple are set to zero. Same result on planning method G as with A, cannot get req’s to generate with lot sizes/increments AND be responding to the forecasted demand. I want to schedule with MS (not MRP) as there is highly variable forecast demand and reduced safety stocks.
Thanks Rodrigo! I am going to pick an item and give that a try. The IFS documentation with our Apps 8 seems a little ambiguous on Forecast 0 vs Forecast 1 - aggregate/disaggregate process and what that functionality really does. If anyone wants to chime in on that, I would appreciate it. From what I can see - consumed forecasts, or unconsumed forecasts that roll forward, move from level 0 to level 1? Unless they’re fixed? Even this is not consistent - I have consecutive proposed consumed forecasts, one in Forecast 0 and the next in Forecast 1, for the same item. I believe our forecasts start as Forecast 0 data only? To my knowledge this forecast data is calculated externally and uploaded as it is into IFS by our demand planners, not using the IFS functionality for calculations and all that. Something for me to investigate - I would not be surprised if our forecast upload is another non-standard practice being performed here. Mergers and acquisitions, along with turnover, have y
Thanks Richard!Had a longwinded response with screenshots - that I have lost twice by hitting back button by accident.I have used the “entire horizon” approach - it does generate purchase req’s ONLY IF all of min/max/multiples are set to 0, and “MS Supply” lines ONLY if any of min/max/multiple are set to any nonzero quantity in any combination. The MS Supply lines will have exactly the same timing as the purchase reqs, just will have the quantities adjusted according to the min/max/multiples. I am going over my data selection to see where it differs from yours, and I see the following differences in ours:Non-zero Safety StocksNon-zero Lead timesForecast 0 rather than Forecast 1 Also, our version has some of the boxes in different places, and some tabs are different on the MS 1 (don’t have a “Reciepts” tab but do have a “Rate by Period” and “Supply and Demand” tab on our MS Level 1 Part.)It is IFS Applications 8, and an upgrade to 9 is coming soon. I am going to try changing the SS
Thank you very much, Ravinatha! This is a start. Methods B, C, D and G would all be useful and applicable to items in our portfolio. I am, however, still looking for some instructions on the following topics:Time fences and their interaction/use in MS and MRP. Also, the thresholds for MS and MRP operation (when and where one or the other is active)Lot sizes (min/max/multiple), and lead times. And my very specific question: There are many items that have a forecasted demand that is highly seasonal/variable, so we are using planning method A to plan to that demand (installed as an MS forecast). However, if any of the lot sizes are set in the planning data (min/max or multiple anything other than 0) - purchase requisitions will no longer be generated, only MS supply lines. The MS supply lines have exactly the same timing, just quantities adjusted for the lot sizes. The desired goal is to have purchase requisitions identical to (in place of) these MS Supply lines - but no combinat
Related question: is there a way to drive req’s into the future (i.e. with lead time or the like). More specifically purchase req’s for finished goods. IF demand creates a need, MRP is dropping it where needed (with a latest order date potentially in the past). As specified above, obviously that can’t happen - I would think earliest availability date would be current date / MRP run date + total lead time (by whatever collection of lead time components). Is there a way to make the “latest order date” no less than current date or MRP run date, i.e. place the req lead time into the future to represent the reality of it. This, of course, means you may be short supply for some period of time - but would prefer that reqs generated/automated by MRP abide by lead time, and short lead time orders only be handled manually.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
