I have done this, and I don’t recommend it. The best bet is to update the part masters so that future jobs will be created correctly. Then let those older jobs naturally close. However, sometimes you just have to get the jobs updated. Before you start with DMT, remember:
- If the job has any labor transactions against the operation, you can’t change it. Use this to help filter out the jobs/operations that can be updated from the ones that can’t. If a job operation can’t be updated you just have to wait until it naturally closes out.
- If you have comments in your operations that you want to keep, don’t forget to export them along with the other data you will need for DMT. Often comments are added to the operations after a job is created. If you just tell DMT to put in a new operation, it will pull in the default comments for that op if there are any, and blank if there aren’t any.
- Break up your changes into multiple files to run through DMT simultaneously. I try to run files less than 1000 records per file. Break up your file as you see fit. Keep processing and reviewing the output files until you have processed all the records and have no remaining errors. If you can push an update file into Pilot twice with no errors, it is safe to move on to Live.
- Always run the DMT in pilot first. Do it twice. Do it three times to make sure your process is sound, and no surprises will pop up. Document how long it takes to process each file to get a good idea of how fast this process will be when you finally do it in Live. You will have to work with Epicor support to refresh your pilot snapshot between your attempts.
See some of my previous attempts here:
DMT - Replacing Job Operations, Missing Scheduling Resources - Kinetic 202X - Epicor User Help Forum (epiusers.help)
Good luck!