I would like to know if anyone in the forum has made any customizations to the ‘Start Production Activity’ that allow a job to be registered while keeping the window open and ready to add new jobs until the user decides to close it. This is necessary because, due to process requirements, the operator needs to register between 10 and 25 jobs at the start of their activity
Jose
It’s right. We have a cut list that covers all the jobs of an SO, if it has 15 or 25 lines, these are the jobs that the worker has to register.
Currently the operator loads a single job and the time of the other jobs is charged to this job. So now we want to record each of the jobs so that the times and costs are reflected in each one.
But the Start Production Activity window is very limited and the loading process takes a long time.
I would like to see if at some point they have made it more agile or what options I have to make this more dynamic. Furthermore, it is complicated since the operator does not know how to use the DTM.
My cut list brings the job and we are going to add the job barcode, We know that it is always the same assembly and operation
Ex.
Barcode 307254-1-1 0 10 CUT
Barcode 307254-2-1 0 10 CUT
Barcode 307254-3-1 0 10 CUT
…
Barcode 307254-20-1 0 10 CUT
I have thought about but did not yet pursue something like this for one of our companies. We had a polishing plate for fiber connectors that held 24 connectors. You never wanted it running not full, so if you had small jobs they would all be running in that same time span.
There is code here about start and end activity. I would build a dashboard that used the current operator and did starts and stops by group.
Could he use the MES Work Queue? You can check all the boxes and then start activity. That moves everything into a tab where they can check all the boxes and end work. A personalization on that screen can put the labor quantity after the job number, so the can just type the quantities in the grid.
Another option would be to batch the jobs since the operations look the same. You need a module to do that. Look at the resource scheduling board and see if the batch operations is available. Then they clock into 1 parent job and type in the quantities for each child job.
Thanks JennL, we are currently working on this option but it does not comply
all the requirements we need.
Now I’m creating a new form for StartProduction Activity.
Can someone help me with the code?
I don’t think anyone is going to do it for you, if you have specific questions shoot, but you need to do it yourself and we’ll help you if you get stuck.
Mario you really need to give us more information. Using UD37 … that’s a table… what are you using it for?
What is “not recognizing the Ice.Core”
To help the community provide the best answer, could you include as much of the information below as you can? Your question appears to be lacking some much needed context
Epicor Version
Deployment Type (Cloud, On Prem, 3rd Party Cloud etc)
The business problem you’re trying to solve
What you’ve already tried
Is this a Kinetic UX (Web) or Epicor Classic issue?
Is it related to a Method Directive, Data Directive, Function, BAQ, UBAQ, Configurator, etc.?
Any screenshots, error messages, or logs.
Any code you’ve written (or borrowed , make sure it is property formatted)
```
code here
```
this sounds like a primary example for the use of JOB BATCHING… you can select all the jobs that need to be cut at the same time, and batch that operation together. The system will create ONE JOB that batches all multiple jobs into one (only the operation you specify). once you complete the work on teh batch job, the work automatically gets separated out to the other jobs again. You can batch jobs in the Resource Scheduling board.
“help” should have some information. It is not super complicated. you simply go into the resource scheduling board and pull up the resource that has the common jobs, then there is a batch tab (in smart client it will look slightly different, but the functionality is the same). you select the jobs to be batched, and then press the batch operations button… then a page comes up to ask you some options. Since you are wanting to batch the FIRST operation (or one of the first), you would choose BACKWARD.
I would recommend you do some experiments in a pilot database to see how it works, and try various options before doing this in production.
I have created the Batch: 308051-1-1 with these jobs
308051-1-1 CNC-CUT
308266-1-1 CNC-CUT
Now I have reported the batch of job (308051-1-1).
Question
I don’t see that it adds the times to each of the jobs that make up the batch. What I see is that the batch keeps them
What tracking should I give to the costs?