I have written a working rest call that allows a user to edit the make to stock qty on a job, however it only works for firm jobs. Trying to add a new demand link or edit the qty in the client also throws an error, saying “Update not allowed, Job Not Firm”. At first I assumed that this was a BPM, but I couldn’t find anything in our method/data directives, and the detailed error doesn’t seem to mention one. Does anyone know if there is any way around this, and/or why the restriction exists in the first place? In my head it makes more sense to be the other way around, you shouldn’t be able to mess with a job once you have firmed/released it.
Firming a job and Releasing a job are separate things and mean something different to Epicor.
An unfirm job suggestion is a suggestion made by MRP or CTP (capable to promise) to satisfy demand for a manufactured part. The system uses the saved MOM to build the job. Importantly, this suggestion (and all of your changes) can be deleted the next time you run MRP. The system does not let you make changes to an unfirm job suggestion since those changes won’t last the next time you run MRP in regen mode. Epicor’s workflow would be to firm the job - telling the system you will make those parts - and then update the firmed job with the updates you need to make. The next time MRP runs, it will take into account the updated, firmed job.
A released job is a job you’ve flagged to release to the floor. This means different things to different companies, but - like you said - this usually is some gate where a job should not be updated after releasing or has to go through additional steps to be updated. Note that you can have a job that’s firmed but not yet released.
1 Like
I understand the dangers since anything you change would be wiped away the next time MRP runs, was hoping Epicor would let you edit some fields since it would make our web tool workflow simpler (we could edit and then firm/release instead of saving the edited fields, firm/release, then have to search for the firm jobnum before sending REST calls to edit those fields). Appreciate the insight.
As for the why, the way I explain the Firm/Engineered/Released checkboxes is:
Firm = We know we WANT to make it
Engineered = We know HOW to make it
Released = Go make it
If your users are editing a job, they know they want to make it, and so should firm the job.
6 Likes