Process for mass rehires?

Does anyone have a good process for doing mass rehires? We have seasonal jobs and will rehire 100-150 in a week.

Would like to let that flow through the onboarding system, but the csv file is not easy to upload for a rehire. Keep getting errors including if data matches what is in the system IE: position code

We are using ClickBoarding for onboarding. Clickboarding creates csv files that we load to Infor for new hires. We have an IPA job that picks up new hire files and creates the new hire record in Infor automatically. Doesn't work for rehires.

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Accepted answers

All comments

unknown

Good Afternoon,

We experienced this issue when we built our New Hire/Rehire Interface with our ATS. 1 would think reactivating rehires would be easy, but turned out to be the hardest portion of the flow.

Our ATS system asks if the applicant previously worked for the organization. If the answer is YES then the flow goes through the rehire process and looks for the employee by their Social Security Number. If no record is found then it routes back to the New Hire flow, because they were never an actual employee.

If the answer is NO then the flow goes through the New Hire process. If Lawson finds a record for the applicant (PA31 and/or HR11) then it throws an error to the HR team for them to review.

Now comes the tricky part. What we did is put in place queries for each part of the employee record (Position, Department, Last Name, etc).

A branch node was inserted before the end node of the query to compare that field to what is on the spreadsheet. For example we have a query that looks at Position. The following logic is employed:

Both Position Records Match (spreadsheet = Lawson) then it is routed to an assign node and the "Position" variable is assigned as blank.

Records do not Match (spreadsheet <> Lawson) it is routed to an assign node where the value on the spreadsheet is assigned to the "Position Variable".

We run about 15 different Lawson queries on Rehires to confirm no 2 fields are alike (we utilize a lot of user fields). i wish there were a better way around this, but have not found one yet.

If you like i can send you over a copy of our New Hire/Rehire automation for you to review. I am also happy to discuss it further offline as well.

Hope this answer helps!

jreese

We use two different 3rd party systems to provide us feeds of employees or contractors that need to be hired or rehired into our system. Based on your scenario I think it matches closest to our contractor process.

The 3rd party vendor is supposed to send us the data for both hires and rehires, with the appropriate reason code, but it isn't always accurate. If the reason code is Rehire they are also supposed to send us their employee number. We first do a check on the Position and Job Codes and if there is no match we send an email to HR and that record is rejected.

We then query the system based on SSN to see if we find a match. If a match is found we then query the associated employee record to see if they are Active or Termed. If Active or information doesn't match new request, we send HR a notification that the requested record is already active so they can notify the vendor. If the record is termed we update the reason code to Rehire and update the Employee field with the current Employee number and the Hire Date field with the Original Start Date.

We then enter a Hire or Rehire record that triggers one of these flows. If the action can't be created with information provided then HR is notified with the error message generated by IPA.

Hope this helps. Please let me know if you have any additional questions.

Copyright © 2025 Infor. All rights reserved.