Dont directly mess with transaction records like PartTran.
Investigate making a BPM that calls a process like whatever is called when you manually issue material to a job.
And you’re missing lots of details. Do you want that transaction to happen at the time the job is created (and that seq 20 exists), and/or when the job is manually updated with a seq 20?
Do this when the job state changes to a particular state (created, released, qty reported, labor applied, job closed, …) ?
Would you please give us the example of what happened in your shop and why a quantity of 1 was entered when it should have been something else?
That’s the root cause you need to fix, I think that’s where Calvin was going. And there’s a way to make adjustments financially I think that are much more appropriate than adjusting that value in that table which serves as a detailed record of what gets posted to your GL… messing with that may compromise your ability to reconcile inventory/wip transactions with the related TranGLC posting.
Why does it need to be one? You’re adjusting the cost of a material right? What is it that you’re doing with this transqty value, are you using it in a report or something?
If you can continue to stick with us I think we will find an answer to what you’re trying to solve.
To help the community provide the best answer, could you include as much of the information below as you can? Your question appears to be lacking some much needed context
Epicor Version
Deployment Type (Cloud, On Prem, 3rd Party Cloud etc)
The business problem you’re trying to solve
What you’ve already tried
Is this a Kinetic UX (Web) or Epicor Classic issue?
Is it related to a Method Directive, Data Directive, Function, BAQ, UBAQ, Configurator, etc.?
Any screenshots, error messages, or logs.
Any code you’ve written (or borrowed , make sure it is property formatted)
```
code here
```
It sounds like you want a solution for a solution to a problem. Can you explain what business problem you’re trying to solve? Why are we adding a new material? Why isn’t it already on the method? Is this a production job? A service job? So many questions.
DO NOT DO THIS! Period.
You should never do something to PartTran directly. PartTran is a historical record of what was done via other processes. Instead, you COULD create a BPM that would execute a transaction (issue material, receive, adjust) which (as a result) would also update PartTran…
But again…
NEVER adjust parttran directly.
To be clear, I was not suggesting a BPM to “tweak” the parttran record during creation.
I didn’t explain it carefully enough. Make a BPM to trigger when the whatever happens that would make you want to alter the parttran. Then call a BO method that does something similar (Issue Material?). In the call to that method, make it do what you want (set the qty, P/N, etc…)