In case anyone else runs across this: It appears that on converting to the new payroll, if JobOps had a record in JT_Employee that it can't find a match for in PR_Employee, it attempts to match on the name fields (and maybe others) and puts the new ID on it.
30-0000077 Bob Jones - no PR_Employee record
30-0000486 Bob Jones - PR_Employee.ID F32CD... this ID is on both records in JT_Employee
------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
Asheville NC
678.273.4010 ext 5
------------------------------
Original Message:
Sent: 08-09-2019 12:13
From: Lee Graham
Subject: JobOps Employee List
Do you see a JT_Employee file?
------------------------------
Lee Graham
Friendly Systems, Inc.
------------------------------
Original Message:
Sent: 08-09-2019 12:01
From: Phil McIntosh
Subject: JobOps Employee List
Did that - not there.
------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
Asheville NC
678.273.4010 ext 5
Original Message:
Sent: 08-09-2019 10:06
From: Lee Graham
Subject: JobOps Employee List
If looking at PR_Employee via DFDM remember that the primary key is Employee Key (not employee #). Switch to kEMPLOYEE and you may find the records.
------------------------------
Lee Graham
Friendly Systems, Inc.