Labor Rate From Resource Group Instead of Employee

Today we noticed some of our employees don’t have labor rates assigned. We don’t do payroll with Epicor, so its just for costing. We expect the labor rate to come from the resource group that the employee is clocked into. Is there a way to force Epicor to use only the resource group labor rate instead of the employee labor rate?

I see a setting in Site Config > Production: Apply Burden From All Operation Resources. This is true in our setup. Is there a similar field that applies labor rate from operation resources instead of using the employee?
Thank you!

The labor rates on the resources and resource groups are just used for job estimated costs and for standard cost roll-ups. When an employee clocks into a job operation, the labor detail will use the employee’s labor rate.

I have not seen any settings to change this, but you could create a method directive on Labor.Update or a data directive on LaborDtl to overwrite the LaborRate field.

3 Likes

I don’t think there is anything OOTB. We don’t use Epicor for payroll but we still have everyones hourly rate in the system for costing purposes.

3 Likes

Same here. When we noticed some new employees didnt have labor rates, we thought it would be safer if job closing was looking at the resource group rate. That way we get a real value even if someone forgot to enter the hourly rate for the employee.

It sounds like we need to enforce labor rates for new employees. That should solve this moving forward.
Thanks!

1 Like

I did a quick method directive on EmpBasic.Update. If ds_EmpBasic has LaborRate=0 and either rowmod “A” or “U”, then pop a warning to the user. This works for now.
Thanks!