Just need a menu or menu/action.
Thanks
Just need a menu or menu/action.
Thanks
Time and Expense is the best way, oddly enough.
I made a uBAQ to hit the jobOper table directly a couple months ago and it took FOREVER. It is also supposedly unsupported per the data dictionary, I think.
T & E is actually much faster, which makes no sense, I know.
Thanks Jason. I thought I did what you listed but the op still shows as complete. We do backflush our material does that make a difference?
Went down the BAQ route as well to try to find the employee entry that caused the entry.
we use job adjustment to unmark operations complete. Load an employee for the operation and the two checkboxes in the bottom right will be checked if it’s already complete. Uncheck them and submit the adjustment it will reverse it. As an adjustment it’s also a recorded action over T&E which is nice
We only started intentionally doing this a month ago; I set up a REST integration to create a LaborDtl each time they want to complete or uncomplete. Kind of wish I had thought of the JobAdj, but it’s all good.
What I meant was an updatable BAQ on JobOper. That was my first attempt for the integration. Turns out that is not a good idea.
I guess the complete/uncomplete is considered along the lines of a transaction, and not just a status field in a table?
It is just a status field if you really wanted you could DB update that bad boy and call it a day. It’s just in the vanilla fashion it’s transaction triggered is all. I just like using JobAdjustment, because we had qty/hrs/completions changing with no record of it happening (other than change log but that’s… meh). I disabled all of those fields in T&E to force forward transactions to correct mistakes.
I created an updateable BAQ for the JobOper table, because we’ve had the issue where Received parts against subcontract operations would automatically mark the operation as complete when they meet the “planned” quantity of the job, and our production team decided to use up the rest of the material that was slightly in excess of what was needed - but we can’t generate the purchase order for the overrun parts because Epicor believed the operation to be completed. We also don’t feel like having the receiving clerk investigate every single subcontract receipt to see if there are more parts to be sent out.
The updateable BAQ was just a simple, straight-forward development with only the OpComplete checkbox being updateable.