Prevent Job Completion without materials being issued

Kinetic ERP
1

Is there anyway to prevent Job Completion without materials being issued in full.
BPM ? Site Configuration? is there any reason to want to be able to complete a job without materials being issued.
We are using a combination of materials being issued to jobs and some backflushing of materials for assorted products.

2

Of course.

Maybe other ways.

I’d like to know the answer to this as well as a few other questions before I speak out of
ignorance.

1 Like
3

Depends on the business. I can imagine a case where you have a job for a service technician to perform some work, and you expect to need some replacement part, so it is on the job as a material requirement. The technician performs the work and realizes he didn’t need the new part, just needed to tighten down the old one.

Totally hypothetical, specific to service/maintenance, and maybe in that case you would delete the material requirement… but there’s always a case to be made for exceptions.

1 Like
4

Hello Epic Users.

Did anyone find an answer to this?

5

He never responded so we dropped it.

6

I wrote a complex set of BPMs to handle our job operations. There are all sorts of specific business logic particular to our manufacturing processes.

It basically doesn’t allow for reporting of quantities above what the materials issued could make. It takes into account DMR and inspection as well.

There is nothing in Epicor itself that I have found that would meet our needs, so BPMs are probably the only way.

7

Hi Doug,

We backflush bulk material and lot track components. I’d like to setup similar logic to what you’ve referenced for when a BOM includes Lot Tracked Material. Can you provide any more insight to what you’ve put into play?

8

Our past ERP system had the ability to fix costing after the material was received/shipped (as long as you did it before month end posting). Some of our past habits came back and was causing issues with our variances.

Basically, I have BPMs on several of the processes in labor reporting and time and expense entry. When a quantity is reported the logic:

  1. makes sure there is enough material issued to report that quantity.
  2. if the operation isn’t the first one, make sure the total reported isn’t greater than the previous operation completed total.
  3. the reported quantity total will include any amount sent to DMR, so the DMR process has to be completed to get the correct amount you can report on the next operation.

The logic also controls the amount that can be received to stock/job or shipped based on the final step reported quantity. It will not let you receive more than has been reported.

The logic also prevents the job from completing while there is any inventory in DMR as the process may yield items being accepted back onto the job.

Note: We do pull costs off of jobs for DMRs. That’s why we monitor what’s left in DMR on a job.

3 Likes
9

I agree with @Doug.C, steps he mentioned is the best way to achieve your business problem. We are using the same thing and we stop them when they mark a particular operation as Complete.

Pre-Processing at Labor->Update should get you started.

10

Thank you Doug

11

Would you be willing to shre you BPM’s. I am looking to do the exact same thing but i am not good enough in epicor to do BPM yet…