Best Practices for Make to Job / Demand Link: Automating Issue to Parent Job

Epicor ERP 10
, ,
1

Hello Everyone,

I have a question regarding the proper use of Make to Job / Demand Link in Epicor.

Our scenario and requirement are:

  • A sub-assembly or material is created as Make to Job and demand-linked to a main (parent) job
  • When the last operation of the demand-linked (sub) job is completed
  • The quantity should automatically issue to the parent job
  • We want to avoid manual Issue Material or Issue Assembly

In short, is it possible that once the demand-linked job’s final operation is completed, the quantity is automatically issued to the main job without any manual transaction?

If my understanding of Make to Job / Demand Link is not correct, please guide me on the proper and recommended way to use Make to Job in Epicor.
Any best practices or examples would be very helpful.

Thanks in advance.

2 Likes
2

The system will only backflush on completed operations and it wont kanban down assemblies when you use PullAsAssembly (which is what I think you mean by sub-assembly) to pull a sub assembly into production by just planning the top level part.

If you set the reporting type of the operation to ‘Backflush’ it will backflush other operations material, you need to have the backflush process running in the background to this to kick in, and again this doesn’t go down sub-assemblies.

2 Likes
3

Your understanding is correct.
Check the auto receive checkbox on the final operation on your sub job.

2 Likes
4

I know a couple of companies where the auto receive checkbox on the final operation is not doing the receipt to the parent job. I created an Epic Idea for this, since they are both on current versions of Kinetic. One workaround suggested is to set the material on the parent job for the child job to backflush. We are still in the testing phase.

1 Like
5

So far, the backflush I mentioned seems to be working. If you want to vote / add comments to the Kinetic Idea I created (in gauging interest): https://epicor.ideas.aha.io/ideas/KIN-I-7288
Best of luck!
Jenn

1 Like
6

If there is a resource group tied to the final operation in Operation Maintenance, check that ResourceGroup.AutoMove = true.

1 Like
7

Auto move is already checked.

1 Like
8

Correction - it did not work. The child material went to the parent with the backflush turned on, but then we ended up with a negative quantity on job closing of the parent. Guess it’s back to doing job-to-job receipts or customizing.

1 Like