Simple way to enforce an operation must be completed before next op?

Epicor ERP 10
1

We have an important operation that needs to be performed before the next operation should be started. Silly analogy, lets say op 1 is “put oil in the engine” and op 2 is “start the engine”. If you start op 2 without having completed op 1 bad things will happen… To add a bit more complexity say the job is for qty 20, and qty 10 have had op 1 completed, is there a simple way to allow op 2 to be started for 10 but any more will prevent them from starting the op?

In a nutshell we want a way to specify if an operation is required, we want to be able to specify dependencies between operations, and we want Epicor to enforce this somehow. As always we’d prefer to customize Epicor as little as possible…

2

A BPM on the labor module would be my first thought. Actually, 2 BPM’s, one on the method that’s called when you change the select operation, and other on labor.update (just in case).

Both would point to a single function that does the actual work of looking up the previous op and checking for completeness and returning the go/no go.

There’s a site or company-wide setting that will enforce completeness of previous ops before allowing work on succeeding ones, but I’m guessing you don’t really want that. You’re looking to enforce this on just the one op, no?

1 Like