> We would like to inactivate about 18,000 parts.You can try to query the PartMtl.MtlPartNum to locate the methods containing your parts.
And query JobMtl.PartNum to find jobs with open requirements for those parts.
Mass updating with DMT is probably a good option.
I've performed mass updates to the PartMtl table with other tools. It is one table I consider "reasonably" safe to update.
Jobs on the other hand, I'd usually handle manually.
>MRP would place jobs that had "inactive"...Yes, this has been a pain for me too. I finally made a few simple customizations to help users recognize inactive parts while they are working on methods.
>... but this is not the case.
- Added the Part.Inactive field to the Engineering workbench and and Job Entry details
- Added a custom indented BOM that includes the Part.Inactive display
"Mass Part Replace/Delete" works nicely if you were only going to inactivate a few parts.
--- In vantage@yahoogroups.com, "mobilevox" <juy@...> wrote:
>
> We would like to inactivate about 18,000 parts. Our problem is we don't have visibility when we do that on parts that are part of a BOM. We have an issue where they are not planned by MRP. We reviewed the job material before releasing and saw that the parts were not planned in time phase by MRP. Further investigation showed that if we manually released the jobs, we would have to "activate" the part before MRP had visibility of it.
>
> We previously thought that MRP would place jobs that had "inactive" parts on the planning workbench as a problem to resolve, but this is not the case. Therefore, we have no visibility or control to identify the problem until it is too late (i.e. the job release date). We get allocations but we don't get suggestions to fulfill the allocations.
>
> Does anyone have this issue and if so, how did you manage to get this to work in your favor. Any suggestions?
>