We are in the middle of implementing MRP and had a curveball thrown at us. Should users be able to create unfirm jobs using Quick Job Entry? So far it seems random, we have tested it on multiple users and parts and cannot find a pattern as to what is causing the job to be unfirm upon creation.
1 Like
No, only MRP can create Unfirm jobs.
Great 
…Epicare here we come!
Do the jobs that are not firm have the unfirm prefix that’s set in company config?
If you create a job in quick job entry and manually type in a job number with the unfirm prefix it will come over unfirm.
I would consider it a bug because if you do it in regular job entry then the job is created as firm.
No, they are using the automated “Next Job” function.
When I asked, I was told that they would not change the system.
Are you sure you don’t have a customization that does that? I just tried it and the job was still created as Firm.
We just have to add an extra step in creating our jobs until we fully implement MRP. Because the jobs were unfirm, MRP was deleting the jobs and replacing it with another unfirm job. User must now ensure the firm field is checked before creating more jobs or moving on to other work tasks.
1 Like
son of a b…you’re right. it doesn’t happen in my demo environment. not what I was expecting, now I have to chase this down!
2 Likes
Turns out it’s not a customization on my end.
In my demo environment (epicor learning one), in both 2024.2.15 and 2024.1.13 if I use the Kinetic quick job entry and manually type a job number in, doesn’t matter what the job starts with, it will come over unfirm.
But! If I manually type a job number in and then click the next job button, the job number doesn’t change but it does come over firm.
This is the same in the browser and client.
If I manually type the job number in classic quick job entry it will always come over firm.
Moral of the story, classic is king
2 Likes