1
For our manufactured products, there are various interchangeable components eg. different types of potato, difference sizes of red pepper. Which one we use depends on what we have on hand and can vary both through the production run and from day-to-day.
It'd be very helpful if the currently substitution data structure (plan group plus priority) could work at point of pick list posting as well as master planning (we are not currently using mater planning) - since our material use is driven by what is to hand for the Team rather than what is
eg. for a product with "Red pepper" and "Red pepper large" as priority 1 and 2 respectively in a plan group, flushing principle of "Finish":
- If Red Pepper is in on hand in the production input location at point of RAF, should be consumed
- If Red Pepper isn't on hand in the production input location at point of RAF, but Red pepper large is on hand, the latter should be consumed instead
STATUS DETAILS
Needs Votes
Administrator
Thank you for your feedback. This is a great suggestion!
Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.
Sincerely,
Johan Hoffmann
PM, Microsoft