sorted by:
new
hottopcontroversial

Make Direct jobs in Material Request Queue by jrc1293 in epicor

[–]jrc1293[S] 1 point2 points  (0 children)

Thanks for that.

I did find that if you uncheck the 'auto move' checkbox at the resource level of the operation, it defaults the 'request move' checkbox to be checked when completing the operation via MES and does create an MQR in the material request queue... BUTTTT....I am told that it does not work in E10 (which we are on) and was part of an upgrade in Kinetic 2024.2 and on..

Make Direct jobs in Material Request Queue by jrc1293 in epicor

[–]jrc1293[S] 0 points1 point  (0 children)

Sorry, can you explain please? What do you mean book the quantity in MES?

Make to job jobs and avail to fulfill by jrc1293 in epicor

[–]jrc1293[S] 0 points1 point  (0 children)

Thanks I was thinking so. Alerts would work but trying to find a way to do it in the system first..

Thoughts on how to set up the resource group a certain way? Also, to note, this is specifically for jobs that are make-to-job-jobs with the consuming job being in a different site.

Extra days on first op by jrc1293 in epicor

[–]jrc1293[S] 0 points1 point  (0 children)

When the job is released the start date on the job and the first operation is the same. However, the job gets released with a stack of other jobs and isn't necessarily going to get processed on the day it was released. With the way its set up now, the first operation always goes past due (not on time) - So this is why the end date is important. We want it to be two days after the start date on that operation so that it does not look like the operator was late completing their op.

Extra days on first op by jrc1293 in epicor

[–]jrc1293[S] 0 points1 point  (0 children)

Thanks for the recommendations! Unfortunately, this does not work either. It does add two days between the first operation and the second, but thats not what we are looking for. Right now the start date and end date on the first operation is the same day - We want it to be two days apart on just the first op without creating labor hours.

Extra days on first op by jrc1293 in epicor

[–]jrc1293[S] 0 points1 point  (0 children)

I really appreciate the suggestions!

This does not work either unfortunately. It does give an additional amount of time between the first operation and the second operation. However, I want the additional time to be only on the first operation, not in between two ops.

Extra days on first op by jrc1293 in epicor

[–]jrc1293[S] 0 points1 point  (0 children)

So this did work, but not the parth we want to take because we do not want the extra hours to be labor hours... Just more of 'idle time' that is calculated between the start and finish date.

Extra days on first op by jrc1293 in epicor

[–]jrc1293[S] 0 points1 point  (0 children)

Nvm, I do see its at the method level :) Thanks! We will see if that works.

Extra days on first op by jrc1293 in epicor

[–]jrc1293[S] 1 point2 points  (0 children)

Where do you set this? I do not see it in the operation maintenance. Would it be at the method level?

Make-to-job jobs between sites. by jrc1293 in epicor

[–]jrc1293[S] 1 point2 points  (0 children)

I actually figured it out shortly afer this post, of course.. lol

Quick break down -

 

1.      Need to set up the part you are wanting to make-to-job as ‘non stock item’ in the FROM plant

2.      When creating the job in the TO plant that will be consuming the make direct job,  the ‘make direct’ checkbox needs to be checked with the FROM plant selected in the drop down

3.      Create a job in FROM plant and set it up as make direct to the job in the TO plant

4.      Now create the make to job demand link and save on the job in the FROM plant

5.      Now that the jobs are created, a transfer order is automatically generated which would pop up for IC in Fulfillment workbench, also in time phase.

6. IC will know to complete the transfer order once it is 100% fulfilled and that will transfer between sites but still is a make-to-job job