I am cleaning up some records in our part table. These are purchased parts. Mostly things like lubricants, thread lockers, epoxies, and coatings. I found one part that is listed under two part numbers, both with transaction history. I can’t keep both active, so I want to inactivate one of them. Before I inactivate this part number, what else do I need to look out for? Whose day am I going to ruin by inactivating this part?
Big one I can think of is it on a BOM.
2 Likes
Without whipping up a BAQ, is there a quick way to check this?
EDIT: ran the Where Used on the part number and it works great! Confirmed the part is not in a BOM. Anything else?
2 Likes
e: The only thing I know it checks for sure is if you have quantity in inventory.
2 Likes
I ran a couple of BAQs to check for any open POs that reference the part, and any open jobs that reference the part as a material. So far so good!
Thanks!
Epicor will not allow you to inactive and part with open PO, Job, or order, should throw an error.
I would think if you looked at time phase and where used you should be ok.
4 Likes
Another nice feature in Kinetic is Run Out and Alternate Part.
If you mark a part as run out, it will warn people trying to buy or make it. If you add the new part as an alternate, it will even prompt the user “Hey, use this instead”.
Try it out in test. It’s a cool feature.
5 Likes
Just query against PartMtl in a BAQ
Epicor does a pretty good job at not allowing you to inactive part if it’s currently in a Job, on an SO, or in Inventory.
Unfortunately, we have had to deactivate more than a few parts as we made a number of adjustments to the part numbers before our go-live.
If you use a DMT, the DMT will spit out specific errors when you try to inactive a part if it’s on a Job, or SO, etc. The nice thing is that it will make an excel of the errors that we then use for turning the ones that could not be made inactive into RUN OUT parts until we can inactive them.
For the ones that we can’t inactivate if it’s an SO that hasn’t been made into a job, we change out the Part # with the correct/new one in the SO. If it’s in production already, we simply change it to a RUN OUT part and change the description of the part to start with RO-PART. Then, every month we check to see if we can inactive the RO-PARTs.
When something is marked as a RUN OUT part, you will get warnings if you try to sell it or create a job with it - which is very useful in not making any more of them…
It’s a process, but we make it work. We do this very infrequently now but in the beg. it was more often than I’d like to admit. 
BOL
3 Likes
Do you know how run out w/ alternate parts set up works in conjunction with MRP? We use it but don’t fully understand what MRP is doing when creating unfirm Job suggestions with the run out parts as a material. Some Jobs have the part that is being run out, others have the alternate part. I am assuming it is first come, first serve based on available inventory at the time the unfirm suggestion is created?
The last time I checked, I don’t think MRP looks at the Run Out flag at all. If there’s demand for the part, MRP will suggest supply if required. I think the idea is for the Run Out to reduce demand slowly until supply is gone, but it’s a manual process for the move to the new part. Others may know better.
EDIT: OK, maybe I should know better. The MRP Technical Reference says:
2 Likes
From the 2024.2 MRP Technical Reference:
Logic/Algorithms
The Run Out functionality uses this logic to calculate its results.
- If a co-part is a Run Out part, generate suggestions against the run out part. The substitute part is ignored.
- If a material part is a Run Out part, then use the substitute part for the suggestions. The run out part is ignored.
3 Likes
Thanks @tgwinn!