Hi,
What does Epicor consider “Actual Prod Hours”, in Job Tracker I can see an operation has 18.71 for actual hours, but when I check the transactions the labor hour transactions equal 20 hours and the burden equals 18.71. seems weird that actual hours is the burden hours.
Could there be break times on your calendar? We found lunch and breaks on prod calendar don’t get costed to jobs.
There are but its not enough to reduce it to 18.71
Were they clocked into more than one job at the same time?
Any of your operations set to backflush time? When you backflush time it uses the estimate as the actual.
They deffiently could be clocked into more than 1 job at a time, but my issue is that the “actual hours” field is pulling burden hours not what from labor hours which is what I would expect.
I also have other examples now of burden hours being greater than labor hours, im not even sure how thats possible.
Under the default settings, if an employee is clocked into more than one job at the same time, the labor will be split between jobs and the burden will not.
That leaves you with more burden hours than labor hours when you look at an individual job.
As to modifiers on labor and burden costs, at Split Burden, Labor = Burden and Use Estimates all change how transactions work when their are either multiple jobs per employee or multiple employees per job.
Ok, but what about the actual hours pulling from burden hours?
I can’t think of a scenario where that happens. It absolutely can go the other way. Burden can be equal to labor hours.
Can you show us what you’re dealing with?
Epicor Support answered it for me, It looks liek Actual Hours field does pull from Burden as intended. seems weird to me.
JobOper.ActProdHours
Total Actual Production Hours. A summary of non-setup LaborDtl.BurdenHrs. This includes REWORK hours. This is maintained via write/delete triggers on the LaborDtl file. Along with JobOper.ActReworkHours it is used to reduce the shop load if the system is configured to remove load by actual hours (JCSyst.RemoveLoad = “H”).
I feel like actual hours = Burden makes sense, the actual hours is on the operation of the job. You could have 5 people working an operation for 8 hours the actual hours of that operation isn’t 40, it’s 8.
Working as designed…
Take a look at Part Advisor to see historical labor hours and burden hours.
Details are shown really well with the jobStatus dashboard
I built a dashboard that will show labor summarized by all job and added standard deviation to see which processes are in control.
As far as splitting burden or labor=burden - both are correct - you have to review what you really need.