Has anyone noticed MRP or manually-created jobs not pulling in the engineering details from the quote for CPQ items?
Since the upgrade, MRP is creating jobs, but not pulling in the engineering details. Using Create Jobs in Sales Order Entry is doing the same thing. I’ve checked everywhere I can think of - MRP is set to get details from the quote, the base part has Process MRP selected.
We are also on 2026.100.7. I have not noticed this behavior either from MRP or the Order Job Wizard. We are, however, having weird job behavior after MRP runs a full Regen. Sometimes MRP just doesn’t create a job for the demand (from a CPQ order) at all, and the Planning Workbench lists this in the description for the suggestion “Create Job or Link to an existing Job - The database operation was expected to affect 1 row(s), but actually affected 0 row(s); data may have been modified or deleted since entities were loaded. See Handling Concurrency Conflicts - EF Core | Microsoft Learn for information on understanding and handling optimist.”
We’ve reviewed the MRP logs and it’s saying similar errors there. Currently working with support on this and it sounds like development is stepping in to look. Running MRP on Net Change resolves the errors but the next Regen makes some (not all) come back, sometimes with new ones.
Not sure if our issues are related at all, but figured I’d mention it. I’d be happy to share our case number with you, or the PRB once I have one.
We rely on MRP to create jobs - we don’t use the Order Job Wizard. I confirmed that Get Details was checked off on the scheduled MRP process.
The issue ended up being that our original configurator designer had a rule in the Snap code that builds our BOMs setting the Part.AnalysisCode to a keyword he intended to trigger another process from in Epicor. Problem is - and I don’t know if this changed with the 2026 upgrade, or if enforcement did - but Part.AnalysisCode is limited to 8 characters, The keyword he was using was longer than 8 characters, so MRP failed.
