I am working on some automation in which I will be reporting quantities from imports from out of our laser nesting software. Until I just thought about it now, I was figuring that I needed to make labor detail records to record the operations, which would require a job header, which I was going to ask, does the clock in/out time matter for a non-payroll, non-cost user to make the labor entry?
But as I was writing this, I’m wondering if it’s a problem to use the job cost adjustment instead and just do the quantity completions there, and totally skip the labor header/detail portion altogether?
I know Epicor will record the ClockIn/Out Time and Auto Lunch regardless if Payroll or not – the Payroll flag merely is used for their Payroll Module to Export it to a Check. We have Payroll and Non-Payroll and the Times are tracked for both the same and Labor Records as well.
I know its used in the PayHours Calculation, but not necessarily in the other field that shows Hours Worked. (cant remember field name)
The Total Labor field just sums up all the LaborDtl.LaborHrs under that header. I don’t think it’s a database field; it’s just calculated on-the-fly for the display.
The only thing I would say is to make sure each day has a new header so the PayrollDate on the LaborDtl is correct. We have dummy employees we use to enter labor when a specific employee shouldn’t get bonus credit (we pay an incentive bonus by the number of parts an employee makes), and have Service Connect automatically clock them in at 12:01 AM and then clock out at 11:59 PM so there’s a fresh header for each day’s entries.
Same we dont use the Payroll Module but we use the Payroll Flag as an indicator just whom to Export to our 3rd party Payroll via our custom built Windows Service which runs daily nothing else, nothing more.
I know the PayHours Field is calculated on LaborHed by Summing the LaborDtls when you ClockOut. If you are clocked in, it will show 0 hrs as soon as you clockout, it adds them all up and writes to LaborHed. Also you may have multiple LaborHeds.
For every ClockIn you get a new LaborHed, so if an Employee Clocksout for Lunch, ClocksIn, then goes home at 3pm ClocksOut, then comes back at 4pm ClocksIn that Employee could have 3 LaborHed’s for the day or 100 depending how many times you clockin, out
Our company just went through this subject. Reporting the quantities on the final operation gets the material, labor and burden costs to the part when the Job Receipt to Inventory step executes. We had to go through the steps to make a LaborHed and LaborDtl record for each quantity reported. If there is a simpler way, I’d love to hear about it!
I’m pretty sure if you do a job cost adjustment, you don’t need a labor header, it just puts a labor header at 0.
You will have to populate everything, but there are places for it on the screen. I’m hoping that this workable this way, I’m in the process of testing it all out. And I need to double check the costing on this one to make sure it flows correctly. I haven’t done that yet.
One caveat is, labor header 0 doesn’t show up anywhere in the UI, so if you have to change something, you can’t do it with out of the box tools. You either need to “undo” it with negatives, or go the UBAQ route. And I don’t know what kind or ramifications that has.
nothing else, nothing more.
