LaborHedSeq is the sequential key used for the LaborHed table so you’ll have to use ones that haven’t been used yet unless you are trying to overwrite current data. Theoretically you could run a query on the laborhed table to return max(LaborHed.LaborHedSeq) and then start at 1 higher but not sure if that will cause you issues when the system tries to create the next record (not sure if it looks for the last one and adds one or if that last used is in a field somewhere.
When you are uploading the DMT, I think that this DMT assumes that there is an existing LaborHed Entry (it’s trying to look at it). You can find this detail If you go to Time Entry and look at the Time Details of an employee.
Full disclosure, we have not used this particular DMT.
At the grid level you can choose personalize and add [LaborDtl].[LaborHedSeq] to the column so that you can see it.
Maybe what you are trying to do is “Job Labor Adjustment?” — I’m not sure because I don’t have context here. You can/are able to choose assembly, opcodes, employees, etc. from that DMT as well. We use that DMT quite a bit (unfortunately!).
Sorry, I couldn’t be of more help, but maybe there is something in there…
Because our upgrade to 2024.2.7 eliminated the ability to batch our jobs. I’m stuck with 180 jobs x 4 operations to process on a daily basis to keep our paint line moving.
LaborHed is the header of the Labor Record whereas LaborDtl is the line item of the Labor Record.
LaborDtl uses LaborHedSeq & LaborDtlSeq as its two keys so if you were only adding one record per laborhed, for your LaborDtlSeq, I would imagine any number here would do.
That being said, by using DMT to add Labor records that do not exist, you may be skipping some other logic that could be being done by the system. Not saying that DMTing won’t work, just that it might potentially cause issues that I am not aware of as we have never created new labor records using DMT.
Try this, I usually just import indirect time but should be close.
Do the import in this sequence.
Company-ZZZZZZ
EmployeeNum-PWD3
LaborHedSeq-0 (tried ZERO, 1, blank all error) Should be “0”
Add “Shift”
Add LaborHed ClockInDate
PayrollDate-1/28/2025
Add LaborHed ClockInTime
Add LaborHed ClockOutTime
Add LaborHed PayHours
LaborDtl#Company
LaborDtl#Employee
LaborDtl#LaborTypePseudo-P
LaborDtl#LaborDtlSequence Should be “0”
LaborDtl#IndirectCode- Shouldn’t be needed for Production work
LaborDtl#ClockInDate-1/28/2025
LaborDtl#ClockInTime-11.42
LaborDtl#ClockOutTime-12.42
LaborDtl#JobNum-FR77728
LaborDtl#AssemblySeq-0
LaborDtl#OprSeq-20
LaborDtl#ResourceGrpID-1300
LaborDtl#LaborHrs-1
LaborDtl#BurdenHrs-1
LaborDtl#TimeStatus-A
