I don’t think this possible, or a very good idea. Changing part numbers for open jobs would break a lot of links and likely invalidate your financials. I would consider closing those jobs and creating new jobs to replace them.
You may be able to use the DMT to mass update your open jobs. I recently updated thousands of open jobs with the DMT. However, I was only adjusting operations and resource groups, not the part number.
If you have a process in mind, give it a shot in Pilot to see if you get the expected results before committing to the production database.
If you haven’t made any material transactions, then this might be possible. But as soon as you have material transactions on a job you are sort of stuck with that material. Same goes for labor transactions, or any other part transactions. Once records get added to the trans tables you really don’t want to change the internals for the job. In many cases you simply can’t change them once you have transactions.
You can change the part numbers in a job. You just can’t delete the material sequence if there is transactions against it.
The best way to do that is DMT.
@NateS , just an FYI, you can issue whatever parts you want to the job as long as the UOM is the correct class. That means if you have Part A on the job, you can issue Part B. This is for substitution purposes. (for say, different sheet sizes with steel). So while the part number drives the demand, it doesn’t actually affect the financials, because it looks at what was actually issued to the material sequence.
I’m pretty sure the part’s aren’t pulled so there won’t be any transactions against it.
I want to do it via the REST API so I can check things prior to updating anything. Which would mean everytime they need to swap parts, they would need to contact me unless I built an interface of some sort.
But knowing the client, I’m guessing they will want to go the DMT route so someone in house does the updates. I worry things could be messed up easier as not many in the office are up to running DMT.
DMT is generally safe than API. DMT utilizes all the proper methods and business objects required to maintain data integrity. REST API requires you to know all the methods that need to be executed and do them all in the right order. There is a lot less work and worry using DMT.
I have a rough idea. Done one or two in the past but it’s a bit blurry.
I’m probably wrong but there isn’t away to specify a parameter that would be used as the swap out part.
I would have two parameters. One for the part to search for. The other is the part to swap with.
Examples:
ABC.1000 - the original part
ABC.2000 - the new part
In a perfect world, I’d want a form to pop up, ask for the original part and then the new part. Hit search/go whatever and bam, it’s all handled.
With the way I’ve done UBAQs in the past you get the query results, then you can edit the results. And then click update.
You can ask for a parameter, and that would pop up with a box to type in both the to and from. Then you can use that info to do what you need to do. You can show a calculated row and simple show the parameter in that column. Then when you loop through the rows, you have that part number available.
Usually what I do when I have stuff like this, is make a check box (calculated field to false and make that updateable) then you check the box if you want to make a change, then when you loop through, you check for that. Then I do a customization on the dashboard so that you can have a button that will check the selected rows to make it easier to select.
What I said won’t work with the basic UBAQ where you let Epicor pick the BO and stuff. You have make a custom BPM to do that. It depends on how automated you want to make it. The way you have it there will work fine, you just have to copy paste the part number over and over again.