Is there an easy way to be putting Job’s on hold? Or does it become somewhat involved?
We have a problem where PO’s sometimes get placed, so material can get ordered, but then the customer decides to change the Revision of a Part while the material is out.
Sometimes that doesn’t get communicated to others and they start programming/engineering to an order that is on hold pending a new revision to be release.
I already brought up unchecking the released button, but that was shot down because the material gets lost in translation somehow I’m told. I really don’t understand this software all that well yet so please bear with me. Thanks.
Unreleasing prevents ALL (inventory, labor, quality, job adjustment) transactions from further occurring but certainly doesn’t prevent editing of job details.
Not sure what your people mean by unreleased jobs that were in process having ‘material lost’.
That doesn’t sound like an Epicor issue but more a weak process/shop floor control/people issue. (ERP can’t fix that for you… That’s a management & process issue).
There are times we Unrelease to freeze system activity on the job entirely and other times we just want a temp hold. To that end, we created a Scheduling Priority Code called “HOLD” and the job remains visible on dispatches, etc., - but carries that clear signal code. (Again though: Only as good as your people process compliance.)
If you want to even stop further planning/procurement actions related to the job from occurring, UnEngineer and UnSchedule it. (MRP will not try to plan it or any of its materials in this state.)
Rob Brown
Yeah, there are definitely some short comings in how some things are implemented here, I was merely trying to come up with a way that would be easy enough that certain people will actually use it.
That Scheduling Priority Code seems like a good option for me. Thanks.