We are in the testing phase of our implementation (not live yet) and we have a lot of parts that were entered incorrectly, as in bad UOM’s etc. We would like to delete these parts but they are used on other methods and jobs, transactions etc. Is there any way to go about this by manual deletion of these transactions to be able to eventually delete or recreate the parts without reloading the entire database? For example, is there a step by step procedure to delete material transactions, then job lines (and any other things), then methods so that the part can be modified? I realize this isn’t an easy question but we are now stuck doing our testing with a lot of bad parts because we (understandably) didn’t know how to enter them correctly initially when we started.
Once you have transactions (that hit the GL) in the system, you are stuck. If they are only in methods and jobs, but haven’t been transacted on, then you could find them and replace them. You would create a BAQ to find them.
If it’s just testing and you want the noise out of the way, close the open jobs, quotes, orders for those parts and manually delete the parts from the database. The effectiveness of that will all depend on how deeply used the parts are. If they are on engineering for other parts those will break, if they are on POs those will break, any of the closed jobs and orders will break if you try to load them. It’s certainly not ideal, but it’s that or just restore a new instance of your database and start fresh. You decide which sounds worse
As always, safe harbor, never do that in production or you’ll have a bad time.
