Seams like after we upgraded to 2025.1.10 our MRP generated jobs are not pulling in materials and operations for stock items. I have a open ticket with support and they have determined that the jobs are on hold. Which in fact, they are on hold but no one can places them on hold and it seams there is no way to put them on hold. There is a hold field in the table but Epicor says it does not get used at this time. But somehow these jobs are on hold after being generated. Has anyone seen this behavior or know how to take these jobs off of hold?
Could be pertinent… looks like this behavior was seen in the past.
@jgiese.wci mentioned in the above post creating a data directive for new JobHead records to ensure JobHeld = false.
Not sure if reviewing the MRP logs would point to any kind of pattern as to when and why certain jobs end up on hold. But the above thread (I believe) was related to version 2022.2 (ish)… so, perhaps the issue has crept back into the works?
I wonder if the top assembly part is put on Hold if that would cause MRP to create jobs that are on Hold?
There is a bug where jobs are created as “on hold” (status box checked), Epicor PRB0249525.
Support calls it a “visual bug” since there is no logic attached and nothing actually happens because of that box being selected, but it’s a REAL pain to explain.
I did create a BPM to take off the hold when jobs are created but now they are not on hold and still do not have any materials or operation. Updated my ticket with Epicor Support waiting for a response.