We created a Config that creates a new part number for each configuration, but doesn’t save it to the Part master. Once the SO is complete and a date given to make it and MRP runs, it releases a Job based on the Method rules in the config. The Job is Engineered, but not Firm or Released, just like MRP jobs would be. Its driving demand, but it doesn’t drive anything to fulfill the demand.
If we firm and release the Job then it will drive the fulfillment demand, which is what I told my schedulers they must do till something is figured out.
So, the only difference between this and the other Configs is that we are doing part creation and the part on the Job it is saying to make doesn’t exist, but that must be affecting something within the Job?
I appreciate any ideas,
Jonathan