Still a little green with Epicor here. Not too familiar with MRP processes and functions. Just a basic knowledge of what it is and what it’s used for. We’re currently seeing an issue where when running MRP, it seems that it’s not pulling the Material Constraints value from parts that are manufactured. Therefore, MRP isn’t scheduling jobs properly with these manufactured parts. It seems to work fine with Purchased parts when this checkbox is applied. We’re also going to be upgrading to Epicor Kinetic sometime early this next year and are wondering if this might happen in Kinetic as well. I have a colleague that suggested we go to Kinetic version 2023 or 2024 as they have supposedly optimized MRP? If anyone needs any other info, I’ll do my best to provide and accomodate in the comments when that info becomes available. Thanks for any help regarding this.
Hi Mark,
Can you provide screenshots of parts you believe are not being correctly scheduled? I would also ensure that MRP is set not to ignore constrained Materials. That is done on the Process MRP scheduled process.
Hi Robert,
Thanks for commenting. MRP is not set to ignore constrainted material. We’re currently looking for some good examples for a material on a job that won’t be available until after the release date on the job. Here’s a screenshot of a job that we have at the moment. Let me know of anything else I can try and provide to help.
Hi
You will have to provide a bit more detail than this for an answer I am afraid as there are so many factors that affect how MRP plans jobs, especially with sub-assmblies involved, and more so when these are manufactured. Some initial questions to get you started:
- What options are selected on the sub-assembly parts in the higher level MOM (plan/pull/view) as this dictates how jobs are created (one job with multiple assemblies, or multiple jobs feeding into a top level job)
- Are the sub-assemblies stocked or non-stocked parts and if stocked are there min/max levels defined
As for upgrading, there are improvements etc. in MRP but it still relies on the underlying data being correct