A client gets this error when running MRP To create a job from a configurator item. In examining the job/mom we haven’t been able to see any issues with the MOM. Epicor suggested that the operation the configurator is setting doesn’t exist, but errors like that would show when they save the configurator in my experience as I do a get Details as part of the save. And the operation does exist. Configurator does all the normal steps to replace an operation. The Operation is a subcontract operation, the client makes a ton of parts using this configurator and it has been around a long time. The qty/parent has a value. They hand create a job to match and it goes through fine. I haven’t done a 100% field by field comparison yet, hoping for a quick answer from the brain trust here.
Any suggestions on what might be wrong with the MOM?
If the JobOper.RunQty field is > 0 on all operations of the configured jobs, my guess would be that Bill of Operations on the un-configured Part Rev is set to 0. I’ve had issues before where something will throw an error based on the un-configured values in the Revision, even though the values are the actual configured jobs are valid.
The value is zero but so far I haven’t been able to get the value to change to 1. The help on the field indicates it is a calculated field that updates when the operation record is modified. It is calculated as (assembly required qty * Qty Per) + Scrap. I’ve checked out the part and made changes to the operation record but no change in the run qty.