We recently ran a DMT to change the buyer on the Part Site level for most of the parts in our part master. We do not use Part Class to define buyer, and I am not aware of any other conflict.
When MRP ran last night, we expected it to take old jobs and old demand before today’s date and switch the buyer based on the Part Site record change. This does not appear to be the case.
We are on 10.1.600.26. Any help is appreciated. Thanks.
You may need to update those “old” files yourself.
After changing a field on a master file, new records will use the new value but the system won’t always automatically update existing files to use that value. I assume that is what is happening to your “old jobs” and “old demand”.
If the “old” records are only “suggestions”, then you might be able to run a “full regen” of MRP…
This would delete existing suggestions first and as it recreates them, use the new buyer.