We’re seeing, what I think is strange behavior, on job operation estimated hours in job entry. In the image below, we have an operation to produce 20 items, at 0.75 hours per item. With a crew size of 1, this should produce an estimated hours value of 15, not 0.15. . . Naturally this will cause issues with the job auto completion and auto closing processes.
I’m probably just missing it but I cannot seem to find any useful information on how Epicor handles the different production standard values. Seems to be that hours/piece should be straight forward: (20 items required * 0.75 hours per item ) * crew size.
In this case it appears that the operation estimated hours is being divided by 100 and I’m not sure where this is coming in at.
Ah, so we have to set the Each/100/1000/10000 dropdown for it to work correctly. Maybe I’m just daft but that doesn’t seem very clear from the documentation or field help.
This functionality is a vestige of the prehistoric era when batch sizing was vastly more prevalent and there was no such thing (in ERP at least) of “quantity pricing”. By default this is set to “EA” or “/1”, but it still gets changed now and again by accident.
I think I’ll create a Idea to HIDE these fields so that doesn’t happen accidentally any more.
