LaborDtl DMT issue

Epicor ERP 10
,
1

I am trying to build a DMT template for TE Labor Combined DMT. I am extracting the data out of our live system for use in a test environment. I thought I had it right but when I try to load the data (just 4 records for now) it gives me Invalid Job Operation Sequence errors on each line.
The fields/columns I have in my DMT are a combination of the data I know I need plus fields suggested by articles from this site. Here are the fields I have:
Company
EmployeeNum
LaborHedSeq
PayrollDate
Shift
ClockInDate
ClockInTime
ClockOutTime
PayHours
TranSet
LaborDtl#Company
LaborDtl#EmployeeNum
LaborDtl#LaborDtlSeq
LaborDtl#LaborTypePseudo
LaborDtl#AssemblySeq
LaborDtl#PhaseOprSeq
LaborDtl#OprSeq
LaborDtl#ResourceGrpID
LaborDtl#OpCode
LaborDtl#LaborHrs
LaborDtl#BurdenHrs
LaborDtl#LaborRate
LaborDtl#BurdenRate
LaborDtl#ResourceID
LaborDtl#PayrollDate
LaborDtl#ProjectID
LaborDtl#PhaseID
LaborDtl#RoleCd
LaborDtl#TimeTypCd
LaborDtl#TimeStatus
LaborDtl#Shift
LaborDtl#EmployeeName_c
LaborDtl#WBSDesc_c
LaborDtl#GALaborHedSeq_c
LaborDtl#CR8Correction_c
LaborDtl#CR8CorrectionLaborDtlSeq_c
LaborDtl#GALaborDtlSeq_c
LaborDtl#CR8CorrectionLaborHedSeq_c
LaborDtl#Reason_c
LaborDtl#GLC_ODC_c
LaborDtl#GLC_Cost_c
LaborDtl#GLC_Loc_c
LaborDtl#ChangedEntry_CR8_c
LaborDtl#ClockInDate
LaborDtl#ClockInTime
LaborDtl#ClockOutTime
LaborDtl#JCDept
LaborDtl#JobNum

I have valid operation sequence numbers in both the PhaseOprSeq and OprSeq columns. I have the job number, project ID, phaseID, OpCode.

image
image997Ă—131 5.53 KB

Does anyone see why I am getting the Invalid Job Operation Sequence error?

2

I think this might be one of the DMT’s where the order of the fields actually matters. I know for certain this order works It also had custom fields in it but I removed them from the end.

Company
EmployeeNum
LaborHedSeq
PayrollDate
LaborDtl#LaborDtlSeq
LaborDtl#Imported
LaborDtl#Company
LaborDtl#EmployeeNum
LaborDtl#LaborTypePseudo
LaborDtl#JobNum
LaborDtl#AssemblySeq
LaborDtl#OprSeq
LaborDtl#OpCode
LaborDtl#LaborQty
LaborDtl#PartNum
LaborDtl#PartDescription
LaborDtl#LaborHrs
LaborDtl#BurdenHrs
Submit
LaborDtl#LaborNote

1 Like
3

Thanks. That got me past the job oper error but now I am getting this one:
This Job is a job type of Project. Entry not allowed for non-project related transactions.

Does this mean I can’t DMT in the LaborDtl data?

4

Do you still have these in there? My import doesn’t use them and I have to admit I have not tried to import project related time before.

LaborDtl#ProjectID
LaborDtl#PhaseID
LaborDtl#PhaseOprSeq

5

Yes they are there. Now that I have moved some columns around I am now getting “This Job is a job type of Project. Entry not allowed for non-project related transactions.”. Of course nothing indicates what is wrong.

6

I don’t recall what makes the project entries different. You may just need to manually record one and compare to your import sheet. There must be some fields missing still.

A super quick glance at some sample data and I see things like RoleCd and TaskSetID set on some of the LaborDtl records. Also seems like TmeTypCd changes sometimes. WFGroupID, WFComplete, ApprovalRequired and PBRateFrom all appear to be in play as well.

1 Like