Wondering if anybody has run into this and what your process is.
Top level job has a custom make direct material on it, so MRP makes a sub job for that material. The sub job gets completed and that material is issued to the top level job.
If the material is non-conformanced, it is immediately unissued from the job. At this point it’s pending inspection.
MRP sees that there is demand for that material on the top level job, so it creates another sub job to satisfy the demand.
The original part that’s been nonconformanced passes inspection and is automatically re-issued to the job. So now demand is satisfied, but we have an extra job for a custom material that is already in process and will eventually be scrapped. Wasted time and material.
Are there settings that I haven’t found that would stop MRP from creating a new job if the material is pending inspection? I only want a new job created if it fails inspection. This makes the most sense to me.
The only thing I came up with is a BPM on job status maintenance that would look at the Job/Asm/Material and flag if there is a pending inspection for it and have a visual indicator so it doesn’t get firmed.
I dislike #2 and would really love it if this was handled natively somehow and I’m missing it. But beggars can’t be choosers I guess.
Once any sort of material/inventory goes into inspection (except PO receipts - those are handled separately), MRP no longer sees that quantity as valid supply. There isn’t any sort of setting we’ve found that changes this behavior.
We’ve added a “Qty in Inspection” field to our scheduling reports that shows the scheduler how much of a part is pending inspection so they have that information while firming new jobs. They also receive daily reports showing what’s currently in inspection. An indicator on Job Entry near the Firmed flag would work also.
We also push for initial inspections to be completed quickly. We don’t want materials to linger before being inspected so they can either be accepted back or put on a DMR. Ideally this is happening later the same day if the NCR was created early enough, or the next day.
Ok, we’re on the same page. I’ll put a field in Job Status Maintenance so it can be caught before the job gets firmed.
I understand the logic, but I wish that there was someway to change MRPs behavior for this situation.
I appreciate the insight.